|Service||Microsoft Docs article||Related commit history on GitHub||Change details|
|SharePoint||Authentication Context Example||https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/authentication-context-example.md||
Authentication contexts are used with sensitivity labels to connect [Azure AD coSome apps do not currently work with authentication contexts. If you have Office apps or third party apps, we recommend testing them on a site with authentication context enabled before broadly deploying this feature. Currently, the following apps and scenarios do *not* work with authentication contexts: - Older version of Office apps (see the [list of supported versions](/microsoft-365/compliance/sensitivity-labels-teams-groups-sites#more-information-about-the-dependencies-for-the-authentication-context-option))
+- Yammer- Teams web app - OneNote app can't be added to channel if the associated SharePoint site has an authentication context - Teams private channel won't provision a SharePoint if the main team site has an authentication context
|SharePoint||Change Your Sharepoint Domain Name||https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/change-your-sharepoint-domain-name.md||
If your organization has gone through a rebranding, merger, or acquisition and n| Delve | It can take 24 hours before People profiles can be viewed. | None | | eDiscovery | Holds can't be removed until you update the URLs. | In the Microsoft Purview compliance portal, change the eDiscovery hold URLs to the new domain name. | | InfoPath forms | Forms that use a SharePoint connection as a data source won't work. | Reconnect these forms to SharePoint. |
+| Microsoft Forms | Forms that have the option to upload attachments in responses won't work. | Remove the upload button and add it again in the form. || Office apps | While the domain name is being changed, users might experience an error when saving Word, Excel, and PowerPoint documents that are located in a site or OneDrive. | Attempt to save the document again and if necessary change the URL of the save location. | | OneDrive | The Quick access links in a OneDrive won't work. | None | | Power Automate | Request sign-off flows that use SharePoint as a connection wonΓÇÖt work. | Remove and re-create the Request sign-off flow. |
If your organization has gone through a rebranding, merger, or acquisition and n| SharePoint 2013 workflows | Workflows that are ΓÇ£in flightΓÇ¥ won't complete and will be orphaned. <br> New 2013 Workflow instances can't be initiated. <br>Association to previous workflow instances isn't available and will be orphaned. | Before changing your domain name, make sure all ΓÇ£in flightΓÇ¥ workflows are completed. After you change the domain name, republish the workflows. | | SharePoint 2013 workflows | URLs embedded in workflows aren't changed. For example, if a workflow contains the embedded URL `contoso.sharepoint.com`, it isn't changed. This might impact the functionality of the workflow. | Workflows that contain URLs referring to the original domain name might need to be updated to the new name. | | SharePoint add-ins | Add-ins might not function as expected. | The add-ins might need to be republished. <br>Review the App configuration settings in Azure AD for the add-in and update any URLs to the new domain name. <br> For SPFx applications, in Azure AD update the Authentication URLs to the new domain for the SharePoint Online Client Extensibility Web Application Principal. |
+| SharePoint hub sites | Sites registered as hub sites won't work. | Unregister and register the affected sites as hub sites in the SharePoint admin center after the rename. || Site customizations and embedded code | Absolute URLs embedded in SharePoint customizations aren't updated. | Edit customizations that contain absolute URLs and if necessary, change the URLs to the new domain name. | | Teams on the web and Teams desktop app | The first time someone tries to access the Files tab for a team or private channel, they'll receive an error. The tab will work for all users after that. | None | | Teams on the web and Teams desktop app | It can take 72 hours for meeting notes to work (for both current and previous meetings). | None |
If your organization has gone through a rebranding, merger, or acquisition and n| Multi-Geo configurations | Your SharePoint domain name can't be changed if your organization is currently set up for Microsoft 365 Multi-Geo or was previously set up for it. | No action available. | | Point-in-time restoration | Restoring a site to a previous time before the domain name change isn't possible. | No action available.| | Root site replacement | Your [root site](modern-root-site.md) can't be replaced (using either the SharePoint admin center or the PowerShell cmdlet Invoke-SPOSiteSwap) between the time you schedule your domain name change and when it completes. | Replace your root site before you schedule the domain name change or after it completes. |
+| Special and government clouds | If your organization uses pecial clouds or government clouds (GCC, GCC High, DoD, etc.), your domain name can't be changed. | No action available. || Vanity domain configurations | If your SharePoint domain is, for example, teams.contoso.com (versus contoso.sharepoint.com), your domain name can't be changed. | No action available. | ## Step 1: Add the new domain name
|SharePoint||Set Crawl Log Permissions||https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/set-crawl-log-permissions.md||
description: "You can grant users or groups read access to crawl log informationAs a global or SharePoint admin in Microsoft 365, you can grant users read access to crawl log information for the tenant. The crawl log tracks information about the status of crawled content.
-A typical use case is in eDiscovery, where you can grant a security group permission to view the crawl log information for the tenant. The users in the security group can view the crawl log data via the eDiscovery portal to check whether crawled content was successfully added to the search index, or whether indexing failed because of an error.
+A typical use case is in eDiscovery, where you can grant a security group permission to view the crawl log information for the tenant. The users in the security group can view the crawl log data via the eDiscovery portal to check whether crawled content was successfully added to the search index, or whether indexing failed because of an error. For more information, see [Get started with eDiscovery (Standard) in Microsoft Purview](/microsoft-365/compliance/get-started-core-ediscovery) and [Investigating partially indexed items in eDiscovery](/microsoft-365/compliance/investigating-partially-indexed-items-in-ediscovery).## Grant users permission to view the crawl log information <a name="__top"> </a>
A typical use case is in eDiscovery, where you can grant a security group permis4. In the **Crawl Log Permissions** box, enter names or email addresses. The names of valid users or user groups appear in the list as you enter letters in the box.
-5. Select **OK**.
+5. Select **OK**.