从德国 Microsoft 云迁移的迁移后活动Post-migration activities for the migration from Microsoft Cloud Deutschland

以下各节提供从德国 Microsoft 云迁移到新的德国数据中心 (Office 365 服务) 多个服务的迁移后活动。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 ADAzure AD

Azure AD ConnectAzure AD Connect

适用于： 所有客户使用 Azure AD 连接同步标识Applies to: All customers synchronizing identities with Azure AD connect

步骤 (步骤) Step(s) DescriptionDescription 影响Impact
更新 Azure AD Connect。Update Azure AD Connect. 完成到 Azure AD 的剪切后，组织将完全使用 Office 365 服务，并且不再连接到德国 Microsoft 云。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. 此时，客户需要确保增量同步过程已完成，此后，在注册表路径 中将字符串值从 3 (Microsoft 云德国) 更改为 AzureInstance Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Azure AD Connect 0。At this point, the customer needs to ensure that the delta sync process has been finalized, and after that, change the string value of AzureInstance from 3 (Microsoft Cloud Deutschland) to 0 in the registry path Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Azure AD Connect. 更改 注册表 AzureInstance 项 的值。Change the value of AzureInstance, the registry key. 如果不这样做，将导致在 Microsoft 云德国终结点不再可用后对象无法同步。Failing to do so, will lead to objects not being synchronized after the Microsoft Cloud Deutschland endpoints are no longer available.

使用 AD FS 的 Azure AD 联合身份验证Azure AD federated authentication with AD FS

适用于： 使用 AD FS 联合身份验证的所有客户Applies to: All customers using federated authentication with AD FS

步骤 (步骤) Step(s) DescriptionDescription 影响Impact
从 Microsoft 云德国 AD FS 中删除信赖方信任。Remove relying party trusts from Microsoft Cloud Deutschland AD FS. 完成到 Azure AD 的切分后，组织将完全使用 Office 365 服务，并且不再连接到德国 Microsoft 云。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. 此时，客户需要删除对德国 Microsoft 云终结点的信赖方信任。At this point, the customer needs to remove the relying party trust to the Microsoft Cloud Deutschland endpoints. 只有在将 Azure AD 用作标识提供程序 (IdP) 时，客户的应用程序均不指向德国 Microsoft 云终结点，才能完成此操作。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

适用于： 迁移前的最后 30 天内未批准其 Azure AD 组审批请求的最终用户Applies to: End-users whose Azure AD group approval requests weren't approved in the last 30 days before migration

步骤 (步骤) Step(s) DescriptionDescription 影响Impact
如果原始请求未获得批准，则需要再次请求迁移前 30 天内加入 Azure AD 组的请求。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. 如果迁移前的最后 30 天内未批准这些请求，最终用户客户将需要使用访问面板再次提交加入 Azure AD 组的请求。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. 查找在迁移前 30 天内等待其成员身份审批的 Azure AD 组。Find an Azure AD group for which membership approval was pending during the 30 days before migration.
  3. 再次请求加入 Azure AD 组。Request to join the Azure AD group again.
在迁移前 30 天内加入活动组的请求无法获得批准，除非迁移后再次请求。Requests to join a group that are active less than 30 days before migration cannot be approved, unless they're requested again after migration.

自定义 DNS 更新Custom DNS updates

适用于： 管理自己的 DNS 区域的所有客户Applies to: All customer managing their own DNS zones

步骤 (步骤) Step(s) DescriptionDescription 影响Impact
为 Office 365 服务终结点更新本地 DNS 服务。Update on-premises DNS services for Office 365 services endpoints. 指向德国 Microsoft 云的客户托管 DNS 条目需要更新为指向 Office 365 全局服务终结点。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

适用于： 为 Office 365 服务终结点使用第三方服务的客户Applies to: Customers using third-party services for Office 365 services endpoints

步骤 (步骤) Step(s) DescriptionDescription 影响Impact
更新 Office 365 服务终结点的合作伙伴和第三方服务。Update partners and third-party services for Office 365 services endpoints.
  • 指向 Office 365 Germany 的第三方服务和合作伙伴需要进行更新，以指向 Office 365 服务终结点。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.
  • 将利用 Graph API 的所有自定义应用程序从 指向 graph.microsoft.de graph.microsoft.com 。Point all custom applications that leverage Graph API from graph.microsoft.de to graph.microsoft.com. 如果利用，还需要更新终结点已更改的其他 API。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 OnlineSharePoint Online

适用于： 使用 SharePoint 2013 工作流的客户Applies to: Customers using SharePoint 2013 Workflows

步骤 (步骤) Step(s) DescriptionDescription 影响Impact
重新发布 SharePoint 2013 工作流。Republish SharePoint 2013 workflows. 在迁移前工作中，我们减少了 SharePoint 2013 工作流的数量。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.
通过 Outlook 共享项目Share items via Outlook 租户切换后，通过 Outlook 共享 SharePoint Online 和 OneDrive for Business 中的项目不再起作用。Sharing items in SharePoint Online and OneDrive for Business via Outlook no longer works after tenant cutover.
  • 在 SharePoint Online 和 OneDrive for Business 中，可以通过 Outlook 共享项目。In SharePoint Online and OneDrive for Business, you can share items via Outlook. 按 Outlook 按钮后，会创建一个可共享的链接，并推送到邮件Outlook Web App。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. 但是，由于此 Outlook 功能位于弃用路径中，因此在推出弃用之前，不会计划修复问题。However, since this Outlook feature is in the path of deprecation, fixing the issue is not planned until the deprecation is rolled out.

Exchange OnlineExchange Online

适用于： 使用混合 Exchange 配置的客户Applies to: Customers using a hybrid Exchange configuration

步骤 (步骤) Step(s) DescriptionDescription 影响Impact
针对 Office 365 服务 (HCW) 重新运行混合配置向导。Rerun Hybrid Configuration wizard (HCW) against Office 365 services. 现有 HCW 配置旨在支持德国 Microsoft 云。The existing HCW configuration is meant to support Microsoft Cloud Deutschland. 完成 Exchange 服务的迁移后，我们将本地配置与德国 Microsoft 云分离。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. 在 Exchange 邮箱迁移 (5 天或 5) ，通知客户端应停止并删除其邮箱的任何载入或载出移动。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.
  • Exchange 邮箱迁移完成后，通知客户端他们可以恢复载入和载出移动。After Exchange mailbox migration is complete, notify clients that they can resume onboarding and offboarding moves.
    在将 Exchange 从德国 Microsoft 云迁移到 Office 365 服务期间，运行 Test-MigrationServerAvailabiilty（PowerShell cmdlet）可能不起作用。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.
  • 如果客户端在迁移邮箱后遇到凭据或授权问题，则用户可以通过运行 或通过使用 Exchange 控制面板 (ECP) ，在迁移终结点中重新输入其本地管理员 Set-MigrationEndpoint endpointName -Credential $(Get-Credential) 凭据。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).