Securing registration uses the Conditional Access user action Register security information, which needs Microsoft Entra ID P1 or higher (Microsoft Learn).
In one minute
- Turn on the Temporary Access Pass for new users and lost phones.
- Create a Conditional Access policy on Register security information.
- Require MFA or a strong authentication method to register outside trusted networks.
- Review recently registered methods, especially on admin accounts.
MFA registration is part of the identity checks in our Microsoft 365 Security Audit.
What it is
Why registration needs its own protection
Microsoft lets you treat the security info registration page like any app in Conditional Access, using the user action Register security information. A policy can require MFA, a strong authentication method or a trusted network before anyone adds or changes a sign-in method (Microsoft Learn).
The pieces involved
| Piece | What it does | Recommendation |
|---|---|---|
| Register security information (user action) | Conditional Access target for the registration page | Protect it |
| Temporary Access Pass | Time-limited code for first registration or a lost phone | Turn on, one-time use |
| Authentication strength | Which methods count for the policy | MFA, or phishing-resistant for admins |
| Trusted locations | Office networks that can be exempted | Use with care, review regularly |
Microsoft notes that a Temporary Access Pass satisfies Conditional Access requirements for MFA, so new users can register from anywhere without weakening the policy (Microsoft Learn).
Why it matters
Attackers keep access by enrolling their own MFA
- Password and one MFA promptPhishing or fatigue.
- Opens Security infoAdds a new authenticator.
- Registration policyNeeds a strong method first.
- Own MFA enrolledWithout it: password reset won’t help.
- Long-term accessMail, files, payments.
Drawing: where a registration policy breaks the path.
of identity attacks were password attacks in the first half of 2025.
Source: Microsoft Digital Defense Report 2025hour is the default lifetime of a Temporary Access Pass; it can be set from 10 minutes to 30 days.
Source: Microsoft Learnsince when registration policies also apply to Windows Hello for Business and macOS Platform SSO enrollment.
Source: Microsoft Learnuse per pass: Microsoft recommends restricting Temporary Access Passes to single use.
Source: Microsoft LearnDocumented incidents
Advisory · FBI and CISA, AA23-320A
Scattered Spider registers its own MFA
The FBI and CISA describe Scattered Spider actors registering their own MFA tokens after compromising an account, and using SIM swapping to take over MFA prompts.
Source: CISA advisory AA23-320A
What we find in audits
What this finding looks like in our audit reports
These are real pages from our published compromise assessment sample, written for a fictional company. Click any page to open it full size.
Your options
What each plan gives you
| Capability | Business Basic and Standard | Entra ID P1 (Business Premium, E3) | Entra ID P2 (E5) |
|---|---|---|---|
| Combined security info registration | Yes | Yes | Yes |
| Audit log of new registrations | Yes | Yes | Yes |
| Conditional Access on Register security information | No | Yes | Yes |
| Risk-based policies on top | No | No | Yes |
Without Conditional Access, review the authentication methods activity report and audit log for new registrations every week.
How to check it yourself
See recent registrations and your policy, without changing anything
Look for an enabled policy whose target is User actions › Register security information. Then check recent registrations in the audit log.
Read-only PowerShell: security info registered in the last 30 days
Connect-MgGraph -Scopes "AuditLog.Read.All"
$since = (Get-Date).AddDays(-30).ToString("yyyy-MM-ddTHH:mm:ssZ")
Get-MgAuditLogDirectoryAudit -All -Filter "activityDisplayName eq 'User registered security info' and activityDateTime ge $since" |
Select-Object ActivityDateTime, @{n="User";e={$_.TargetResources[0].UserPrincipalName}}, ResultThe commands only read data. Registrations on admin accounts, or several on the same day, should be confirmed with each person.
How to configure
How to protect MFA registration, step by step
Entra ID P1 or P2
Create the policy
- In Authentication methods › Policies, enable Temporary Access Pass and set one-time use.
- Create a Conditional Access policy for All users; exclude guests and your two emergency accounts.
- Under Target resources › User actions, select Register security information.
- Under Grant, require an authentication strength (MFA, or phishing-resistant for admins).
- Start in Report-only, then switch to On.
Every week
Check what was registered
- Review new registrations, starting with admin accounts.
- Confirm unexpected ones with the person by phone, not email.
- Remove unknown methods and revoke sessions.
- Issue a Temporary Access Pass when someone loses a phone, instead of resetting MFA blindly.
What your users will notice
Registering from the office or with an existing MFA method works as before. New starters get a Temporary Access Pass from IT.
How to undo it
Set the policy to Report-only or Off.
Proof and questions
How to prove it is fixed, and what to ask your IT provider
Evidence it is fixed
- A registration policy is On, with only emergency accounts and guests excluded.
- Temporary Access Pass is enabled for one-time use.
- Admin registrations require phishing-resistant methods.
- A weekly review of new registrations.
Questions for your IT provider
- Do we protect the security info registration page with Conditional Access?
- How do new starters and people with lost phones register?
- Who reviews new MFA registrations on admin accounts?
- Have any admins registered new methods this month?
- Do we confirm help desk MFA resets by calling the user back?
Signs it was already abused
If an attacker may already have registered MFA, look for these signs
Red flags
- New authenticator registrations from unfamiliar IP addresses.
- Several admins registering a new method on the same day.
- A phone number changed shortly before a password reset.
- MFA approvals the user didn’t make.
- Registrations soon after a risky or foreign sign-in.
If you see these, remove the unknown methods, reset the password, revoke sessions and keep the logs. Our account takeover investigation establishes what was reached, and the Microsoft 365 Evidence Clock shows how long the records are kept.
Framework mapping
Where MFA registration controls fit
| Framework | Where it fits |
|---|---|
| NIST CSF 2.0 | PR.AA-03: users authenticated; PR.AA-01: credentials managed |
| ISO/IEC 27001:2022 | Annex A 8.5 Secure authentication; 5.17 Authentication information |
| SOC 2 | CC6.1 logical access security |
Reviewed by
Written and reviewed by a practicing CISO
Ali Hassani, C|CISO, CISSP
Ali has more than 25 years of IT and cybersecurity experience and holds the Certified CISO and CISSP certifications along with Microsoft and Cisco credentials. He leads every OC Security Audit engagement from Irvine, on-site across Southern California and remotely nationwide. Every Microsoft 365 audit is read-only.
FAQ
Frequently asked questions about MFA registration
What does protecting MFA registration mean?
Requiring a Conditional Access check, such as MFA, a strong method or a trusted network, before anyone can add or change their sign-in methods.
How do new users register if MFA is required first?
Give them a Temporary Access Pass. Microsoft says it satisfies the MFA requirement for registration.
Does this apply to guests?
Microsoft notes Temporary Access Pass doesn't work for guests, so exclude guests from the TAP-based policy and handle them separately.
Does it cover Windows Hello for Business?
Since July 6, 2026, policies on Register security information also apply to Windows Hello for Business and macOS Platform SSO registration.
What should we do with methods already registered?
Review them, starting with admins, and confirm any unexpected method with the person directly.
Which plans include this?
Conditional Access needs Entra ID P1: Business Premium, E3 or E5.
Next step
Keep MFA in the right hands
Prevent
Microsoft 365 Security Audit
$3,500 fixed
About 200 read-only checks across sign-in protection, email, sharing and devices, for any tenant size, with four reports and a remediation roadmap.
Respond
Microsoft 365 & Azure Compromise Investigation
From $3,500
For when an unknown MFA method shows up on an account: we establish who added it and what they reached.
Want to see the deliverables first? Open the Microsoft 365 audit sample report or browse all our sample reports.

Service
Microsoft 365 Security Audit
The fixed-price audit that checks this item and about 200 more.
See the audit ›
Service
Microsoft Entra ID Security Audit
A deeper look at identities, Conditional Access, roles and apps.
See the Entra ID audit ›
Service
Compromise Investigation
When an account or mailbox may already be in an attacker’s hands.
See the investigation ›Related reading: How to replace SMS and voice MFA · How to block sign-ins from other countries · How to set up emergency access accounts
Sources
Sources used on this page
- Microsoft Learn, Protect security info registration with Conditional Access policy
- Microsoft Learn, Combined security information registration
- Microsoft Learn, Configure Temporary Access Pass
- Microsoft Learn, Configure Microsoft Entra for Zero Trust: protect identities and secrets
- Microsoft Learn, Conditional Access: Target resources, user actions
- CISA and FBI, Advisory AA23-320A Scattered Spider
- Microsoft Source, Microsoft releases 2025 Digital Defense Report
This guide is general information, not a guarantee of protection or legal advice. Microsoft changes its admin centers often: menu names and steps were checked against Microsoft Learn on November 20, 2026. Drawings are simplified and are not screenshots of Microsoft products. Sample findings come from fictional companies. Incidents are described as reported by the cited sources; OC Security Audit was not involved in them. Questions? Call 949-777-5567 or email support@ocsecurityaudit.com.



