Microsoft 365 change management: Message center, service health and release preferences

Microsoft 365 changes every week: features switch on, settings move and older capabilities retire on dates you don't choose. You can't stop the flow, but you can make sure each change that matters reaches an owner before it reaches your users. In this post I'll build a lightweight change routine from Message center, Planner, service health, release preferences and the Graph service communications API.

Prerequisites#

• Message center access for every owner. Most admin roles can read Message center, but some can't, including Intune Administrator, Compliance Administrator, Conditional Access Administrator and Reports Reader. Assign the Message center reader role to anyone who should read and share posts without other admin rights.
• Someone for privacy notices. Posts tagged Data privacy are visible only to Global Administrators and the Message center privacy reader role. Give that role to your privacy or compliance lead instead of creating another Global Administrator.
• A plan in Microsoft Planner owned by the admin team, for example "Microsoft 365 change", with one bucket per workload.
• For reporting: the Microsoft Graph PowerShell SDK and consent for ServiceMessage.Read.All and ServiceHealth.Read.All.

Step-by-step#

1. Give every workload an owner#

Write down who owns Exchange Online, SharePoint and OneDrive, Teams, Microsoft 365 Apps, Intune and Windows, Purview and Copilot. Message center views are personal: reading or archiving a post changes only your view, so ownership has to live outside the Inbox. That's what Planner is for in step 4.

2. Tune Message center preferences#

In the Microsoft 365 admin center, open Health › Message center and select Preferences. Each admin sets their own:

• Custom view: keep only the services you own selected. This trims your Inbox; other admins still see whatever they've chosen.
• Email: the weekly digest is on by default and goes to your primary address. Pick the services the digest covers, then decide separately whether you want immediate emails for major updates and for data privacy messages; privacy posts are never included in the digest. You can add up to two email addresses separated by a semicolon, and a shared team mailbox is a good choice.

Digests and emailed posts are sent in English only, even if you read Message center with machine translation.

3. Learn which signals mean "act now"#

Use Choose columns to show Act by, Relevance and Category (Category is hidden by default), then triage with this table:

For a limited set of Teams features, Status for your org also shows Scheduled, Rolling out or Launched, which tells you when a feature actually reaches your tenant.

4. Sync posts to Planner#

In Message center, select Planner sync and set up syncing to your change plan: choose the plan and bucket, filter which posts are synced and decide whether to import existing messages. Each post becomes a task you can assign, date and close. Quote the message ID (MC plus digits) in tickets and support calls.

5. Get service health alerts#

Message center covers planned change; Health › Service health covers what's broken right now. Incidents are significant problems with clear user impact, while advisories are limited in scope. On that page, pick your services and turn on email notifications for incidents and advisories to the team mailbox. If users report a problem that isn't listed, use Report an issue on the same page. For an Intune-flavoured checklist, see Is it me or is it Intune?

6. Create an early-warning ring with Targeted release#

Go to Settings › Org settings › Organization profile › Release preferences. The options are Standard release (the default), Targeted release for everyone and Targeted release for select users. Choose the last one and add IT staff, helpdesk leads and a few departmental champions, so they see eligible changes before everyone else. Not every feature uses Targeted release, and Microsoft 365 Apps update channels are managed separately, so treat it as an early warning, not a gate.

7. Report with the service communications API#

Microsoft Graph exposes the same data for reports. This lists recent major changes and Act by posts, unhealthy services and open issues:

Connect-MgGraph -Scopes "ServiceMessage.Read.All","ServiceHealth.Read.All"

# Message center posts changed in the last 7 days that need attention
Get-MgServiceAnnouncementMessage -All |
    Where-Object { $_.LastModifiedDateTime -ge (Get-Date).AddDays(-7) -and
                   ($_.IsMajorChange -or $_.ActionRequiredByDateTime) } |
    Sort-Object ActionRequiredByDateTime |
    Select-Object Id, Title, ActionRequiredByDateTime, IsMajorChange,
        @{ n = 'Services'; e = { $_.Services -join ', ' } }

# Services that aren't currently healthy
Get-MgServiceAnnouncementHealthOverview |
    Where-Object Status -ne 'serviceOperational' |
    Select-Object Service, Status

# Open incidents and advisories
Get-MgServiceAnnouncementIssue -All |
    Where-Object { -not $_.IsResolved } |
    Select-Object Id, Service, Classification, Status, Title

For a scheduled job, use an app registration with the application permissions of the same names and certificate authentication instead of an interactive sign-in.

Verify#

• The weekly digest arrives in the team mailbox and covers only the services you selected; the privacy owner gets data privacy emails separately.
• New posts appear as Planner tasks, and every open task has an owner and a due date.
• An Intune administrator holding Message center reader can open Health › Message center.
• Release preferences list your pilot users under Targeted release.
• The script's output matches Message center filtered on the Major update tag.

Tips & gotchas#

• Run a short weekly triage. Walk the Planner tasks and write one line per relevant change for the helpdesk. That habit is the real control; the tooling just feeds it.
• Share, don't screenshot. Share emails a post to anyone; Copy link works only for people with Message center access.
• Give feedback. A thumbs down with "This change isn't relevant to my org" helps tune the relevance recommendations.
• Check the roadmap. Feature posts often link to the public roadmap, now called the Microsoft AI at Work Roadmap (formerly the Microsoft 365 Roadmap).
• Go mobile. The Microsoft 365 Admin app shows Message center with push notifications.

References#

• Track new and changed features in the Microsoft 365 Message center
• Set up a weekly Message center digest (Defender for Office 365 walkthrough)