從 Microsoft Cloud Deutschland 遷移的遷移階段動作和影響 (advanced) Migration phases actions and impacts for the migration from Microsoft Cloud Deutschland (advanced)

從 Microsoft Cloud Deutschland 將租使用者遷移至 Microsoft Office 365 服務的德國地區時,會做為每一個工作負載的一組階段和各自設定的動作執行。Tenant migrations from Microsoft Cloud Deutschland to the Germany region of Microsoft's Office 365 services are executed as a set of phases and their configured actions for each workload. 下圖顯示遷移至新德文資料中心的九個階段。This figure shows the nine phases of migration to the new German datacenters.

遷移至新的德國資料中心的九個階段

下列各節將提供客戶經驗的其他資訊,從 Microsoft Cloud 德國 (Microsoft Cloud Deutschland) 到新德文 datacenter 區域中的 Office 365 服務。The following sections provide additional information on customer experiences when moving from Microsoft Cloud Germany (Microsoft Cloud Deutschland) to Office 365 services in the new German datacenter region.

服務Services

在9的階段2和階段3之9之間,可能無法存取夥伴入口網站。Between Phase 2 of 9 and Phase 3 of 9, Partner Portal may not be accessible. 在這段時間內,合作夥伴可能無法存取合作夥伴入口網站上的承租人資訊。During this time, Partner may not be able to access the tenants information on the Partner Portal. 由於每個遷移都不同,以協助工具的持續時間可能是以小時為單位。Since each migration is different, the duration of in-accessibility could be in hours.

Azure AD (階段2之 9) Azure AD (Phase 2 of 9)

步驟 (s) Step(s) 描述Description 適用於Applies to 影響Impact
Microsoft Cloud Deutschland 中的 Azure AD 租使用者已複製到 Office 365 服務。Azure AD tenant in Microsoft Cloud Deutschland copied to Office 365 Services. Azure AD 會將租使用者複製到 Office 365 服務。Azure AD copies the tenant to Office 365 services. 會保留承租人和使用者識別碼。Tenant and user identifiers are preserved. Azure AD 服務呼叫會從 Microsoft Cloud Deutschland 重新導向至 Office 365 服務,且對服務而言是透明的。Azure AD service calls are redirected from Microsoft Cloud Deutschland to Office 365 services and are transparent to services. 所有 Office 客戶All Office customers -一般資料保護法規 (GDPR) 資料主體要求 (Dsr) 會從 Azure Admin 入口網站執行,以供未來的要求使用。- General Data Protection Regulation (GDPR) Data Subject Requests (DSRs) are executed from the Azure Admin portal for future requests. 在 Microsoft 雲端 Deutschland 中的任何舊版或非客戶診斷資料會在經過30天之後刪除。Any legacy or non-customer diagnostic data that is resident in Microsoft Cloud Deutschland is deleted at or before 30 days elapse.

-使用與 Active Directory Federation Services 的同盟驗證的客戶 (AD FS) 不應該變更在遷移期間用於所有內部部署 Active Directory 驗證的 issuer URIs。- Customers who use federated authentications with Active Directory Federation Services (AD FS) shouldn't make changes to issuer URIs that are used for all authentications with on-premises Active Directory during migration. 變更簽發者 URIs 會導致網域中的使用者驗證失敗。Changing issuer URIs will lead to authentication failures for users in the domain. 簽發者 URIs 可以直接在 AD FS 中變更,或將網域從 managed 轉換成 同盟,反之亦然Issuer URIs can be changed directly in AD FS or when a domain is converted from managed to federated and vice-versa. 我們建議客戶不要新增、移除或轉換已遷移之 Azure AD 租使用者中的同盟網域。We recommend that customers do not add, remove, or convert a federated domain in the Azure AD tenant that has been migrated. 在遷移完全完成後,可以變更發行者 URIs。Issuer URIs can be changed after the migration is fully complete.

-多重要素驗證 (,當租使用者複製到 Office 365 服務時,使用 Microsoft 驗證者的 MFA) 要求會顯示為使用者 ObjectID (GUID) 。- Multi-factor authentication (MFA) requests that use Microsoft Authenticator display as the user ObjectID (a GUID) while the tenant is copied to Office 365 services. 雖然這種顯示行為,MFA 要求仍會如期執行。MFA requests will perform as expected despite this display behavior. 使用 Office 365 服務端點所啟動的 Microsoft 驗證程式帳戶會顯示使用者主要名稱 (UPN) 。Microsoft Authenticator accounts that were activated by using Office 365 services endpoints will display the user principal name (UPN). 使用 Microsoft Cloud Deutschland 端點新增的帳戶會顯示使用者 ObjectID,但會同時搭配 Microsoft Cloud Deutschland 和 Office 365 服務端點使用。Accounts added by using Microsoft Cloud Deutschland endpoints will display the user ObjectID but will work with both Microsoft Cloud Deutschland and Office 365 services endpoints.
建立指向全域 STS 服務的 Set-authserver 內部部署。Establish AuthServer on-premises pointing to global STS service. 這可確保針對目標為混合式內部部署環境的 Exchange 可用性要求進行遷移至 Microsoft Cloud Deutschland 的使用者要求經過驗證,才能存取內部部署服務。This ensures that requests from users who migrate to Microsoft Cloud Deutschland for Exchange availability requests that target the hybrid on-premises environment are authenticated to access the on-premises service. 同樣的,這會確保從內部部署到 Office 365 服務端點的要求驗證。Similarly this will ensure authentication of requests from on-premises to Office 365 services endpoints. 具有混合式 (內部部署) 部署的 Exchange Online 客戶Exchange Online customers with hybrid (on-premises) deployments Azure AD 遷移完成之後,內部部署 Exchange 的系統管理員 (混合) 拓撲必須為 Office 365 服務新增新的驗證服務端點。After Azure AD migration is complete, the administrator of the on-premises Exchange (hybrid) topology must add a new authentication service endpoint for the Office 365 services. 使用來自 Exchange PowerShell 的此命令,取代 <TenantID> 您組織的租使用者識別碼 (在 Azure Active Directory) 上的 azure 入口網站中找到。With this command from Exchange PowerShell, replace <TenantID> with your organization's tenant ID (found in Azure portal on Azure Active Directory).

- New-AuthServer GlobalMicrosoftSts -AuthMetadataUrl https://accounts.accesscontrol.windows.net/<TenantId>/metadata/json/1

無法完成此工作可能會導致混合空閒忙碌要求無法為已從 Microsoft Cloud Deutschland 遷移至 Office 365 服務的信箱使用者提供資訊。Failing to complete this task may result in hybrid free-busy requests failing to provide information for mailbox users who have been migrated from Microsoft Cloud Deutschland to Office 365 services.
遷移 Azure 資源。Migration of Azure resources. 使用 Office 365 和 Azure 資源的客戶 (例如,網路、計算和儲存) 會執行將資源遷移至 Office 365 服務實例。Customers who use Office 365 and Azure resources (for example, networking, compute, and storage) will perform the migration of resources to the Office 365 services instance. 這種遷移是客戶的責任。This migration is a responsibility for customers. 訊息中心文章會通知開始。Message Center posts will signal the start. 在 Office 365 服務環境中完成 Azure AD 組織之前,必須完成遷移。Migration must be completed before finalization of the Azure AD organization in the Office 365 services environment. Azure 客戶Azure Customers 如需 Azure 遷移,請參閱 azure 遷移行動手冊( Azure 德國遷移指南的概述)。For Azure migrations, see the Azure migration playbook, Overview of migration guidance for Azure Germany.

Exchange Online (階段5之 9) Exchange Online (Phase 5 of 9)

如果您使用 的是設定 UserPhotoIf you're using Set-UserPhoto:

步驟 (s) Step(s) 描述Description 適用於Applies to 影響Impact
新的德國區域會新增至現有的組織設定,並將信箱移至 Office 365 服務。The new Germany region is added to an existing organization setup, and mailboxes are moved to Office 365 services. Exchange Online 設定會將新的隨用本機德文區域新增至轉換的組織。Exchange Online configuration adds the new go-local German region to the transitioning organization. 此 Office 365 服務區域已設定為預設值,可讓內部負載平衡服務將信箱重新分配至 Office 365 服務中的適當預設區域。This Office 365 services region is set as default, which enables the internal load-balancing service to redistribute mailboxes to the appropriate default region in Office 365 services. 在此轉換中,任何一側 (德國或 Office 365 服務) 的使用者都位於相同的組織中,而且可以使用 URL 端點。In this transition, users on either side (Germany or Office 365 services) are in the same organization and can use either URL endpoint. Exchange OnlineExchange Online 如果使用者信箱已遷移,但系統管理員信箱尚未遷移,或反過來,系統管理員將無法執行 UserPhoto,請使用 PowerShell Cmdlet。If a user mailbox has been migrated but an administrator mailbox hasn't been migrated, or vice-versa, administrators won't be able to run Set-UserPhoto, a PowerShell cmdlet. 在此情況下,系統管理員必須 ConnectionUri 使用下列語法,在連接設定期間傳遞另一個字串:In this situation, an admin must pass an additional string in ConnectionUri during connection set up by using the following syntax:

https://outlook.office.de/PowerShell-LiveID?email=<user_email>

其中 <user_email> 是使用者的電子郵件識別碼的預留位置,其相片需要使用 UserPhoto 加以變更。where <user_email> is the placeholder for the email-ID of the user whose photo needs to be changed by using Set-UserPhoto.

如果您使用的是混合式內部部署,請執行下列步驟:If you're using a hybrid, on-premises deployment:

步驟 (s) Step(s) 描述Description 適用於Applies to 影響Impact
停止或刪除信箱的任何上架或脫離移動。Stop or delete any onboarding or offboarding moves of mailboxes. 這可確保移動要求不會失敗,併發生錯誤。This ensures the move requests don't fail with an error. 具有混合式 (內部部署) 部署的 Exchange Online 客戶Exchange Online customers with hybrid (on-premises) deployments 必要的動作。Required action. 若失敗,可能會導致服務或軟體用戶端失敗。Failure to do so may result in failure of the service or of software clients.

Dynamics (階段8之 9) Dynamics (Phase 8 of 9)

步驟 (s) Step(s) 描述Description 適用於Applies to 影響Impact
Microsoft Dynamics 資源Microsoft Dynamics resources 使用 Microsoft Dynamics 的客戶將會進行工程或 FastTrack,以將動態轉換為 Office 365 服務實例。 *Customers with Microsoft Dynamics will be engaged by Engineering or FastTrack to transition Dynamics to the Office 365 services instance.* Microsoft Dynamics 365 客戶Microsoft Dynamics 365 customers -遷移後,系統管理員會驗證組織。- After migration, the admin validates the organization.

-系統管理員會視需要修改工作流程。- The admin modifies workflows, as necessary.

-系統管理員會視需要清除 AdminOnly 模式。- The admin clears AdminOnly mode as appropriate.

-系統管理員會適當地從 沙箱 變更組織類型。- The admin changes the organization type from Sandbox, as appropriate

-通知使用者新的 URL 存取實例 (org) 。- Notify end users of the new URL to access the instance (org).

-更新任何指向新端點 URL 的輸入連線。- Update any inbound connections to the new endpoint URL.

-轉換期間,使用者將無法使用 Dynamics 服務。- The Dynamics service will be unavailable to users during the transition.

-在遷移每個組織之後,使用者必須驗證組織的健康情況和功能。- Users are required to validate the org health and features after migration of each org.

* (i) 使用 Microsoft Dynamics 365 的客戶,必須在此遷移案例中採取動作,如所提供的遷移程式所定義。* (i) Customers with Microsoft Dynamics 365 must take action in this migration scenario as defined by the migration process provided. (ii) 客戶採取行動的失敗即表示 Microsoft 將無法完成遷移。(ii) Failure by the customer to take action will mean that Microsoft will be unable to complete the migration. (iii) 當 Microsoft 因客戶的 inaction 而無法完成遷移時,客戶的訂閱會在2021年10月29日到期。(iii) When Microsoft is unable to complete the migration due to the customer's inaction, then the customer's subscription will expire on October 29, 2021.

Power BI (階段8之 9) Power BI (Phase 8 of 9)

步驟 (s) Step(s) 描述Description 適用於Applies to 影響Impact
Power BI 資源的遷移Migration of Power BI resources 當手動觸發現有的 PBI 遷移工具,將 Power BI 轉換為 Office 365 服務實例後,Microsoft Power BI 的客戶將會涉嫌從事工程或 FastTrack。**Customers with Microsoft Power BI will be engaged by Engineering or FastTrack after manually triggering an existing PBI migration tool to transition Power BI to the Office 365 services instance.** Microsoft Power BI 客戶Microsoft Power BI customers - 會轉換下列的 Power BI 專案,必須重新建立這些專案:- The following Power BI items will not be transitioned, and they'll have to be re-created:

-即時資料集 (例如,流式傳送或推入資料集) 。- Real-time datasets (for example, streaming or push datasets).
-Power BI 內部部署資料閘道設定和資料來源。- Power BI on-premises data gateway configuration and data source.
-在遷移後,在即時資料集之上建立的報告將無法使用,且必須重新建立。- Reports built on top of the real-time datasets won't be available after migration and are required to be recreated.

-在轉換期間,使用者將無法使用 Power BI 服務。- Power BI services will be unavailable to users during the transition. 無法取得服務,不應超過24小時。The unavailability of the service shouldn't be more than 24 hours.

-遷移後,使用者將需要使用 Power BI 服務重新設定資料來源及其內部部署資料閘道。- Users will be required to reconfigure data sources and their on-premise data gateways with the Power BI service after migration. 在執行這項作業之前,使用者將無法使用這些資料來源,對這些資料來源執行排程的重新整理和/或直接查詢。Until they do so, users will be unable to use these data sources to perform scheduled refresh and/or direct queries against these data sources.

-無法遷移容量與特優工作區。- Capacities and premium workspaces cannot be migrated. 客戶必須先刪除所有容量,再進行遷移,然後在遷移之後重新建立。Customers need to delete all capacities before migration and re-create them after migration. 視需要將工作區移回容量。Move workspaces back to capacities as desired.

** (i) 使用 Microsoft Power BI 的客戶必須採取遷移程式所定義的遷移程式,採取行動。** (i) Customers with Microsoft Power BI must take action in this migration scenario as defined by the Migration process provided. (ii) 客戶採取行動的失敗即表示 Microsoft 將無法完成遷移。(ii) Failure by the customer to take action will mean that Microsoft will be unable to complete the migration. (iii) 當 Microsoft 因客戶的 inaction 而無法完成遷移時,客戶的訂閱會在2021年10月29日到期。(iii) When Microsoft is unable to complete the migration due to the customer's inaction, then the customer's subscription will expire on October 29, 2021.

在移轉期間During migration

SharePoint 線上 (階段4之 9) SharePoint Online (Phase 4 of 9)

步驟 (s) Step(s) 描述Description 適用於Applies to 影響Impact
會轉換 SharePoint 和 OneDrive。SharePoint and OneDrive are transitioned. 在此階段中,SharePoint 和 OneDrive 會從 Microsoft Cloud Deutschland 遷移至 Office 365 服務。SharePoint and OneDrive are migrated from Microsoft Cloud Deutschland to Office 365 services in this phase. 現有的 Microsoft Cloud Deutschland URLs 會保留 (contoso.sharepoint.de) 中。Existing Microsoft Cloud Deutschland URLs are preserved (contoso.sharepoint.de). Microsoft Cloud Deutschland 或 Office 365 服務所簽發的標記在轉換期間是有效的。Tokens issued by Microsoft Cloud Deutschland or Office 365 services are valid during the transition. SharePoint 客戶SharePoint customers Inflight SharePoint 2013 工作流程會在遷移期間中斷,且必須在遷移之後重新發佈。Inflight SharePoint 2013 workflows will be broken during migration and must be republished after migration.

Exchange Online (階段5之 9) Exchange Online (Phase 5 of 9)

針對 eDiscovery:For eDiscovery:

步驟 (s) Step(s) 描述Description 適用於Applies to 影響Impact
在遷移期間,電子檔探索搜尋會失敗,或傳回0個結果,以供 SharePoint 線上、OneDrive 商務及已遷移的 Exchange Online 位置。During migration, eDiscovery searches will fail or return 0 results for SharePoint Online, OneDrive for Business, and Exchange Online locations that have been migrated. 在遷移期間,客戶可以繼續在 安全性 & 規範中心(包括 內容搜尋)中建立案例、保留、搜尋和匯出。During migration, customers can continue to create cases, holds, searches, and exports in the Security & Compliance Center, including Content Search. 不過,針對已遷移的 SharePoint 線上、OneDrive 商務和 Exchange Online 位置進行搜尋會傳回0個結果或產生錯誤。However, searches against SharePoint Online, OneDrive for Business, and Exchange Online locations that have been migrated will either return 0 results or produce an error. 如需修正,請參閱 影響 欄。For remediation, see the Impact column. 所有使用 eDiscovery 的客戶All customers using eDiscovery 在遷移期間,如果搜尋傳回0個結果或發生錯誤,請在線上 SharePoint 執行下列動作:In the event that a search returns 0 results or an error during migration, please take the following action for SharePoint Online:

遵循 從 OneDrive 或 SharePoint 下載檔案及資料夾中的指示,直接從 SharePoint Online/OneDrive 取得商務網站下載網站。Download sites directly from SharePoint Online/ OneDrive for Business site by following the instructions in Download files and folders from OneDrive or SharePoint. 此方法將需要 SharePoint 線上系統管理員許可權或網站的唯讀許可權。This method will require SharePoint Online administrator permissions or read-only permissions on the site.

若超出限制( 從 OneDrive 或 SharePoint 下載檔案及資料夾中所述),客戶可以遵循 與電腦同步 SharePoint 及小組檔案的指導方針,使用 OneDrive 進行商務同步處理用戶端。If limits are exceeded, as explained in Download files and folders from OneDrive or SharePoint, customers can use the OneDrive for Business sync client by following the guidance in Sync SharePoint and Teams files with your computer.

-Exchange Online- Exchange Online

- 在 Exchange Server 中 In-Place eDiscovery- In-Place eDiscovery in Exchange Server

商務用 Skype Online (階段7之 9) Skype for Business Online (Phase 7 of 9)

步驟 (s) Step(s) 描述Description 適用於Applies to 影響Impact
將商務用 Skype 遷移至小組。Migration of Skype for Business to Teams. 現有商務用 Skype 客戶會遷移至歐洲的 Office 365 服務,然後轉換為 Office 365 服務的德國地區中的 Microsoft 團隊。Existing Skype for Business customers are migrated to Office 365 services in Europe and then transitioned to Microsoft Teams in the Germany region of Office 365 services. 商務用 Skype 客戶Skype for Business customers PowerShell 會使用來管理租使用者和使用者的設定和原則。PowerShell will use to administer settings and policies for your tenant and users. 連線至 PowerShell 會話時,請新增下列專案:When connecting to a PowerShell session, add the following:

-OverridePowershellUri "https://admin4E.online.lync.com/OcsPowershellOAuth"

移轉後Post-migration

Azure AD (階段9之 9) Azure AD (Phase 9 of 9)

若為混合式:For hybrid:

步驟 (s) Step(s) 描述Description 適用於Applies to 影響Impact
更新 Azure AD Connect。Update Azure AD Connect. 在完成剪下 Azure AD 後,組織就完全使用 Office 365 服務,而且不再連接至 Microsoft 雲端 Deutschland。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. 此時,客戶必須確定已完成的 delta 同步處理常式,然後在該程式中,將 AzureInstance Deutschland Microsoft Cloud) 中的字串 (值變更為登錄路徑中的 0 Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Azure AD ConnectAt 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. 混合式 Azure AD –連線的組織Hybrid Azure AD–connected organizations 變更登錄機碼的值 AzureInstanceChange the value of AzureInstance, the registry key. 若無法這麼做,將在不再提供 Microsoft Cloud Deutschland 端點後,導致物件不會進行同步處理。Failing to do so, will lead to objects not being synchronized after the Microsoft Cloud Deutschland endpoints are no longer available.

對於同盟驗證:For federated authentication:

步驟 (s) Step(s) 描述Description 適用於Applies to 影響Impact
從 Microsoft Cloud Deutschland AD FS 移除信賴憑證者信任。Remove relying party trusts from Microsoft Cloud Deutschland AD FS. 在完成剪下 Azure AD 後,組織就完全使用 Office 365 服務,而且不再連接至 Microsoft 雲端 Deutschland。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 Cloud Deutschland 端點的信賴憑證者信任。At this point, the customer needs to remove the relying party trust to the Microsoft Cloud Deutschland endpoints. 只有當 Azure AD 以身分識別提供者的方式 (IdP) 時,才可以在未客戶的任何應用程式指向 Microsoft Cloud Deutschland 端點時執行此動作。This can only be done when no applications of the customer point to Microsoft Cloud Deutschland endpoints when Azure AD is leveraged as an Identity Provider (IdP). 同盟驗證組織Federated Authentication organizations 無。None.

針對 Azure AD:For Azure AD:

步驟 (s) Step(s) 描述Description 適用於Applies to 影響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 request to join an Azure AD group again if those requests weren't approved in the last 30 days before the migration. 在遷移前30天內,未核准 Azure AD 群組核准要求的使用者End users whose Azure AD group approval requests weren't approved in last 30 days before migration 做為使用者:As an end user:
  1. 流覽至 Access 面板Navigate to Access panel.
  2. 尋找在遷移前30天內,成員核准已擱置的 Azure AD 群組。Find an Azure AD group for which membership approval was pending in 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 re-requested after migration.

若為 DNS:For DNS:

步驟 (s) Step(s) 描述Description 適用於Applies to 影響Impact
更新 Office 365 服務端點的內部部署 DNS 服務。Update on-premises DNS services for Office 365 services endpoints. 客戶管理的 DNS 專案(指向 Office 365 德國)必須更新,以指向 Office 365 服務端點。Customer-managed DNS entries that point to Office 365 Germany need to be updated to point to the Office 365 services endpoints. 所有 Office 客戶All Office customers 必要的動作。Required action. 若失敗,可能會導致服務或軟體用戶端失敗。Failure to do so may result in failure of the service or of software clients.

針對 Office 365 服務端點的協力廠商服務:For third-party services for Office 365 services endpoints:

步驟 (s) Step(s) 描述Description 適用於Applies to 影響Impact
更新合作夥伴及 Office 365 服務端點的協力廠商服務。Update partners and third-party services for Office 365 services endpoints. -指向 Office 365 德國的協力廠商服務和合作夥伴必須更新,以指向 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.

-Point 所有利用圖形 API 的自訂應用 graph.microsoft.de 程式 graph.microsoft.com- Point all custom applications that leverage Graph API from graph.microsoft.de to graph.microsoft.com. 其他含有已變更端點的 APIs 也必須更新(如果利用)。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.
所有 Office 客戶All Office customers 必要的動作。Required action. 若失敗,可能會導致服務或軟體用戶端失敗。Failure to do so may result in failure of the service or of software clients.

SharePoint 線上 (階段4之 9) SharePoint Online (Phase 4 of 9)

步驟 (s) Step(s) 描述Description 適用於Applies to 影響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. 所有 Office 客戶All Office customers 這是必要的動作。This is a required action. 若失敗,可能會造成使用者混淆和問訊台通話。Failure to do so may result in user confusion and help desk calls.
透過 Outlook 共用專案Share items via Outlook 在租使用者切換後,透過 Outlook 共用專案將不再運作。Sharing items via Outlook no longer works after tenant cutover. SharePoint Online 和商務用 OneDriveSharePoint Online and OneDrive for Business -在線上和商務 OneDrive 中 SharePoint,您可以透過 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 Online (階段5之 9) Exchange Online (Phase 5 of 9)

如果您使用的是混合式 Exchange 設定:If you're using a hybrid Exchange configuration:

步驟 (s) Step(s) 描述Description 適用於Applies to 影響Impact
針對 Office 365 服務,重新執行混合式設定向導 (HCW) 。Rerun Hybrid Configuration wizard (HCW) against Office 365 services. 現有的 HCW 設定是為了支援 Microsoft Cloud Deutschland。The existing HCW configuration is meant to support Microsoft Cloud Deutschland. 隨著 Exchange 服務的遷移完成,我們會將內部部署設定從 Microsoft Cloud Deutschland 中分離出來。With migration of Exchange services complete, we decouple on-premises configuration from Microsoft Cloud Deutschland. 執行混合式部署的 Exchange Online 客戶Exchange Online customers who are running a hybrid deployment 必要的動作。- Required action. 若失敗,可能會導致服務或軟體用戶端失敗。Failure to do so may result in failure of the service or of software clients. 在 Exchange 信箱遷移開始 (,但有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.
在從 Microsoft Cloud Deutschland 將 Exchange 遷移至 Office 365 服務時,執行 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.

如果在遷移信箱之後,用戶端遇到認證或授權問題,使用者可以執行 Set-MigrationEndpoint endpointName -Credential $(Get-Credential) ,或是使用 Exchange 控制台 (ECP) ,在遷移端點中重新輸入其內部部署系統管理員認證。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).

針對 eDiscovery:For eDiscovery:

步驟 (s) Step(s) 描述Description 適用於Applies to 影響Impact
所有的 SharePoint 線上、商務 OneDrive 和 Exchange Online 位置都與安全性與合規性中心一起遷移, (SCC) 。All SharePoint Online, OneDrive for Business, and Exchange Online locations have been migrated along with Security and Compliance Center (SCC). 所有 eDiscovery 活動都應該從世界租使用者執行。All eDiscovery activity should be run from the worldwide tenant. 搜尋現在會是100% 成功。Searches will now be 100% successful. 任何失敗或錯誤都應該遵循正常支援通道。Any failures or errors should follow normal support channels. 使用 eDiscovery 的所有客戶All customers who use eDiscovery 無。None.
移除在遷移前步驟中建立的全組織保留原則Remove organization-wide retention policies that were created during pre-migration steps 客戶可以移除在客戶的預先遷移工作中所建立的全組織保留原則。Customers can remove the organization-wide retention policies that were created during the customers' pre-migration work. 所有在遷移前步驟中套用保留原則的客戶。All customers who applied a retention policy as part of pre-migration steps. 無。None.

下一步Next step

瞭解遷移階段的動作和影響Understand migration phases actions and impacts

詳細資訊More information

開始:Getting started:

在轉換中移動:Moving through the transition:

雲端應用程式:Cloud apps: