Microsoft 365でのCloudM Migrate移行日付の修正

CloudM Migrate is commonly used to migrate メールボックス from Google Workspace, on-premises Exchange, and other platforms into Microsoft 365. When CloudM uploads emails to Microsoft 365, the Exchange Online transport pipeline processes each message and adds a Receivedヘッダー with the current upload timestamp. This becomes the most recent Receivedヘッダー in the message's ヘッダーチェーン.

Microsoft 365 uses this delivery timestamp across its entire ecosystem. Outlook desktop, Outlook on the web, Outlook mobile, and even Microsoft's AI-powered features all reference the same PR_MESSAGE_DELIVERY_TIME property, which is set from the migration Receivedヘッダー. Unlike Google Workspace (where the web client can mask the issue), Microsoft 365 displays the 移行日 consistently across all its client applications.

The consistency of the 間違った日付 across all Microsoft 365 clients makes the problem すぐに visible to every ユーザー. After a CloudM migration to Microsoft 365, the entire 組織 sees the same symptom: every email in every メールボックス appears to have been received on the 移行日. There is no client-specific workaround; the 日付の破損 is embedded in the message metadata at the サーバーレベル.

Microsoft 365's unified date handling means the 移行日 appears everywhere simultaneously. Outlook desktop, OWA, Outlook mobile, Teams email integration, and Microsoft Search all show the wrong received date. Users cannot escape the in正しい日付s by switching to a different Microsoft 365 application.

For Microsoft 365 管理者, the impact extends to management and コンプライアンス tools. The Exchange Admin Center, Microsoft Purview (formerly Compliance Center), and eDiscovery Premium all index messages by the corrupted delivery date. Content searches for emails within a specific date range return incorrect results. Retention labels applied 自動的に based on message age operate on the wrong timeline, potentially causing premature deletion or indefinite 保持 of messages that should have been handled differently.