Microsoft 365 Baseline Security Mode: What to Check First

Microsoft 365 baseline security mode is a set of Microsoft-recommended security settings in the Microsoft 365 admin centre, covering sign-in, Office apps, files, Teams, SharePoint, Exchange and devices. Each setting can be reviewed for impact and turned on separately.

 

Microsoft announced the 2026 release of baseline security mode on 17 November 2026. It adds settings that block unapproved Office add-ins, hold external Teams guests in the lobby and require multi-factor authentication for guest users.

Many of those settings are sensible. Some will also stop something your business relies on, such as an Excel add-in from your practice software or a client who joins Teams meetings from another organisation.

This guide explains what Microsoft 365 baseline security mode is, what the 2026 release changes, how it differs from security defaults and what to check with your IT provider before any setting is switched on. It was checked against Microsoft’s documentation on 18 November 2026.

What is Microsoft 365 baseline security mode?

Microsoft 365 baseline security mode is a page in the Microsoft 365 admin centre that lists Microsoft’s recommended security settings and lets an administrator check, test and apply each one, and it first appeared at Microsoft Ignite in November 2025.

The settings are grouped into categories: authentication, applications, files and devices. They include blocking legacy sign-in protocols, hardening Office macro security, opening old file formats in Protected View and blocking classic SharePoint pages.

Microsoft’s baseline security mode settings documentation says the settings can be configured on all Microsoft 365 subscriptions and plans. The page is under Settings, Org settings, Security and privacy in the admin centre. A Global Administrator sees every setting, while workload administrators such as the SharePoint or Teams administrator see the settings for their own service.

Being able to configure a setting does not license the service behind it. Check the workload, feature and licence requirements before planning a change, particularly where Intune, Purview or Entra features are involved. Plan, licence and add-on choices are covered on our Microsoft 365 business plans page.

Microsoft describes baseline security mode as an evolving standard rather than a one-time feature. It also states that turning the mode on does not by itself make a business compliant with any law or regulatory framework.

Baseline security mode vs security defaults: one sign-in switch compared with separate settings across Microsoft 365

What changed in baseline security mode 2026, and what is available to us?

The 2026 release adds settings for Intune, Purview and Dynamics 365 to the original Office, SharePoint, Teams, Exchange and Entra coverage, and introduces an applications category. Microsoft’s general availability announcement says it adds 24 settings in total.

Area Status on 18 November 2026 Examples
Applications Generally available Block unlisted COM add-ins, lobby for external Teams users
Authentication Generally available MFA for guests and external users
Intune devices Generally available Device compliance policy, second admin approval
Azure Private preview Storage and Key Vault settings
Windows Private preview Secure Boot and related device settings
Dashboard and reports Private preview Downloadable reports, framework mapping

General availability is rolling out in phases across Microsoft’s cloud environments, and Microsoft has not published dates for individual tenants. If a setting described in the announcement is not in your admin centre yet, the rollout may not have reached your tenant.

Preview features may change before they are generally available, so plan around what your own tenant shows rather than the announcement.

For a small business, the new applications and authentication settings matter more than the Azure or Windows previews, because they change how Office, Teams and guests behave day to day.

Microsoft also says the 2025 baseline will become the default configuration for new Microsoft 365 tenants. It has not said that existing tenants will have settings turned on automatically, and it encourages existing customers to opt in.

How does baseline security mode differ from Entra security defaults?

Security defaults are a single on-or-off switch for basic sign-in protection. Baseline security mode is a list of separate settings across Microsoft 365 that also covers how apps, files, meetings and devices behave.

Microsoft’s security defaults documentation lists what the switch enforces: MFA registration for every user, MFA for administrators, MFA for users when needed, blocking legacy authentication, blocking device code flow and extra protection for privileged activities. Security defaults cost nothing extra and cannot be customised, with directory synchronisation accounts the only documented exclusion.

Microsoft says security defaults might already be enabled in tenants created on or after 22 October 2019. Check the current tenant setting and any Conditional Access policies rather than inferring protection from the age of the account. A business that switched them off to introduce Conditional Access should check that its policies still cover MFA for every user and the block on legacy authentication.

Security defaults also cannot run alongside Conditional Access policies. Businesses on Microsoft 365 Business Premium, which includes Microsoft Entra ID P1, can turn security defaults off and use Conditional Access instead.

Baseline security mode does not replace either approach. Several of its authentication settings, such as blocking legacy authentication flows, overlap with rules you may already enforce, so ask your provider how each one relates to your current policies before turning it on.

Our guide to identity and access management for NZ businesses covers how sign-in policies, MFA and access reviews fit together. Microsoft 365 baseline security mode is one input to that work, not the whole of it.

Which business applications and workflows should we check?

Check every workflow that depends on an older protocol, an Office add-in, a macro, an external connection or a guest. Those are the areas where Microsoft 365 baseline security mode settings are the likeliest to stop something working.

  • Office add-ins. Practice management, tax, document management and e-signature tools that install COM add-ins in Outlook, Word or Excel.
  • Macros and old spreadsheets. Workbooks that use VBA macros, Excel 4.0 macros, DDE links or Microsoft Query files.
  • Older file formats. Legacy Word and Excel files that would open in Protected View, and any Microsoft Publisher files still in use.
  • Exchange connections. Apps that read mailboxes or calendars through Exchange Web Services, including Excel or Power BI reports that pull mail data.
  • External meetings. Clients, auditors or suppliers who join Teams meetings and would now wait in the lobby.
  • Guests. External users in Teams or SharePoint who would be asked to complete MFA.
  • Third-party apps. Apps that hold broad permissions to SharePoint and OneDrive files, or apps users have consented to themselves.

Microsoft’s settings documentation gives a concrete example. Turning off Exchange Web Services can break the Exchange connector in Excel and Power BI, cross-tenant calendar free and busy sharing, and some older device authentication. It also lists the minimum Office versions that must be installed across the business before Exchange Web Services is turned off.

In professional firms, Office add-ins come mainly from practice management, document management and CRM software. Ask each supplier whether its add-in is a COM add-in, and whether a newer web-based version is available that would not depend on the COM allow list.

Ask staff as well as suppliers. The person who runs month-end reporting or sends engagement letters knows which spreadsheet, template or add-in they open each week, and that detail may not appear in any IT asset list. A short conversation with each team lead can surface dependencies that a technical report will not show, such as a shared workbook that pulls figures from a mailbox.

Which baseline security mode settings should a small business review first?

Start with the settings that protect administrator accounts and remove older features your business has confirmed it does not need, then move to the ones that change daily work, so the early protection comes with the least disruption.

  • Admin sign-in. Phishing-resistant authentication for admin portals, and MFA for administrators signing in to Intune and Power Platform.
  • Legacy sign-in. Blocking legacy and basic authentication, which older devices, scanners and line-of-business apps can still depend on.
  • Dormant features. Blocking ActiveX controls, Excel 4.0 macros, DDE server lookups and Microsoft Publisher, once you know nobody uses them.
  • Teams federation. Blocking chats started by Teams free accounts and federation with Microsoft 365 trial tenants.
  • SharePoint scripts. Stopping new custom scripts on SharePoint sites, after checking that no site relies on them.

Each of these still needs an impact report. A multifunction printer that scans to email using basic authentication is the kind of dependency that holds a legacy authentication block back until the device is reconfigured or replaced.

Settings that change daily work come next: the COM add-in allow list, the Teams lobby for external users and MFA for guests. Bring the workflow owners into those decisions before anything is enabled, because they know which clients, suppliers and reports depend on the current behaviour.

How should we assess impact before enabling settings?

Assess each Microsoft 365 baseline security mode setting on its own, using Microsoft’s impact report and a check with the people who use the affected workflow. Microsoft’s guidance is to run the impact report for each setting, turn it on if it shows no impact, and hold it back where critical dependencies exist.

The 2026 announcement adds that administrators can run settings in simulation mode to see the potential impact in their own tenant. Reporting detail varies by setting, so check what activity each report or simulation covers before relying on it.

An impact report covers the period it looked at. A quarterly workflow, an end-of-year process or a supplier who connects once a month may not appear, so ask the business owner of each workflow as well as reading the report.

Do not assume every setting can be piloted with a small group. Microsoft documents each setting as managed independently, but it does not describe group-based pilots for the Microsoft 365 settings, and several are written as tenant-wide defaults. Confirm the scope of each one with your provider before you plan a pilot around it, and expect some to apply to everyone at once.

A short worksheet keeps the decisions in one place. The format below is a planning example, not a Microsoft form.

Field What to record
Proposed setting Name as shown in the admin centre
Affected workflow Task, app or group of users at risk
Business owner Person who can confirm the workflow
Impact evidence Impact report or simulation result, and its date range
Decision Enable, hold, or enable after a fix
Reversal, recovery or alternative plan How to turn it back off, or what to do if it cannot be reversed, and who can do it
Review date When to recheck a held setting

Recovery matters as much as the decision. Many settings can be turned off again, but Microsoft notes that blocking new custom scripts in SharePoint permanently removes the ability to add them, so read each setting’s notes before enabling it.

Before enabling a baseline security mode setting: impact report, workflow owner check, decision and review date

Who approves exceptions and checks the result?

The business owner of each affected workflow approves any exception, and the administrator who changes the setting checks the result afterwards. Write both names on the worksheet before anything is enabled, alongside the date the change is planned.

  • Decision owner. A director or operations manager who accepts the risk of holding a setting back.
  • Workflow owners. The people who rely on each add-in, report or external connection.
  • Administrator. The internal or provider administrator with the right Microsoft 365 role for that setting.
  • Communication. A short note to staff and, where relevant, to clients or guests who will see a change.

Agree a change window and a recovery or alternative plan before each change. Afterwards, test the critical workflows the change could affect before signing it off, then follow up with users and support requests over the following week for less frequent tasks. A held setting needs a reason, a fix and a review date, or it stays held indefinitely.

Give the administrator only the roles the settings need. Microsoft’s documentation names the role for many settings, such as SharePoint administrator or Security administrator, and a provider working in your tenant does not need Global Administrator for every change.

Device settings in the release, such as requiring a compliance policy, depend on how devices are enrolled. Our guide to Microsoft Intune for NZ businesses covers enrolment and compliance before access rules are tied to it.

What should we ask our IT provider before enabling it?

Ask your IT provider which settings your tenant shows, what the impact reports found and how each change would be reversed. Those answers show whether the rollout has been planned or is a matter of switching settings on.

  • Availability. Which Microsoft 365 baseline security mode settings does our tenant show today, and which are still rolling out or in preview?
  • Overlap. Which of them are already enforced through security defaults, Conditional Access or other policies?
  • Evidence. What do the impact reports show, and over what period?
  • Scope. Which settings apply to the whole tenant, and can any be limited to a group first?
  • Recovery. How would each setting be turned off again, and who can do it?
  • Timing. Which changes should wait until after month-end, GST returns or the end of the financial year?
  • Communication. Who tells staff, clients and guests about changes they will notice?

Ask for the answers on the worksheet or something like it. A record of why each setting was enabled, held or fixed first gives the next administrator the reasoning behind each decision. It may also help answer audit or insurance questions, although the requirements depend on the engagement or policy.

What does this look like for a small accounting practice?

Take an illustrative accounting practice with 20 staff, an Office add-in from its practice management software, regular Teams meetings with clients and auditors, and guests in a few SharePoint client folders. It is an example, not an Exodesk client case.

1

List the candidates

The administrator lists the settings available in the tenant and the workflows each one could touch.

2

Check the evidence

The administrator reviews the available impact evidence, and conversations with staff identify the practice management add-in and an old Excel workbook with DDE links that two people still use.

3

Ask the owners

The practice manager confirms the add-in is essential and that an auditor joins monthly from another tenant.

4

Decide each setting

The add-in goes on the COM allow list before the block is enabled, and the old workbook is rebuilt first.

5

Tell the people affected

Clients are told they may wait briefly in the Teams lobby, and guests are told they will be asked to complete MFA.

6

Check and review

The administrator tests each workflow after each change and sets a review date for anything still held.

The practice records which settings were enabled, held or dependent on a fix, and each held setting has an owner and a review date. That record explains the configuration to the next administrator and may help answer audit or insurance questions.

Guest access and file sharing are worth reviewing at the same time. A Microsoft 365 permissions audit finds the sites, folders and guests that settings alone do not fix.

Microsoft 365 baseline security mode is configuration. It does not monitor sign-ins, detect an attacker or restore deleted data, so monitoring and backup still need their own arrangements.

Get Help Planning Baseline Security Mode

Exodesk has supported New Zealand businesses since 1989. Today, our Christchurch and Dunedin teams support businesses nationwide.

We help businesses review the settings their tenant shows, test the workflows at risk and agree which settings to enable, hold or fix first.

NEXT STEP

Which of your add-ins, guests and old workbooks would a new setting stop?

Discuss a staged Microsoft 365 security review with Exodesk. We confirm the scope with you first, then work through the settings your tenant shows, the workflows they affect and the order to enable them.

Or see what an IT assessment covers.

Frequently Asked Questions

What is Microsoft 365 baseline security mode?

It is a set of Microsoft-recommended security settings in the Microsoft 365 admin centre, covering sign-in, Office apps, files, Teams, SharePoint, Exchange and devices. Each setting can be reviewed for impact and turned on separately.

Why can we not see baseline security mode 2026 yet?

Microsoft is rolling the 2026 release out in phases and has not published dates for individual tenants. Workload administrators also see only their own settings, and the Azure and Windows settings are still in private preview.

Does Microsoft 365 Business Premium configure baseline security mode automatically?

No. Buying Business Premium does not mean baseline security mode has been reviewed and enabled for your business. An administrator still checks the settings your tenant shows, your existing policies and the workflows that depend on them. Having the settings available also does not license every service behind them, so confirm the requirements for each control.

Does baseline security mode replace security defaults or Conditional Access?

No. Security defaults and Conditional Access still control how people sign in, and baseline security mode adds separate recommended settings across Microsoft 365 services. Check how its authentication settings relate to the policies you already enforce.

What is the difference between baseline security mode and security defaults?

Security defaults are one free on-or-off switch for basic sign-in protection, including MFA and blocking legacy authentication. Baseline security mode is a list of separate settings that also covers Office apps, files, Teams, SharePoint and devices.

Does baseline security mode replace monitoring and backup?

No. It changes configuration, so it does not watch for suspicious sign-ins, respond to an incident or restore lost data. Those need their own monitoring and backup arrangements.

Can we test a setting before turning it on?

Yes, for many settings. Microsoft recommends running each setting’s impact report and says settings can run in simulation mode, but confirm with the workflow owners as well, because a report only covers the period it looked at.

Can a setting be turned off again if it breaks something?

Many can, but check each setting’s notes first. Microsoft says blocking new custom scripts in SharePoint permanently removes the ability to add them, so record a recovery plan before enabling anything.

Does baseline security mode make us compliant?

No. Microsoft states that baseline security mode does not by itself make a business compliant with any law or regulatory framework. It is a configuration baseline, and compliance depends on your obligations, processes and evidence.

Can Exodesk help businesses in Christchurch and Dunedin plan baseline security mode?

Yes. Our Christchurch and Dunedin teams support businesses nationwide. We can review the settings your tenant shows, test the workflows at risk and agree the order to enable them, with scope confirmed first.

Contact us or call 0800 396 337 to talk about your Microsoft 365 security settings.

Start typing and press Enter to search

FMA cyber incident notification: an advice firm passing incident facts from its IT and platform suppliers to the regulator Call Us Now