Every one of these arrived as an announcement before it arrived as a problem. Azure ACS stopped working on 2 April 2026, and legacy SharePoint sign-in followed on 1 May.
The Visio export for Power Automate went on 14 July and the Power Automate mobile app goes on 31 August. Phased blocking of Exchange Web Services starts on 1 October, and a block of AI Builder credits disappears on 1 November.
Six dates, one year, largely the same tenants. Not one of them was a fault, an outage or a bug. They were all published in advance, and most small businesses found out afterwards.
The notice reaches an address, not a person
Microsoft publishes this material properly. The Message center carries upcoming changes and required actions, with filters and an email digest an administrator can switch on (checked: 2026-08-20). The change management guidance sets out how the phases are meant to work (checked: 2026-08-20).
None of that helps if the administrator account belongs to a supplier you stopped using in 2022. Nor does it help when the digest lands with the founder, who reads it between two site visits and cannot tell which of the eleven items matters.
That is the actual failure, and it is organisational rather than technical. The information is public, dated, and free. What is missing is a person whose job it is to read it and decide.
A notice with no owner is just a fault with a delay built into it.
The cost is easy to miss because it never appears as one line. It shows up as a scanner that stopped emailing, an accountant who cannot open a folder, an approval that quietly stopped notifying anyone. Each gets fixed as its own small emergency, at the worst possible moment, usually by whoever is nearest.
Where the changes are actually published
Four places cover almost everything a small business needs.
The Message center in the Microsoft 365 admin centre carries service changes and required actions for your specific tenant, which makes it the only one of the four that is personalised to you.
The Power Platform deprecations list covers Power Automate, Power Apps and Dataverse. That is where the mobile app retirement appears, alongside changes to connectors and audit data (checked: 2026-08-20).
Product documentation carries the detail once you know what to look for, including the Exchange Web Services timeline and its final dates (checked: 2026-08-20).
Your own suppliers matter too. The firm that installed your scanners or your warehouse system knows whether their product depends on something being switched off, and they will usually only say so if you ask.
Twenty minutes a month
The routine that works in a small business is deliberately unambitious, because an ambitious one gets abandoned by March.
Once a month, open the Message center and read only the items marked as requiring action. Ignore the feature announcements. Most months this takes minutes and produces nothing, and that is a good outcome rather than a wasted meeting.
For anything that does require action, write three lines: what it affects here, who owns it, and when it has to be done.
If you cannot answer the first line, that is your finding. Something in the business depends on a thing nobody can name.
Then put the date in the same calendar you use for everything else. Not a task list nobody opens, and not a note in an inbox. A change with a date and no calendar entry is a change you will meet again in October, at the point where it stops working.
Twice a year, ask your suppliers one question in writing: does the current version of what you sold us depend on anything Microsoft has announced it is retiring. Keep the answers.
Turning a notice into scheduled work
The difference between a firm that copes and a firm that gets surprised comes down to one thing: whether a notice becomes a piece of scheduled work with a name attached.
A useful entry has four parts and fits on one line: the change, the business process it touches, the person accountable, and the date it must be finished by. "EWS retirement, scanner-to-email in the warehouse, Marek, by mid-September" is a plan. "Check EWS thing" is a note that will still be there in December.
Two of the 2026 changes make good practice cases. The Exchange Web Services retirement needs an inventory before it needs a decision. The Power Automate mobile app retirement needs a decision about where approvals are recorded, which is a process question wearing a technical hat.
What not to do
Do not forward the digest to everyone. A message sent to five people is owned by none of them, and it teaches the team that these emails can be ignored.
Do not wait for something to break as a filter. It works, in the sense that you will definitely find out. It costs a customer-facing failure each time, and those are expensive in a way the fix never is.
Do not respond to every announcement. Most items in the Message center are features you have not enabled and will never use. Reading everything is how people stop reading anything.
Do not confuse a notice with a project. Some changes need an afternoon and a supplier email. Treating each one as an initiative is the other way to guarantee that none of them get done.
When this needs someone from outside
Plenty of firms can run this themselves. If one person holds administrator access, understands roughly what the business depends on, and can spare twenty minutes a month, keep it in house and spend the money elsewhere.
It stops being realistic when nobody can say what the tenant contains, or when administrator access sits with a supplier you no longer work with. The same applies when the honest answer to "what would break" is a shrug. It also stops working when the person who could do it is the same person who has to be on site all week, which is the usual situation in a firm of thirty.
That is the gap our ongoing technology partnership is built for. Someone who already knows your setup reads the notices, tells you which three of the eleven matter, and books the work before it becomes an outage.
None of this is glamorous. The measure of it is that the next dated change comes and goes and nobody in the business notices, which is exactly what it should feel like.