Merge pull request #31208 from MicrosoftDocs/main

[AutoPublish] main to live - 03/25 13:41 PDT | 03/26 02:11 IST

Author: m365-skilling-repo-management[bot]

microsoft-365/enterprise/cross-tenant-identity-mapping.md

@@ -96,7 +96,7 @@ The target MailUser must have these attributes from the source mailbox or assign
 3. LegacyExchangeDN (flow as proxyAddress, `"x500:<LegacyExchangeDN>"`): The LegacyExchangeDN must be present on the target MailUser as x500: proxyAddress. All the x500 addresses from the source mailbox must be on the target mail user. The move process doesn't proceed if these x500 addresses aren't present on the target object. This step is important for enabling reply ability for emails sent before migration. The sender/recipient address in each email item and the autocomplete cache in Microsoft Outlook and in Microsoft Outlook Web App (OWA) use the value of the LegacyExchangeDN attribute. If a user can't be located using the LegacyExchangeDN value, the delivery of email messages may fail with a 5.1.1 NDR.
 4. UserPrincipalName: UPN aligns to the user's ***new*** identity or target company (for example, [email protected]).
 5. Primary SMTPAddress: Primary SMTP address aligns to the user's NEW company (for example, [email protected]).
-6. TargetAddress/ExternalEmailAddress: MailUser references the user's current mailbox hosted in source tenant (for example [email protected]). When this value is assigned, confirm you're also assigning PrimarySMTPAddress. Otherwise, this value sets the PrimarySMTPAddress, which causes move failures.
+6. TargetAddress/ExternalEmailAddress: MailUser references the user's current mailbox hosted in source tenant (for example, [email protected]). When this value is assigned, confirm you're also assigning PrimarySMTPAddress. Otherwise, this value sets the PrimarySMTPAddress, which causes move failures.
 7. You can't add legacy SMTP proxy addresses from the source mailbox to the target MailUser. For example, you can't maintain source.com on the MEU in target.onmicrosoft.com tenant objects. Domains are associated with one Microsoft Entra ID or Exchange Online tenant only.
 
 To confirm the source user's attributes, run:
@@ -385,6 +385,7 @@ The CTIMwrite command writes the following attributes from the mapped source mai
     ```powershell
     Write-CtimIdentitiesInOnPremises -IdentitiesCsvFilepath <path> -ProgressOutputCsvFilePath <path>
     ```
+    Using Cross-Tenant Identity Mapping reduces mistakes when configuring target objects for a migration by automatically configuring values such as _ExchangeGuid_, _ArchiveGuid_, and all necessary _X.500 proxy addresses_.
 
    This command updates MailUser attributes in the on-premises Active Directory (AD).
 

microsoft-365/enterprise/cross-tenant-mailbox-migration.md

@@ -571,24 +571,24 @@ [email protected]      {FullAccess}
 > [!NOTE]
 > Cross-tenant mailbox and calendar permissions aren't supported. You must organize principals and delegates into consolidated move batches so that these connected mailboxes are transitioned at the same time from the source tenant.
 
-### What X500 proxy should be added to the target MailUser proxy addresses to enable migration?
+### What X.500 proxy should be added to the target MailUser proxy addresses to enable migration?
 
-The cross-tenant mailbox migration requires that the LegacyExchangeDN value of the source mailbox object is stamped as an x500 email address on the target MailUser object.
+The cross-tenant mailbox migration requires that the LegacyExchangeDN value of the source mailbox object is stamped as an X.500 email address on the target MailUser object.
 
 Example:
 
 ```PowerShell
 LegacyExchangeDN value on source mailbox is:
 /o=First Organization/ou=Exchange Administrative Group(FYDIBOHF23SPDLT)/cn=Recipients/cn=d11ec1a2cacd4f81858c81907273f1f9Lara
 
-so, the x500 email address to be added to target MailUser object would be:
+so, the X.500 email address to be added to target MailUser object would be:
 x500:/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=d11ec1a2cacd4f81858c81907273f1f9-Lara
 ```
 
 > [!NOTE]
-> In addition to this X500 proxy, you need to copy all X500 proxies from the mailbox in the source to the mailbox in the target.
+> In addition to this X.500 proxy, you need to copy all X.500 proxies from the mailbox in the source to the mailbox in the target.
 > 
-> While rare, you could also run across an X400 proxy address on a mailbox. While it's not a requirement for the move to complete, we recommend you also stamp this address on the target mail user object.
+> While rare, you could also run across an X.400 proxy address on a mailbox. While it's not a requirement for the move to complete, we recommend you also stamp this address on the target MailUser object.
 
 ### Can the source and target tenants utilize the same domain name?
 

microsoft-365/enterprise/cross-tenant-multitenant-migration.md

@@ -142,7 +142,7 @@ After mapping identities, you must write mailbox attributes from the source tena
 - Initiate the write request:
   - `New-CtimWriteRequest -SourceTenantGuid <GUID>`
 
-This command writes attributes (ExchangeGuid, ArchiveGuid, X500 proxy addresses, and so on) from the mapped source mailbox user to the target MailUser object.
+This command writes attributes (ExchangeGuid, ArchiveGuid, X.500 proxy addresses, and so on) from the mapped source mailbox user to the target MailUser object.
 
 ### Validation
 
@@ -152,11 +152,11 @@ This command writes attributes (ExchangeGuid, ArchiveGuid, X500 proxy addresses,
 
 **Before the write process**
 
-MailUser objects have no ExchangeGuid or X500 addresses—only SMTP addresses.
+MailUser objects have no ExchangeGuid or X.500 addresses—only SMTP addresses.
 
 **After the write process**
 
-ExchangeGuid, ArchiveGuid (if applicable), and X500 proxy addresses are populated. All necessary attributes for migration and mail routing are present.
+ExchangeGuid, ArchiveGuid (if applicable), and X.500 proxy addresses are populated. All necessary attributes for migration and mail routing are present.
 
 ## Migration application setup