014 - Microsoft 365 Message Center: 2,500 changes a year, but who's reading them?!

How many unread items are sat in your Message Center right now? We counted at the top of this one, and between the three of us we had 2,179.

In episode fourteen of 365 Explained, Ben and Zach are joined by Tom Arbuthnot of Empowering.Cloud, whose team watches close to a hundred tenants' Message Centers, to work out how you turn that pile into decisions: what to read, who owns it, and what happens next.

In this episode, we explore:

◆ Roadmap versus Message Center, and why one is public direction of travel and the other is what's actually landing in your tenant

◆ Why no two tenants see the same list: licensing, geo, tenant type, and messages targeted right down to a single customer

◆ The numbers — around 2,500 messages a year for a typical tenant, of which roughly 260 genuinely matter

◆ 60% of messages changed at some point last year, against a product that keeps no change history at all (so good luck proving what it originally said)

◆ What notice you actually get, and why it's a window rather than a date

◆ Who can see Message Center, and why the internal comms team expected to announce the changes usually can't

◆ Frontier, Standard and Deferred: three release audiences replacing the targeted release model you already know

◆ The native gap. No assignment, no sign-off, no audit trail, and a Planner sync that keeps dragging your triaged items back to square one

◆ Multi-tenant and MSPs: Lighthouse saves you the logins and not much else, and partners get no early access or secret feed

◆ The two MCP servers, one you point a URL at and one that wants an enterprise app, consent and an exposed endpoint (guess which one we'd recommend)

◆ Azure updates — a separate feed again, and just as noisy

◆ What good looks like: named owners per product area, items that get assigned rather than eyeballed, and a written record of why you said yes or no

Plus the cautionary tale: a message about Android devices, an Intune team who said "we don't allow Android, ignore it", and every Teams phone in the building going offline. Teams phones run Android.

Whether you've got a Message Center you've never opened, or you're the one person in the org who does read it and then can't get anyone to act on it, this one's for you.

So who owns Message Center where you work? Be honest, "whoever notices first" is an answer. Let us know.

Follow the show for a new episode on the last Thursday of the month. The video version is on YouTube: https://youtu.be/Hj1rLZHhLEM