Microsoft Whiteboard standalone apps are retiring: what enterprise users need to do before October 2026

Microsoft Whiteboard is not going away, but the way you access it is about to change permanently. The standalone desktop and mobile apps are retiring, legacy whiteboards stored in Azure face permanent deletion, and the deadlines are closer than many organisations realise.

Here is the full picture, including the revised dates Microsoft issued on 25 August 2026, because the original timeline caused enough confusion that Microsoft extended it.

What is actually changing

Microsoft has been storing new Whiteboard files in OneDrive since January 2022. Any whiteboard created before that date is likely still sitting in Azure-backed storage, and those are the boards at risk.

The retirement covers two distinct things:

1. The standalone apps. The Microsoft Whiteboard apps for Windows, iOS, and Android retire on 16 October 2026 for work, school, and personal Microsoft accounts. After that date, opening the app shows a retirement screen instead of your boards.

2. Legacy Azure-backed whiteboards. Boards stored in Azure that have not been migrated to OneDrive will be permanently deleted on 16 October 2026. There is no recovery after that point.

The standalone apps retiring does not delete your OneDrive-backed whiteboards. Those remain fully accessible through Microsoft Teams and the Whiteboard web app at whiteboard.cloud.microsoft.

The revised timeline in full

Microsoft’s original message centre advisory (MC1441775, issued 28 July 2026) set earlier deadlines. After pushback and confusion, Microsoft updated the schedule on 25 August 2026. The dates that matter now are:

Date	What happens
25 September 2026	Migration tooling is retired. Remaining Azure-backed boards become read-only
16 October 2026	Remaining Azure-backed boards are permanently deleted. Standalone apps retire
30 November 2026	Legacy Azure Whiteboard service shuts down entirely

The read-only window between 25 September and 16 October gives users a final chance to view and export content, but migration is no longer possible after 25 September.

What this means for you

If you are an enterprise or education user, Whiteboard itself is not going anywhere. Microsoft is simply consolidating access through Teams and the web. Your OneDrive-backed boards created after January 2022 are unaffected. The action you need to take is about the older boards, not the product itself.

If you use the standalone app, you will need to switch to Whiteboard inside Microsoft Teams or via the browser. The functionality is the same; it is the delivery mechanism that changes.

If you have a personal Microsoft account, the situation is more limited. After 22 August 2026, editing requires an eligible Microsoft 365 Business account. Personal account holders could view and export their boards until 5 September 2026, after which that content is gone.

How migration works (and where it can go wrong)

For most enterprise users, migration is automatic. When a user opens Microsoft Whiteboard on Windows, in Teams on desktop or web, or in the web app, their legacy Azure boards begin migrating to OneDrive in the background. It takes a few minutes and does not interrupt work.

There are a few important exceptions:

• Mobile clients do not trigger migration. If a user only opens Whiteboard on their phone, their boards will not migrate automatically.
• Surface Hub and Teams Rooms devices. Whiteboards initiated on these devices are stored in Azure and will not migrate through the standard user-triggered flow. Admins need to identify these boards separately.
• Boards owned by departed employees. If the original owner has left the organisation, their OneDrive may not be provisioned or may have been deleted. Those boards are stranded and will not migrate without admin intervention.

What admins need to do before 25 September 2026

The migration tooling closes on 25 September 2026, so there is limited time for remediation. Microsoft recommends the following steps:

1. Identify unmigrated boards. Use the WhiteboardAdmin PowerShell module with the Get-WhiteboardsForTenant cmdlet to see which users still have Azure-stored boards. This requires Global Administrator or SharePoint Administrator rights.

2. Address stranded boards. For users who have left the organisation or never had OneDrive provisioned, admins will need to transfer ownership before migration can complete.

3. Check meeting room boards. Actively look for boards initiated on Surface Hub or Teams Rooms devices. A search filtered only by creation date may miss these.

4. Communicate with users. Particularly anyone who only accesses Whiteboard on mobile, because their boards will not have auto-migrated.

5. Update internal guidance. Point employees to Whiteboard in Teams or at whiteboard.cloud.microsoft. Remove any references to the standalone app from training materials or support documentation.

Why the deadlines keep shifting

Microsoft’s original announcement in late July 2026 did not include an accompanying blog post, which meant many users and admins encountered the retirement notice via a pop-up in the Windows app rather than through any proactive communication. That caused significant confusion. The 25 August 2026 update extended the deadlines and added more clarity, but the sequence of changes has left some organisations uncertain about which dates actually apply.

The dates above reflect the most recent published guidance. Admins should monitor the Microsoft 365 message centre for any further updates, particularly for message centre IDs MC1441775, MC1469559, and MC1469957.

The bottom line

Whiteboard as a product continues. The standalone app does not. If your organisation has legacy Azure-backed boards, the window to migrate them closes on 25 September 2026, and the boards themselves are permanently deleted on 16 October 2026. The migration process is largely automatic once a user opens an eligible client, but the edge cases around mobile users, meeting room devices, and departed employees require active admin attention.

The safest approach is to run the PowerShell audit now, identify anything that has not yet migrated, and make sure those boards are either migrated or exported before the end of September.