Post-migration activities for the migration from Microsoft Cloud Deutschland

The following sections provide post-migration activities for multiple services after moving from Microsoft Cloud Germany (Microsoft Cloud Deutschland) to Office 365 services in the new German datacenter region.

Azure AD

Azure AD federated authentication with AD FS

Applies to: All customers using federated authentication with AD FS

Step(s) Description Impact
Remove relying party trusts from Microsoft Cloud Deutschland AD FS. After the cut-over to Azure AD is complete, the organization is fully using Office 365 services and is no longer connected to Microsoft Cloud Deutschland. At this point, the customer needs to remove the relying party trust to the Microsoft Cloud Deutschland endpoints. This can only be done when none of the customer's applications points to Microsoft Cloud Deutschland endpoints when Azure AD is leveraged as an Identity Provider (IdP). Federated Authentication organizations None.

Group approvals

Applies to: End-users whose Azure AD group approval requests weren't approved in the last 30 days before migration

Step(s) Description Impact
Requests to join an Azure AD group in the last 30 days before migration will need to be requested again if the original request wasn't approved. End-user customers will need to use the Access panel to submit a request to join an Azure AD group again if those requests weren't approved in the last 30 days before the migration. As an end-user:
  1. Navigate to Access panel.
  2. Find an Azure AD group for which membership approval was pending during the 30 days before migration.
  3. Request to join the Azure AD group again.
Requests to join a group that are active less than 30 days before migration cannot be approved, unless they're requested again after migration.

Custom DNS updates

Applies to: All customer managing their own DNS zones

Step(s) Description Impact
Update on-premises DNS services for Office 365 services endpoints. Customer-managed DNS entries that point to Microsoft Cloud Deutschland need to be updated to point to the Office 365 Global services endpoints. Failure to do so may result in failure of the service or of software clients.

Third-party services

Applies to: Customers using third-party services for Office 365 services endpoints

Step(s) Description Impact
Update partners and third-party services for Office 365 services endpoints.
  • Third-party services and partners that point to Office 365 Germany need to be updated to point to the Office 365 services endpoints. Example: Re-register, in alignment with your vendors and partners, the gallery app version of applications, if available.
  • Point all custom applications that leverage Graph API from graph.microsoft.de to graph.microsoft.com. Other APIs with changed endpoints also need to be updated, if leveraged.
  • Change all non-first-party enterprise applications to redirect to the worldwide endpoints.
Required action. Failure to do so may result in failure of the service or of software clients.

SharePoint Online

Applies to: Customers using SharePoint 2013 Workflows

Step(s) Description Impact
Republish SharePoint 2013 workflows. In the pre-migration work, we reduced the number of SharePoint 2013 workflows. Now with migration complete, the customer can republish the workflows. This is a required action. Failure to do so may result in user confusion and help desk calls.
Share items via Outlook Sharing items in SharePoint Online and OneDrive for Business via Outlook no longer works after tenant cutover.
  • In SharePoint Online and OneDrive for Business, you can share items via Outlook. After pressing the Outlook button, a shareable link is created and pushed into a new message in the Outlook Web App.
  • After tenant cutover, this method of sharing won't work. We recognize this is a known issue. However, since this Outlook feature is in the path of deprecation, fixing the issue is not planned until the deprecation is rolled out.

Exchange Online

Applies to: Customers using a hybrid Exchange configuration

Step(s) Description Impact
Rerun Hybrid Configuration wizard (HCW) against Office 365 services. The existing HCW configuration is meant to support Microsoft Cloud Deutschland. With migration of Exchange services complete, we decouple on-premises configuration from Microsoft Cloud Deutschland.
  • Required action. Failure to do so may result in failure of the service or of software clients. Before Exchange mailbox migration begins (with 5 or more days of notice), notify clients that they should stop and delete any onboarding or offboarding moves of their mailboxes. If they don't, they'll see errors in their move requests.
  • After Exchange mailbox migration is complete, notify clients that they can resume onboarding and offboarding moves.
    Running Test-MigrationServerAvailabiilty, a PowerShell cmdlet, during migration of Exchange from Microsoft Cloud Deutschland to Office 365 services might not work. However, it will work properly after migration is complete.
  • If clients run into issues with credentials or authorization after mailboxes are migrated, users can reenter their on-premises administrator credentials in the migration endpoint by running Set-MigrationEndpoint endpointName -Credential $(Get-Credential), or by setting the same by using Exchange Control Panel (ECP).