That last point matters. Some of the announcement is GA and some is still preview, and admins will need to keep track of which is which.
What reached general availability
Microsoft announced at Ignite 2026 that BSM 2026 is "next major milestone in the BSM journey in helping organizations operationalize secure by default protections across their Microsoft environments." In its Microsoft 365 Blog post, the company says rollout is phased across all supported Microsoft 365 cloud environments worldwide. It did not give a completion date or a schedule by region or cloud.
The first version had a long rollout. BSM 2025 was announced at Ignite 2025, and Microsoft's Message Center post MC1193689 listed staggered schedules for each cloud. Worldwide GA rollout began in mid-November 2025 and was scheduled to finish by late January 2026. Government clouds came later: GCC in January 2026, DoD in February 2026, and GCCH in March 2026. Microsoft hasn't said whether BSM 2026 will follow the same pattern. Still, based on the last release, admins in sovereign or government clouds shouldn't expect the new settings right away.
Coverage by version:
| Release | Workloads | Status |
|---|---|---|
| BSM 2025 | Office, SharePoint, Teams, Exchange, Entra | GA |
| BSM 2026 additions | Intune, Purview, Dynamics 365 | GA (phased rollout) |
| BSM 2026 additions | Azure (Storage, Key Vault) | Private preview |
| BSM 2026 additions | Windows (VBS, Secure Boot, security processor) | Private preview |
BSM 2026 organizes its settings into four categories: Applications (new), Authentication, Devices & Endpoints and Files.
Where to find it
Microsoft's announcement says that as Global Administrator, you can navigate to: Microsoft 365 admin center → Org Settings → Security & Privacy → Baseline security mode to get started with BSM. Microsoft Learn gives the full path:
- Sign in to the Microsoft 365 admin center.
- Select Show all, then Settings.
- Choose Org Settings.
- Open Security and Privacy.
- Select Baseline Security Mode.
Not every change needs a Global Admin. According to Microsoft Learn, workload-specific administrators can manage only the settings for their own workload. For example, a Security Administrator handles Entra-related controls. Learn also says BSM settings can be configured on all Microsoft 365 subscriptions and plans.
If the page doesn't show the new 2026 settings yet, your tenant probably hasn't received the rollout.
The new Applications category
Application permissions are a common way attackers get into tenants, and the new category deals with them. It covers what apps can do, how they access data and which permissions they hold. Microsoft says 16 Applications settings are now generally available. The ones it highlights:
- Tenant assignment for new apps (Entra): Admins control which tenants a new app can be instantiated in. This limits multi-tenant apps.
- COM add-in allow list (Office): Native COM add-ins are blocked unless they're on an admin-approved list.
- Lobby for external users (Teams): External participants wait in the meeting lobby until someone admits them.
- No eDiscovery roles for guests (Purview): Microsoft describes eDiscovery roles as highly privileged because they can search and export large amounts of Microsoft 365 content. Microsoft Learn adds an important detail: the control stops new guest accounts from getting these roles, and existing guest assignments stay in place. You'll still need to review and remove any guest eDiscovery assignments you already have.
- Classic SharePoint pages: Users can no longer create or edit classic publishing, wiki and web part pages. Existing published pages stay viewable and aren't deleted.
- Exchange App RBAC reporting: BSM flags apps that access Exchange without Exchange App RBAC permissions, so you can find apps with overly broad mailbox access.
- Scoped access for high-privileged apps (SharePoint/OneDrive): Apps with broad permissions must use a limited scope instead of organization-wide access to files and sites.
The announcement also lists stronger Office macro security among the new recommendations. Learn describes this setting as wider runtime scanning of VBA macros, stricter signing requirements and tighter trusted-publisher rules.
Authentication: MFA for guests
Four Authentication settings are now generally available:
- Block Microsoft 365 trial tenants from federating with your organization (Teams)
- Block external apps from using pre-authenticated tokens to access OneDrive and SharePoint content
- Enable Continuous Access Evaluation for Dynamics 365
- Require MFA for guests and external users (Entra)
BSM 2025 required MFA for admin accounts, and the guest MFA requirement extends that to external users. Microsoft says it reduces risk from external access across Exchange, SharePoint, OneDrive, Teams and the Microsoft 365 apps.
Microsoft Learn explains why the trial-tenant block matters. Attackers can create trial tenants quickly and anonymously, then use them for impersonation and social engineering. Blocking federation with those tenants also removes trial-tenant users from existing chats. That second effect is easy to miss: users may suddenly lose external contacts from chats they're already in.
Devices & Endpoints: two admins for sensitive Intune actions
Intune brings four settings:
- Alert users when a new device is enrolled
- Require a device compliance policy
- Restrict how many devices a user can enroll
- Require a second administrator to approve sensitive actions
Microsoft sums up the last one as "two admins, one critical action." Microsoft Learn lists the kinds of operations it protects, including wiping devices, changing RBAC roles, deploying scripts and changing app configurations. A single compromised admin account can do a lot of damage with those powers.
Check the compliance-policy setting before you enable it. Learn says that without this requirement, devices that have no compliance policy are treated as compliant by default. Turning it on marks those devices as noncompliant and blocks them until a valid policy is applied. If any devices in your tenant have no compliance policy assigned, users on those devices could lose access when you flip the switch.
Azure and Windows: preview only
Azure (private preview): Seven settings across Azure Storage and Key Vault:
- Storage: require secure transfer, block anonymous public access, enforce a minimum TLS version, and prevent Shared Key authorization.
- Key Vault: restrict public network access, and require purge protection and soft delete.
Microsoft says these controls are built on Azure Policy. Admins can review security posture and workload impact before enrolling scopes for enforcement.
Windows (private preview): Microsoft Baseline security mode expands to include three Windows settings, enable virtualization-based security (VBS), enable secure boot, and enable the security processor. VBS isolates security-sensitive operations from the main OS. Secure Boot helps stop malicious software from loading at startup. The security processor uses dedicated hardware to protect credentials and keys.
These are long-standing Windows hardening controls, so this isn't new technology. What's new is that Microsoft now treats them as part of its official baseline and shows their status next to the rest of your tenant's posture. Older devices without the required firmware or hardware support will stand out in that view, which could make hardware-refresh conversations easier to have.
The Windows controls in BSM are separate from Microsoft's other Windows baseline protection announcement. Keep the two apart in your planning.
Preview admin tools and a compliance caveat
Four admin features are also in private preview:
- an action-oriented posture dashboard
- downloadable security and compliance reports
- mapping of BSM settings to regulatory frameworks
- geographic context for Multi-Geo tenants
According to Microsoft, preview features are available to a limited set of customers and may change before general availability.
The framework mapping comes with a caveat. Microsoft explicitly says BSM does not guarantee compliance with any law or regulatory framework, and customers remain responsible for their own obligations. The mapping can help in conversations with auditors, but it doesn't certify anything.
How to roll it out
All 24 new settings can be managed individually, and each one can be applied directly or run in simulation mode first. Microsoft Learn recommends this approach:
- Run the impact report for a setting before turning it on.
- Enable it if the report shows zero impact.
- If critical dependencies show up, leave it off and fix the dependencies before making the change permanent.
- Test by temporarily disabling a setting for a few days if you need to confirm a dependency.
That process existed for BSM 2025 and hasn't changed. When BSM 2025 shipped, Cybersecurity News reported that admins could select "Automatically apply default policies" for seven low-impact controls or "Generate report" for simulation on the rest, reviewing audit-based impact data within 24 hours.
The 2026 settings that will likely need the most testing:
- COM add-in blocking: Line-of-business Office add-ins are common in finance and engineering teams. Build your allow list before you enforce.
- Macro hardening: Expect legacy VBA workbooks to break.
- Classic SharePoint page blocking: Intranets that still rely on wiki or publishing pages will become read-only.
- Guest MFA: Partners and contractors will get MFA prompts. Warn them first.
One more thing from Microsoft Learn: tenants that opened the BSM page between November 2025 and early February 2026 may have two disabled draft Entra Conditional Access policies that appear to have been created by whichever admin signed in. Microsoft says these drafts don't affect security, that it will remove them after notifying customers, and that a fix is in progress. If you find them during a Conditional Access audit, that's where they came from.
What's next
Microsoft says BSM 2025 will become the default configuration for all new Microsoft 365 tenants. It gave no date, so treat this as a roadmap item for now. Microsoft is also urging existing Microsoft 365 and Entra customers to opt in to every BSM 2025 setting.
Separately, Microsoft announced On-Premises Baseline Security Mode, starting with supported Exchange Server, SharePoint Server and Skype for Business Server workloads. It's meant to provide a tested, secure-by-default configuration from the initial deployment while leaving admins in control. It's a related effort, not part of the Microsoft 365 BSM release.
Bottom line
BSM 2026 is a useful step forward. The Applications category addresses risky app permissions, which current attacks often exploit, and the Intune and Purview controls fix weaknesses that many tenants already have. The extended rollout window is the main caveat, along with the fact that Azure, Windows and the reporting tools are still in preview.
Where to start:
- Look for the BSM 2026 settings in your admin center. If they aren't there yet, your tenant is still waiting on the rollout.
- If you haven't finished opting in to BSM 2025, do that first. It's the baseline Microsoft plans to make the default for new tenants.
- Run simulations on the new settings, starting with the ones least likely to break things, such as the Exchange RBAC report and enrollment alerts.
- Before enforcing the related settings, check guest eDiscovery assignments, COM add-in inventories and devices without a compliance policy.
References
- Ignite’26 Spotlight: Announcing Microsoft Baseline security mode 2026 General Availability Microsoft 365 Blog · 2026-11-17T17:00:00+00:00
- Ignite’26 Spotlight: Announcing Microsoft Baseline security mode 2026 General Availability | Microsoft Community Hub techcommunity.microsoft.com
- Baseline security mode settings | Microsoft Learn learn.microsoft.com