Managed IT

Securing Microsoft 365: security settings for SMEs

A new Microsoft 365 tenant is ready to use, but not secured in every respect. This guide covers the most important settings for SMEs, from MFA and administrator accounts to sharing, logs and email authentication, each with what your licence allows. It is based on Microsoft Learn, the SCuBA baselines of the US agency CISA and the IT-Grundschutz of the German Federal Office for Information Security (BSI). As of October 2026.

As of
Reading time
13 minutes
Updates reach your fleet in stages.
  1. 01Inventory & plan
  2. 02Pilot & rollout
  3. 03Monitor
Concept: take inventory, plan updates, test a pilot group and expand in stages with monitoring.

Starting point: what Microsoft sets by default

Microsoft runs the platform; the settings in the tenant are the business’s responsibility. The IT-Grundschutz module OPS.2.2 (cloud usage) therefore requires the areas of responsibility between cloud provider and customer to be clearly separated and documented. Some defaults are deliberately open so that collaboration works straight away:

Defaults that need a deliberate decision

SettingDefault according to MicrosoftRecommendation
External sharing in SharePoint and OneDriveOn for the entire environmentDecide deliberately; “Anyone” links only with an expiry date, or not at all
POP3 and IMAP4Enabled when a mailbox is createdAllow only for mailboxes that demonstrably need them
Audit log (Unified Audit Log)Not on by default in Business Basic, Standard and PremiumTurn it on and check the status
DKIM for custom domainsCurrently no DKIM signing for custom domainsSet up DKIM, then DMARC
Consent to appsNew tenants: Microsoft-managed policy; users may consent, except to access to files, mail, calendars and chats, among othersCheck your own setting; limit to verified publishers or require admin consent

As of October 2026, per Microsoft Learn; recommendations per Microsoft and the CISA SCuBA baselines. Sources at the end of the article.

The SCuBA baselines apply to US federal agencies and assume Microsoft 365 E3; for others they are for information only, but they state every setting with its rationale. Backups are covered in Backup strategy for SMEs.

What your licence includes

Which tools are available depends on the plan. This is how Microsoft documents the differences:

Security features by Microsoft 365 plan

AreaBusiness Basic / StandardBusiness Premium, Microsoft 365 E3Microsoft 365 E5
Entra IDFreeP1P2
Enforcing MFASecurity defaultsConditional AccessConditional Access, plus risk-based
Privileged Identity ManagementNot includedNot includedIncluded
Email protectionBuilt-in protection for all cloud mailboxes; Defender for Office 365 as an add-onDefender for Office 365 Plan 1Defender for Office 365 Plan 2
Audit logAudit (Standard), 180 daysAudit (Standard), 180 daysAudit (Premium), one year for Entra ID, Exchange, SharePoint and OneDrive

As of October 2026, per Microsoft Learn (Entra licensing, Defender for Office 365, Purview). Add-ons supplement individual features, for example Entra ID P2 through the Defender Suite for Business Premium.

MFA for everyone: registration and enforcement

Without Entra ID P1, security defaults are Microsoft’s free baseline. In tenants created on or after 22 October 2019 they may already be on; Microsoft periodically notifies tenants without Conditional Access, without premium licences and without legacy clients in use that it will enable them automatically. When enabled, they:

  • Require all users to register for MFA. Microsoft removed the former 14-day grace period on 29 July 2024.
  • Require administrators in 16 roles, from Global Administrator to Exchange and SharePoint Administrator, to complete MFA at every sign-in, and all other users whenever Microsoft considers it necessary based on location, device, role and task.
  • Block legacy authentication protocols; in tenants created since 1 July 2026, according to Microsoft, also sign-in by device code (device code flow).
  • Require MFA for anyone using the Azure portal, the Entra admin center, Azure PowerShell or the Azure CLI.

With Entra ID P1, Microsoft considers security defaults probably not the right fit, as they allow no exceptions; introducing Conditional Access means switching them off. Microsoft then recommends a baseline policy: all users, all resources, MFA required, excluding only emergency accounts and, where used, the Entra Connect synchronisation account. New policies run in report-only mode first. Separately, since October 2024 Microsoft has been gradually enforcing mandatory MFA for the Azure portal and the Entra and Intune admin centers, since February 2025 for the Microsoft 365 admin center as well, and since October 2025 for Azure CLI and Azure PowerShell.

Not every method protects equally well. SCuBA requires phishing-resistant MFA for all users, explicitly including highly privileged roles, and wants SMS, voice call and email one-time passcodes disabled. The BSI recommends MFA with suitable knowledge and possession factors and considers passkeys very secure because they prevent phishing; accounts with far-reaching permissions should be protected by multi-factor authentication (ORP.4.A10). For NIS2 entities, MFA or continuous authentication is mandatory according to the BSI; see NIS2 for SMEs. Tying sign-in to managed devices requires device management; see endpoint management.

Caution: Check first what still signs in the old way

With security defaults on, SMTP AUTH is disabled in Exchange Online, and older protocols such as IMAP, POP3 or SMTP are blocked. Multifunction devices that send email via SMTP AUTH, or old line-of-business applications, then stop sending.

Administrator accounts: few, separate, cloud-only

Global Administrators have virtually unrestricted access to the tenant. Microsoft recommends assigning the role to fewer than five people; the SCuBA baseline requires at least two and at most eight, because emergency access and some operational scenarios may need additional accounts. In addition:

  • Least privilege: someone who only creates users gets the User Administrator role, not Global Administrator.
  • Separate accounts: administrators use a normal account for everyday work and the admin account only when needed. According to Microsoft, admin-only accounts need no Microsoft 365 licence.
  • Cloud-only accounts: do not assign admin roles to accounts synchronised from on-premises Active Directory; otherwise, says Microsoft, a compromised on-premises account can compromise Entra ID as well.
  • Emergency accounts: at least two cloud-only accounts on the onmicrosoft domain with the Global Administrator role, not assigned to any person and protected with a passkey (FIDO2) or certificate. They are excluded from Conditional Access policies that block or restrict sign-in, including MFA or device requirements; signing in with a passkey or certificate still satisfies the MFA requirement. Their sign-ins are monitored, their credentials stored securely and the accounts tested at least every 90 days.
  • Privileged Identity Management (PIM): with Entra ID P2 or Entra ID Governance, administrators receive their role only on request and for a limited time; emergency accounts keep a permanent active assignment.

Note: Emergency accounts need MFA too

A Microsoft page for the Business plans (dated January 2026) still recommends excluding emergency accounts from MFA. Since MFA became mandatory for the Azure and admin portals, the Entra documentation states that emergency accounts must sign in there with MFA too. Microsoft recommends a passkey (FIDO2) or certificate; an emergency account with only a password can no longer reach the admin portals.

Switching off legacy sign-in methods

Legacy sign-in methods do not support MFA; according to Microsoft, an older protocol can be used to bypass MFA. In Exchange Online, Microsoft removed Basic authentication for ActiveSync, POP, IMAP, Remote PowerShell, EWS and Outlook from 1 October 2022 and disabled SMTP AUTH in every tenant where it was not in use. Three areas remain open:

  • SMTP AUTH: Microsoft recommends disabling SMTP AUTH submission organisation-wide and allowing it only for mailboxes that still need it; the mailbox setting takes precedence. Outlook and other modern clients do not use SMTP AUTH. The SCuBA baseline requires it to be disabled.
  • POP3 and IMAP4: both are enabled when a mailbox is created. They can be switched off per mailbox in the Exchange admin center.
  • Conditional Access: with Entra ID P1, a policy blocks legacy authentication for the whole tenant. Without P1, security defaults do this, according to Microsoft.

Microsoft is retiring Basic authentication for SMTP AUTH as well. Under the Exchange team’s timeline as updated in January 2026, it will be switched off by default in existing tenants at the end of December 2026, though administrators can switch it back on for the time being; in tenants created after that it is unavailable by default. Microsoft intends to name the final date in the second half of 2027. Devices and applications should therefore move to OAuth 2.0 or another sending method such as the Microsoft Graph API.

Guests and external sharing in SharePoint, OneDrive and Teams

External sharing in SharePoint and OneDrive is on by default for the entire environment. The organisation-level setting has four levels: “Anyone” (links without sign-in), new and existing guests, existing guests only, and only people in your organisation. Each site can be set to the same level or a stricter one, but not a looser one.

  • “Anyone” links: if this level is enabled, the default link is normally an “Anyone” link, according to Microsoft, which works without sign-in and allows editing. Microsoft advises setting the default link to your own organisation, enforcing an expiry date and allowing view only.
  • SCuBA values: limit external sharing to existing guests or the organisation only, default link “Specific people”, default permission view, “Anyone” links valid for 30 days at most, re-verification by code after 30 days at most.
  • Guest access expiry: administrators can set guest access to a site or OneDrive to end automatically after a set number of days.
  • Separate confidential content: Microsoft recommends storing confidential information in sites without external sharing.
  • Tightening later: if sharing is restricted, guests usually lose access within one hour.

In Teams, every invited guest gets a guest account in Entra ID, which remains after leaving the team until an administrator removes it. IT-Grundschutz requires accounts that are not needed to be disabled or deleted (ORP.4.A1). Guest accounts therefore need regular review; access reviews are available in basic form with Entra ID P2 (for example in Microsoft 365 E5), and advanced capabilities with Entra ID Governance.

Limiting user consent to apps

Before an app can access company data, a user or administrator has to grant it permissions. Which permissions users may grant themselves is set by a consent policy. In new tenants, according to Microsoft, this is the Microsoft-managed policy: users may consent, except to access to files, mail, calendars and chats, among others; popular mail apps are allowed through a separate policy. Older Microsoft documentation still describes the default as users being allowed to consent to any permission that does not require admin consent, for example to let an app read their mailbox. In existing tenants it is therefore worth checking your own setting. Because malicious apps deliberately trick users into consenting, Microsoft recommends limiting user consent to apps from verified publishers. The options:

  • Limited consent: only for apps from verified publishers and apps registered in your own tenant, and only for permissions you have classified as low impact.
  • Admin consent workflow: users request access, designated reviewers receive the request by email and decide. The reviewer role on its own grants no additional rights.
  • SCuBA values: restrict user consent, configure an admin consent workflow and allow only administrators to register apps.

Turning on and retaining audit logs

The Unified Audit Log records user and administrator activity in Microsoft 365. According to Microsoft it is on by default, with important exceptions: in Business Basic, Business Standard and Business Premium, and in trial tenants on enterprise trial licences, it is not on by default and has to be turned on manually. If it is off, searching the log returns no results.

Log retention by licence

LogRetentionLicence
Audit log, Audit (Standard)180 days (records from 17 October 2023)Business Basic to Premium, Microsoft 365 E3
Audit log, Audit (Premium)One year for Entra ID, Exchange, SharePoint and OneDrive; up to ten years with an add-onMicrosoft 365 E5
Entra ID sign-in and audit logs7 daysEntra ID Free
Entra ID sign-in and audit logs30 daysEntra ID P1 or P2

As of October 2026, per Microsoft Learn. The Entra logs are separate from the Unified Audit Log.

Get-AdminAuditLogConfig in Exchange Online PowerShell shows whether it is running: UnifiedAuditLogIngestionEnabled must be True. SCuBA requires logs to stay searchable for at least three months and retrievable for twelve. If you need records for longer than your licence keeps them, export them through the Office 365 Management Activity API. Logs do not replace archiving; see Exchange Online and the GoBD.

Email protection: SPF, DKIM, DMARC and Defender

Three DNS records show recipients that emails with your sender domain really come from you. For the original onmicrosoft domain, Microsoft sets up SPF and DKIM itself; you create the DMARC record in the Microsoft 365 admin center. For custom domains:

  • SPF: setting up Microsoft 365 already requires the record, but it must cover every other sender as well, such as a newsletter service. Microsoft recommends ending it with -all (hard fail) and using a separate subdomain for bulk mail.
  • DKIM: Microsoft 365 currently does not sign for custom domains. Create two CNAME records with your DNS provider, then turn on signing in the Defender portal.
  • DMARC: Microsoft recommends a gradual rollout: start with p=none and analyse the reports, then move via p=quarantine to p=reject. Domains that never send email get p=reject straight away. The SCuBA baseline also requires p=reject in the end.

Every cloud mailbox has basic protection against malware, spam and phishing. According to Microsoft, Defender for Office 365 Plan 1 adds protection against zero-day malware, phishing and business email compromise, for example with Safe Links and Safe Attachments; Plan 2 adds phishing simulations and automated response. The Standard and Strict preset policies are usually off on first visit and have to be assigned to users. SCuBA also requires automatic forwarding to external domains to be disabled.

Microsoft Secure Score as a metric

Microsoft Secure Score in the Defender portal measures how many recommended security actions have been implemented. Each action is worth 10 points at most, some of them proportionally: if 50 of 100 users are protected by MFA, you get 5 of 10 points. Actions you deliberately skip can be marked as accepted risk, and according to Microsoft not every recommendation fits every environment. The score is therefore most useful for the trend: is it rising, and what is still open? It is not evidence of GDPR or NIS2 compliance.

I manage and secure Microsoft 365 tenants for businesses; I set up policies such as Conditional Access according to security needs and available licences. My own product Auditspiegel reviews a tenant’s security settings read-only and evaluates up to 121 settings depending on licences, mapped among others to the SCuBA baselines, Secure Score and BSI IT-Grundschutz. That is a reference, not a statement of compliance. You or your IT make the changes in the tenant, with my help if you wish as part of IT infrastructure.

Questions and answers

Are security defaults enough for a small business?

For tenants with Entra ID Free, such as Business Basic or Standard, Microsoft intends them as the starting point: MFA registration for everyone, MFA for administrators and blocking of legacy protocols. They allow no exceptions for individual accounts or devices; that requires Conditional Access with Entra ID P1.

Do I need Business Premium for Conditional Access?

Conditional Access requires Entra ID P1. P1 is included in Business Premium and in Microsoft 365 E3 and E5, and is also available on its own. Risk-based policies that react to suspicious sign-ins require Entra ID P2, for example in Microsoft 365 E5.

Why does our multifunction device no longer send emails after the change?

Many devices send via SMTP AUTH with a username and password, and according to Microsoft SMTP AUTH is disabled when security defaults are on. For multifunction devices, Microsoft describes other sending methods, including SMTP relay through a connector and Direct Send.

How many Global Administrators should a tenant have?

Microsoft recommends fewer than five, the SCuBA baseline at least two and at most eight, emergency accounts included. For everyday tasks, narrower roles such as User or Exchange Administrator are usually enough.

Is a high Secure Score proof of security or NIS2 compliance?

No. Secure Score counts implemented Microsoft recommendations, some proportionally, and recommendations can be marked as accepted risk. It is useful for tracking progress. Which measures are appropriate depends on your security needs and, where applicable, your legal obligations.

Sources

The information reflects the date above. Sources are named so you can look them up; the website does not link to external sites.

  1. Microsoft Learn: Security defaults in Microsoft Entra ID, 16 October 2026
  2. Microsoft Learn: Require multifactor authentication for all users, 24 March 2026
  3. Microsoft Learn: Microsoft Entra Conditional Access (Overview, License requirements), 27 April 2026
  4. Microsoft Learn: Block legacy authentication with Conditional Access, 24 March 2026
  5. Microsoft Learn: Mandatory multifactor authentication for Azure and admin portals, 3 April 2026
  6. Microsoft Learn: Manage emergency access accounts in Microsoft Entra ID, 5 June 2026
  7. Microsoft Learn: Best practices for Microsoft Entra roles, 1 June 2026
  8. Microsoft Learn: Admin account security in Microsoft 365 for business, 6 January 2026
  9. Microsoft Learn: Microsoft Entra licensing, 28 July 2026
  10. Microsoft Learn: Deprecation of Basic authentication in Exchange Online, 16 July 2026
  11. Microsoft Exchange Team Blog: Updated Exchange Online SMTP AUTH Basic Authentication Deprecation Timeline, 27 January 2026
  12. Microsoft Learn: Enable or disable authenticated client SMTP submission (SMTP AUTH) in Exchange Online, 16 September 2026
  13. Microsoft Learn: How to set up a multifunction device or application to send email using Microsoft 365, 16 September 2026
  14. Microsoft Learn: Managing email apps for user mailboxes, 20 May 2024
  15. Microsoft Learn: Overview of external sharing in SharePoint and OneDrive in Microsoft 365, 7 May 2026
  16. Microsoft Learn: Manage sharing settings for SharePoint and OneDrive in Microsoft 365, 30 June 2026
  17. Microsoft Learn: Best practices for unauthenticated sharing, 3 January 2024
  18. Microsoft Learn: Guest access in Microsoft Teams, 16 July 2026
  19. Microsoft Learn: Configure how users consent to applications, 24 June 2025
  20. Microsoft Learn: Manage app consent policies, 17 June 2026
  21. Microsoft Learn: Configure the admin consent workflow, 19 January 2026
  22. Microsoft Learn: Turn auditing on or off, 19 June 2026
  23. Microsoft Learn: Learn about auditing solutions in Microsoft Purview, 18 May 2026
  24. Microsoft Learn: Microsoft Purview service description (Audit), 3 August 2026
  25. Microsoft Learn: Microsoft Entra data retention, 25 March 2026
  26. Microsoft Learn: Set up SPF to identify valid email sources for your Microsoft 365 domain, 3 July 2026
  27. Microsoft Learn: How to use DKIM for email in your custom domain, 3 July 2026
  28. Microsoft Learn: Set up DMARC to validate email in Microsoft 365, 17 July 2026
  29. Microsoft Learn: Why do I need Microsoft Defender for Office 365?, 21 May 2026
  30. Microsoft Learn: Preset security policies, 3 July 2026
  31. Microsoft Learn: Microsoft Secure Score, 7 March 2026
  32. Cybersecurity and Infrastructure Security Agency (CISA): CISA M365 Secure Configuration Baseline for Microsoft Entra ID (ScubaGear v2.0.0), 22 October 2026
  33. Cybersecurity and Infrastructure Security Agency (CISA): CISA M365 Secure Configuration Baseline for Exchange Online (ScubaGear v2.0.0), 22 October 2026
  34. Cybersecurity and Infrastructure Security Agency (CISA): CISA M365 Secure Configuration Baseline for SharePoint Online and OneDrive (ScubaGear v2.0.0), 22 October 2026
  35. Cybersecurity and Infrastructure Security Agency (CISA): CISA M365 Secure Configuration Security Suite Baseline (ScubaGear v2.0.0), 22 October 2026
  36. Bundesamt für Sicherheit in der Informationstechnik (BSI): IT-Grundschutz-Kompendium, module ORP.4 Identitäts- und Berechtigungsmanagement, Edition 2023
  37. Bundesamt für Sicherheit in der Informationstechnik (BSI): IT-Grundschutz-Kompendium, module OPS.2.2 Cloud-Nutzung, Edition 2023
  38. Bundesamt für Sicherheit in der Informationstechnik (BSI): #nis2know: Multi-Faktor-Authentisierung, kontinuierliche Authentifizierung und gesicherte Kommunikation, retrieved 27 Oct 2026

AI. Software. Infrastructure. One point of contact.

Good IT starts
with a conversation.

Tell me what you are planning. Together, we will work out which AI, software and IT support will move you forward.

Free initial consultation · Personal and without obligation

  • AI development
  • Custom software
  • Thoughtful infrastructure
  • Practical automation
  • One personal point of contact
  • Support that thinks ahead