Skip to content

Commit fa898d6

Browse files
committed
[AzureAD] Additional edits and updates
1 parent 8d1a0b9 commit fa898d6

File tree

4 files changed

+7
-13
lines changed

4 files changed

+7
-13
lines changed

articles/active-directory/authentication/concept-mfa-authprovider.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,13 +17,13 @@ ms.collection: M365-identity-device-management
1717
---
1818
# When to use an Azure Multi-Factor Authentication Provider
1919

20+
> [!IMPORTANT]
21+
> Effective September 1st, 2018 new auth providers may no longer be created. Existing auth providers may continue to be used and updated, but migration is no longer possible. Multi-factor authentication will continue to be available as a feature in Azure AD Premium licenses.
22+
2023
Two-step verification is available by default for global administrators who have Azure Active Directory, and Office 365 users. However, if you wish to take advantage of [advanced features](howto-mfa-mfasettings.md) then you should purchase the full version of Azure Multi-Factor Authentication (MFA).
2124

2225
An Azure Multi-Factor Auth Provider is used to take advantage of features provided by Azure Multi-Factor Authentication for users who **do not have licenses**.
2326

24-
> [!NOTE]
25-
> Effective September 1st, 2018 new auth providers may no longer be created. Existing auth providers may continue to be used and updated, but migration is no longer possible. Multi-factor authentication will continue to be available as a feature in Azure AD Premium licenses.
26-
2727
## Caveats related to the Azure MFA SDK
2828

2929
Note the SDK has been deprecated and will only continue to work until November 14, 2018. After that time, calls to the SDK will fail.

articles/active-directory/authentication/concept-registration-mfa-sspr-combined.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -136,7 +136,7 @@ A user who has previously set up at least one method that can be used for Multi-
136136

137137
## Next steps
138138

139-
[Force users to re-register authentication methods](howto-mfa-userdevicesettings.md#manage-authentication-methods)
139+
[Force users to re-register authentication methods](howto-mfa-userdevicesettings.md#manage-user-authentication-methods)
140140

141141
[Enable combined registration in your tenant](howto-registration-mfa-sspr-combined.md)
142142

articles/active-directory/authentication/howto-mfa-userdevicesettings.md

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -17,17 +17,11 @@ ms.collection: M365-identity-device-management
1717
---
1818
# Manage user settings for Azure Multi-Factor Authentication
1919

20-
As an administrator, you can manage the following user and device settings:
21-
22-
* Require users to provide contact methods again
23-
* Delete app passwords
24-
* Require MFA on all trusted devices
20+
To help manage the users of Azure Multi-Factor Authentication, you can require users to reset their password, re-register for MFA, or revoke existing MFA sessions. For users that have defined app passwords, you can also choose to delete these passwords, causing legacy authentication to fail in those applications. These actions may be necessary if you need to provide assistance to a user, or want to reset their security status.
2521

2622
## Manage user authentication options
2723

28-
If you're assigned the *Authentication Administrator* role you can require users to reset their password, re-register for MFA, or revoke existing MFA sessions from their user object. These actions may be necessary if you need to provide assistance to a user, or want to reset their security status.
29-
30-
To manage user settings, complete the following steps:
24+
If you're assigned the *Authentication Administrator* role you can require users to reset their password, re-register for MFA, or revoke existing MFA sessions from their user object. To manage user settings, complete the following steps:
3125

3226
1. Sign in to the [Azure portal](https://portal.azure.com).
3327
1. On the left, select **Azure Active Directory** > **Users** > **All users**.

articles/active-directory/authentication/howto-registration-mfa-sspr-combined.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ The following policy applies to all selected users, who attempt to register usin
8686

8787
## Next steps
8888

89-
[Force users to re-register authentication methods](howto-mfa-userdevicesettings.md#manage-authentication-methods)
89+
[Force users to re-register authentication methods](howto-mfa-userdevicesettings.md#manage-user-authentication-methods)
9090

9191
[Available methods for Multi-Factor Authentication and SSPR](concept-authentication-methods.md)
9292

0 commit comments

Comments
 (0)