This chapter covers the Microsoft 365 Roadmap and preview features, a topic that appears in 5-10% of MS-900 exam questions under objective 4.3 (M365 Pricing). You'll learn how Microsoft releases new features through a structured pipeline: private preview, public preview, targeted release, and standard release. We'll also explore the Microsoft 365 Roadmap site, Message Center, and how organizations can control feature rollout. Understanding this lifecycle helps you plan adoption, manage change, and answer exam questions about release channels and preview options.
Jump to a section
Think of Microsoft 365's release process as a major airline launching a new fleet of aircraft. The airline doesn't just put a new plane into service immediately. First, the manufacturer builds a prototype and tests it in secret — this is the 'Microsoft internal' or 'private preview' phase. Then, a select group of frequent flyers and maintenance crews get to fly the prototype on limited routes — this is 'public preview' or 'targeted release.' These testers report issues, suggest improvements, and the airline refines the design. After validation, the airline rolls out the aircraft in stages: first on a few domestic routes (targeted release), then gradually to international routes (standard release). Some features, like new seat designs, may be optional and only available on certain planes (optional updates). The airline also publishes a roadmap showing which new planes are coming, when they'll be tested, and when they'll enter full service. This roadmap is updated quarterly and lets airlines (organizations) plan for pilot training, maintenance schedules, and passenger experience changes. If a critical safety issue is found during testing, the airline may delay the rollout or issue a recall — similar to Microsoft pausing a feature rollout or posting a known issue. The key takeaway: you can choose when to adopt new features, just as an airline can choose to be an early adopter of a new aircraft or wait until it's proven across the fleet.
What is the Microsoft 365 Roadmap?
The Microsoft 365 Roadmap is a publicly accessible website (https://www.microsoft.com/en-us/microsoft-365/roadmap) that lists all upcoming, rolling out, and launched features for Microsoft 365 services. It provides a single source of truth for feature availability across products like Teams, Exchange Online, SharePoint, OneDrive, Microsoft 365 Apps, and more. The Roadmap is updated regularly — typically weekly — and includes:
Feature ID: A unique numeric identifier for each feature.
Title: A concise name for the feature.
Description: A brief explanation of the feature and its benefit.
Product: Which Microsoft 365 service the feature applies to (e.g., Teams, SharePoint).
Cloud Instance: Whether the feature is available for Worldwide (Standard), GCC, GCC High, DoD, or other sovereign clouds. Many features roll out to Worldwide first, then to government clouds later.
Release Phase: One of: In development, Preview (private or public), Rolling out (targeted or standard), Launched, or Cancelled.
Last Modified Date: When the roadmap entry was last updated.
More Info Link: A URL to a detailed article, often in the Microsoft 365 admin center Message Center.
The Roadmap is free to access without a subscription. It allows filtering by product, release phase, and cloud instance. For example, you can filter to see only Teams features in public preview for GCC.
Why the Roadmap Exists
Microsoft 365 is a continuous service — new features are added monthly, sometimes weekly. The Roadmap gives IT professionals and business decision-makers visibility into upcoming changes so they can:
Plan training and communication for end users.
Assess impact on existing workflows and integrations.
Test preview features in non-production environments.
Prepare for deprecations or changes that may break current processes.
The Roadmap also supports the Microsoft 365 adoption framework by helping organizations stay ahead of changes rather than reacting to them.
How Features Move Through the Pipeline
Microsoft uses a phased approach to release features. Not all features go through every phase, but the typical lifecycle is:
1. In Development: The feature is being built. No external access is available. The Roadmap entry appears to signal intent. 2. Private Preview: A limited set of customers (often invited by Microsoft) can test the feature in a production or sandbox environment. Access is by invitation only, and participants must sign a non-disclosure agreement (NDA) in some cases. Private preview is not available to all tenants. 3. Public Preview: The feature is made available to all tenants that opt in. In the admin center, you can enable preview features under Settings > Org settings > Release preferences. Public preview features are not fully supported and may have bugs. They are not subject to SLAs. Organizations should test them in non-production environments. 4. Targeted Release: The feature is released to a subset of tenants that have opted into targeted release. There are two targeted release options: - Targeted release for everyone: All users in the tenant get features early. - Targeted release for selected users: Only a specific security group (usually IT staff) gets early access. 5. Standard Release: The feature is released to all tenants worldwide. This is the default release channel. Standard release can take weeks or months to complete, as Microsoft rolls out gradually to monitor telemetry and fix issues.
Some features skip preview and go directly to targeted/standard release. Others may be cancelled after preview.
Release Preferences in the Admin Center
To control feature rollout, you configure release preferences in the Microsoft 365 admin center:
- Navigate to Settings > Org settings > Release preferences. - Choose one of three options: - Standard release: Users get features when Microsoft fully releases them (default). - Targeted release for selected users: Choose a security group (max 10,000 users) to receive features early. - Targeted release for everyone: All users get features early (not recommended for large tenants).
Important: Release preferences apply to Microsoft 365 services (Exchange, SharePoint, Teams, etc.) but NOT to Microsoft 365 Apps (Word, Excel, etc.). Microsoft 365 Apps use the Microsoft 365 Apps update channels: Current Channel, Monthly Enterprise Channel, Semi-Annual Enterprise Channel (Preview), and Semi-Annual Enterprise Channel. These are configured separately via Group Policy or Intune.
Message Center
The Message Center is another critical tool. Located in the admin center under Health > Message Center, it provides:
Service change messages: Planned changes that may require action.
Feature updates: New features rolling out.
Deprecation notices: Features being removed.
Incident postings: Service health issues.
Messages have a severity level (High importance or Normal) and a timeline. You can mark messages as read, dismiss them, or share them with colleagues. The Message Center also allows you to set up email digests (daily or weekly) to stay informed.
Microsoft 365 Roadmap vs. Message Center
The Roadmap is forward-looking (what's coming). Message Center is about changes happening now or soon. Both are essential for change management.
Preview Features and Licensing
Some preview features require specific licenses. For example, Microsoft 365 Copilot preview required an E3 or E5 license plus a Copilot add-on license. Always check the Roadmap entry or associated documentation for licensing requirements. Preview features are typically included in the existing subscription, but some may require additional purchase.
Opting Out of Preview Features
You can disable preview features entirely. In the admin center under Settings > Org settings > Release preferences, select Standard release. This ensures your tenant receives only fully released features. However, some preview features may be enabled by default for all tenants — check the Message Center for such announcements.
APIs and PowerShell
You can programmatically access the Roadmap and Message Center using Microsoft Graph APIs. For example:
GET /admin/serviceAnnouncement/messages retrieves Message Center posts.
GET /admin/serviceAnnouncement/issues retrieves service health issues.
PowerShell cmdlets like Get-MessageCenterMessage (from the Exchange Online module) also work.
Interaction with Other Technologies
Microsoft 365 Admin Center: Central console for managing release preferences.
Microsoft Graph: APIs for automating change management.
Azure AD: Security groups used for targeted release.
Microsoft 365 Apps Admin Center: Manages update channels for Office apps.
Service Health Dashboard: Shows current service health, distinct from Message Center.
Timers and Defaults
Targeted release: Features typically arrive 1-2 weeks before standard release.
Standard release rollout: Can take 2-4 weeks for worldwide deployment, sometimes longer for complex features.
Preview duration: Varies; some features are in preview for months, others for weeks.
Roadmap update frequency: Weekly, but can be more frequent.
Message Center retention: Messages are available for 30 days after the change is completed.
Exam Focus on Release Channels
For MS-900, you need to know:
The difference between private preview, public preview, targeted release, and standard release.
How to configure release preferences in the admin center.
That targeted release can be for everyone or selected users.
That release preferences apply to cloud services, not Office apps.
The purpose of the Roadmap and Message Center.
That preview features are not covered by SLAs.
That government clouds (GCC, GCC High, DoD) often receive features later than Worldwide.
Common exam scenario: An organization wants to test a new Teams feature before it is released broadly. They should enable targeted release for a pilot group. Another scenario: A company wants to see upcoming features for planning — they should check the Microsoft 365 Roadmap.
Detailed Walkthrough of a Feature Release
Let's trace a hypothetical feature: "Teams Meeting Recording Auto-Expiration."
In Development: Microsoft announces on the Roadmap that it's building auto-expiration for Teams recordings. No action available.
Private Preview: Microsoft invites 50 large enterprise customers to test. They provide feedback. Bugs are fixed.
Public Preview: The feature appears in the admin center under Preview features. Any tenant can enable it by toggling a setting. The Roadmap status changes to "Rolling out (Preview)."
Targeted Release: Tenants on targeted release see the feature enabled automatically. They can test with their pilot users.
Standard Release: After 3 weeks, Microsoft starts rolling out to all tenants. The Roadmap status changes to "Rolling out (Standard)." After 2 weeks, all tenants have the feature. Roadmap status becomes "Launched."
If a critical issue is found during standard release, Microsoft may pause the rollout and post a message in Message Center. They may also revert the feature for some tenants.
Key Values and Numbers
Targeted release: Max 10,000 users in selected users group.
Message Center retention: 30 days post-change.
Roadmap update: Weekly.
Preview features: No SLA, no support guarantee.
Release preferences: Three options (Standard, Targeted for selected, Targeted for everyone).
Cloud instances: Worldwide, GCC, GCC High, DoD.
Configuration Verification
To check your release preferences via PowerShell:
Connect-MsolService
Get-MsolCompanyInformation | Select-Object -ExpandProperty ReleaseTrackValues: 0 = Standard, 1 = Targeted for selected, 2 = Targeted for everyone.
To set release preferences:
Set-MsolCompanySettings -ReleaseTrack 1Note: The MsolService module is deprecated; use the Microsoft Graph PowerShell SDK instead.
Summary of Key Points
The Roadmap lists all upcoming features with release phases.
Message Center provides actionable change notifications.
Release preferences control when users get new features.
Preview features are optional and not fully supported.
Targeted release helps organizations test and prepare.
Government clouds have separate release schedules.
Office apps use update channels, not release preferences.
Access the Microsoft 365 Roadmap
Navigate to https://www.microsoft.com/en-us/microsoft-365/roadmap. No sign-in is required. The page displays a table of features with columns: Feature ID, Title, Product, Cloud Instance, Release Phase, Last Modified. Use filters at the top to narrow by product (e.g., Teams), release phase (e.g., Preview), or cloud instance (e.g., GCC). Click on a feature title to see a detailed description and a link to the Message Center post if available. This is the primary source for planning upcoming changes.
Configure Release Preferences in Admin Center
Go to the Microsoft 365 admin center (admin.microsoft.com). Navigate to Settings > Org settings > Release preferences. You'll see three options: Standard release, Targeted release for selected users, and Targeted release for everyone. Select the desired option. If choosing targeted release for selected users, you must specify a security group. Note: This setting affects cloud services only, not Office apps. Changes take effect within a few hours. Verify by checking the Roadmap for features in 'Rolling out (Targeted Release)' phase.
Enable Public Preview Features
In the admin center, go to Settings > Org settings > Release preferences. Under 'Preview features,' you can enable or disable the ability to receive public preview features. By default, this is enabled. If disabled, your tenant will not receive any preview features even if you are on targeted release. Note that some preview features are enabled tenant-wide by default and require explicit opt-out via Message Center. Always check the Message Center for preview feature announcements.
Monitor Message Center for Changes
In the admin center, go to Health > Message Center. You'll see a list of posts categorized as 'Change messages' or 'Feature updates.' Each post has a title, description, affected services, and a timeline. Filter by 'High importance' to see changes requiring action. You can mark messages as read, dismiss them, or share them. Set up email digests (daily or weekly) under Preferences. Message Center posts are retained for 30 days after the change is completed.
Test Features in Targeted Release
After configuring targeted release for a security group, have the pilot users test the new features. They will see features that are in targeted release phase. Monitor feedback and report issues to Microsoft via the admin center feedback tool. Use the Roadmap to know which features are expected. After validation, you can plan broader rollout when features move to standard release. Remember: targeted release features are still under development and may change.
Plan for Standard Release Rollout
Once a feature reaches standard release, it will gradually appear for all users. The Roadmap status changes to 'Rolling out (Standard).' Monitor the Message Center for any known issues or rollout pauses. Communicate with end users about the change using the information from the Roadmap and Message Center. After the rollout is complete, the Roadmap status becomes 'Launched.' Archive any relevant communications.
Enterprise Scenario 1: Global Financial Institution
A multinational bank with 50,000 employees uses Microsoft 365 across 30 countries. They need to ensure new features don't break regulatory compliance or critical workflows. They configure targeted release for a security group containing 200 IT staff and power users. When Microsoft announces a new Teams compliance recording feature on the Roadmap, the IT team enables it in targeted release and tests it in a sandbox environment. They validate that recordings are stored in the correct geo-location and comply with local data residency laws. After two weeks of testing, they plan user training and communication. When the feature reaches standard release, they are ready. Common mistakes: forgetting to disable preview features for non-pilot users, which can cause confusion if a feature changes unexpectedly. They also monitor the Message Center for any deprecation notices about older features.
Enterprise Scenario 2: Small Business with Limited IT
A 50-person legal firm uses Microsoft 365 Business Basic. They have no dedicated IT staff. They rely on the default standard release channel. When Microsoft rolls out a new SharePoint document library template, it appears automatically. The firm's admin checks the Message Center weekly and reads the Roadmap monthly to stay informed. They once accidentally enabled targeted release for everyone, causing early access to a preview feature that had a bug. They reverted to standard release within a day. Lesson: For small organizations without testing resources, standard release is safest. They also set up email digests from Message Center to avoid missing critical changes.
Enterprise Scenario 3: Government Contractor with GCC
A defense contractor operates in GCC High. Their Microsoft 365 Roadmap shows that features often arrive 6-12 months after Worldwide. They plan their adoption cycles accordingly. When a new secure messaging feature appears in preview for GCC High, they must request access through their Microsoft representative. They cannot use the public preview toggle because preview features for government clouds are managed differently. They rely heavily on the Message Center for GCC-specific announcements. A common issue: assuming a feature's Worldwide release date applies to GCC. They always check the cloud instance filter on the Roadmap.
Performance and Scale Considerations
For large tenants (>10,000 users), targeted release for selected users is limited to 10,000 users. You may need multiple pilot groups.
Message Center posts can be overwhelming; use filters and email digests to manage.
Roadmap data is cached; refresh the page to see latest updates.
Preview features may impact performance; test in non-production environments.
Rollout pauses can affect your timeline; have contingency plans.
What Goes Wrong When Misconfigured
Enabling targeted release for everyone can cause end-user confusion if features change frequently.
Disabling preview features prevents access to beneficial early capabilities.
Ignoring Message Center posts can lead to missed deprecations (e.g., a feature you rely on being removed).
Assuming all features follow the same pipeline — some skip preview entirely.
Not differentiating between release preferences (cloud services) and update channels (Office apps).
What MS-900 Tests on This Topic (Objective 4.3)
The exam focuses on:
Understanding the purpose of the Microsoft 365 Roadmap and Message Center.
Differentiating between private preview, public preview, targeted release, and standard release.
Knowing how to configure release preferences in the admin center.
Understanding that release preferences apply to cloud services, not Office apps.
Recognizing that preview features are not covered by SLAs.
Knowing that targeted release can be for everyone or selected users (max 10,000).
Understanding that government clouds have separate release schedules.
Common Wrong Answers and Why Candidates Choose Them
1. Wrong: "Targeted release gives users access to preview features." Why chosen: Candidates confuse targeted release with preview. Targeted release is for features that are fully developed but not yet released to all. Preview features are still in development. Targeted release features are more stable.
2. Wrong: "The Roadmap shows only features that are already released." Why chosen: Candidates think a roadmap shows past releases. Actually, it shows upcoming, rolling out, and launched features — past releases are removed.
3. Wrong: "Release preferences control updates for Office apps like Word." Why chosen: Overlooking the distinction between cloud services and client apps. The exam tests this distinction directly.
4. Wrong: "All preview features require additional licensing." Why chosen: Some preview features do require licenses, but most are included in existing subscriptions. The exam may present a scenario where licensing is needed.
Specific Numbers, Values, and Terms That Appear Verbatim
Targeted release selected users: up to 10,000 users.
Message Center retention: 30 days.
Roadmap update frequency: weekly (though not explicitly stated on exam, it's common knowledge).
Release preference options: Standard, Targeted for selected users, Targeted for everyone.
Preview features: no SLA, no support.
Cloud instances: Worldwide, GCC, GCC High, DoD.
Edge Cases and Exceptions the Exam Loves to Test
Government clouds: Features arrive later; preview may require special request.
Office apps vs. cloud services: Release preferences don't affect Office apps; those use update channels.
Private preview: Invitation-only, NDA may be required.
Cancelled features: Sometimes features are removed before release; Roadmap shows 'Cancelled' phase.
Default preview setting: Preview features are enabled by default; you must opt out.
How to Eliminate Wrong Answers Using the Underlying Mechanism
Ask yourself:
Is this about a cloud service (Teams, Exchange) or an Office app (Word, Excel)? If Office app, release preferences don't apply — look for update channel options.
Is the feature still in development? If so, it's not available via targeted release; only preview.
Is the question about planning? Then Roadmap is the answer. About active changes? Message Center.
Is the organization in a government cloud? Then expect delays and different preview access.
By understanding the pipeline stages and their characteristics, you can eliminate distractors like "targeted release for everyone" when the scenario describes a pilot group, or "Message Center" when the question asks about future features.
The Microsoft 365 Roadmap lists upcoming features with release phases: In development, Preview, Rolling out, Launched, Cancelled.
Release preferences in the admin center control when users get new cloud service features: Standard, Targeted for selected users (max 10,000), or Targeted for everyone.
Preview features are not covered by SLAs and may have limited support.
Release preferences do NOT affect Microsoft 365 Apps (Office); those use update channels.
Government clouds (GCC, GCC High, DoD) receive features later than Worldwide.
Message Center provides change announcements and is accessible under Health > Message Center.
Targeted release is for testing features that are ready for production but not yet broadly released.
These come up on the exam all the time. Here's how to tell them apart.
Microsoft 365 Roadmap
Lists all upcoming, rolling out, and launched features.
Publicly accessible without sign-in.
Updated weekly.
Provides high-level planning information.
Includes feature IDs and cloud instance filters.
Message Center
Provides actionable change notifications and timelines.
Requires admin sign-in to Microsoft 365 admin center.
Updated in real-time as changes occur.
Includes severity levels and required actions.
Retains messages for 30 days after change completion.
Mistake
Targeted release gives access to preview features.
Correct
Targeted release provides early access to fully developed features that are ready for production but not yet rolled out broadly. Preview features are still in development and may be unstable. Targeted release features are more mature.
Mistake
The Microsoft 365 Roadmap shows all past features.
Correct
The Roadmap shows upcoming, rolling out, and recently launched features. Features are removed after they are fully launched and have been in the 'Launched' phase for a while. It is not an archive.
Mistake
Release preferences control updates for Microsoft 365 Apps like Word and Excel.
Correct
Release preferences only affect cloud services (Teams, SharePoint, Exchange Online). Microsoft 365 Apps (Office) use separate update channels: Current Channel, Monthly Enterprise Channel, Semi-Annual Enterprise Channel.
Mistake
All preview features require an additional license.
Correct
Most preview features are included in the existing subscription. Some, like Microsoft 365 Copilot preview, required a separate add-on license. Always check the Roadmap entry for licensing details.
Mistake
The Message Center and the Service Health Dashboard are the same thing.
Correct
Message Center provides proactive change announcements (new features, deprecations). Service Health Dashboard shows real-time service incidents and outages. They serve different purposes.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Use the Microsoft 365 Roadmap at https://www.microsoft.com/en-us/microsoft-365/roadmap. It lists all features with their release phases. You can filter by product, cloud instance, and phase. For features that are rolling out, check the Message Center in the admin center for detailed timelines and required actions.
Targeted release delivers features to a subset of users (either everyone or a selected security group) earlier than standard release. Standard release is the default and delivers features to all users after they have been validated in targeted release. Targeted release helps organizations test and prepare for changes.
Yes. In the admin center under Settings > Org settings > Release preferences, you can disable 'Preview features' to prevent your tenant from receiving public preview features. However, some preview features may be enabled by default; you may need to opt out via a setting in the specific service.
No. Release preferences only affect cloud services (Teams, SharePoint, Exchange Online). Microsoft 365 Apps use update channels: Current Channel, Monthly Enterprise Channel, Semi-Annual Enterprise Channel. These are configured separately via Group Policy or Intune.
Messages are retained for 30 days after the change is completed. After that, they are removed. You should download or archive important messages if you need to keep them longer.
Private preview is an invitation-only phase where a limited set of customers can test a feature under NDA. It is not available to all tenants. Public preview, in contrast, is available to any tenant that opts in.
Enable targeted release in the admin center (Settings > Org settings > Release preferences). You can choose targeted release for selected users (up to 10,000) or for everyone. This gives you early access to features that are in the targeted release phase.
You've just covered Microsoft 365 Roadmap and Preview Features — now see how well it sticks with free MS-900 practice questions. Full explanations included, no account needed.
Done with this chapter?