Share via

On-prem Multi Factor Authenticator activation requirement

J. Random-Sysadm 41 Reputation points
2022-10-19T17:18:56.137+00:00

I need to set up a MFA 8.0.8.1 standalone server in a test environment in an isolated domain (domain.dev [non-publicly registered / no public DNS]).

Is activation in Azure a requirement during the setup or can a MFA server be set up?

We do have our primary domain (domain.com) syncing with a tenant in Azure via AD Connect. Could that tenant be used to activate the server in the domain .dev environment?

Microsoft Security | Microsoft Entra | Microsoft Entra ID
0 comments

Answer accepted by question author

Vasil Michev 126.9K Reputation points MVP Volunteer Moderator
2022-10-19T18:05:38.85+00:00

You can install the server without activating it, but you will not be able to use it. And you might also be unable to generate activation credentials if you haven't activated previous instances in the same tenant. MFA Server has not been supported for new deployments since few years now, and last week at Ignite Microsoft announced the deprecation plan:

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.

Was this answer helpful?

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.