Microsoft retired the MS-900 Microsoft 365 Fundamentals exam on March 31, 2026. It is no longer a test new candidates can book, so a present-tense “MS-900 practice test” guide needs careful framing. The older exam remains useful as a historical map of foundational Microsoft 365 concepts—cloud service models, productivity workloads, security and trust, and licensing and support—but passing an unavailable test cannot be a legitimate current preparation goal. The better use of this material is to identify which Microsoft 365 concepts remain relevant to the job you want to perform, then choose up-to-date learning and practical exercises.
What MS-900 covered while it was available
The assessment was intended for people who needed a broad understanding of Microsoft 365 rather than specialist administration skills. It introduced the value of cloud services, described common productivity and collaboration capabilities, surveyed security, compliance and privacy concepts, and considered subscription management, support and billing. A successful candidate needed to understand how these subjects connect in an organization; the exam was not proof that someone could troubleshoot a tenant-wide identity outage or design a complex Teams environment.
The historical blueprint can still help structure a first conversation with a small business migrating from local file servers and independently managed email to Microsoft 365. A responsible discussion would cover user identities, mailbox and document migration, collaboration requirements, data retention, employee offboarding and expected support cost. Those decisions remain concrete even though the MS-900 examination has ended.
Connect service models to operational responsibility
Cloud software changes the distribution of responsibilities; it does not remove them. A provider may operate much of the underlying infrastructure while the customer still decides who has access, what information is stored, which retention rules apply and how staff are trained. An introductory exercise is to take a common failure—a former employee retaining access to a shared resource—and identify which controls the organization must configure and monitor.
Compare the purpose of software as a service with managed platform and infrastructure approaches without implying that one is universally better. Microsoft 365 is predominantly a collection of SaaS productivity and collaboration services; understanding the model helps explain why administrators configure policies and access while Microsoft operates the service infrastructure. The precise balance of duties still depends on the product and the organization’s obligations.
Understand how the workloads interact
Exchange Online, SharePoint, OneDrive, Teams and the productivity applications support different tasks and often share identity and content-management boundaries. For example, a project group collaborating through Teams might store documents in SharePoint-backed locations, exchange messages and organize meetings. If a colleague cannot access a shared file, fixing Teams notifications alone will not resolve a SharePoint permission problem. Product names are not a substitute for understanding the flow of work and data.
Study a realistic scenario: an organization must share a financial review with one external accountant for two weeks. What should be shared, who approves it, how should access expire, and where will the organization look if the file is downloaded? The answer involves policy, identity, content permissions and evidence—not only the presence of a “Share” button. Explore the administrative concepts using a properly authorized tenant or a controlled lab, not production data you do not own.
Security and compliance begin with identity
A foundation-level understanding should distinguish authentication from authorization. Multifactor authentication helps verify a sign-in; it does not decide whether someone should be allowed to read a confidential document. Conditional access and device-related decisions address context and policy, while role assignment limits administrative privilege. The details of particular Microsoft licenses and feature availability change, so confirm product eligibility instead of repeating an old MS-900 course’s feature table.
Threat protection, data-loss prevention, retention and audit capabilities serve different purposes. A retention policy does not guarantee that every inappropriate external share will be prevented; a data-loss-prevention rule can be useful but depends on classification and the way content is handled. A well-designed explanation names the threat and the control’s limit. It also considers how a policy affects legitimate workflows, such as responding to an external regulator or collaborating with a supplier.
Use licensing examples to practice careful reasoning
Microsoft 365 plans vary by product family, subscription, customer type and add-on. A sales brochure from a retired exam may give the wrong feature comparison today. Instead, make a requirements table for a hypothetical twenty-person company: business email, document collaboration, secure remote access, information protection, desktop application needs and administrative support. Compare the currently published service descriptions against that checklist; record what is included, what requires an add-on and what cannot be concluded without asking the provider.
Include lifecycle costs. Staff onboarding, device management, support, data migration and retention can matter more than the headline subscription price. A low-cost license does not deliver a sound deployment if the required controls are unavailable, and the most comprehensive plan may be unnecessary for a narrowly scoped team. This exercise develops the judgment the old exam aimed to introduce without pretending the retired objectives remain a current price list.
How to practice after retirement without an exam target
Replace test-day drilling with a sequence of concrete demonstrations. First, map how a user signs in and gains access to collaboration services. Second, trace where a document lives when someone shares it through a Teams channel. Third, design a least-privilege offboarding process that removes access while preserving records the organization must keep. Fourth, define who responds when an external user is accidentally granted access. Fifth, compare licensing options using current documentation, including any feature restrictions and support assumptions.
After each exercise, describe the result to a colleague who does not administer Microsoft 365. Explain why the policy exists, what a user experiences and how an administrator can audit or reverse the change. That combination of clarity and operational understanding is more durable than memorizing a retired exam’s practice answers.
For readers who already passed MS-900, the credential’s history remains part of their learning record. For new candidates, Microsoft recommends using its current credential catalogue to select an exam that fits a real job role, rather than assuming a named successor with identical objectives exists. The current Microsoft exam retirement listing confirms that MS-900 can no longer be taken.
Practice the lifecycle of an employee identity
Consider a company hiring an employee who needs mail, document collaboration and access to a particular project team. The onboarding sequence must establish a verified identity, assign appropriate subscriptions and access, and confirm that the user can work without inheriting unnecessary privileges. A sensible lab records which administrative action creates access and how that access is removed when duties change. Simply checking whether the user can sign into a browser does not prove the intended security model.
Now reverse the scenario. The employee leaves while some project files must remain available to the business and a legal retention requirement applies. Suspending the account alone may not address active sessions, application permissions, shared links or delegated access. Deleting everything may conflict with required record preservation. Map the actions to responsible owners and distinguish access revocation, content ownership transfer, retention and eventual deletion. This practical reasoning illustrates why cloud fundamentals involve people, policy and workflows as well as service names.
Distinguish collaboration settings from information governance
Suppose a department allows external guests in its collaboration workspace but forbids sharing a particular classification of financial records. A workspace permission may control who can enter, while information-protection and data-handling rules constrain what content may move. Administrators need to understand the layers instead of expecting one tenant setting to solve every risk. Test an allowed example and a restricted example using non-sensitive sample documents, then confirm the outcome and audit trail.
Document which behaviors depend on licensing or enabled features. If a hypothetical small business has no entitlement to a control recommended in a guide, the plan must use an available control or reconsider the subscription. A foundation-level discussion should teach how to verify these assumptions, not promise every security feature is included in every plan. This keeps the historical MS-900 learning map useful without misrepresenting Microsoft 365 products in 2026.
Keep the foundation, retire the booking advice
Good foundational knowledge lets a reader recognize the boundaries between communication, content, identity, compliance and licensing. Those distinctions continue to influence tenant design and day-to-day support. The MS-900 code now identifies a retired exam, not a new registration opportunity. Use the former syllabus to organize understanding, but use current product documentation and role-specific training to decide what to learn next.