Microsoft Whiteboard: legacy boards deleted October 16

If your tenant still holds whiteboards in Microsoft's legacy Azure storage, there is a date worth putting somewhere visible: October 16, 2026. Microsoft's wording is unusually blunt for a lifecycle notice.

“On October 16, remaining Azure-based Whiteboards are permanently deleted and cannot be recovered.”

Most end-of-support dates on this blog describe software that keeps running while you carry the risk. This one describes content that stops existing. That is a different category of deadline and it deserves different handling.

The sequence, in Microsoft's own words

• Before September 25, 2026 — “Complete migration of all remaining Azure-based Whiteboards before September 25, 2026.”
• September 25, 2026 — “On September 25, migration ends and remaining Azure boards become read-only.” This is the point of no return for self-service: the migration path itself closes, not just the boards.
• October 16, 2026 — permanent deletion, no recovery.
• November 30, 2026 — “On November 30, 2026, the Azure Whiteboard service shuts down.”

Read that ordering carefully, because the gap between the first two dates is where the real risk lives. September 25 is three weeks before the deletion, and it is the date that actually constrains you — after it, remaining boards are read-only and the migration route is gone. A team that discovers the problem on October 1 has content it can read, cannot migrate, and will lose fifteen days later.

Migration is user-triggered, which is the operational problem

Migration happens when an affected user opens Whiteboard on an eligible client. That sounds convenient and it creates a specific failure: the boards least likely to migrate belong to the people least likely to open them.

Long-term leave. Secondments. Anyone who left the organisation with a board still owned by their account. A board created for a project that finished in 2021 and has not been opened since — which, given these are boards old enough to predate the OneDrive move, describes a large share of them.

Microsoft also notes that mobile apps do not trigger the Azure-to-OneDrive migration. A user who works entirely from a phone or tablet will not migrate anything by using Whiteboard normally, however often they open it.

Find out what you have, and read the caveat on the tool

Microsoft gives administrators a direct answer: “Administrators can check whether their tenant has Azure Whiteboards by using Get-WhiteboardsForTenant in the WhiteboardAdmin PowerShell module.”

⚠️ And then it attaches a caveat that changes how you should read the output. Inventory data is precalculated and can take approximately two weeks to reflect recent changes. So a report showing zero Azure boards is evidence about roughly a fortnight ago, not about now — and with three weeks left before the migration route closes, a two-week-stale inventory is most of your remaining runway. Run it now rather than in late September, and run it twice.

The part a regulated firm should think about first

This is our read rather than Microsoft's, and we flag it as ours. If your organisation is subject to retention obligations or has ever been through a legal hold, a permanent deletion date on a content store is not purely an IT scheduling question.

Two things follow from that. First, content sitting in the legacy Azure backend is not in OneDrive, which means it is not covered by the retention and discovery tooling your Microsoft 365 policies are written against. A retention policy that says "collaboration content is retained for seven years" may quietly have an exception nobody documented, and the exception is about to resolve itself by deleting the content.

Second, and more sharply: if any of those boards are within the scope of a current hold, an automated permanent deletion is exactly the event a hold exists to prevent. Nobody will action it — it happens on Microsoft's schedule whether or not the hold exists. That is a conversation to have with whoever owns legal or compliance before October 16, and it is a short conversation if the answer is "we have none", which is the most likely answer and still worth having on the record.

Microsoft's two pages disagree, and we could not reconcile them

Three things are ending here and they are easy to conflate: the Azure storage backend, the boards inside it, and the standalone Whiteboard apps for Windows, iOS and Android. The first two have clean, consistent dates. The third does not.

Microsoft's migration article states: “The standalone Windows, iOS, and Android apps retire on September 14, 2026.”

Microsoft's dedicated retirement article states: “The standalone Microsoft Whiteboard apps for Windows, iOS, and Android retire on October 16, 2026. This retirement applies to users with work or school accounts and users with personal Microsoft accounts.”

Thirty-two days apart, same three platforms, same product. The obvious explanation would be that the two pages address different audiences — but the second page closes that door itself by naming both work or school accounts and personal Microsoft accounts. We read both pages directly on September 5, 2026 and could not reconcile them.

⚠️ There is also third-party reporting, including a Microsoft 365 Message Center notice, giving the standalone app deprecation as November 30, 2026 — which is the date Microsoft's migration article assigns to the Azure service shutdown, not the apps. We have not verified that ourselves and are not asserting it. We note it because it means there are potentially three values circulating for one event, and anyone planning against a number they read secondhand should check which of the three they have.

The practical answer is boring and safe: plan against September 14, the earliest of the dates, because being early costs a support conversation and being late costs the app. The contradiction is not a reason to wait for clarity. It is a reason not to build a plan on a single page.

What we would do this week

• Run Get-WhiteboardsForTenant today. Not because the answer is urgent, but because the data is two weeks stale and you want the clock started.
• If the answer is not zero, identify the owners. Only the owner's activity triggers migration, so the list you actually need is people, not boards — and specifically people who are absent, departed, or mobile-only.
• Treat September 25 as the deadline, not October 16. The later date is when content disappears; the earlier one is when you lose the ability to do anything about it.
• Decide whether any of it matters. These are boards nobody has opened in years. Some organisations should migrate them; some should confirm in writing that they are content to lose them. Both are defensible. Silence is not — because on October 16 silence becomes a decision that was made for you.
• Tell users the product is not going away. The most likely internal reaction to "Whiteboard is being retired" is alarm about a tool people use in Teams every day, which is not what is happening.

Sources

Both Microsoft support articles were read in full on September 5, 2026: Migration of Whiteboards from Azure to OneDrive and Retirement of the standalone Microsoft Whiteboard apps. Neither page displays a last-updated date, which is itself worth knowing when two of them disagree. If Microsoft corrects either page, we will update this post and say which one moved.

If you would rather have the tenant inventory, the owner list and the migrate-or-accept decision handled as a bounded piece of work, scope it with us.