Courseiva

Microsoft Identity and Access Administrator Associate (SC-300) — Questions 226–242

242 questions total · 4 pages · All types, answers revealed

Page 3

Page 4 of 4

226
MCQmedium

A company wants to extend their Lifecycle Workflows to trigger a custom script in an on-premises environment whenever a new user is onboarded. Which feature should be used to integrate the workflow with the custom script?

A.Use a Microsoft Graph API call directly from the workflow tasks list.
B.Configure a dynamic group that triggers a PowerShell script when a user joins.
C.Create a 'Custom Task Extension' that calls an Azure Logic App.
D.Set up a Conditional Access 'Custom Authentication Extension'.
AnswerC

This is the supported method for extending Lifecycle Workflows. The custom task extension allows the workflow to send a payload to a Logic App, which can then use connectors to interact with on-premises systems, databases, or other third-party SaaS applications to complete the onboarding process.

Why this answer

Lifecycle Workflows in Microsoft Entra ID Governance support 'Custom Task Extensions' that allow you to call an external service — specifically an Azure Logic App — as part of a workflow. The Logic App can then execute the custom script in the on-premises environment (e.g., via an on-premises data gateway or hybrid runbook worker). This is the designed extensibility mechanism for integrating Lifecycle Workflows with external systems and custom code.

Exam trap

SC-300 often tests the misconception that Lifecycle Workflows can directly execute scripts or call Graph APIs — candidates overlook that the supported extension path is a Custom Task Extension invoking an Azure Logic App.

How to eliminate wrong answers

Option A is wrong because Lifecycle Workflows do not provide a built-in 'Microsoft Graph API call' task that lets you arbitrarily invoke external scripts — the supported extension mechanism is the Custom Task Extension, not direct Graph calls from the task list. Option B is wrong because dynamic groups are membership rules based on user attributes; they do not trigger PowerShell scripts on membership changes, and they have no execution capability. Option D is wrong because Conditional Access 'Custom Authentication Extensions' are used during the authentication flow to call external systems for additional authentication signals — they are not part of Lifecycle Workflows and cannot trigger onboarding scripts.

227
MCQmedium

Which of the following describes the correct process to rotate a client secret for a service principal?

A.Delete the existing secret and generate a new one immediately.
B.Add a new secret, update the application, then remove the old secret.
C.Change the service principal display name in the portal.
D.Restart the Azure Virtual Machine hosting the application.
AnswerB

This is the safest method for secret rotation. By having two valid secrets simultaneously, you allow for a smooth transition. Once you verify that the application has successfully adopted the new secret, you can safely remove the old one, ensuring no interruption in service during the rotation process.

Why this answer

The correct process to rotate a client secret for a service principal is to add a new secret, update the application to use the new secret, and then remove the old secret. This ensures that the application continues to function without downtime, as the old secret remains valid until the new one is in use. This approach follows the principle of least disruption and is a best practice for secret rotation.

Exam trap

The trap is thinking that you must delete the old secret before creating a new one to avoid confusion. Candidates may choose to delete first, which causes downtime. The correct approach is to add new, update, then remove old.

How to eliminate wrong answers

Option A is wrong because deleting the existing secret immediately would cause the application to fail authentication until the new secret is configured. Option C is wrong because changing the display name has no effect on the secret. Option D is wrong because restarting a VM does not rotate the secret and is unrelated.

228
MCQmedium

You administer a Microsoft Entra tenant. A line-of-business application runs as an Azure App Service web app and must read blobs from an Azure Storage account. The security team requires that no credentials be stored in code or configuration, and that access be granted only to that specific app. You enable a system-assigned managed identity on the App Service. Which action must you take next to allow the app to read the blobs?

A.Assign the Storage Blob Data Reader role to the managed identity's service principal at the storage account scope.
B.Create a new app registration for the App Service and upload a client certificate.
C.Generate a shared access signature (SAS) for the storage account and store it in the App Service application settings.
D.Add the App Service's outbound IP addresses to the storage account firewall and enable public network access.
AnswerA

After enabling the system-assigned managed identity, Microsoft Entra creates a service principal for the App Service. Granting that principal the Storage Blob Data Reader role at the storage account scope authorizes blob reads using the identity's token, with no credentials stored anywhere. This is the standard authorization step for managed identities accessing Azure Storage.

Why this answer

The system-assigned managed identity creates a service principal in Microsoft Entra ID that represents the App Service. To let it read blobs, you must grant that principal a data-plane role such as Storage Blob Data Reader on the target storage account. This provides credential-free authentication and least-privilege authorization, satisfying both the no-secrets and app-specific access requirements.

Exam trap

The trap here is assuming that enabling the managed identity alone grants access, when in fact you must also assign an appropriate Azure RBAC role to its service principal on the target resource.

229
MCQmedium

When configuring an Azure AD application for a multi-tenant environment, what is the impact of changing the 'Supported account types' to 'Accounts in any organizational directory'?

A.The application can only be used by users within your home tenant.
B.The application can accept authentication from any Azure AD tenant.
C.The application becomes a public application and ignores authentication.
D.The application is automatically deleted and must be re-registered.
AnswerB

Multi-tenant applications are accessible across the entire Azure AD ecosystem. This allows for scenarios like SaaS applications where users from different organizations can sign in using their own corporate credentials. This configuration requires careful handling of tenant-specific authorization logic within the application code.

Why this answer

Setting 'Supported account types' to 'Accounts in any organizational directory' makes the app multi-tenant, meaning any Azure AD tenant can consent to and authenticate to the application. This is the standard configuration for SaaS apps that need to serve customers across many organizations.

Exam trap

SC-300 often tests the difference between single-tenant and multi-tenant app registration, tricking candidates into thinking multi-tenant apps bypass authentication or require re-registration.

How to eliminate wrong answers

Option A is wrong because single-tenant apps are restricted to the home tenant; the multi-tenant setting explicitly removes that restriction. Option C is wrong because 'public application' refers to the OAuth client type (public vs confidential), not the account type setting, and it does not ignore authentication. Option D is wrong because changing supported account types does not delete or require re-registration of the app; it only changes the audience claim and consent behavior.

230
MCQmedium

You are configuring Self-Service Password Reset (SSPR) for your organization. You need to ensure that users are prompted to verify their contact information periodically to maintain the accuracy of recovery data. Which setting should you configure?

A.Number of days before users are asked to re-confirm their authentication information.
B.The registration policy in Microsoft Entra ID Protection for MFA enrollment.
C.The password expiration policy within the Microsoft 365 Admin Center settings.
D.The 'Notify users on password resets' toggle in the SSPR notification settings.
AnswerA

This specific setting in the SSPR configuration portal allows administrators to define an interval, such as 180 days, after which users must verify their details. When the interval expires, users are prompted during their next sign-in to confirm or update their phone numbers and emails. This proactive measure ensures that the recovery data remains valid and useful.

Why this answer

The setting 'Number of days before users are asked to re-confirm their authentication information' directly controls the re-confirmation interval for SSPR authentication methods. Configuring this value (default 180 days) forces users to periodically verify their registered phone or email, ensuring recovery data stays accurate. This is found under Microsoft Entra ID > Password reset > Registration.

Exam trap

SC-300 often tests the confusion between SSPR registration settings and MFA or password expiration policies, causing candidates to pick options that sound related but govern different identity lifecycle aspects.

How to eliminate wrong answers

Option B is wrong because the registration policy in Entra ID Protection governs MFA enrollment and risk-based policies, not SSPR contact re-confirmation. Option C is wrong because password expiration policy controls when passwords must be changed, not when authentication info is re-confirmed. Option D is wrong because the 'Notify users on password resets' toggle only controls email notifications when a password is reset, not periodic verification prompts.

231
MCQhard

Refer to the exhibit. You have configured a service principal for an enterprise application. A user in your organization attempts to access the application but receives an error stating that they are not authorized, despite having the correct URL. Based on the configuration shown in the exhibit, what is the most likely cause of the access denial?

A.The application's client secret has expired.
B.The user must be assigned to the application.
C.The service principal type is set incorrectly.
D.The application is missing a verified publisher.
AnswerB

The exhibit shows 'appRoleAssignmentRequired' set to true. This configuration mandates that an administrator must explicitly assign users or groups to the application in the 'Users and groups' pane. Without this assignment, Entra ID will block sign-in attempts for all users by default.

Why this answer

In Microsoft Entra ID, the 'appRoleAssignmentRequired' property on a service principal determines whether a user must be explicitly assigned to the application before they can sign in. When this value is set to true, any user or service principal not explicitly granted a role for the application will be denied access, regardless of tenant-level permissions.

Exam trap

Candidates often overlook the 'appRoleAssignmentRequired' flag, assuming that if a user exists in the tenant, they can access any application. This property is a critical security gate that overrides default 'all users can sign in' behavior.

232
MCQmedium

An organization needs to allow an Azure Function to access secrets in an Azure Key Vault without storing any credentials in the Function's configuration files. Which solution should you implement to satisfy this requirement with the least administrative effort?

A.Create a service principal and store the client secret in the Function app settings.
B.Configure a system-assigned managed identity for the Azure Function.
C.Use a shared access signature (SAS) token with a five-year expiration date.
D.Register a new application in Microsoft Entra ID and grant it Key Vault Secrets Officer permissions.
AnswerB

System-assigned managed identities are created directly on the resource and are tied to its lifecycle. They provide an identity for the resource to use when authenticating to services that support Microsoft Entra authentication, such as Key Vault, without requiring the developer to manage or store any credentials.

Why this answer

A system-assigned managed identity for the Azure Function allows it to authenticate to Azure Key Vault without storing credentials. The identity is created in Microsoft Entra ID and can be granted access to Key Vault secrets, eliminating the need for secrets in configuration.

Exam trap

SC-300 often tests the difference between managed identities and service principals; candidates may choose to register an app because they are familiar with it, but that still requires credential management, whereas managed identity is credential-free.

How to eliminate wrong answers

Option A is wrong because storing a client secret in app settings still requires managing and rotating that secret, which is the problem to avoid. Option C is wrong because SAS tokens are for storage accounts, not Key Vault, and long expiration increases risk. Option D is wrong because registering an app and granting permissions still requires managing credentials (client secret or certificate) for that app, adding administrative effort.

233
Multi-Selecthard

You are configuring an access review for a privileged role in Microsoft Entra ID. The review must automatically remove access if reviewers do not respond within the review period. You also need to ensure that the review recurs every quarter. What should you configure? (Choose two.)

Select 2 answers
A.Configure the review to send reminders to reviewers every day.
B.Enable 'Justification required' for reviewers to provide a reason for their decision.
C.Set 'Auto apply results to resource' to 'Enable' and configure 'If reviewers don't respond' to 'Remove access'.
D.Set the review to apply results manually after the review period ends.
E.Set the review recurrence to 'Quarterly' and specify the duration of the review.
AnswersC, E

This setting ensures that when reviewers do not respond, the system automatically removes access. Enabling auto-apply means the decision is enforced without manual intervention. This directly satisfies the requirement to automatically remove access if reviewers do not respond within the review period.

Why this answer

To automatically remove access when reviewers do not respond, you must enable auto-apply and set the no-response action to remove access. To make the review recur quarterly, you must configure the recurrence to quarterly. Reminders, justification, and manual application do not meet the automatic removal and recurrence requirements.

Exam trap

The trap here is confusing reminders with automatic enforcement; reminders do not remove access, only auto-apply with the correct no-response action does.

234
MCQmedium

You are using Microsoft Entra ID Governance to manage the lifecycle of guest users. You need to ensure that guest users are automatically removed from the tenant after 90 days of inactivity. What should you configure?

A.Use an access package with an expiration policy of 90 days and assign it to all guests.
B.Configure a lifecycle workflow that triggers when a guest user is inactive for 90 days and runs a 'Delete user' task.
C.Set the external collaboration settings to automatically delete guest users after 90 days.
D.Create an access review for guest users that runs every 90 days and automatically removes access if no response.
AnswerB

Lifecycle workflows can be triggered based on user inactivity. You can create a workflow that checks for guest users who have not signed in for 90 days and then executes a 'Delete user' task. This directly removes the guest accounts from the tenant, meeting the requirement. This is a native capability in Entra ID Governance.

Why this answer

Lifecycle workflows in Microsoft Entra ID Governance can automate guest user lifecycle. You can create a workflow triggered by inactivity (e.g., no sign-in for 90 days) that executes a 'Delete user' task. This removes the guest account from the tenant.

Access reviews and access packages manage access but do not delete accounts. External collaboration settings do not handle automatic deletion. Therefore, the lifecycle workflow is the correct solution.

Exam trap

The trap here is confusing access removal with account deletion; access reviews and access packages remove access but leave the account, while lifecycle workflows can delete the account.

235
Multi-Selectmedium

You are managing service principals for an application that spans multiple environments. You need to ensure that credentials for these principals are rotated securely. Which TWO actions should you perform? (Choose two)

Select 2 answers
A.Store all service principal secrets in Azure Key Vault and configure automated rotation.
B.Use the Azure AD portal to manually update secrets every 30 days.
C.Replace client secrets with federated identity credentials where supported.
D.Enable password writeback in Azure AD Connect to force rotation.
E.Configure the service principal to rotate its own password every hour.
AnswersA, C

Azure Key Vault provides native support for secret management. By integrating with Azure Functions, you can automate the process of generating new secrets, updating the service principal in Azure AD, and updating the vault value, ensuring no downtime and reducing the surface area for credential exposure through manual intervention.

Why this answer

Option A is correct because storing service principal secrets in Azure Key Vault and configuring automated rotation lets you centralize secret storage and use Key Vault's rotation capabilities (for example, Event Grid notifications plus an Azure Function or Logic App) to replace credentials on a schedule without manual intervention. Option C is correct because federated identity credentials (workload identity federation) let the application obtain Microsoft Entra ID tokens via an external identity provider such as GitHub Actions, Kubernetes, or AWS, eliminating the need to store and rotate a client secret at all. Option B is not ideal because manual 30-day updates are error-prone and do not provide secure, automated rotation.

Option D is incorrect because password writeback in Azure AD Connect synchronizes on-premises password changes to Microsoft Entra ID for user accounts and does not rotate service principal secrets. Option E is incorrect because a service principal cannot self-rotate its own password every hour, and such a short interval would be impractical and unsupported.

Exam trap

The trap is thinking manual rotation or password writeback can secure service principals; the exam expects knowledge of automated secret management and federated credentials as best practices.

236
MCQmedium

You manage a Microsoft Entra tenant. A third-party SaaS application needs to read directory data via Microsoft Graph without storing a client secret. The vendor supports the client credentials flow and has published a JWKS endpoint. You create an app registration and configure a federated identity credential. The vendor's token service issues a JWT with an 'iss' claim that does not match the default issuer URL. What should you do to ensure authentication succeeds?

A.Enable the 'acceptMappedClaims' property on the application manifest and add a claim mapping policy.
B.Create a new client secret and provide it to the vendor for authentication.
C.Configure a custom issuer URL in the federated identity credential by setting the 'issuer' field to the vendor's token service URL.
D.Add the vendor's token service URL to the application's redirect URIs in the authentication blade.
AnswerC

A federated identity credential includes an issuer field that must exactly match the 'iss' claim in the incoming token. If the vendor uses a non-standard issuer, you must set the issuer to that exact URL. The subject and audience fields must also match; the issuer is a required matching condition for the trust to be established.

Why this answer

Workload Identity Federation relies on matching three claims: issuer, subject, and audience. When the external token's issuer does not match the default Microsoft Entra issuer, you must explicitly set the issuer in the federated identity credential to the exact URL from the vendor's token service. This allows Microsoft Entra ID to trust tokens from that issuer without a client secret.

Exam trap

The trap here is assuming that any external token can be trusted without validating the issuer claim, or that claim mapping can bypass issuer validation.

237
MCQmedium

Your organization has a group of contractors who use personal devices to access corporate resources. You want to ensure that if their sign-in is flagged as medium or high risk, they are forced to perform MFA, but if the user risk is high, they are blocked entirely. Where should you configure these specific risk-based responses?

A.Conditional Access policies using the Sign-in risk and User risk conditions.
B.The Security Defaults setting in the Microsoft Entra properties menu.
C.The Microsoft Entra ID Protection dashboard under 'Notify'.
D.The Microsoft Defender for Cloud Apps 'Activity Policy' section.
AnswerA

Conditional Access is the modern way to implement risk-based security. It allows you to create separate policies: one that triggers MFA when 'Sign-in risk' is medium or high, and another that blocks access when 'User risk' is high. This approach is more flexible and integrated than using the legacy Identity Protection standalone policies, and it is the recommended method for most organizations.

Why this answer

Conditional Access is the only place where you can combine sign-in risk and user risk conditions with grant controls (require MFA) and session/block controls in a single policy. You create one policy for sign-in risk = medium/high requiring MFA, and another for user risk = high blocking access. This maps directly to the requirement.

Exam trap

SC-300 often tests the confusion between ID Protection's detection/notification features and Conditional Access's enforcement — candidates pick the ID Protection dashboard thinking it enforces actions, but only Conditional Access applies grant/block controls.

How to eliminate wrong answers

Option B is wrong because Security Defaults is a one-size-fits-all baseline that enforces MFA for all users and cannot differentiate by risk level or apply block controls based on user risk. Option C is wrong because the ID Protection 'Notify' settings only configure who receives risk alert emails — they do not enforce authentication or blocking actions. Option D is wrong because Defender for Cloud Apps Activity Policies govern app behavior (e.g., download, share) after sign-in, not the authentication flow itself, and cannot force MFA or block sign-in based on Entra ID risk detections.

238
MCQmedium

Refer to the exhibit. An administrator is using the Microsoft Graph PowerShell SDK to create a new user. Which additional step must be taken if the administrator wants this user to be prompted to change their password at the first sign-in?

A.Add the parameter -ForceChangePasswordNextSignIn $true to the New-MgUser command.
B.Set the 'ForceChangePasswordNextSignIn' property to true within the $passwordProfile object.
C.Run the command Set-MgUserPassword -UserId "tuser@contoso.com" -ForceChange $true after creation.
D.The user will automatically be prompted to change their password because 'AccountEnabled' is set to true.
AnswerB

In Microsoft Graph, the 'PasswordProfile' object contains a property called 'ForceChangePasswordNextSignIn'. By setting this to true before passing the object to the 'New-MgUser' command, the directory will flag the account to require a password update immediately after the user successfully authenticates for the first time.

Why this answer

To force a password change at first sign-in, the 'ForceChangePasswordNextSignIn' property must be set to true within the $passwordProfile object when creating the user with New-MgUser. This is the correct method in Microsoft Graph PowerShell SDK.

Exam trap

SC-300 often tests the misconception that a separate parameter or cmdlet is used to force password change, but it is a property within the password profile.

How to eliminate wrong answers

Option A is wrong because there is no -ForceChangePasswordNextSignIn parameter for New-MgUser; the property must be set in the password profile. Option C is wrong because Set-MgUserPassword does not have a -ForceChange parameter, and the password profile should be set during creation. Option D is wrong because AccountEnabled does not control password change prompts; it only enables the account.

239
MCQhard

You are the Identity and Access Administrator for a company that uses Microsoft Entra ID. The company has a requirement that all administrative actions in Microsoft Entra ID must be performed from a trusted location. You need to configure a Conditional Access policy that blocks access to the Microsoft Entra admin center for administrators when they are not on the corporate network. The corporate network is defined as a named location with a specific public IP address range. What should you do?

A.Create a Conditional Access policy that targets the 'Microsoft Entra admin center' cloud app, includes the 'Directory roles' assignment and selects all administrative roles, and under Conditions > Locations, include 'Any location' and exclude the named location 'Corporate Network'. Set the access control to 'Block'.
B.Create a Conditional Access policy that targets the 'Microsoft Entra admin center' cloud app, includes the 'Directory roles' assignment and selects the Global Administrator role, and under Conditions > Locations, include 'Any location' and exclude the named location 'Corporate Network'. Set the access control to 'Block'.
C.Create a Conditional Access policy that targets 'All cloud apps', includes the 'Directory roles' assignment and selects all administrative roles, and under Conditions > Locations, include 'Any location' and exclude the named location 'Corporate Network'. Set the access control to 'Block'.
D.Create a Conditional Access policy that targets the 'Microsoft Entra admin center' cloud app, includes the 'All users' assignment, and under Conditions > Locations, include 'Any location' and exclude the named location 'Corporate Network'. Set the access control to 'Block'.
AnswerA

This policy targets the admin center app, applies to all administrative roles, and blocks access when the user is not on the corporate network (by excluding the trusted named location). This precisely meets the requirement that all administrative actions must be performed from a trusted location. It ensures that any user with an admin role is blocked when off-network.

Why this answer

The correct policy scopes the block to the Microsoft Entra admin center, applies to all administrative roles, and excludes the trusted corporate network location. This ensures that administrators can only access the admin center from the trusted network. Targeting all users or only the Global Administrator role would not meet the requirement, and targeting all cloud apps would be too broad.

Exam trap

The trap here is either targeting all users instead of directory roles, or selecting only the Global Administrator role instead of all administrative roles, which would leave gaps in the policy.

240
Multi-Selecthard

You need to implement a high-security authentication strategy for your executive team. The strategy must support phishing-resistant authentication. Which THREE authentication methods meet this requirement?

Select 3 answers
A.FIDO2 security keys
B.Windows Hello for Business
C.Certificate-based authentication (CBA)
D.Microsoft Authenticator push notifications
E.SMS-based authentication codes
AnswersA, B, C

FIDO2 security keys use public-key cryptography to provide strong, phishing-resistant authentication. The key is physically held by the user and requires a local gesture, such as a PIN or biometric touch, to activate. Because the authentication is tied to the specific domain of the website, it cannot be spoofed by attackers using traditional phishing or man-in-the-middle techniques.

Why this answer

Phishing-resistant authentication is a cornerstone of modern identity security, as it prevents attackers from using stolen credentials or intercepting MFA codes. These methods rely on cryptographic keys bound to the hardware or the device, making it impossible for a user to accidentally provide their credentials to a malicious site. Implementing these methods significantly reduces the risk of account takeovers for high-profile users.

Exam trap

Candidates often select standard MFA methods like SMS, voice calls, or standard Microsoft Authenticator push notifications, forgetting that these are vulnerable to modern interception and social engineering attacks.

241
MCQmedium

You are the Identity and Access Administrator for a Microsoft Entra ID tenant. You need to delegate the ability to manage user accounts, including creating users and resetting passwords, to a helpdesk team. The solution must follow the principle of least privilege. Which role should you assign?

A.Helpdesk Administrator
B.Global Administrator
C.Password Administrator
D.User Administrator
AnswerD

The User Administrator role allows management of all aspects of users and groups, including creating users, resetting passwords, and managing group memberships. It does not grant permissions to manage other administrators or tenant-wide settings, aligning with least privilege for helpdesk tasks.

Why this answer

The User Administrator role grants the necessary permissions to create users and reset passwords without granting excessive privileges. Helpdesk Administrator can reset passwords but cannot create users, and Password Administrator only handles password resets. Global Administrator is overly permissive.

Thus, User Administrator is the least privileged role that meets the requirements.

Exam trap

The trap here is selecting Helpdesk Administrator because it sounds like the right fit for helpdesk, but it cannot create users.

242
Multi-Selectmedium

You need to implement Authentication Strengths in Microsoft Entra ID to enforce phishing-resistant MFA for your IT administrators. Which TWO authentication methods are considered phishing-resistant by the built-in 'Phishing-resistant MFA' strength?

Select 2 answers
A.FIDO2 security keys
B.Microsoft Authenticator (Push)
C.Windows Hello for Business
D.Email OTP
E.Password + SMS
AnswersA, C

FIDO2 security keys are a primary example of phishing-resistant technology. They use public-key cryptography to authenticate the user and are physically present during the process. This prevents remote attackers from intercepting or replaying the authentication credentials, making it a core part of the phishing-resistant MFA strength.

Why this answer

Option A (FIDO2 security keys) is correct because FIDO2/WebAuthn credentials are bound to the origin and use public-key cryptography, making them inherently resistant to phishing, AiTM, and replay attacks, which is exactly what the built-in 'Phishing-resistant MFA' authentication strength requires. Option C (Windows Hello for Business) is correct because it is also based on FIDO2/WebAuthn (or certificate-based) asymmetric key authentication tied to the device and origin, and Microsoft explicitly includes it in the Phishing-resistant MFA strength. Option B (Microsoft Authenticator push) is not included because push notifications with number matching are only classified as MFA (not phishing-resistant) since they can be relayed in real time by an adversary-in-the-middle.

Option D (Email OTP) is not included because one-time codes delivered by email are phishable and are only considered single-factor or weak MFA. Option E (Password + SMS) is not included because SMS codes are susceptible to interception, SIM swapping, and phishing, so they do not meet the phishing-resistant bar.

Exam trap

SC-300 often tests the misconception that any MFA method counts as phishing-resistant; candidates must remember that only FIDO2 keys, Windows Hello for Business, and CBA qualify, while Authenticator push and SMS do not.

Page 3

Page 4 of 4

All pages