Who should use this checklist?
IT directors, Microsoft 365 administrators and security teams can use this guide to plan a tenant review. Start with the current settings and affected users. Agree who owns each control before changing a policy.
- Record the scope, license requirements and approved exceptions.
- Test changes with a pilot group and keep a recovery route.
- Save evidence, assign follow-up work and set the next review date.
For implementation and ongoing support, explore Microsoft 365 consulting and cybersecurity services.
Use the 18 checkboxes to track this review. Selections stay in this browser view and are not submitted or saved. The count is a work aid, not a security or compliance score.
0 of 18 checkedBefore you change a tenant security policy
A Microsoft 365 tenant rarely stays still. A project needs external sharing, a new application asks for permissions, or an administrator gains extra access during an incident. Each change may be reasonable. The risk is that exceptions and privileged access remain long after the original need has passed.
This Microsoft 365 security checklist helps enterprise administrators turn a hardening review into owned, testable work. It covers Microsoft Entra ID, Intune, Exchange Online, Defender, SharePoint, OneDrive, Teams and Purview. For each control, identify the responsible team, confirm the settings in your tenant and record evidence that they work.
Use the recommendations as a review framework. The effective setting depends on your users, identity model, supported clients, licensing and business requirements. Pilot policy changes before enforcement and agree a recovery path.
- Inventory the environment: users, privileged roles, domains, applications, identity dependencies and security subscriptions.
- Agree ownership: identify who changes the control and who verifies its effect.
- Pilot and recover: use report-only mode where supported, test representative user journeys and protect emergency access.
- Keep evidence: capture effective scope, exceptions, outcomes and the next review date.
Identity and access management
Start with the accounts and policies that determine who can administer the tenant. Review ordinary administrator access and emergency recovery as separate operating paths.
Reduce standing Global Administrator access
Use the least-privileged role that supports the task. Microsoft recommends fewer than five people with Global Administrator access; review the actual assignments, including emergency accounts, rather than treating a fixed account count as the whole control.
Keep normal administrator identities separate from daily email and browsing. Use time-limited PIM activation for routine privileged work where licensed. Emergency accounts need a permanent active recovery role, not an activation process that can fail during an outage. [1] [14]
- Where to review
- Microsoft Entra admin center → Roles & admins; Privileged Identity Management.
- Evidence to keep
- Role inventory, business justification, emergency-account custody and recent activation records.
Require MFA and prioritize phishing-resistant methods
Cover interactive user access with a tested MFA policy. Prioritize phishing-resistant authentication for administrators and other high-impact roles. Confirm authentication-method registration, policy scope and exceptions in sign-in evidence.
Use Conditional Access for granular controls and staged deployment. Security Defaults provides a no-additional-license baseline but does not offer the same customization. Do not turn it off until replacement controls are ready. Review legacy authentication and noninteractive workloads separately; a human MFA prompt is not a service-account design. [3] [4]
- Where to review
- Microsoft Entra admin center → Conditional Access and Authentication methods.
- Evidence to keep
- Policy coverage, report-only observations, authentication-method readiness and reviewed exclusions.
Maintain and test at least two emergency (break-glass) accounts
Use at least two cloud-only accounts on the tenant’s onmicrosoft.com domain. Protect them with phishing-resistant methods independent of normal administrator dependencies. Assign their recovery roles permanently, control credential custody, and alert on every use.
Microsoft recommends excluding these accounts from Conditional Access policies that block or restrict sign-in. Adding a dedicated enforced policy can recreate the dependency you need to avoid. This is not an exemption from Microsoft’s mandatory MFA requirements. Test the recovery path and its alerting on a defined schedule. [2]
- Where to review
- Microsoft Entra users, role assignments, authentication methods, Conditional Access exclusions and sign-in monitoring.
- Evidence to keep
- Successful recovery test, separate credential custody, reviewed exclusions and delivered sign-in alerts.
Remove broad location-based MFA bypasses
Do not treat an office or VPN IP address as sufficient proof of identity. Review trusted-location exclusions and the legacy per-user MFA trusted-IP configuration alongside your current policies.
Named locations can contribute useful context. They should not quietly remove protection for sensitive applications or privileged roles. Test the revised access paths before retiring legacy settings, and document any remaining exception with an owner and review date. [3] [4]
- Where to review
- Microsoft Entra Conditional Access → Named locations; legacy MFA service settings where still used.
- Evidence to keep
- List of location-based exclusions, approved exceptions and representative sign-in tests.
Replace routine password expiry with modern password controls
Microsoft recommends avoiding routine password expiration for cloud-only users. Combine this with MFA, password protection and an effective response when compromise is suspected. Reset credentials when necessary; “never expire” is not “never respond.”
Check hybrid identities separately: password-hash synchronization, pass-through authentication and federation can follow different expiration paths. Review the cloud and on-premises policy together. Custom banned-password lists and on-premises password protection have their own licensing prerequisites. [5]
- Where to review
- Microsoft 365 admin center → Password expiration policy; Microsoft Entra Authentication methods / Password protection; on-premises AD where applicable.
- Evidence to keep
- Documented cloud/hybrid policy, password-protection settings and compromise-response procedure.
Device compliance and application governance
Agree which devices and applications may handle business data. Identity, endpoint and application owners need a common exception process.
Define device compliance and a supported BYOD path
Build and test Intune compliance policies before requiring compliant devices through Conditional Access. Confirm that supported users can enroll, become compliant and recover from common failures before broad enforcement.
For approved BYOD scenarios, Intune app protection can protect organizational data in supported apps and platforms. It is not a universal replacement for managed-device compliance. Design separate policy paths where needed and test their grant controls, supported clients and emergency exclusions. [6] [18]
- Where to review
- Intune → Device compliance / App protection; Microsoft Entra → Conditional Access.
- Evidence to keep
- Agreed compliance baseline, pilot results, supported BYOD scenarios and exception ownership.
Control app consent and make reviews workable
Restrict user consent to an approved low-risk policy or require administrator approval. Review the permissions requested, the publisher and the business purpose; a verified publisher is useful information, not proof that every permission is appropriate.
Enable a review workflow with named reviewers and a realistic turnaround target. Assign the correct approval roles: being designated a reviewer does not itself grant permission to approve every request. Review existing grants and unused apps, not just new requests. [7] [14]
- Where to review
- Microsoft Entra → Enterprise apps → Consent and permissions → User consent settings / Admin consent settings.
- Evidence to keep
- Consent policy, request decisions, reviewer roles and a periodic grant-review record.
Email authentication and threat protection
Coordinate messaging, DNS and security operations. An email control is not finished until legitimate senders work and the right team receives actionable alerts.
Deploy SPF, DKIM and DMARC with sender evidence
Inventory legitimate senders, including marketing, payroll, ticketing and other third parties. Maintain SPF, enable DKIM for supported sending domains, and use DMARC reporting to validate alignment before moving toward enforcement.
DMARC passes when SPF or DKIM passes with the required alignment; publishing all three records does not prove that every sender is configured correctly. Move from monitoring to quarantine or reject as the evidence supports it. Review non-sending and parked domains separately, with the DNS owner. [8]
- Where to review
- Authoritative DNS; Microsoft Defender email authentication settings; third-party sender administration.
- Evidence to keep
- Sender inventory, DNS records, aligned message samples, DMARC reports and approved enforcement rollout.
Review threat policies against Standard and Strict baselines
Use Configuration Analyzer to identify deviations from Microsoft’s Standard and Strict recommendations for the protections available in your tenant. Evaluate preset security policies for consistent coverage.
Apply stronger protection to higher-risk groups where appropriate, then test real mail flows and policy precedence. Some Defender for Office 365 features require additional entitlement. Recheck the configuration after changes and periodically to catch drift. [9]
- Where to review
- Microsoft Defender → Email & collaboration → Policies & rules → Threat policies → Configuration Analyzer / Preset security policies.
- Evidence to keep
- Analyzer findings, assigned policy scope, accepted exceptions and mail-flow test results.
Connect security alerts to an owned response process
Choose which Defender alerts and incidents require action, route them to monitored operations channels, and test that someone receives and owns the work. A portal showing an incident is not the same as a response process.
Use the supported notification, SIEM or ticketing integration for your environment. Agree triage responsibility, escalation, coverage hours and response targets. Correlation and visibility depend on the licensed Defender workloads and connected telemetry, so validate the signals you actually collect. [16]
- Where to review
- Microsoft Defender incident/alert notifications; supported SIEM and ITSM connectors.
- Evidence to keep
- Delivered test incident, assigned ticket, escalation path and runbook.
SharePoint, OneDrive and Teams collaboration security
Make external collaboration deliberate. Use different sharing and meeting settings where sensitivity or business workflows justify them.
Limit guest resharing and review external access
Review the setting that allows guests to share items they do not own. Where it is not needed, disable it and test the effect on the sites that collaborate with partners.
Pair the setting with site-level sharing controls and an external-access review or expiration process. It does not prevent every form of redistribution, such as a permitted download. Treat access reviews and sensitivity-label features as additional controls with their own prerequisites. [10]
- Where to review
- SharePoint admin center → Policies → Sharing → More external sharing settings; site-level sharing settings.
- Evidence to keep
- Tested guest permissions, external user inventory and review or expiration records.
Choose a restrictive default sharing link
For sensitive collaboration, consider Specific people with View as the default. Choose organization-wide and site-level defaults according to how each audience needs to work.
A default is a starting selection, not an enforcement boundary. Users may still choose other allowed link types or permissions. Review Anyone-link availability, site permissions and sensitivity requirements separately, and test the common sharing paths. [10]
- Where to review
- SharePoint admin center → Policies → Sharing → File and folder links; individual site settings.
- Evidence to keep
- Tenant/site defaults, tested sharing links and an inventory of broader allowed sharing.
Control anonymous Teams joining through organizer policies
Decide which organizers need anonymous participants. Use per-organizer meeting policies to restrict unverified anonymous joining and allow it for approved business scenarios.
Microsoft is retiring the organization-wide anonymous-join setting and recommends managing this through organizer policies. While the organization-wide setting still exists, switching it off can prevent policy-based exceptions from working. Verify the effective combination in your tenant, and distinguish anonymous participants from authenticated guests or external users. [11]
- Where to review
- Teams admin center → Meetings → Meeting policies → Meeting join & lobby; organization-wide setting where still present.
- Evidence to keep
- Policy assignments and external/anonymous test joins for representative organizers.
Set lobby defaults for the meeting audience
Choose who can bypass the lobby according to the meeting’s sensitivity. People in the organization can be a starting point for internal meetings; leadership or sensitive sessions may need a tighter setting.
Test anonymous participants, external users, dial-in access and who may admit attendees. A lobby default does not by itself guarantee that an organizer cannot change meeting options. Use supported enforcement or template capabilities if the requirement demands a locked setting. [17]
- Where to review
- Teams admin center → Meetings → Meeting policies → Meeting join & lobby; organizer meeting options.
- Evidence to keep
- Effective lobby defaults and tests for internal, external and anonymous attendees.
Keep external calendar detail to the minimum needed
Use availability-only sharing where partners do not need appointment details. Review the applicable cross-tenant and Exchange sharing configuration, rather than assuming one organization setting covers every recipient.
Calendar subjects and locations can disclose sensitive context. For Microsoft 365-to-Microsoft 365 sharing, check whether Cross-Tenant Access Policy (XTAP) is available and follow Microsoft’s migration guidance. Retain the required sharing policies and organization relationships for on-premises or hybrid scenarios. Document exceptions and test what each external recipient can see. [19]
- Where to review
- Microsoft 365 calendar and cross-tenant settings; Exchange sharing policies or organization relationships where applicable.
- Evidence to keep
- External visibility test, configured sharing levels and approved partner exceptions.
Auditing, monitoring and tenant hygiene
Confirm that evidence is available before an incident requires it. Put recurring ownership, licensing and drift checks into the same operating backlog as other production work.
Verify audit collection and the retention you actually have
Check Microsoft Purview Audit collection and retrieve representative events. Define the investigation period you need, then confirm it against record types, user licensing and retention policies. Standard audit retention is generally 180 days for current records; qualifying Premium records can have longer retention.
Microsoft Entra sign-in and audit logs are separate from the Microsoft 365 Unified Audit Log. Their default retention is seven days for Entra Free and 30 days for P1/P2. Validate diagnostic export and downstream retention separately; do not assume Purview settings preserve every identity signal. [12] [13]
- Where to review
- Microsoft Purview → Audit; Microsoft Entra → Monitoring & health → Diagnostic settings; your SIEM or archive.
- Evidence to keep
- Retrieved workload events, identity logs, retention mappings and successful export/ingestion tests.
Keep operational and security contacts current
Review tenant contacts and the subscriptions or routing used for Service health, Message center and security notices. Confirm that each notification path reaches a monitored team.
Use team-owned addresses where the service permits them, and document the people responsible for review and escalation. A contact record alone does not subscribe every operations team to every notice. Test delivery and remove dependencies on former employees. [20]
- Where to review
- Microsoft 365 → Organization profile, Service health and Message center preferences; relevant Entra tenant properties.
- Evidence to keep
- Current contacts, subscribed recipients, delivered notices and escalation ownership.
Reconcile security feature coverage and license assignments
Map the controls you rely on to the users and devices that need the corresponding entitlement. Check joiners, movers, leavers and assignment failures, rather than assuming an active policy proves that licensing is correct.
Group-based licensing can support consistent assignment, but group membership, usage location, available subscriptions and provisioning errors still need oversight. Check the current licensing requirements for group-based assignment and dynamic membership. Removing a license is not a complete leaver-data or retention procedure. [14] [15]
- Where to review
- Microsoft 365 admin center → Billing → Licenses; group assignments and provisioning/error reports.
- Evidence to keep
- Control-to-license mapping, reconciled group membership, exception report and error remediation.
Quick reference: controls, owners and licensing
Use this ownership and licensing reference to plan the review. Confirm feature availability and coverage for the users and devices in scope before rollout. The licensing notes identify prerequisites to verify against your current agreement.
| Domain | Control | Target configuration | Typical owner | Licensing considerations |
|---|---|---|---|---|
| Identity and access management | Reduce standing Global Administrator access | Minimize standing Global Administrator assignments; scoped roles and controlled elevation for routine work. | Identity / Entra team | Base role controls; PIM requires Entra ID P2 or eligible ID Governance licensing. |
| Identity and access management | Require MFA and prioritize phishing-resistant methods | MFA for interactive users; phishing-resistant authentication for privileged access. | Identity / Entra team | Conditional Access: Entra ID P1; risk-based policies: Entra ID P2. |
| Identity and access management | Maintain and test at least two emergency (break-glass) accounts | At least two independent cloud-only recovery accounts, protected and tested. | Identity team + security operations | Confirm method availability; emergency role assignment itself does not require PIM. |
| Identity and access management | Remove broad location-based MFA bypasses | No blanket MFA bypass based solely on a corporate or VPN network. | Identity / Entra team | Conditional Access requires Entra ID P1. |
| Identity and access management | Replace routine password expiry with modern password controls | No routine cloud-only expiry unless an applicable requirement calls for it; effective password protection. | Identity / Entra team | Basic cloud password policy; verify premium password-protection features separately. |
| Device compliance and application governance | Define device compliance and a supported BYOD path | Tested device-compliance controls; explicit supported app-protection exceptions for BYOD. | Endpoint / Intune + identity teams | Eligible Intune entitlement plus Entra ID P1 for Conditional Access. |
| Device compliance and application governance | Control app consent and make reviews workable | Restricted user consent, owned administrator review and periodic permission cleanup. | Identity team + application owners | Check the selected consent/governance features; access reviews need eligible governance licensing. |
| Email authentication and threat protection | Deploy SPF, DKIM and DMARC with sender evidence | Legitimate senders authenticated and aligned; DMARC enforcement based on verified mail flows. | Messaging team + DNS / application owners | Applicable mail service and DNS administration; optional reporting tools are separate. |
| Email authentication and threat protection | Review threat policies against Standard and Strict baselines | Reviewed Standard/Strict alignment with documented business exceptions. | Messaging + security teams | Built-in cloud-mail protections; Defender for Office 365 entitlement for applicable advanced features. |
| Email authentication and threat protection | Connect security alerts to an owned response process | Actionable security signals delivered to an accountable response team. | Security operations + platform owners | Relevant Defender workload entitlements; SIEM ingestion and retention can add cost. |
| SharePoint, OneDrive and Teams collaboration security | Limit guest resharing and review external access | Guest sharing limited to approved collaboration needs; external access reviewed. | Collaboration + information owners | SharePoint/OneDrive entitlement; advanced access reviews and labeling may require more. |
| SharePoint, OneDrive and Teams collaboration security | Choose a restrictive default sharing link | A suitable restrictive default, with broader sharing explicitly governed. | Collaboration + information owners | SharePoint/OneDrive entitlement; labeling capabilities depend on the selected features. |
| SharePoint, OneDrive and Teams collaboration security | Control anonymous Teams joining through organizer policies | Anonymous access restricted by organizer need, with tested exceptions. | Teams / collaboration team | Applicable Teams entitlement; advanced verification features may require Teams Premium. |
| SharePoint, OneDrive and Teams collaboration security | Set lobby defaults for the meeting audience | Lobby behavior matched to sensitivity and actual participant types. | Teams / collaboration + business owners | Applicable Teams entitlement; advanced enforcement/templates can require additional licensing. |
| SharePoint, OneDrive and Teams collaboration security | Keep external calendar detail to the minimum needed | Free/busy visibility by default where sufficient; approved exceptions for more detail. | Messaging + business owners | Applicable Exchange Online entitlement. |
| Auditing, monitoring and tenant hygiene | Verify audit collection and the retention you actually have | Required workload and identity evidence collected, retrievable and retained to policy. | Security operations + compliance + identity teams | Eligible Purview Audit entitlement; longer retention and Entra exports depend on feature and storage choices. |
| Auditing, monitoring and tenant hygiene | Keep operational and security contacts current | Current team-owned contacts with tested notification routes. | Microsoft 365 operations | Existing administration features; connected workflow services may add requirements. |
| Auditing, monitoring and tenant hygiene | Reconcile security feature coverage and license assignments | Required security entitlements assigned and reconciled through the user lifecycle. | Microsoft 365 operations + licensing / identity teams | Feature-specific entitlements; confirm group-based licensing and dynamic-group requirements. |
Keep the tenant hardened as it changes
The most useful outcome is a maintained baseline with clear ownership—not a checklist completed once and forgotten. Keep security-relevant changes in change management, review exceptions, and link findings to a remediation backlog.
Use supported PowerShell and Microsoft Graph interfaces to collect evidence and compare settings where practical. Configuration monitoring tools such as Microsoft365DSC can help with drift management, but coverage and authentication vary by workload. Test the automation and review the differences before applying changes.
Use Secure Score, Configuration Analyzer, access reviews and incident findings together. Treat a higher score as a prompt for investigation, not proof that every control is effective. Include adjacent checks such as legacy authentication, mailbox forwarding rules, data protection and recovery in your wider program.
How TechTiera helps Microsoft 365 teams
TechTiera works with enterprise IT and security teams on Microsoft 365 assessments, identity and access policies, collaboration governance, endpoint management and ongoing operations. Our teams can help turn a baseline review into a prioritized improvement plan with clear owners, test evidence and a practical support model.
For platform delivery, explore Microsoft 365 and SharePoint consulting. For operational coverage, see managed IT and infrastructure services and cybersecurity services.
Frequently asked questions
What should a Microsoft 365 tenant security checklist include?
Cover privileged access, MFA and emergency recovery, devices and app consent, email authentication and threat policies, collaboration settings, audit retention, alert ownership and license coverage. Record an owner, evidence and exceptions for each control.
Should we use Security Defaults or Conditional Access?
Security Defaults is a useful baseline without an additional premium license. Conditional Access offers granular policy scope and controls for organizations that need customization, with Entra ID P1 or higher licensing. Prepare and test replacement policies before disabling Security Defaults.
Should emergency access accounts be exempt from MFA?
No. Use a phishing-resistant method that satisfies Microsoft’s mandatory MFA requirements. Exclude recovery accounts from Conditional Access policies that could block or restrict emergency sign-in, and test access independently of everyday administrator dependencies.
Do Intune app protection policies replace device compliance?
Only for the supported applications, platforms and scenarios for which they are designed. App protection secures organizational data in the app; it does not make an unmanaged device compliant. Define and test the separate access paths.
Does Microsoft Purview Audit retain all Entra sign-in logs?
No. Purview audit records and Entra sign-in/audit logs have distinct collection and retention models. Verify each source, the applicable licensing, diagnostic export and downstream retention.
Is Microsoft Secure Score proof that our tenant is secure?
No. It is a useful improvement signal, not a compliance certificate or a substitute for testing policy scope, exceptions, business workflows and incident response. Use it alongside operational evidence.
How often should enterprise teams review tenant security?
As an operating approach, review changes and high-priority findings continuously, reconcile key controls on a regular monthly cycle, and perform deeper access and recovery reviews on a defined schedule. Reassess after major changes or incidents; set the cadence to your environment and obligations.
Sources and further reading
- Microsoft Entra role best practices
- Manage emergency access accounts
- Security Defaults and Conditional Access
- Require phishing-resistant MFA for administrators
- Password policy recommendations
- Require device compliance with Conditional Access
- Configure the admin consent workflow
- Configure DMARC and email authentication
- Configuration Analyzer for threat policies
- Manage SharePoint and OneDrive external sharing
- Manage anonymous participants in Teams meetings
- Manage Purview audit retention policies
- Microsoft Entra audit and sign-in log retention
- Microsoft Entra ID Governance licensing
- Assign or unassign group-based licenses
- Configure Defender alert notifications
- Manage Teams lobby options
- Intune app protection policy overview
- External calendar sharing configuration
- Microsoft 365 Message center



