Browse Certification Practice Tests by Exam Family

Microsoft MS-102 Cheat Sheet: Microsoft 365 Admin

Review the Microsoft 365 Administrator (MS-102) scope, tenant administration, identity, collaboration, security, compliance, service health, and admin workflow traps before practicing.

MS-102 is a tenant-administration exam. Use this cheat sheet to keep administration decisions grounded in identity, licensing, workload configuration, security, compliance, monitoring, and lifecycle operations.

Use this with practice. Review the Microsoft 365 administration checkpoints, then return to the MS-102 exam page for sample questions and update tracking.

Open MS-102 practice page Compare Microsoft 365 routes

Exam snapshot

FieldDetail
IssuerMicrosoft
Certification laneMicrosoft 365 Administrator
Exam codeMS-102
Main scopeTenant administration, identity, security, compliance, collaboration, endpoint integration, and service operations
IT Mastery statusSample questions available

Administration map

AreaWhat to knowCommon trap
Tenant and licensingDomains, users, groups, licenses, service plans, admin centers, and service healthTroubleshooting access without checking license or service-plan assignment
Identity and accessMicrosoft Entra ID, hybrid identity, MFA, Conditional Access, roles, and privileged accessAssigning broad admin roles for narrow support tasks
Collaboration workloadsExchange, SharePoint, OneDrive, Teams, external sharing, lifecycle, and policy boundariesTreating every collaboration issue as a Teams-only problem
Security postureBaselines, Defender, audit, alerts, identity protection, and risk reductionIgnoring admin and identity hardening
CompliancePurview retention, DLP, labels, eDiscovery, audit, and information governanceConfusing retention with backup or DLP
OperationsService health, message trace, reports, change management, and support workflowAssuming every outage is Microsoft-side service failure

Must-know distinctions

DistinctionHow to decide
User issue vs tenant issueA user issue affects one or a few accounts; a tenant issue affects broad workloads or policy.
License vs policyLicense enables service availability; policy controls allowed behavior.
Admin role vs workload roleAssign roles scoped to the task and workload instead of defaulting to global administrator.
Exchange vs SharePoint vs TeamsMail, file/site storage, and collaboration settings often overlap but are administered differently.
Retention vs DLPRetention manages lifecycle; DLP manages risky movement or sharing.
Service health vs configurationService health checks Microsoft-side issues; configuration checks tenant-side behavior.

High-yield checklist

  • Confirm user, group, license, service plan, and policy targeting before deeper troubleshooting.
  • Use least-privilege admin roles for support and operations.
  • Review Microsoft Entra configuration when access symptoms span multiple workloads.
  • Use Exchange tools for mail-flow and mailbox issues.
  • Use SharePoint and OneDrive settings for file collaboration and external sharing.
  • Use Teams policies for meetings, messaging, voice, apps, and collaboration behavior.
  • Use Purview controls for retention, DLP, labels, audit, and eDiscovery.
  • Use service health and tenant reports before assuming root cause.
  • Treat Copilot and agent administration as dependent on identity, permissions, data access, and governance.

Common traps

  • Solving a licensing problem with a workload policy change.
  • Granting global administrator to fix a simple helpdesk task.
  • Forgetting that Teams file behavior depends on SharePoint and OneDrive.
  • Treating compliance settings as optional after a legal or retention requirement appears.
  • Ignoring hybrid identity when on-premises and cloud accounts are both involved.
  • Skipping service health checks during broad tenant incidents.

Practice strategy

For MS-102 misses, name the admin surface first: identity, license, Exchange, SharePoint, OneDrive, Teams, Purview, endpoint, or service health. Then identify whether the question asks for configuration, troubleshooting, governance, or escalation.

Revised on Monday, May 25, 2026