大网数据广告活动
启动与系统组件

Windows 365 BCDR Known Issues

· 52CE 我爱测

Learn about known issues that involve Windows 365 disaster recovery, including workarounds and updated fixes.

This article addresses a known issue that's related to Windows 365 Business Continuity and Disaster Recovery (BCDR) scenarios.

Classic Outlook is corrupted after disaster recovery failover or failback

After you restore a Cloud PC from a snapshot during a disaster recovery failover, or upon failing back to the primary region after the disaster, users might encounter an error message when they start classic Outlook.

This issue occurs because the Outlook offline cache becomes corrupted because the client and the server become out of sync during a failover. The client on the snapshot reflects a past state relative to the server's current status. The process of resynchronizing the Offline Storage Table (OST) file can take time.

This process doesn't cause any data loss.

Workaround

After you complete a failover or failback operation, delete the Cloud PC's OST file.

This action forces Outlook to rebuild the search index and the offline cache of the mailbox. This process doesn't cause any data loss.

Resolution

Use the new Outlook app. The new Outlook app uses a different caching mechanism that eliminates this synchronization issue.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
See source applicability · Source date 02/12/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。