Microsoft 365 Message Centre and Change Management

The Microsoft 365 Message Centre is a centralized dashboard within the Microsoft 365 admin center (admin.microsoft.com) that provides official, proactive communications from Microsoft about changes to the Microsoft 365 services your organization uses. These changes include new features, updates, deprecations, service maintenance, known issues, and required actions. The Message Centre is the primary tool for change management in Microsoft 365, replacing the older 'Service Health Dashboard' for planned changes. It is accessible to users who have been assigned the following admin roles: Global Admin, Service Support Admin, Message Centre Reader, or Reports Reader.

Microsoft 365 is a continuously evolving cloud service. New features are rolled out regularly, and existing features are updated or deprecated. Without a structured communication channel, IT administrators would be blindsided by changes that could break integrations, confuse users, or require policy updates. The Message Centre ensures that admins have at least 30 days' notice for most changes (and up to 12 months for major changes) so they can plan, test, and communicate internally.

Microsoft uses a staged rollout process for changes. When a change is planned, a message (also called a post or communication) is created in the Message Centre system. The message contains:

Messages are published to the Message Centre API, which the admin center UI consumes. Admins can filter messages by service, category, status, and date range. They can also mark messages as 'Dismiss' (to hide from default view) or 'Star' (to highlight).

- Default Retention: Messages are retained for 30 days after the change is completed or the message is marked as 'Completed'. After that, they are automatically removed from the Message Centre but can be accessed via the Message Centre archive (if enabled) or by downloading as CSV. - Message Types: - Plan for change: Requires admin action (e.g., update a URL, enable a new feature). At least 30 days notice. - Stay informed: No action required, but admins should be aware (e.g., new feature rollout, UI change). - Fixed: A known issue has been resolved. No action required. - Rollout Phases: Microsoft rolls out changes in phases (e.g., First Release, Standard Release, Targeted Release). The Message Centre indicates which release rings are affected. - Email Notifications: Admins can subscribe to receive daily or weekly digest emails summarizing new and updated messages. This is configured in the Message Centre preferences. - Message Centre Reader Role: This role grants read-only access to the Message Centre and service health. It is a least-privilege role for monitoring changes without full admin rights.

While the Message Centre is primarily accessed via the admin center UI, there are PowerShell and API options for programmatic access.

PowerShell (Exchange Online):

To retrieve Message Centre posts using the Exchange Online PowerShell module:

Get-MessageTrace | Where-Object {$_.MessageType -eq "ServiceMessage"}

Note: This cmdlet is primarily for message trace, not the Message Centre. The correct cmdlet for Message Centre is not directly available in standard PowerShell; instead, use the Microsoft Graph API.

Microsoft Graph API:

To list all Message Centre posts:

GET https://graph.microsoft.com/v1.0/admin/serviceAnnouncement/messages

Authorization: Bearer token with ServiceMessage.Read.All permission.

Admin Center UI Verification:

Large enterprises often automate the ingestion of Message Centre posts into their internal ticketing systems (e.g., ServiceNow). Using the Microsoft Graph API, you can:

Example PowerShell script to export messages to CSV:

# Connect to Graph API (requires module)
Connect-MgGraph -Scopes "ServiceMessage.Read.All"

# Get all active messages
$messages = Get-MgAdminServiceAnnouncementMessage -Filter "isAssigned eq true"

# Export to CSV
$messages | Export-Csv -Path "MessageCentre_$(Get-Date -Format 'yyyyMMdd').csv" -NoTypeInformation

The Message Centre is the cornerstone of change management in Microsoft 365. By proactively monitoring and acting on its posts, IT administrators can ensure smooth transitions, minimize user disruption, and maintain compliance. For the MS-900 exam, focus on understanding the purpose, roles, categories, retention, and the distinction from Service Health.

A large financial services company with 10,000 users relies on legacy email clients that use Basic Authentication (POP/IMAP). A Message Centre post announces that Microsoft will permanently disable Basic Authentication for Exchange Online on a specific date (e.g., October 1, 2022). The IT team must migrate all users and applications to Modern Authentication (OAuth 2.0). They assign a project manager to monitor the Message Centre, identify affected apps via usage reports, and communicate with business units. They use the Message Centre API to automatically create tickets in ServiceNow for each application owner. The team configures Conditional Access policies to block Basic Authentication gradually. They also set up a pilot group with Targeted Release to test the change. After successful migration, they mark the message as dismissed and export the CSV for compliance. Without the Message Centre, the company would have faced a sudden outage, causing significant business disruption.

A multinational retail chain uses Microsoft Teams extensively for collaboration. A Message Centre post announces a new 'Together Mode' feature with a phased rollout over three months. The 'Stay informed' message includes details on the user experience and admin controls (e.g., ability to disable the feature). The IT team decides to enable the feature for all users immediately because it enhances engagement. They prepare a short training video and an FAQ document. They use the Message Centre to track the rollout status and verify that the feature is available in their tenant. They also monitor Teams admin center reports to see adoption rates. The team dismisses the message after the rollout is complete. This proactive communication prevents confusion and support calls when users suddenly see a new button.

A large engineering firm with 5,000 users and massive data storage receives a Message Centre post that SharePoint Online storage limits are increasing from 1 TB to 25 TB per site collection. The 'Plan for change' message requires no action from admins; it's informational. However, the IT team uses this information to update their internal documentation and inform users that they no longer need to request storage increases. They also adjust their data retention policies. The Message Centre helps them stay ahead of capacity planning. If they had missed the message, they might have unnecessarily purchased additional storage or rejected user requests.