How to track service retirements across multiple client tenants
Vendor deprecation notices are scattered across dozens of individual client tenants and separate vendor emails, leaving no single source of truth. This forces managed service providers to hunt for updates manually, leading to last-minute client warnings and reactive troubleshooting instead of proactive guidance.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
- 1Using third-party archive tools and custom AI workflows like Merill's Message Center ArchiveDid this help you?
- 2Setting up custom RSS feeds and PowerAutomate flows to aggregate specific vendor blogs into Teams channelsDid this help you?
- 3Treating the message center as a weekly triaged queue with custom tracking matricesDid this help you?
- 4Relying on community roundups and forums like Reddit's r/sysadmin monthly change listsDid this help you?
- 5Skimming weekly message center items manually and maintaining a spreadsheet mapping tenants to workloads to determine impact before creating tickets.Did this help you?
- 6Building custom PowerShell scripts with undo logsDid this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“One thing we have never done well is notifying customers of changes to their tenant or retiring of certain services. Anytime we have notified them, it always seems to be last minute, or even worse, they ask us for support on something we should be going to them about!”source ↗
“I'm pulling my hair out with Claude trying to figure this out because it doesn't seem to know what I am looking for. I'm looking for a single-source of truth for all notifications Microsoft send out regarding depreciation of services, retiring of applications, etc.”source ↗
“It just seems insane to me that there's no single source of truth from Microsoft for this stuff. As an MSP, I don't want to have to rely on notifications from dozens of different tenants, it makes no sense”source ↗
“Throw the other gazillion vendors we support into the mix and it’s very hard to stay on top of things and guide customers through retirements, services changes and whatnot. While remaining profitable and sane.”source ↗
“Message Center in each tenant is still the source. The work is tagging which items are real for that client.”source ↗
“Do not auto-open a ticket for every retirement. Skim the weekly MC items, mark impact (Teams phone, SharePoint, auth), then open a ticket only if that tenant uses the feature.”source ↗
“A simple sheet of tenants vs workloads beats a tool that opens 40 tickets. RMM is for the ones that need an endpoint change. It does not replace reading the MC item.”source ↗
“I kept doing the same manual cleanup across client machines: disabling the same handful of services, ripping out the same bloatware, flipping the same privacy settings, then finding out six months later that nobody remembered what changed.”source ↗
Where this came up
People with this problem also raised
- 3How to manage software updates across multiple client accounts
- 12How do you keep track of clients, projects, deadlines, and follow-ups?
- 4Why is supplier communication spread across so many apps?
- 4Tracking down unmanaged SaaS accounts when an employee leaves
- 6Client tries to reverse cancellation during offboarding
- 3How to handle month-end close for multiple clients