Updates from: 03/02/2021 04:02:55
Category Microsoft Docs article Related commit history on GitHub Change details
enterprise Ms Cloud Germany Transition Add Pre Work https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/ms-cloud-germany-transition-add-pre-work.md
Reworked as text:
| Step(s) | Description | Applies to | Impact | |:-|:--|:-|:-|
-| Uninstall previous versions of Hybrid Configuration wizard (HCW), and then install and execute the latest version, 17.0.5378.0, from [https://aka.ms/hybridwizard](https://aka.ms/hybridwizard). | The latest version of the HCW includes necessary updates to support customers who are transitioning from Microsoft Cloud Deutschland to Office 365 Services. <br><br> Updates include changes to on-premises certificate settings for Send connector and Receive connector. | Exchange Online customers running Hybrid deployment | Required action. Failure to do so before Phase 5 of 9 (Exchange) may result in service or client failure. |
+| Update to the latest version of the Hybrid Configuration Wizard (HCW) before migration. <br><br> Microsoft Cloud Deutschland hybrid Exchange Online customers must uninstall previous versions of HCW, and then install and execute the latest version (17.0.5378.0 or higher) from [https://aka.ms/hybridwizard](https://aka.ms/hybridwizard). | The latest version of the HCW includes necessary updates to support customers who are transitioning from Microsoft Cloud Deutschland to Office 365 Services. <br><br> Updates include changes to on-premises certificate settings for the Send connector and the Receive connector. <br><br> Customers must re-install using Office 365 Germany settings before Phase 5 of 9 (Exchange migration) begins. <br><br> NOTE: Upon completion of the migration to Office 365 services, you will remove and re-install the HCW again, this time using Office 365 Worldwide settings to complete your Hybrid setup with the global service. | Exchange Online customers running Hybrid deployment | Required action. Failure to do so before Phase 5 of 9 (Exchange migration) may result in service or client failure. |
||||| <!--
enterprise Ms Cloud Germany Transition Phases https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/ms-cloud-germany-transition-phases.md
Additional considerations:
| Step(s) | Description | Applies to | Impact | |:-|:--|:-|:-|
-| New Germany region is added to existing organization setup, and mailboxes are moved to Office 365 services. | Exchange Online configuration adds the new go-local German region to the transitioning organization. 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. In this transition, users on either side (Germany or Office 365 services) are in the same organization and can use either URL endpoint. | Exchange Online | - Transition users and services from Germany URLs to Office 365 services URLs (`https://outlook.office365.com`). <br><br> - Users will continue to access the service via legacy Germany URLs during the migration. No immediate action needed. <br><br> - Users should begin to use the office.com portal for Office Online features (Calendar, Mail, People). Navigation to services that aren't yet migrated to Office 365 services won't function until migrated. <br><br> - Outlook Web App won't provide the public folder experience during migration. |
+| New Germany region is added to existing organization setup and mailboxes are moved to Office 365 services. | Exchange Online configuration adds the new go-local German region to the transitioning organization. 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. In this transition, users on either side (Germany or Office 365 services) are in the same organization and can use either URL endpoint. | Exchange Online | - Transition users and services from your legacy Germany URLs (outlook.office.de) to new Office 365 services URLs (`https://outlook.office365.com`). <br><br> - Users may continue to access the service through legacy Germany URLs during the migration, however they need to stop using the legacy URLs on completion of the migration. <br><br> - Users should transition to using the worldwide Office portal for Office Online features (Calendar, Mail, People). Navigation to services that aren't yet migrated to Office 365 services won't function until they are migrated. <br><br> - The Outlook Web App won't provide the public folder experience during migration. |
+| Update custom DNS Settings for AutoDiscover| Customer-managed DNS settings for AutoDiscover that currently point to Microsoft Cloud Deutschland need to be updated to point to Office 365 on completion of the Exchange Online phase (phase 5). <br> Existing DNS entries with CNAME pointing to autodiscover-outlook.office.de need to updated to point to autodiscover.outlook.com. | Exchange Online | Availability requests and service discovery calls via AutoDiscover point directly to the Office 365 services. Customers who do not perform these DNS updates may experience Autodiscover service issues when the migration is finalized. |
||||| Additional considerations:
Additional considerations:
- If you're using Exchange Online hybrid:
- - You must rerun the Hybrid Configuration wizard (HCW) to update on-premises configuration against Microsoft Cloud Deutschland before the transition, and rerun the HCW upon cleanup against the Office 365 services. Additional DNS updates may be required if you use custom domains.
+ - Exchange Online Hybrid customers must execute the Hybrid Configuration wizard (HCW) multiple times as part of this transition. **Before the migration step phase 5 begins,** any Exchange Online hybrid customer needs to run the latest version of the HCW in Office 365 Germany mode to prepare on-premises configuration for the migration to Office 365 global. On **completion of the migration phase 5** (when the Message Center notice is published), you need to run the HCW against using Office 365 Worldwide settings to point your on-premises systems to the global service. Additional DNS updates may be required if you use custom domains.
To find out more about the differences for organizations in migration and after Exchange Online resources are migrated, review the information in [Customer experience during the migration to Office 365 services in the new German datacenter regions](ms-cloud-germany-transition-experience.md).
knowledge Edit A Topic https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/knowledge/edit-a-topic.md
Knowledge managers can also edit topics directly from the Manage Topics page by
### To edit a topic page
-1. On the topic page, select **Edit**. This allows you to make changes as you need to the topic page.
+1. On the topic page, select **Edit**. This lets you make changes as needed to the topic page.
![Edit control](../media/knowledge-management/topic-page-edit.png) </br>
managed-desktop Readiness Assessment Tool https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/managed-desktop/get-ready/readiness-assessment-tool.md
For details about using the downloadable readiness assessment checker, see [Down
## Online readiness assessment tool for management settings
-The online tool checks settings in Microsoft Endpoint Manager (specifically, Microsoft Intune), Azure Active Directory (Azure AD), and Microsoft 365 to ensure they will work with Microsoft Managed Desktop. Microsoft Managed Desktop retains the data associated with these checks for 12 months after the last time you run a check in your Azure AD organization (tenant). After 12 months, we retain it in de-identified form. You can choose to delete the data we collect.
+The [online tool](https://aka.ms/mmdart) checks settings in Microsoft Endpoint Manager (specifically, Microsoft Intune), Azure Active Directory (Azure AD), and Microsoft 365 to ensure they will work with Microsoft Managed Desktop. Microsoft Managed Desktop retains the data associated with these checks for 12 months after the last time you run a check in your Azure AD organization (tenant). After 12 months, we retain it in de-identified form. You can choose to delete the data we collect.
Anyone with at least the Global Reader or Intune Administrator role will be able to run this tool, but two of the checks ([Conditional access policies](readiness-assessment-fix.md#conditional-access-policies) and [Multifactor authentication](readiness-assessment-fix.md#multifactor-authentication) require additional permissions.