Edit

Security defaults in Microsoft Entra ID

Security defaults make it easier to help protect your organization from identity-related attacks like password spray, replay, and phishing common in today's environments.

Microsoft is making these preconfigured security settings available to everyone, because we know managing security can be difficult. Based on our learnings more than 99.9% of those common identity-related attacks are stopped by using multifactor authentication and blocking legacy authentication. Our goal is to ensure that all organizations have at least a basic level of security enabled at no extra cost.

These basic controls include:

Who's it for?

  • Organizations who want to increase their security posture, but don't know how or where to start.
  • Organizations using the free tier of Microsoft Entra ID licensing.

Who should use Conditional Access?

  • If you're an organization with Microsoft Entra ID P1 or P2 licenses, security defaults are probably not right for you.
  • If your organization has complex security requirements, you should consider Conditional Access.

Enabling security defaults

If your tenant was created on or after October 22, 2019, security defaults might be enabled in your tenant. To protect all of our users, security defaults are being rolled out to all new tenants at creation.

While security defaults is enabled on all new tenants by default, there is a 24‑hour grace period before protections are enforced. This allows customers to access and provision their tenant before MFA is required.

To help protect organizations, we're always working to improve the security of Microsoft account services. As part of this protection, customers are periodically notified for the automatic enablement of the security defaults if they:

  • Don't have any Conditional Access policies
  • Don't have premium licenses
  • Aren’t actively using legacy authentication clients

After this setting is enabled, all users in the organization will need to register for multifactor authentication. To avoid confusion, refer to the email you received and alternatively you can disable security defaults after it's enabled.

To configure security defaults in your directory, you must be assigned at least the Conditional Access Administrator role.

By default, the user who creates a Microsoft Entra tenant is automatically assigned the Global Administrator role.

To enable security defaults:

  1. Sign in to the Microsoft Entra admin center as at least a Conditional Access Administrator.
  2. Browse to Entra ID > Overview > Properties.
  3. Select Manage security defaults.
  4. Set Security defaults to Enabled.
  5. Select Save.

Screenshot of the Microsoft Entra admin center with the toggle to enable security defaults

Revoking active tokens

As part of enabling security defaults, administrators should revoke all existing tokens to require all users to register for multifactor authentication. This revocation event forces previously authenticated users to authenticate and register for multifactor authentication. This task can be accomplished using the Revoke-MgUserSignInSession cmdlet in the Microsoft Graph PowerShell SDK.

Enforced security policies

Require all users to register for Microsoft Entra multifactor authentication

Note

Starting July 29, 2024, new tenants and existing tenants have the 14-day grace period for users to register for MFA removed. We made this change to help reduce the risk of account compromise during the 14-day window, as MFA can block over 99.2% of identity-based attacks.

When users sign in and are prompted to perform multifactor authentication, they see a screen providing them with a number to enter in the Microsoft Authenticator app. This measure helps prevent users from falling for MFA fatigue attacks.

Screenshot showing an example of the Approve sign in request window with a number to enter.

Require administrators to do multifactor authentication

Administrators have more access to your environment. Because of the power these highly privileged accounts have, treat them with special care. One common method to improve the protection of privileged accounts is to require a stronger form of account verification for sign-in, like requiring multifactor authentication.

Tip

Recommendations for your admins:

  • Ensure all your admins sign in after enabling security defaults so that they can register for authentication methods.
  • Have separate accounts for administration and standard productivity tasks to significantly reduce the number of times your admins are prompted for MFA.

After registration is finished, the following administrator roles will be required to do multifactor authentication every time they sign in:

  • Global Administrator
  • Application Administrator
  • Authentication Administrator
  • Billing Administrator
  • Cloud Application Administrator
  • Conditional Access Administrator
  • Exchange Administrator
  • Helpdesk Administrator
  • Password Administrator
  • Privileged Authentication Administrator
  • Privileged Role Administrator
  • Security Administrator
  • SharePoint Administrator
  • User Administrator
  • Authentication Policy Administrator
  • Identity Governance Administrator

Also available as a Microsoft-managed Conditional Access policy if you disable security defaults.

Require users to do multifactor authentication when necessary

We tend to think that administrator accounts are the only accounts that need extra layers of authentication. Administrators have broad access to sensitive information and can make changes to subscription-wide settings. But attackers frequently target end users.

After these attackers gain access, they can request access to privileged information for the original account holder. They can even download the entire directory to do a phishing attack on your whole organization.

One common method to improve protection for all users is to require a stronger form of account verification, such as multifactor authentication, for everyone. After users complete registration, they'll be prompted for another authentication whenever necessary. Microsoft decides when a user is prompted for multifactor authentication, based on factors such as location, device, role, and task. This functionality protects all registered applications, including SaaS applications.

Note

In case of B2B direct connect users, any multifactor authentication requirement from security defaults enabled in resource tenant needs to be satisfied, including multifactor authentication registration by the direct connect user in their home tenant.

Also available as a Microsoft-managed Conditional Access policy if you disable security defaults.

Block legacy authentication protocols

To give your users easy access to your cloud apps, we support various authentication protocols, including legacy authentication. Legacy authentication is a term that refers to an authentication request made by:

  • Clients that don't use modern authentication (for example, an Office 2010 client)
  • Any client that uses older mail protocols such as IMAP, SMTP, or POP3

Today, most compromising sign-in attempts come from legacy authentication. Legacy authentication doesn't support multifactor authentication. Even if you have a multifactor authentication policy enabled on your directory, an attacker can authenticate by using an older protocol and bypass multifactor authentication.

After security defaults are enabled in your tenant, all authentication requests made by an older protocol will be blocked. Security defaults blocks Exchange Active Sync basic authentication.

Warning

Before you enable security defaults, make sure your administrators aren't using older authentication protocols. For more information, see How to move away from legacy authentication.

Also available as a Microsoft-managed Conditional Access policy if you disable security defaults.

Block device code flow

Device code flow is an authentication flow that lets users sign in to devices or applications that have limited input capabilities, such as devices without a browser or keyboard. Attackers can abuse device code flow in phishing attacks by tricking users into entering a code on another device.

After security defaults are enabled in your tenant, authentication requests that use device code flow are blocked. Applications or devices that depend on device code flow won't be able to complete sign-in while security defaults are enabled. If your organization needs granular control and exceptions, you should consider Conditional Access.

Note

Starting July 1, 2026, all new Microsoft Entra tenants block device code flow as part of security defaults. Applications or devices that depend on device code flow won't be able to complete sign-in while security defaults are enabled.

Protect privileged activities like access to the Azure portal

Organizations use various Azure services managed through the Azure Resource Manager API, including:

  • Azure portal
  • Microsoft Entra admin center
  • Azure PowerShell
  • Azure CLI

Using Azure Resource Manager to manage your services is a highly privileged action. Azure Resource Manager can alter tenant-wide configurations, such as service settings and subscription billing. Single-factor authentication is vulnerable to various attacks like phishing and password spray.

It's important to verify the identity of users who want to access Azure Resource Manager and update configurations. You verify their identity by requiring more authentication before you allow access.

After you enable security defaults in your tenant, any user accessing the following services must complete multifactor authentication:

  • Azure portal
  • Microsoft Entra admin center
  • Azure PowerShell
  • Azure CLI

This policy applies to all users who are accessing Azure Resource Manager services, whether they're an administrator or a user. This policy applies to Azure Resource Manager APIs such as accessing your subscription, VMs, storage accounts, and so on. This policy doesn't include Microsoft Entra ID or Microsoft Graph.

Note

Exchange Online tenants created before 2017 have modern authentication disabled by default. In order to avoid the possibility of a login loop while authenticating through these tenants, you must enable modern authentication.

Note

The Microsoft Entra Connect / Microsoft Entra Cloud Sync synchronization accounts (or any security principal assigned to the "Directory Synchronization Accounts" role) are excluded from security defaults and aren't prompted to register for or perform multifactor authentication. Organizations shouldn't be using this account for other purposes.

Also available as a Microsoft-managed Conditional Access policy if you disable security defaults.

Deployment considerations

Preparing your users

It's critical to inform users about upcoming changes, registration requirements, and any necessary user actions. We provide communication templates and user documentation to prepare your users for the new experience and help to ensure a successful rollout. Send users to https://myprofile.microsoft.com to register by selecting the Security Info link on that page.

Authentication methods

Security defaults users are required to register for and use multifactor authentication using the Microsoft Authenticator app using notifications. Users might use verification codes from the Microsoft Authenticator app but can only register using the notification option. Users can also use any non-Microsoft application using OATH TOTP to generate codes.

Warning

Don't disable methods for your organization if you're using security defaults. Disabling methods might lead to locking yourself out of your tenant. Leave all Methods available to users enabled in the MFA service settings portal.

B2B users

Any B2B guest users or B2B direct connect users that access your directory are treated the same as your organization's users.

Disabled MFA status

If your organization is a previous user of per-user based multifactor authentication, don't be alarmed to not see users in an Enabled or Enforced status if you look at the multifactor authentication status page. Disabled is the appropriate status for users who are using security defaults or Conditional Access based multifactor authentication.

Disabling security defaults

Organizations that choose to implement Conditional Access policies that replace security defaults must disable security defaults.

Disable security defaults in your directory:

  1. Sign in to the Microsoft Entra admin center as at least a Conditional Access Administrator.
  2. Browse to Entra ID > Overview > Properties.
  3. Select Manage security defaults.
  4. Set Security defaults to Disabled (not recommended).
  5. Select Save.

Move from security defaults to Conditional Access

While security defaults are a good baseline to start your security posture from, they don't allow for the customization that many organizations require. Conditional Access policies provide a full range of customization that more complex organizations require.

Security defaults Conditional Access
Required licenses None At least Microsoft Entra ID P1
Customization No customization (on or off) Fully customizable
Enabled by Microsoft or administrator Microsoft or administrator
Complexity Simple to use Fully customizable based on your requirements

Organizations who would like to test out the features of Conditional Access can sign up for a free trial to get started.

After administrators disable security defaults, organizations should immediately enable Conditional Access policies to protect their organization. Microsoft-managed Conditional Access policies are available to maintain the same protections, covering blocking legacy authentication, requiring MFA for Azure management, requiring MFA for admins, and requiring MFA for all users. Organizations should review these policies and consider enabling more policies from the secure foundations category of Conditional Access templates. Organizations with Microsoft Entra ID P2 licenses that include Microsoft Entra ID Protection can expand on this list to include user and sign in risk-based policies to further strengthen their posture.

Microsoft recommends that organizations have two cloud-only emergency access accounts permanently assigned the Global Administrator role. These accounts are highly privileged and aren't assigned to specific individuals. The accounts are limited to emergency or "break glass" scenarios where normal accounts can't be used or all other administrators are accidentally locked out. These accounts should be created following the emergency access account recommendations.

Manage individual Security Defaults protections (preview)

Organizations need to protect their accounts from common identity attacks, even when they don't have the resources to build and maintain custom security policies. Security Defaults provides a Microsoft-managed security baseline that helps protect accounts with multifactor authentication (MFA) and blocks vulnerable or commonly abused sign-in methods.

The original Security Defaults experience uses one on/off setting for all protections. The updated experience introduces individual rules, so administrators can see what each protection does, whom it covers, and whether it's enabled. You can change one protection without turning off the others.

This article explains how to manage these protections in Microsoft Entra ID Free. Security Defaults is available at no extra cost; no P1 or P2 license is required for the baseline protections.

Important

The updated experience is in private preview for selected Microsoft Entra ID Free tenants. Available protections can vary during the preview.

Why use Security Defaults?

  • Start with a Microsoft-managed baseline. Use preconfigured protections without creating and maintaining your own policies.
  • Understand your settings. Review the purpose, scope, and state of each protection.
  • Manage protections individually. Change a specific protection while leaving the other rules in place.

Relationship to Conditional Access

The updated Security Defaults baseline can work alongside customer-created Conditional Access policies. Unlike the original experience, it doesn't require you to disable Security Defaults to use Conditional Access.

Security Defaults provides the common baseline across free and premium tenants. In the updated model, the management location is:

  • Microsoft Entra ID Free: Manage individual protections on the Security Defaults page, using the steps in this article.
  • Microsoft Entra ID P1 or P2: Manage the same baseline as a Microsoft-managed Security Defaults policy plan in Conditional Access.

Organizations can use custom Conditional Access policies for additional requirements, such as device compliance or location-based controls. Creating those policies requires the appropriate premium license.

At sign-in, every applicable Security Defaults rule and Conditional Access policy must be satisfied. The baseline and custom policies work together; one doesn't replace the other.

Security Defaults protections

The updated experience brings together four Microsoft-managed rules. Each rule defines the sign-ins it covers and the protection it applies. Microsoft manages the rule definitions, while administrators control whether each rule is enabled.

Require MFA for administrators

Administrator accounts can change settings, manage users, and access sensitive resources. Requiring MFA helps protect those accounts if a password is stolen.

This rule requires MFA for administrator sign-ins that match its scope. Open the rule to see the administrator roles and resources it covers.

Require MFA for all users

Ordinary user accounts also need protection. An attacker who gains access to a user account can read information or use that account to target other people in the organization.

This rule requires MFA for all users within its scope, including administrators. It broadens the original Security Defaults behavior from requiring MFA when necessary to requiring MFA for the sign-ins covered by the rule.

Users who haven't registered an authentication method might be asked to do so during sign-in. A valid existing MFA sign-in can satisfy the requirement, so users won't necessarily receive a new MFA prompt every time.

Block legacy authentication

Legacy authentication refers to older sign-in methods that don't support MFA, such as basic authentication used by older mail clients and applications.

When enabled, this rule blocks sign-ins that use legacy authentication. Applications and devices that depend on those methods need to use modern authentication to continue signing in.

Block device code flow

Device code flow lets an application or device ask the user to complete sign-in in a separate browser. It's useful for devices with limited input capabilities, but attackers can abuse it by tricking users into entering a code that gives the attacker access.

When enabled, this rule blocks sign-ins that use device code flow. Applications and devices that rely on this flow need an alternative sign-in method.

Required roles

To view and change Security Defaults protections, use one of the following Microsoft Entra roles:

  • Conditional Access Administrator
  • Security Administrator
  • Global Administrator

Global Reader and Security Reader can view the protections but can't change them.

Use the least-privileged role needed for the task. Conditional Access Administrator is recommended for managing these settings.

Manage a protection

  1. Sign in to the Microsoft Entra admin center with one of the roles that can change protections.
  2. Switch to the free tenant enabled for your private preview.
  3. Open the access link provided in your preview invitation.
  4. On the Security Defaults page, select the name of a protection.
  5. Review its description, current state, and the users, roles, or resources it covers.
  6. Turn the protection on or off and follow the confirmation prompt. If you're turning it off, provide the requested feedback.
  7. Confirm that the updated state is shown on the page.

The change applies to the tenant, not just the administrator making it. Each rule is managed independently. For example, turning off the administrator MFA rule can still leave administrators covered by the all-users MFA rule.

Microsoft recommends keeping protections enabled. Turning off a protection reduces security for the sign-ins it covers.

Prepare your organization

Before enabling or changing protections:

  • Prepare users for MFA. Make sure administrators and users can complete registration and authentication. Users can review their registered methods through My Account.
  • Review application compatibility. Identify applications or devices that rely on legacy authentication or device code flow and plan an alternative sign-in method.
  • Inform your support team. Explain the MFA change and how to help users who have trouble registering or signing in.

Moving to the updated experience

Microsoft introduces the updated controls through a phased rollout. When your tenant receives the update, you manage the Microsoft-provided rules individually instead of using the original single setting. You don't need to recreate the rules.

Rollout communications explain changes to your tenant's protections, including any planned device code flow enablement. Review each rule's state when the update arrives and prepare users for the broader all-users MFA requirement.

Next steps