

When enabled users sign in and complete the registration process, their state changes to Enforced. When you enroll users in per-user Azure AD Multi-Factor Authentication, their state changes to Enabled. Multi-Factor Authentication statusĪll users start out Disabled. In the next step, we will show how to create an MFA report. Is there a better way to have an insight into the MFA instead of the Microsoft 365 page? Yes, there is, and that’s when PowerShell will come to the rescue. That’s because Microsoft did not provide a way for that.

The PowerShell script can’t identify the MFA status if it’s enabled with Conditional Access. Note: If you see that MFA is enabled or enforced, it does not mean that MFA is configured.
