Microsoft has confirmed a double-barreled deadline for Whiteboard users: personal account holders must export their boards before September 5, 2026, or see them permanently wiped, while enterprise admins have until August 22 to complete migration of legacy Azure-hosted boards to OneDrive—the same day the standalone Whiteboard app enters its final days. The announcements, first reported by Windows Report, also set a September 14 date for the standalone Whiteboard app’s end of support, pushing all business users into Teams or the web client.

What Actually Changes on August 22

The immediate impact splits between personal and commercial use. For anyone signed into Whiteboard with a personal Microsoft account—Outlook.com, Hotmail, Live.com, or similar—August 22 is the last day you can create or edit anything. After that, the app flips to view-only mode. You’ll still see your boards until September 5, but at that point Microsoft deletes them permanently. No recovery, no archive.

For businesses and schools, August 22 marks the cutoff for the migration tooling that moves older Azure-stored Whiteboards into OneDrive. Microsoft’s own support documentation describes an automatic migration trigger that starts when a user opens Whiteboard in Teams, a browser, or the Windows app, but Windows Report is clear: the migration capability itself retires on that date. Any Azure-hosted board still sitting in a “Not migrated” state after August 22 becomes inaccessible dead data. The standalone Whiteboard application then reaches end of support on September 14, leaving Teams and the web client as the only official entry points for commercial customers.

What It Means for You

For Home Users

If you’ve ever sketched out a project plan, brainstormed with a study group, or doodled a flow chart in Whiteboard using a personal Microsoft account, this is your moment. On August 22 you lose the ability to change anything. Two weeks later the files themselves are gone. Exporting preserves a static copy—typically a PNG image or PDF—not an interactive whiteboard. That means you’ll need to import the image into a supported tool like OneNote, Miro, or even a Word document if you want to keep collaborating. There is no grace period after September 5, and Microsoft’s published guidance says deleted content cannot be restored.

For IT Administrators

The enterprise story is less about a shutdown and more about a forced migration with a hard stop. Whiteboards created after 2022 already live in OneDrive. Older ones, built before Microsoft made OneDrive the default storage, still sit in Azure. Microsoft’s automated migration moves those boards when users open them from a supported client, but the process isn’t foolproof. Common failures include OneDrive quota limits, missing OneDrive assignments, and the quiet killer: departed employees or long-dormant accounts whose boards never get triggered.

After August 22, the migration pipeline closes. Any Azure board that hasn’t been moved becomes inaccessible. At that point, even the 90-day recovery window described in Microsoft’s support article becomes irrelevant, because there’s no way to initiate the migration after the tool retires. The standalone app’s September 14 retirement then forces the last holdouts into Teams or the browser, but that doesn’t help with content still stuck in Azure.

How Whiteboard Storage Got Here

The current crunch is the final chapter of a storage overhaul Microsoft began in 2022. Before that, every Whiteboard—commercial and personal—lived in Azure. When Microsoft switched to OneDrive for new boards, it touted better security, revision history, eDiscovery, and access to newer features. The catch: boards already in Azure stayed there until a user triggered migration. Microsoft rolled out the migration process in phases starting in December 2024, targeting a 2025 completion, but the persistence of “Not migrated” boards shows that the opt-in, trigger-by-use model left plenty of content behind.

Personal accounts never got the migration option. Instead, Microsoft opted to let the service wither. The company hasn’t publicly detailed why personal Whiteboard is being retired, but the pattern fits a broader push to anchor consumer productivity around Microsoft 365 subscriptions and deprecate free-tier standalone tools. The standalone Windows app’s retirement parallels similar moves with other legacy applications, funneling users toward Teams—a hub that Microsoft increasingly treats as the control center for business collaboration.

Your Action Plan

For Personal Account Holders

  1. Open every Whiteboard you care about. You can do this in the Windows app, a browser whiteboard.office.com, or—if you still have access—the mobile app.
  2. Export a snapshot. From the settings menu (typically a gear or three-dot overflow), choose Export and save the file. The output is usually a PNG or PDF; it won’t be editable, but it’s your record.
  3. Move the content. If you need to keep collaborating, import the exported image into an app that supports interactive whiteboarding. OneNote, Miro, or even PowerPoint can embed the image. If you used Whiteboard for light sketching, a simple screenshot might suffice.
  4. Finish by August 22 if possible. While the deletion doesn’t happen until September 5, you lose the ability to open and export from the desktop app after editing is blocked, and the view-only web experience may not offer the export option you want.

For Enterprise IT Teams

  • Run a tenant inventory immediately. Use the Get-WhiteboardsForTenant PowerShell cmdlet (documented on Microsoft Learn) to see how many Azure-hosted boards remain. If the cmdlet returns a non-zero count, you have work to do.
  • Map owners to boards. Identify which users own those Azure boards. Pay special attention to accounts for employees who have left the organization or haven’t signed in for months. Microsoft provides PowerShell cmdlets to transfer ownership from a dormant user to an active one, allowing you to trigger migration.
  • Trigger migration. For each board, have the owner open Whiteboard in Teams, the web client, or the Windows app before August 22. This starts the automatic migration. Users will see a progress message at the top of the canvas.
  • Fix failures proactively. The three common errors Microsoft flags are: “unable to migrate—will retry later” (sometimes resolves automatically after 30 days, but you don’t have that long), “OneDrive is out of space,” and “couldn’t find your OneDrive.” Address quota issues, assign OneDrive storage to users who lack it, and monitor the “Not migrated” section that appears in the app when boards can’t be moved.
  • Validate the migration. Once a board migrates, confirm that it appears in the owner’s OneDrive under the Whiteboard folder. Recovered Azure boards can be restored for up to 90 days after migration, but only if the migration completes before the tool retires.
  • Prepare for the standalone app’s end of support. After September 14, the Windows app stops receiving updates and may become unavailable. Instruct users to switch to Teams or the web client now, and update any internal documentation or training materials. For Teams channel Whiteboards, note that Microsoft plans to move storage from individual OneDrive accounts to the channel’s SharePoint site later in 2026—a change that will eventually simplify permissions but doesn’t affect the immediate migration crisis.

What Comes Next

Once the August and September deadlines pass, Whiteboard becomes strictly a business tool backed by OneDrive and SharePoint. The retirement of personal Whiteboard accounts and the standalone app clears the deck for Teams-centric collaboration, and the coming SharePoint storage shift for channel boards hints at a more tenant-driven architecture. For IT admins, the lesson from this migration is clear: Microsoft’s gradual, opt-in transitions can leave critical data dangling unless you run the audit commands and force the issue before the tooling disappears. Keep an eye on the Microsoft 365 roadmap for final dates on Azure board deprecation and any additional migration windows—but for now, the clock is ticking.