Updated April 15, 2024: We have updated the rollout timeline below. Thank you for your patience.
Whiteboard previously stored whiteboard files in Azure storage. In 2022, Whiteboard switched to OneDrive as the storage location for most newly created boards. We are making a client-based migration available for your organization soon.
This message is associated with Microsoft 365 Roadmap ID 117394
[When this will happen]
The client-based migration experience will begin in July 2024 (previously May). We will provide an additional update as we get closer.
[How this will affect your organization]
Any user who launches an eligible Whiteboard client (Whiteboard on Windows, Whiteboard in Teams desktop/web) will automatically kick off a non-blocking migration of all their whiteboards. Depending on how many whiteboards they have, on average the process will take between a few seconds to a few minutes.
The migration will provide many benefits for your organization and users on the migrated boards, including:
- Features unique to whiteboards stored in OneDrive, such as Follow, Commenting, and more.
- Improved performance on whiteboards now stored in OneDrive.
- Improved compliance and security associated with whiteboard being stored in OneDrive.
There is no possibility to delay the migration.
[What you need to do to prepare]
The migration will happen naturally and automatically for most users in your organization with no disruption, but please ensure that users are aware they need to launch Whiteboard in one of the previously mentioned clients in order to keep their content prior to the conclusion of migration (date to be announced)
In the unlikely case that a user’s whiteboards fail to migrate, they will see an error banner. We will attempt to migrate the board again in 30 days. If the board contains important information, we recommend the user copy the content to a new whiteboard.
Users will be able to see which boards have not migrated in a dedicated section on the board picker. Admins will be able to verify what whiteboard content remains in Azure and obtain the userIDs via our PSH cmdlets, if you wish to proactively notify users to get their content.
As we get closer to the release of the client-based migration experience we will provide additional information via Message center.
