Skip to content
+90 850 885 27 43 info@argeict.com

Guide · Security

Microsoft 365 security settings: the first 10 steps

In Microsoft 365, Microsoft is responsible for running the service, and the organization is responsible for identity settings and data protection. This guide gives Microsoft 365 administrators the first ten settings to configure, in order.

ARGE ICT · Published November 11, 2026 · Updated November 15, 2026

When a Microsoft 365 tenant is first created, many security settings are left for the organization to configure. Email, files, and identity live in the same service, so a single compromised account gives access to all of that data.

Scope and prerequisites

Under the shared responsibility model, Microsoft operates the service infrastructure and keeps the service available. Identities, devices, access settings, and the data itself remain the organization's responsibility.

This guide assumes a tenant whose identities are held in Microsoft Entra ID. Some steps depend on licensing; the guide notes each step where a feature varies by license.

Three preparations come first: a list of the accounts that hold administrator roles, a set of emergency access accounts, and an announcement for users. Microsoft Secure Score can also be used to track progress.

The ten steps are a starting level and do not cover the full Microsoft 365 security needs of an organization. Setting names and behavior can change, so confirm each step against Microsoft's current documentation.

1. Separating administrator accounts

The Global Administrator role is held by as few accounts as possible. Administration is done with an account separate from the one used for daily email and files. The narrowest role that covers the task is assigned.

The tenant also keeps at least two emergency access accounts that are excluded from Conditional Access policies that block or restrict sign-in. These accounts sign in with a phishing-resistant method such as a security key or a certificate, their credentials are stored somewhere secure, and every sign-in with one of them raises an alert.

2. Multi-factor authentication (MFA)

MFA is enabled for administrators first and then for all users. An authenticator app, a passkey, or a security key is a stronger second step than a code sent by SMS.

In tenants without a Conditional Access license, security defaults provide a basic level of MFA. Service accounts and shared mailboxes are handled separately from user accounts.

3. Blocking legacy authentication

Protocols that use legacy authentication cannot enforce MFA; POP, IMAP, SMTP AUTH, and older clients fall in this group. Because the second step never runs when a password is stolen, these paths make it easier to get around MFA.

Start by finding, in the sign-in logs, the scanners, printers, older mail clients, and business applications that still use these methods. Move them to modern authentication, and only then block the method. Microsoft is also retiring these methods on its own side in stages; the timeline changes, so check its current documentation.

4. Conditional Access policies

Conditional Access evaluates each sign-in request by user, location, device, application, and risk level. Depending on the result, it requires MFA, blocks access, or requires a compliant device. The feature varies by license and may not be present in every tenant.

Every policy is first enabled in report-only mode, its effect is observed in the logs, and only then is it enforced. These are the first policies to set up.

  • MFA is required for all users.
  • Legacy authentication is blocked.
  • A compliant device is required for administrator actions.
  • Access is restricted from locations where the organization does not operate.

Emergency access accounts stay outside these policies, so a policy error cannot lock administrators out of the service.

5. Password and session settings

A password should be long and not reused elsewhere. NIST SP 800-63B advises against forcing periodic password changes when there is no sign of compromise, and recommends blocking common, predictable passwords instead.

Letting users reset their own passwords with MFA reduces the help desk load. On unmanaged devices the session length is shortened and idle sessions are closed; the organization sets the exact values according to its own risk level.

6. Limiting external sharing

The external sharing level for SharePoint and OneDrive is set for the whole organization. Links that anyone can use without signing in are turned off or limited by time, and sharing can also be restricted to approved domains.

Guest users and the teams they can access are reviewed periodically. In Teams, external access and guest access are separate settings, and both need their own check.

7. Email authentication and filtering

SPF, DKIM, and DMARC let receivers verify mail sent from the organization's domain. DMARC is published first with a monitoring policy, the reports are reviewed, and the policy then moves to quarantine and reject.

Automatic forwarding from mailboxes to outside addresses is turned off, because an attacker who takes over an account can set up a forwarding rule to keep reading its mail. Phishing protection and scanning of malicious attachments and links vary by license.

8. Threat protection and device compliance

Endpoint protection and device compliance policies vary by license, and a compliance policy can require disk encryption, a current operating system, and a screen lock.

Compliance status is attached to Conditional Access as a condition. Unmanaged devices can be limited to browser-only access without file downloads.

9. Audit log

First confirm that the audit log is turned on. How long records are kept varies by license. If longer retention is needed, the records are forwarded to the organization's log management system (SIEM).

The events that should trigger alerts fall into the four groups below.

  • Assignment of a new administrator role
  • Creation of a mailbox forwarding rule
  • Bulk file downloads
  • Sign-ins from an unusual location

10. Data protection and backup

Sensitivity labels and data loss prevention (DLP) policies vary by license and are introduced in stages. Users need administrator approval before they can grant third-party applications access to data.

Retention policies and the recycle bin are not backups; deleted items can be recovered only for a limited time. Whether to keep a separate backup of Exchange Online, SharePoint, OneDrive, and Teams data is the organization's decision.

A backup also has to be tested by restoring it; see the Restore test guide for the steps.

Rollout order and user communication

Identity steps (1 to 3) come first, then access policies, and data steps last. Each change is tested with a small pilot group before it is rolled out to everyone.

Users are told in advance when MFA is switched on and when legacy authentication is blocked, and the help desk prepares for extra requests during the changeover. The settings are reviewed again when the administrator team changes and when the organization turns on a new service.

Sources

  • Microsoft Entra documentation: Conditional Access, security defaults, emergency access accounts, Microsoft Learn (learn.microsoft.com)
  • Microsoft 365 security documentation and shared responsibility in the cloud, Microsoft Learn (learn.microsoft.com)
  • NIST SP 800-63B-4, Digital Identity Guidelines: Authentication and Authenticator Management, NIST (nist.gov)
  • RFC 7208 (SPF), RFC 6376 (DKIM), RFC 9989 (DMARC), IETF (rfc-editor.org)

Expert call for Microsoft 365 security

Share your user count and which of the ten steps are in place today; we respond to your request within one business day.

Speak to an expert