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.