Note: The question is included in a number of questions that depicts the identical set-up. However, every question has a distinctive result. Establish if the solution satisfies the requirements.
Your company makes use of Multi-Factor Authentication for when users are not in the office. The Per Authentication option has been configured as the usage model.
After the acquisition of a smaller business and the addition of the new staff to Azure Active Directory (Azure AD) obtains a different company and adding the new employees to Azure Active Directory (Azure AD), you are informed that these employees should also make use of Multi-Factor Authentication.
To achieve this, the Per Enabled User setting must be set for the usage model.
Solution: You reconfigure the existing usage model via the Azure portal.
Does the solution meet the goal?
A. Yes
B. No
Answer : B
✅ Explanation:
The "Per Authentication" usage model and "Per Enabled User" usage model are different MFA models in Azure. Simply reconfiguring the existing usage model via the Azure portal does not automatically enforce MFA for the newly added users using the "Per Enabled User" model.
To meet the goal, you would need to:
Enable MFA for each new user individually under the Per User MFA settings in Azure AD.
Or, better yet, consider moving to Conditional Access policies, which is the modern and recommended approach for enforcing MFA based on conditions (like sign-in location, risk, etc.).