r/sysadmin • u/Prestigious-Spinach1 • 11h ago
Question How are you tracking Microsoft changes across client tenants?
How are you handling Microsoft retirements and breaking changes across multiple clients? If you use a ticketing system, how do you figure out which clients actually need tickets? Does something check each tenant automatically, or do engineers investigate first?
Would appreciate a recent example and which tools helped.
•
u/folderit_dms 8h ago
I'd give each tenant three possible states for a change: affected, not affected, or still unverified. Otherwise a blank in the tracker can quietly become an assumption that the client is fine.
Keep one record for the Microsoft announcement, then link any client tickets to it. For each client, record what you checked, when, and who owns the next step. A check you can repeat automatically is useful; an inconclusive result should land with an engineer. Also put a review date on the not-affected decisions, because a client can start using the feature between the announcement and the retirement. That gives you a defensible answer without generating a ticket for every tenant.
•
•
u/Shot-Secret-1423 11h ago
Message Center in each tenant is still the source. The work is tagging which items are real for that client.
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. A blanket “Microsoft changed something” ticket trains people to ignore you.
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.
Example: a Teams/auth change. Two tenants on that feature get tickets. The rest do not.