Skip to content

Commit 0abf4fb

Browse files
committed
added deprecation date
1 parent 6889dcd commit 0abf4fb

File tree

1 file changed

+2
-7
lines changed

1 file changed

+2
-7
lines changed

articles/active-directory/authentication/multi-factor-authentication-faq.yml

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ metadata:
77
ms.service: active-directory
88
ms.subservice: authentication
99
ms.topic: faq
10-
ms.date: 07/14/2020
10+
ms.date: 11/03/2022
1111
ms.author: justinha
1212
author: justinha
1313
manager: amycolannino
@@ -18,12 +18,7 @@ summary: |
1818
This FAQ answers common questions about Azure AD Multi-Factor Authentication and using the Multi-Factor Authentication service. It's broken down into questions about the service in general, billing models, user experiences, and troubleshooting.
1919
2020
> [!IMPORTANT]
21-
> As of July 1, 2019, Microsoft will no longer offer MFA Server for new deployments. New customers who would like to require multi-factor authentication from their users should use cloud-based Azure AD Multi-Factor Authentication. Existing customers who have activated MFA Server prior to July 1 will be able to download the latest version, future updates and generate activation credentials as usual.
22-
>
23-
> The information shared below regarding the Azure Multi-Factor Authentication Server is only applicable for users who already have the MFA server running.
24-
>
25-
> Consumption-based licensing is no longer available to new customers effective September 1, 2018.
26-
> Effective September 1, 2018 new auth providers may no longer be created. Existing auth providers may continue to be used and updated. Multi-factor authentication will continue to be an available feature in Azure AD Premium licenses.
21+
> In September 2022, Microsoft announced deprecation of Azure Multi-Factor Authentication Server. Beginning September 30, 2024, Azure Multi-Factor Authentication Server deployments will no longer service multifactor authentication (MFA) requests, which could cause authentications to fail for your organization. To ensure uninterrupted authentication services and to remain in a supported state, organizations should [migrate their users’ authentication data](how-to-migrate-mfa-server-to-azure-mfa-user-authentication.md) to the cloud-based Azure MFA service by using the latest Migration Utility included in the most recent [Azure MFA Server update](https://www.microsoft.com/download/details.aspx?id=55849). For more information, see [Azure MFA Server Migration](how-to-migrate-mfa-server-to-azure-mfa.md).
2722
2823
2924
sections:

0 commit comments

Comments
 (0)