Microsoft Entra Security Defaults provide a practical baseline for small organizations that need to require multifactor authentication (MFA) and block legacy authentication without designing a full Conditional Access policy set. This guide explains how to check the current state, enable the baseline safely, prepare users, verify the result, and decide when Conditional Access is the better option.
The steps and product behavior below were verified against Microsoft documentation current at publication time. They were not executed in a live customer tenant for this article, so portal labels may vary slightly by tenant or licensing state.
What Security Defaults do
Security Defaults are a Microsoft-managed identity baseline available at no extra charge. When enabled, they provide several protections:
- Users are required to register for multifactor authentication.
- Administrators are required to use multifactor authentication.
- Users are prompted for multifactor authentication when Microsoft determines it is necessary.
- Legacy authentication protocols are blocked because they do not support modern MFA controls.
- Device code flow is blocked.
- Privileged activities, such as access to the Azure portal, receive additional protection.
Security Defaults are intentionally simple. They are a good starting point for organizations using Microsoft Entra ID Free, but they do not provide the user, application, location, device, or risk-based targeting available in Conditional Access. See Microsoft’s Security Defaults documentation for the current control set.
When to use Security Defaults instead of Conditional Access
Use Security Defaults when your organization needs a strong baseline and does not need granular exceptions or conditions. This is often appropriate for a small business with Microsoft 365 Business Basic or Standard, or another subscription that does not include Microsoft Entra ID P1.
Use Conditional Access when you need policies such as requiring phishing-resistant authentication for administrators, applying different rules to contractors, requiring compliant devices, controlling access by location or application, or using sign-in and user-risk signals. Microsoft Entra ID P1 is included with Microsoft 365 Business Premium and Microsoft 365 E3; Microsoft Entra ID P2 is included with Microsoft 365 E5. Licensing can change, so confirm the tenant’s current entitlements before designing the policy set.
Security Defaults and Conditional Access are alternatives. Do not disable Security Defaults merely to experiment with Conditional Access. If you switch, recreate the baseline protections first and test them in Report-only mode where possible.
Before you enable the setting
Complete these checks before changing the tenant:
- Confirm administrative access. Use the Microsoft Entra admin center and an account with at least the Conditional Access Administrator role. Microsoft documentation also identifies Security Administrator or higher for the mandatory MFA verification workflow.
- Inventory administrators. List every Global Administrator and other privileged administrator. They will be prompted for MFA and should not share one administrator account.
- Plan user communication. Tell users why registration is required, when they will be prompted, and where to get help. Link them to Guava’s Microsoft Authenticator setup guide.
- Check older clients and devices. Printers, scanners, scripts, mail clients, and line-of-business applications that use basic authentication may stop working when legacy authentication is blocked. Identify replacements before enabling the setting.
- Prepare emergency access. Maintain at least two cloud-only emergency access accounts with strong authentication, protected credentials, monitoring, and a documented test process. These accounts are for genuine lockout or outage scenarios, not normal administration.
- Record the current state. Capture the current Security Defaults state, Conditional Access policies, per-user MFA state, and any documented authentication exceptions. This gives you a recovery reference.
1. Check whether Security Defaults is already enabled
- Sign in to the Microsoft Entra admin center with an appropriately privileged account.
- Open Entra ID.
- Select Overview, then open the Properties tab.
- Scroll to Security defaults.
- Select Manage security defaults.
Review the current value rather than assuming the setting is enabled. Newer tenants can have Security Defaults enabled by default, and Microsoft may automatically enable them in some tenants that have no Conditional Access policies, no premium licenses, and no active legacy-authentication clients. A new tenant can also have a grace period before protections are enforced.
2. Enable Security Defaults
- In the Security defaults pane, set Security defaults to Enabled.
- Review the warning and confirm that your users can register an MFA method.
- Select Save.
- Record the change in your change log, including the administrator, date, tenant, and previous value.
Do not enable the setting immediately before a major business event. Users may be prompted to register for MFA, and older clients that depend on legacy authentication may fail. A controlled change window gives the help desk time to respond.
3. Prepare administrators and users for registration
After Security Defaults is enabled, users are required to register for MFA. Administrators receive stronger protection because privileged accounts have access to tenant-wide settings and data.
- Ask administrators to sign in and complete MFA registration before the wider user population.
- Have administrators use separate accounts for administration and normal email or web activity.
- Ask users to register an approved authentication method when prompted.
- Tell users never to approve an unexpected Authenticator request. An unsolicited prompt can indicate that an attacker knows the password and is attempting an MFA-fatigue attack.
- Confirm that users can complete a normal Microsoft 365 sign-in after registration.
Security Defaults does not let you define a custom MFA schedule or choose a different rule for each department. If the organization requires that level of control, plan a Conditional Access deployment rather than trying to work around the baseline.
4. Verify that the baseline is working
Verification should use a test user and a separate browser session. Do not rely on a cached administrator session as proof that the tenant is protected.
- Open a private browser window and sign in to a Microsoft 365 application with a test user.
- Confirm that the user is prompted to register for MFA or is challenged for an already registered method.
- Sign in to the Microsoft Entra admin center with a test administrator and confirm that MFA is required.
- Review Entra ID > Monitoring & health > Sign-in logs.
- Inspect the Client App information and look for legacy authentication attempts. A failed legacy-authentication attempt is expected after the block, but it may identify a device or application that needs remediation.
- Test the applications that send mail, retrieve mail, scan documents, submit alerts, or call Microsoft APIs.
- Confirm that the test user outside any intended exception path is protected. Security Defaults does not support arbitrary user exclusions.
Keep the sign-in-log review separate from the user experience test. A successful browser sign-in confirms modern authentication, but it does not prove that every older device or service has migrated.
5. Remediate legacy-authentication failures
Legacy authentication includes older client and protocol patterns that send a username and password without the modern authentication controls required for MFA. Common examples can include old mail clients, Exchange ActiveSync configurations, POP or IMAP clients, SMTP AUTH workflows, scanners, and custom scripts. The exact impact depends on the application and its configuration.
For each failed sign-in:
- Open the sign-in event and record the user, application, client app, timestamp, and source device or address.
- Update the client to a modern-authentication version where supported.
- Replace service passwords with OAuth, a managed identity, a certificate, or another supported workload-authentication method where the application allows it.
- For printers and scanners, use a supported authenticated relay design instead of re-enabling basic authentication across the tenant.
- Retest the workload and document the owner and replacement date.
Do not disable Security Defaults to preserve an undocumented legacy workflow. That trades a known operational problem for a broad identity-security gap.
Emergency access and lockout safeguards
Security Defaults is designed to protect the tenant, but a tenant can still be made difficult to administer if every administrator depends on one phone, one identity provider, or one network path. Microsoft recommends at least two emergency access accounts. They should be cloud-only, have credentials stored securely, use strong authentication that is independent of normal administrator methods where practical, and be monitored for every sign-in.
Document who can use these accounts, where the credentials are stored, and what qualifies as an emergency. Validate the accounts at least every 90 days and after major identity or licensing changes. Never use an emergency account for routine work. If the accounts are later targeted by Conditional Access, carefully exclude them from policies that could block emergency access while retaining monitoring and strong authentication.
Troubleshooting
The Manage security defaults option is unavailable
You may lack the required role, or Conditional Access may already be present. Check your directory role and review Entra ID > Conditional Access > Policies. Microsoft states that Security Defaults cannot be enabled while Conditional Access policies exist, including policies in Report-only or Off state.
Users say MFA registration is unexpected
Check the Security Defaults state and the date it was enabled. Explain the change through a trusted channel and provide the registration instructions. Never ask users to send verification codes or approve prompts on someone else’s behalf.
An old application stopped sending or receiving mail
Use sign-in logs to identify the client app and protocol. Migrate the application to modern authentication or a supported relay design. Do not restore broad legacy authentication unless you have a documented, time-limited exception and an approved migration plan.
We need different MFA rules for different groups
Security Defaults is not the right control for that requirement. Obtain the appropriate Microsoft Entra ID P1 or P2 licensing, design Conditional Access policies, create emergency access exclusions, and use Report-only mode to assess impact before enforcement.
Security Defaults checklist
- Verify the current state instead of assuming Security Defaults is off.
- Confirm that administrators and users can register approved MFA methods.
- Inventory legacy-authentication dependencies before the change.
- Enable the setting during a controlled change window.
- Test normal sign-in, administrative sign-in, and critical workloads.
- Review sign-in logs for blocked legacy clients.
- Maintain and test at least two emergency access accounts.
- Move to Conditional Access when the organization needs granular rules.
Frequently asked questions
Does Security Defaults require a separate Microsoft Entra license?
No. Microsoft documents Security Defaults as a baseline available for organizations using Microsoft Entra ID Free. Conditional Access requires Microsoft Entra ID P1 or later, either as a standalone license or through a qualifying Microsoft 365 plan.
Can Security Defaults and Conditional Access run at the same time?
No. They are alternative policy models. If you move to Conditional Access, recreate the baseline protections and test the new policies before turning Security Defaults off.
Does enabling Security Defaults force every user to use Microsoft Authenticator?
It requires MFA registration, but the exact available authentication methods depend on the tenant’s authentication-method configuration and Microsoft’s current supported options. Do not promise one specific method unless you have checked the tenant policy.
Will Security Defaults block old mail clients?
It can block clients and protocols that rely on legacy authentication. Review sign-in logs and migrate affected applications before enabling the setting.
Can I exclude one user from Security Defaults?
Security Defaults does not provide the granular user and group exclusions available in Conditional Access. If the organization needs exceptions or differentiated controls, use Conditional Access with carefully designed emergency-access exclusions.
References
- Microsoft Learn: Security defaults in Microsoft Entra ID
- Microsoft Learn: Set up multifactor authentication for Microsoft 365
- Microsoft Learn: Verify mandatory multifactor authentication setup
- Microsoft Learn: Manage emergency access accounts in Microsoft Entra ID
- Microsoft Learn: Block legacy authentication
- Microsoft: Microsoft Entra pricing and licensing overview


