Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update cross-tenant-mailbox-migration.md #13640

Open
wants to merge 1 commit into
base: public
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions microsoft-365/enterprise/cross-tenant-mailbox-migration.md
Original file line number Diff line number Diff line change
Expand Up @@ -168,6 +168,8 @@ Now that you've successfully created the migration application and secret, the n

> [!NOTE]
> You'll need the application ID of the mailbox migration app you just created and the password (secret) you configured in [Prepare the target (destination) tenant by creating the migration application and secret](#prepare-the-target-destination-tenant-by-creating-the-migration-application-and-secret). Depending on the Microsoft 365 cloud instance you use, your endpoint may be different. See the [Microsoft 365 endpoints](microsoft-365-endpoints.md) page; select the correct instance for your tenant; then review the Exchange Online _Optimize/Required_ address, and replace as appropriate.

> Your trusted partner (source tenant administrator) should accept the application using the URL mentioned in the previous section before you proceed with the next steps, otherwise, the last command in the below commands will fail with an authentication error and you will not be able to complete the migration endpoint creation.

```PowerShell
# Enable customization if tenant is dehydrated
Expand Down