M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions→ m365con.net

Blog · Mirko Peters

PIM Role Activation Shows No MFA Prompt: How to Check What Is Really Enforced

By ·

You required MFA for a PIM role but users activate without a prompt? Check the role setting, earlier MFA in the session, authentication context and the audit log before you assume it is broken.

An administrator enables MFA for a role in Privileged Identity Management (PIM). A user then activates the Exchange Administrator role and nothing asks for a second factor. That looks like a gap in the setup. Usually it is not.

Key points

  • Learn says users might not be prompted for MFA at activation if they already used strong credentials or MFA earlier in the same session.
  • The role setting On activation, require multifactor authentication is a fallback. If an authentication context is set and an enabled Conditional Access policy targets it, that policy decides.
  • The fallback does not apply if the Conditional Access policy is off, in report-only mode, or excludes the user.
  • Use sign-in frequency set to Every time in the policy if every activation must prompt again.

This article is based on a Microsoft Q&A thread from April 2025. A Microsoft moderator answered, and the person who asked confirmed that the answer helped. A second thread, from August 2026, asked why an eligible role did not show up at all, and its only reply was generated by AI, so I treat it as an open question. The checks below come from current Microsoft Learn pages. This is not an official Microsoft procedure.

What you may be seeing

  • A user activates an eligible role and sees no extra verification step.
  • The role settings say that MFA is required, but the user was never asked.
  • Or the eligible role does not appear in the list at all.

Step 1: Read the role setting

You need at least the Privileged Role Administrator role.

  1. In the Microsoft Entra admin center, go to ID Governance > Privileged Identity Management > Microsoft Entra roles > Roles.
  2. Select the role, then Role settings, then Edit.
  3. Look at these options, using the labels from Learn:
  • On activation, require multifactor authentication
  • On activation, require Microsoft Entra Conditional Access authentication context
  • Require justification on activation
  • Require ticket information on activation
  • Require approval to activate

The first two options control the MFA step at activation. Check which of them is set for your role, because they behave differently (see step 4).

Step 2: Understand why no prompt can be normal

Learn says users might not be prompted for MFA if they authenticated with strong credentials or provided MFA earlier in the session. The activation guide says you are required to authenticate only once per session.

In the 2025 thread, the moderator gave the same explanation and added that a Conditional Access policy that enforces MFA for admin portals can have the same effect. The moderator described this as the likely cause: MFA had probably been satisfied earlier, so the activation step did not ask again. The thread does not show that anyone verified it.

So before you change anything, answer one question: did this user complete MFA when they signed in?

Step 3: Check the audit log

Learn describes the PIM audit view like this:

  1. Sign in as a Global Administrator, Global Reader, Privileged Role Administrator, Security Administrator or Security Reader.
  2. Go to ID Governance > Privileged Identity Management > Microsoft Entra roles > Resource audit.
  3. Filter by date.

My audit in the same area shows only your own activity.

The moderator in the thread pointed to the audit details of the activation event and a field named IsAuthenticatedWithMfa. I could not find that field name on the Learn page about the PIM audit history, so treat it as reported in the thread, not confirmed in Learn. Open an activation event and see what your tenant shows.

Learn also says PIM data is available for the past 30 days. If you need more, send the logs to Azure Monitor with diagnostic settings.

Step 4: Decide if you need a stricter control

If "MFA once per session" is not enough, switch from the plain MFA setting to an authentication context. Learn's description:

  1. Create a Conditional Access policy for the authentication context. Do not scope it to the authentication context and a directory role at the same time, because during activation the user does not have the role yet.
  2. In the role settings, select On activation, require Microsoft Entra Conditional Access authentication context and choose the context.
  3. To force a new authentication each time, set sign-in frequency to Every time under Session controls in the policy.

Three details from Learn that cause confusion:

  • Fallback. If no enabled Conditional Access policy targets the configured context, PIM falls back to requiring MFA as in On activation, require multifactor authentication. That fallback does not apply if the policy is turned off, in report-only mode, or excludes an eligible user. So a policy left in report-only mode means the fallback MFA requirement does not apply either.
  • Ten-minute window. After a user re-authenticates for one activation, activating another eligible role within 10 minutes does not prompt again. This covers Microsoft Entra roles, Azure resource roles and PIM for Groups.
  • After activation. The setting does not stop the user from using the activated role from another session, device or location. For that, create a second Conditional Access policy that targets directory roles.

Learn adds a security note: people who can manage Conditional Access policies, such as Conditional Access Administrators or Security Administrators, can change or remove these requirements, so treat them as highly privileged.

Step 5: If the role does not appear under My roles

This is the 2026 thread's question. It has no confirmed answer, and the Learn activation page has no portal troubleshooting section for it. These checks are grounded in other Learn statements:

  1. In ID Governance > Privileged Identity Management > My roles > Microsoft Entra roles, confirm you are looking at the right area. Learn says this lists your eligible Microsoft Entra roles.
  2. As an administrator, open Microsoft Entra roles and find the user's assignment on the Eligible roles tab (the exact navigation to it can differ in your portal). An assignment can be time-bound and expire at the end of its period. Learn says the assignment type must be Eligible for a member to need an activation step, while Active assignments are always on.
  3. If approval is required, go to My requests to see whether a pending request exists. Learn says that for a role that needs approval, selecting Cancel cancels the request and you must submit a new one.
  4. Learn notes that when someone gets eligibility through group membership, the Microsoft Graph request used to list eligible roles does not return it. That statement is about the Graph call, not the portal.

If the role is active but another admin portal does not recognize it, Learn says an application that cached the "no role" state may not grant access, and that signing out and back in may help.

Verify

  1. Sign out fully and sign in again with MFA. Activate the role and note whether you were prompted.
  2. Sign in from a new session and activate again, and compare.
  3. Open Resource audit and match the events to your tests.
  4. If you use an authentication context, use a test user and confirm that the policy is On, not report-only.

Limits

  • The 2025 thread explains the missing prompt but does not prove anything about your tenant. Your sign-in logs do.
  • The IsAuthenticatedWithMfa field is not confirmed in Learn.
  • The 2026 thread about a missing role has no confirmed answer.

Related

Sources

Follow the showApple PodcastsSpotify

Entities in this article

Microsoft Entra Privileged Identity Management (PIM) Multifactor authentication (MFA) Conditional Access authentication context Conditional Access

Related articles

RSS