Learn more about migration endpoints the first time you create a migration batch

[Cette rubrique est une documentation préliminaire et peut être modifiée dans les versions ultérieures. Des rubriques vides sont incluses comme espaces réservés. N’hésitez pas à nous transmettre vos commentaires. Envoyez-nous un e-mail à l’adresse ExchangeHelpFeedback@microsoft.com.]  

S’applique à :Exchange Online, Exchange Server, Exchange Server 2013

If no migration endpoints have been created in your Exchange Online organization when you create a migration batch (or in your on-premises Exchange organization when you run a cross-forest enterprise move), you have to provide credentials of a user account that has administrative privileges in the organization that hosts the mailboxes you're migrating. This account is typically called the migration administrator.

Exchange Online uses the migration administrator account and the Autodiscover service to detect the connection settings to the server that hosts the mailboxes you're migrating. It also tests the connectivity to a mailbox in the host organization to verify that the migration administrator account has the necessary permissions to access that mailbox. If the connection settings are successfully discovered, Exchange Online uses those settings to create a new migration endpoint after the migration batch is created.

tipConseil :
It's a good idea to create migration endpoints before you create a migration batch. When you create a migration endpoint, Exchange Online tests the connection to the source server. The migration endpoint isn't created unless Exchange Online can successfully connect to the server. This lets you troubleshoot and resolve connectivity issues before you create a migration batch. Otherwise, you have to cancel the migration batch and resolve any connectivity issues before you can create a migration batch.
 
Afficher: