Skip to content

Commit 8341094

Browse files
committed
Update howto-mfaserver-deploy-upgrade-pf.md
1 parent 136e1d9 commit 8341094

File tree

1 file changed

+8
-9
lines changed

1 file changed

+8
-9
lines changed

articles/active-directory/authentication/howto-mfaserver-deploy-upgrade-pf.md

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -6,25 +6,24 @@ services: multi-factor-authentication
66
ms.service: active-directory
77
ms.subservice: authentication
88
ms.topic: how-to
9-
ms.date: 07/11/2018
9+
ms.date: 10/10/2022
1010

1111
ms.author: justinha
1212
author: justinha
1313
manager: amycolannino
14-
ms.reviewer: michmcla
14+
ms.reviewer: jpettere
1515

1616
ms.collection: M365-identity-device-management
1717
---
18-
# Upgrade the PhoneFactor Agent to Azure Multi-Factor Authentication Server
18+
# Upgrade the PhoneFactor Agent to Azure AD Multi-Factor Authentication Server
1919

20-
To upgrade the PhoneFactor Agent v5.x or older to Azure Multi-Factor Authentication Server, uninstall the PhoneFactor Agent and affiliated components first. Then the Multi-Factor Authentication Server and its affiliated components can be installed.
20+
To upgrade the PhoneFactor Agent v5.x or older to Azure AD Multi-Factor Authentication Server, uninstall the PhoneFactor Agent and affiliated components first. Then the Multi-Factor Authentication Server and its affiliated components can be installed.
2121

2222
> [!IMPORTANT]
23-
> As of July 1, 2019, Microsoft no longer offers MFA Server for new deployments. New customers that want to require multi-factor authentication (MFA) during sign-in events should use cloud-based Azure AD Multi-Factor Authentication.
24-
>
23+
> In September 2022, Microsoft announced deprecation of Azure AD Multi-Factor Authentication Server. Beginning September 30, 2024, Azure AD 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).
24+
2525
> To get started with cloud-based MFA, see [Tutorial: Secure user sign-in events with Azure AD Multi-Factor Authentication](tutorial-enable-azure-mfa.md).
26-
>
27-
> Existing customers that activated MFA Server before July 1, 2019 can download the latest version, future updates, and generate activation credentials as usual.
26+
2827

2928
## Uninstall the PhoneFactor Agent
3029

@@ -76,6 +75,6 @@ The installation path is picked up from the registry from the previous PhoneFact
7675
7776
## Next steps
7877

79-
- [Install the users portal](howto-mfaserver-deploy-userportal.md) for the Azure Multi-Factor Authentication Server.
78+
- [Install the users portal](howto-mfaserver-deploy-userportal.md) for the Azure AD Multi-Factor Authentication Server.
8079

8180
- [Configure Windows Authentication](howto-mfaserver-windows.md) for your applications.

0 commit comments

Comments
 (0)