Microsoft retired the MS-900 Microsoft 365 Fundamentals exam on March 31, 2026, as recorded in its retired-exam register. The Microsoft 365 services described by that historical exam continue to matter, but planning to book MS-900 now is not a valid certification route. This article focuses on how to choose useful foundational knowledge and translate it into credible administrative work without claiming that the retired badge is still available.
Understand a Microsoft 365 tenant before choosing a credential
A tenant is an identity and administration boundary, not simply an account for Office applications. Confirm which organization controls its domains, who can manage its licenses, how Entra identities are synchronized or created, and which security defaults are enabled. A new employee may have an assigned license while lacking access to a workload because group membership, service plans or access policies are missing. Distinguishing these layers prevents troubleshooting by indiscriminate license changes.
For learning purposes, sketch a tenant map with identity providers, device enrollment, collaboration workloads and data locations. It should explain where responsibility moves from Microsoft-managed service operation to customer configuration and governance.
Treat collaboration as an information architecture problem
Teams, SharePoint and OneDrive overlap but solve different collaboration needs. Teams brings conversation and channels to groups; SharePoint manages sites and shared document structures; OneDrive starts from personal ownership and sharing. Inappropriate external sharing, unmanaged guests or broad default permissions can erase the intended boundaries between them. Choose a test scenario involving a temporary supplier and specify exactly which files should remain accessible after the engagement ends.
Retention, sensitivity labels and access expiration should follow the data category rather than the tool selected. A confidential contract requires a different lifecycle from a public team announcement, even when both are stored in SharePoint.
Separate licensing questions from access questions
Suppose a small consultancy has one hundred employees, contractors from three outside firms and documents with different confidentiality levels. The IT team could default to broad Teams guest sharing, but a better design begins with named project owners and an explicit policy for external access. Define which groups may invite guests, where sensitive work resides and when access ends. Configure a pilot project, verify guest access with a representative account and test removal when the contract expires. Record any content that remains exposed through anonymous links. This example connects Microsoft 365 fundamentals to a business obligation: people should collaborate without accidentally creating permanent third-party access to internal files.
Purchasing a license does not guarantee that a person can reach every feature. Service availability can depend on plan, region, tenant settings and administrative role. When a user reports a missing app, check assigned product and service plans, conditional access policies, device compliance and the workload’s own permission model before requesting an upgrade. Document what evidence led to the answer, because changes to subscriptions can affect recurring spend.
A small reference table for representative job roles is more useful than memorizing promotional feature lists. State which functions each role needs and which functions it must not see.
Apply a basic security operating model
MFA and phishing-resistant authentication address sign-in risk; they do not replace access reviews or device security. Test what happens when an employee leaves: token sessions, group membership, shared mailbox access, external shares, enrolled devices and ownership of automated workflows need separate attention. A departure checklist should assign responsibility for each item.
Zero Trust in this context means evaluating every access request against identity, device and session risk rather than assuming internal network location establishes trust. Start with a low-risk test group, measure impact and define a rollback for a policy that blocks legitimate work.
Use compliance controls for known data obligations
A useful comparison of Microsoft 365 administration roles is between a frontline support technician, collaboration owner and compliance operator. The support person needs to diagnose an individual’s access problem; the collaboration owner governs who belongs in a project team; the compliance operator may need to preserve a record even when the user wants it deleted. Give each role only the tools and privileges required for its obligation. When a customer asks “Why can my colleague open this document but I cannot?”, the response should identify the effective permission and organizational policy, not just repeat a licensing brochure. A tenant demonstration with two user groups and a guest account can reveal whether the configuration enforces those distinctions.
Retention policies and legal holds are not interchangeable. A retention setting keeps data for an organizational period; a hold can preserve relevant material for a legal or investigation process. Sensitivity labels classify and protect documents while data loss prevention evaluates actions such as inappropriate sharing. These mechanisms need business rules and administrators who understand false positives.
In a lab, follow a document from creation through sharing, renaming and deletion. Record which permissions and retention controls apply at each point. The outcome should explain what a user can do versus what the organization must preserve.
Select current learning by role, not by old exam code
A useful baseline exercise is to investigate a mailbox complaint without buying an additional license. First inspect assigned products and individual service plans. Then check whether the account is enabled, whether mail provisioning has completed and whether a policy blocks the client connection. Compare sign-in records and Exchange-side indicators if available. An administrative change should have a hypothesis: enabling the correct service plan may solve the issue, while temporarily removing conditional access can create an unnecessary security risk. Explain the result to the user in ordinary terms and keep an audit trail for the team. These operational habits remain relevant even though the MS-900 test has retired.
A help-desk analyst may need strong tenant navigation and troubleshooting; an identity engineer needs deeper Entra administration; a compliance specialist needs policy interpretation and evidence handling. Microsoft’s current certification catalog is the right place to evaluate those separate roles. A historical MS-900 practice checklist can orient vocabulary, but should not be sold as evidence of coverage for a different modern exam.
Use the old syllabus as a diagnostic: can you explain tenant identity, licensing, collaboration, security and support? Where the answer is weak, build a working demonstration instead of purchasing obsolete exam-specific materials.
MS-900 is part of Microsoft’s credential history. Its most useful legacy is the ability to explain how identity, service access, information protection and administration fit together in a Microsoft 365 environment.