You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/app-provisioning/application-provisioning-quarantine-status.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,8 @@ There are three ways to check whether an application is in quarantine:
34
34
35
35
36
36
37
+
- In the Azure portal, navigate to **Azure Active Directory** > **Audit Logs** > filter on **Activity: Quarantine** and review the quarantine history. While the view in the progress bar as described above shows whether provisioning is currently in quarantine, the audit logs allow you to see the quarantine history for an application.
38
+
37
39
- Use the Microsoft Graph request [Get synchronizationJob](https://docs.microsoft.com/graph/api/synchronization-synchronizationjob-get?view=graph-rest-beta&tabs=http) to programmatically get the status of the provisioning job:
@@ -68,4 +70,4 @@ After you've resolved the issue, restart the provisioning job. Certain changes t
68
70
69
71
- Use Microsoft Graph to [restart the provisioning job](https://docs.microsoft.com/graph/api/synchronization-synchronizationjob-restart?view=graph-rest-beta&tabs=http). You'll have full control over what you restart. You can choose to clear escrows (to restart the escrow counter that accrues toward quarantine status), clear quarantine (to remove the application from quarantine), or clear watermarks. Use the following request:
Copy file name to clipboardExpand all lines: articles/active-directory/authentication/concept-authentication-passwordless.md
+68-3Lines changed: 68 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ services: active-directory
6
6
ms.service: active-directory
7
7
ms.subservice: authentication
8
8
ms.topic: conceptual
9
-
ms.date: 01/30/2020
9
+
ms.date: 03/23/2020
10
10
11
11
ms.author: iainfou
12
12
author: iainfoulds
@@ -23,7 +23,7 @@ Multi-factor authentication (MFA) is a great way to secure your organization, bu
23
23
| --- | --- | --- |
24
24
| Passwordless | Windows 10 Device, phone, or security key | Biometric or PIN |
25
25
26
-
Each organization has different needs when it comes to authentication. Microsoft offers the following three passwordless authentication options:
26
+
Each organization has different needs when it comes to authentication. Microsoft offers the following three passwordless authentication options that integrate with Azure Active Directory (Azure AD):
27
27
28
28
- Windows Hello for Business
29
29
- Microsoft Authenticator app
@@ -35,6 +35,20 @@ Each organization has different needs when it comes to authentication. Microsoft
35
35
36
36
Windows Hello for Business is ideal for information workers who have their own designated Windows PC. The biometric and PIN is directly tied to the user's PC, which prevents access from anyone other than the owner. With public key infrastructure (PKI) integration and built-in support for single sign-on (SSO), Windows Hello for Business provides a convenient method for seamlessly accessing corporate resources on-premises and in the cloud.
37
37
38
+
39
+
40
+
The following steps show how the sign-in process works with Azure Active Directory.
41
+
42
+
43
+
44
+
1. A user signs into Windows using biometric or PIN gesture. The gesture unlocks the Windows Hello for Business private key and is sent to the Cloud Authentication security support provider, referred to as the *Cloud AP provider*.
45
+
1. The Cloud AP provider requests a nonce from Azure AD.
46
+
1. Azure AD returns a nonce that's valid for 5 minutes.
47
+
1. The Cloud AP provider signs the nonce using the user's private key and returns the signed nonce to the Azure AD.
48
+
1. Azure AD validates the signed nonce using the user's securely registered public key against the nonce signature. After validating the signature, Azure AD then validates the returned signed nonce. When the nonce is validated, Azure AD creates a primary refresh token (PRT) with session key that is encrypted to the device's transport key and returns it to the Cloud AP provider.
49
+
1. The Cloud AP provider receives the encrypted PRT with session key. Using the device's private transport key, the Cloud AP provider decrypts the session key and protects the session key using the device's Trusted Platform Module (TPM).
50
+
1. The Cloud AP provider returns a successful authentication response to Windows. The user is then able to access Windows as well as cloud and on-premises applications without the need to authenticate again (SSO).
51
+
38
52
The Windows Hello for Business [planning guide](https://docs.microsoft.com/windows/security/identity-protection/hello-for-business/hello-planning-guide) can be used to help you make decisions on the type of Windows Hello for Business deployment and the options you'll need to consider.
39
53
40
54
## Microsoft Authenticator App
@@ -43,7 +57,20 @@ Allow your employee's phone to become a passwordless authentication method. You
43
57
44
58
45
59
46
-
The Authenticator App turns any iOS or Android phone into a strong, passwordless credential. Users can sign in to any platform or browser by getting a notification to their phone, matching a number displayed on the screen to the one on their phone, and then using their biometric (touch or face) or PIN to confirm.
60
+
The Authenticator App turns any iOS or Android phone into a strong, passwordless credential. Users can sign in to any platform or browser by getting a notification to their phone, matching a number displayed on the screen to the one on their phone, and then using their biometric (touch or face) or PIN to confirm. Please refer to [Download and install the Microsoft Authenticator app](https://docs.microsoft.com/azure/active-directory/user-help/user-help-auth-app-download-install) for installation details.
61
+
62
+
Passwordless authentication using the Authenticator App follows the same basic pattern as Windows Hello for Business. It's a little more complicated as the user needs to be identified so that Azure AD can find the Microsoft Authenticator App version being used:
63
+
64
+
65
+
66
+
1. The user enters their username.
67
+
1. Azure AD detects that the user has a strong credential and starts the Strong Credential flow.
68
+
1. A notification is sent to the app via Apple Push Notification Service (APNS) on iOS devices, or via Firebase Cloud Messaging (FCM) on Android devices.
69
+
1. The user receives the push notification and opens the app.
70
+
1. The app calls Azure AD and receives a proof-of-presence challenge and nonce.
71
+
1. The user completes the challenge by entering their biometric or PIN to unlock private key.
72
+
1. The nonce is signed with the private key and sent back to Azure AD.
73
+
1. Azure AD performs public/private key validation and returns a token.
47
74
48
75
## FIDO2 security keys
49
76
@@ -53,6 +80,20 @@ For public preview, employees can use security keys to sign in to their Azure AD
53
80
54
81
55
82
83
+
The following process is used when a user signs in with a FIDO2 security key:
84
+
85
+
86
+
87
+
1. The user plugs the FIDO2 security key into their computer.
88
+
2. Windows detects the FIDO2 security key.
89
+
3. Windows sends an authentication request.
90
+
4. Azure AD sends back a nonce.
91
+
5. The user completes their gesture to unlock the private key stored in the FIDO2 security key's secure enclave.
92
+
6. The FIDO2 security key signs the nonce with the private key.
93
+
7. The primary refresh token (PRT) token request with signed nonce is sent to Azure AD.
94
+
8. Azure AD verifies the signed nonce using the FIDO2 public key.
95
+
9. Azure AD returns PRT to enable access to on-premises resources.
96
+
56
97
While there are many keys that are FIDO2 certified by the FIDO Alliance, Microsoft requires some optional extensions of the FIDO2 Client-to-Authenticator Protocol (CTAP) specification to be implemented by the vendor to ensure maximum security and the best experience.
57
98
58
99
A security key **MUST** implement the following features and extensions from the FIDO2 CTAP protocol to be Microsoft-compatible:
@@ -89,6 +130,30 @@ If you're a vendor and want to get your device on this list of supported devices
89
130
- Microsoft Authenticator App: Works in scenarios where Azure AD authentication is used, including across all browsers, during Windows 10 Out Of Box (OOBE) setup, and with integrated mobile apps on any operating system.
90
131
- Security keys: Work on lock screen for Windows 10 and the web in supported browsers like Microsoft Edge (both legacy and new Edge).
91
132
133
+
## Choose a passwordless method
134
+
135
+
The choice between these three passwordless options depends on your company's security, platform, and app requirements.
136
+
137
+
Here are some factors for you to consider when choosing Microsoft passwordless technology:
138
+
139
+
||**Windows Hello for Business**|**Passwordless sign-in with the Microsoft Authenticator app**|**FIDO2 security keys**|
140
+
|:-|:-|:-|:-|
141
+
|**Pre-requisite**| Windows 10, version 1809 or later<br>Azure Active Directory| Microsoft Authenticator app<br>Phone (iOS and Android devices running Android 6.0 or above.)|Windows 10, version 1809 or later<br>Azure Active Directory|
142
+
|**Mode**|Platform|Software|Hardware|
143
+
|**Systems and devices**|PC with a built-in Trusted Platform Module (TPM)<br>PIN and biometrics recognition |PIN and biometrics recognition on phone|FIDO2 security devices that are Microsoft compatible|
144
+
|**User experience**|Sign in using a PIN or biometric recognition (facial, iris, or fingerprint) with Windows devices.<br>Windows Hello authentication is tied to the device; the user needs both the device and a sign-in component such as a PIN or biometric factor to access corporate resources.|Sign in using a mobile phone with fingerprint scan, facial or iris recognition, or PIN.<br>Users sign in to work or personal account from their PC or mobile phone.|Sign in using FIDO2 security device (biometrics, PIN, and NFC)<br>User can access device based on organization controls and authenticate based on PIN, biometrics using devices such as USB security keys and NFC-enabled smartcards, keys, or wearables.|
145
+
|**Enabled scenarios**| Password-less experience with Windows device.<br>Applicable for dedicated work PC with ability for single sign-on to device and applications.|Password-less anywhere solution using mobile phone.<br>Applicable for accessing work or personal applications on the web from any device.|Password-less experience for workers using biometrics, PIN, and NFC.<br>Applicable for shared PCs and where a mobile phone is not a viable option (such as for help desk personnel, public kiosk, or hospital team)|
146
+
147
+
Use the following table to choose which method will support your requirements and users.
0 commit comments