Microsoft never stops changing.
Somebody has to keep the receipts.
Somewhere in your tenant, right now, there is a setting you've never touched. It works the way it works because Microsoft shipped it that way. And one quiet Tuesday, Microsoft will change its mind — a Message Center post goes out, thirty days pass, the post expires, the default flips, and something in your organisation behaves differently. Nobody clicked anything. That's not a hypothetical. It's the operating rhythm of Microsoft 365.
The disappearing paper trail
Microsoft announces hundreds of changes a year — new features, retirements, security defaults flipping from off to on. The announcements are genuinely useful. They are also temporary: roughly a month after a change lands, its Message Center post expires and takes the details, the screenshots and the deadlines with it. Six months later, when someone asks "when did this behaviour change, and were we told?" — the evidence is gone.
We think that's backwards. So we keep everything.
What lives here
- Every Message Center change, kept forever. Reaching back to September 2023, and not just the posts — every edit Microsoft makes to them, and every screenshot, mirrored before it can vanish. When a post says "(Updated)", we can show you exactly what changed underneath it.
- The full roadmap, tracked from promise to rollout. What's coming, for which products, on which platforms, and when — connected to the announcements that eventually make it real.
- PowerShell commands, actually explained.
Not a parameter dump — every Exchange, Teams and SharePoint cmdlet comes with a plain-English
purpose, advice on how to approach it, and a ready-to-run script that captures state before you
change anything. Because the difference between an admin and an ex-admin is a backup of
$before. - Service incidents with their endings. What broke, what Microsoft said while it was broken, and how it was actually resolved — the part of the story status pages forget the moment the dashboard turns green.
And none of it stands alone: a change links to the commands that control it, a command links to the changes that touch it, an incident links to the tools that diagnose it. One connected picture instead of forty browser tabs.
Where this is heading
Everything above answers "what changed?" The question that actually keeps admins up at night is "does it change anything for us?" That's the engine we're building: connect your tenant with a single admin consent, and serv365 reads your real configuration, compares it against every announced change, and hands you a verdict with the evidence attached — affected, not affected, or we honestly can't tell. It notices when a setting drifts overnight. And it tells your Teams channel, not another dashboard you'll forget to check.
The one rule we won't break
Unknown is never displayed as safe. A tool that quietly skips what it cannot read isn't reassuring — it's manufacturing confidence that nobody should have. If we can't verify something, you'll see that we couldn't, and why. On the internet in 2026, we reckon honesty is a feature.
Microsoft, Microsoft 365, Microsoft Teams, Exchange Online and related names are trademarks of Microsoft Corporation. serv365.ai is independent and not affiliated with or endorsed by Microsoft. Command reference facts derive from Microsoft documentation under CC BY 4.0.