| Category | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| admin | Microsoft 365 Copilot Usage | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/activity-reports/microsoft-365-copilot-usage.md | To access accurate information on Copilot for Microsoft 365 usage, use one of th Yes. Intelligent Recap has been captured in Teams Copilot in Copilot for Microsoft 365 usage. +### Is Copilot chat in Outlook usage counted towards active users of Outlook Copilot active users? ++No. Meanwhile, Copilot chat in Outlook usage is counted towards Copilot chat active users. + ### WhatΓÇÖs the scope of the user-level table? The user-level table in the report is configured to show all users who were licensed for Copilot for Microsoft 365 at any point over the past 180 days, even if the user has since had the license removed or never had any Copilot active usage. |
| enterprise | Enabling SP Multigeo Satellite Geolocation | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/Enabling-SP-MultiGeo-satellite-geolocation.md | Title: "Enabling SharePoint Multi-Geo in your satellite geo location" Previously updated : 08/10/2020 Last updated : 08/01/2024 +- must-keep ms.localizationpriority: medium description: This article provides information for Global or SharePoint admins about enabling SharePoint Multi-Geo in satellite geo locations. description: This article provides information for Global or SharePoint admins a This article is for Global or SharePoint administrators who created a Multi-Geo satellite location **before** SharePoint Multi-Geo capabilities became generally available on March 27, 2019, and who didn't enable SharePoint Multi-Geo in their satellite geo locations. ->[!Note] ->If you have added a new geo location **after March 27th, 2019**, you do not need to perform these instructions, as your new geo location will already be enabled for OneDrive and SharePoint Multi-Geo. +> [!NOTE] +> If you have added a new geo location **after March 27th, 2019**, you do not need to perform these instructions, as your new geo location will already be enabled for OneDrive and SharePoint Multi-Geo. -These instructions allow you to enable SharePoint in your satellite location, so your Multi-Geo satellite users can take advantage of both OneDrive and SharePoint Multi-Geo capabilities in O365. +These instructions allow you to enable SharePoint in your satellite location, so your Multi-Geo satellite users can take advantage of both OneDrive and SharePoint Multi-Geo capabilities in O365. ->[!IMPORTANT] ->Please note that this is a one way enablement. Once you set SPO mode, you will not be able to revert your tenant to OneDrive only Multi-Geo mode without an escalation with support. +> [!IMPORTANT] +> Please note that this is a one way enablement. Once you set SPO mode, you will not be able to revert your tenant to OneDrive only Multi-Geo mode without an escalation with support. ## To set a geo location into SPO Mode To set a geo location into SPO mode, connect to the geo location you want to set in SPO Mode: -1. Open your SharePoint Online Management Shell -2. Connect-SPOService -URL "https://$tenantGeo-admin.sharepoint.com" -Credential $credential -3. Set-SPOMultiGeoExperience</br></br> +1. Open your SharePoint Online Management Shell and run the following commands: +2. `Connect-SPOService -URL "https://$tenantGeo-admin.sharepoint.com" -Credential Get-Credential` +3. `Set-SPOMultiGeoExperience`</br></br> -4. This operation usually takes about an hour while we perform various publish backs in the service and re-stamp your tenant. After at least 1 hour, perform a Get-SPOMultiGeoExperience. This shows you whether this geo location is in SPO mode.</br></br> - +4. This operation usually takes about an hour while we perform various publish backs in the service and re-stamp your tenant. After at least 1 hour, perform a `Get-SPOMultiGeoExperience`. This shows you whether this geo location is in SPO mode.</br></br> + ++> [!NOTE] +> Certain caches in the service update every 24 hours, so it is possible that for a period of up to 24 hours, your satellite geo may intermittently behave as if it was still in ODB mode. This does not cause any technical issues. - ->[!Note] ->Certain caches in the service update every 24 hours, so it is possible that for a period of up to 24 hours, your satellite geo may intermittently behave as if it was still in ODB mode. This does not cause any technical issues. - For additional information regarding SharePoint Multi-Geo, refer to [aka.ms/sharepointmultigeo](multi-geo-capabilities-in-onedrive-and-sharepoint-online-in-microsoft-365.md) |
| enterprise | Contoso Mdm | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/contoso-mdm.md | f1.keywords: - NOCSH Previously updated : 09/13/2018 Last updated : 08/01/2024 audience: ITPro +- must-keep description: Understand how Contoso uses Microsoft Intune in Microsoft 365 for enterprise to manage its devices and the apps that run on them. |
| enterprise | Delay Loading Images And Javascript In Sharepoint Online | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/delay-loading-images-and-javascript-in-sharepoint-online.md | Title: "Delay loading images and JavaScript in SharePoint" Previously updated : 12/3/2019 Last updated : 08/01/2024 audience: Admin +- must-keep f1.keywords: - CSH Don't miss the article and code sample on [JavaScript injection](https://go.micr [How to: Apply a master page to a site in SharePoint 2013](/sharepoint/dev/general-development/how-to-apply-a-master-page-to-a-site-in-sharepoint) -[How to: Create a page layout in SharePoint 2013](/sharepoint/dev/general-development/how-to-create-a-page-layout-in-sharepoint) +[How to: Create a page layout in SharePoint 2013](/sharepoint/dev/general-development/how-to-create-a-page-layout-in-sharepoint) |
| enterprise | Deploy High Availability Federated Authentication For Microsoft 365 In Azure | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/deploy-high-availability-federated-authentication-for-microsoft-365-in-azure.md | Title: "Deploy high availability federated authentication for Microsoft 365 in A Previously updated : 11/25/2019 Last updated : 08/01/2024 audience: ITPro +- must-keep f1.keywords: - CSH description: "Summary: Configure high availability federated authentication for This article has links to the step-by-step instructions for deploying high availability federated authentication for Microsoft 365 in Azure infrastructure services with these virtual machines: - Two web application proxy servers- + - Two Active Directory Federation Services (AD FS) servers- + - Two replica domain controllers- + - One directory synchronization server running Microsoft Entra Connect- + Here's the configuration, with placeholder names for each server. **A high availability federated authentication for Microsoft 365 infrastructure in Azure** All of the virtual machines are in a single cross-premises Azure virtual network Each pair of virtual machines for a specific role is in its own subnet and availability set. > [!NOTE]-> Because this VNet is connected to the on-premises network, this configuration does not include jumpbox or monitoring virtual machines on a management subnet. For more information, see [Running Windows VMs for an N-tier architecture](/azure/guidance/guidance-compute-n-tier-vm). +> Because this VNet is connected to the on-premises network, this configuration does not include jumpbox or monitoring virtual machines on a management subnet. For more information, see [Running Windows VMs for an N-tier architecture](/azure/guidance/guidance-compute-n-tier-vm). The result of this configuration is that you'll have federated authentication for all of your Microsoft 365 users, in which they can use their AD DS credentials to sign in rather than their Microsoft 365 account. The federated authentication infrastructure uses a redundant set of servers that are more easily deployed in Azure infrastructure services, rather than in your on-premises edge network. The result of this configuration is that you'll have federated authentication fo This baseline configuration requires the following set of Azure services and components: - Seven virtual machines- + - One cross-premises virtual network with four subnets- + - Four resource groups- + - Three availability sets- + - One Azure subscription- + Here are the virtual machines and their default sizes for this configuration. |**Item**|**Virtual machine description**|**Azure gallery image**|**Default size**| To compute the estimated costs for this configuration, see the [Azure pricing ca You deploy this workload in the following phases: - [Phase 1: Configure Azure](high-availability-federated-authentication-phase-1-configure-azure.md). Create resource groups, storage accounts, availability sets, and a cross-premises virtual network.- + - [Phase 2: Configure domain controllers](high-availability-federated-authentication-phase-2-configure-domain-controllers.md). Create and configure replica AD DS domain controllers and the directory synchronization server.- + - [Phase 3: Configure AD FS servers](high-availability-federated-authentication-phase-3-configure-ad-fs-servers.md). Create and configure the two AD FS servers.- + - [Phase 4: Configure web application proxies](high-availability-federated-authentication-phase-4-configure-web-application-pro.md). Create and configure the two web application proxy servers.- + - [Phase 5: Configure federated authentication for Microsoft 365](high-availability-federated-authentication-phase-5-configure-federated-authentic.md). Configure federated authentication for your Microsoft 365 subscription.- + These articles provide a prescriptive, phase-by-phase guide for a predefined architecture to create a functional, high availability federated authentication for Microsoft 365 in Azure infrastructure services. Keep the following in mind: - If you're an experienced AD FS implementer, feel free to adapt the instructions in phases 3 and 4 and build the set of servers that best suits your needs.- + - If you already have an existing Azure hybrid cloud deployment with an existing cross-premises virtual network, feel free to adapt or skip the instructions in phases 1 and 2 and place the AD FS and web application proxy servers on the appropriate subnets.- + To build a dev/test environment or a proof-of-concept of this configuration, see [Federated identity for your Microsoft 365 dev/test environment](federated-identity-for-your-microsoft-365-dev-test-environment.md). ## Next step |
| enterprise | Deploy Update Channels Examples | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/deploy-update-channels-examples.md | f1.keywords: - NOCSH Previously updated : 07/21/2020 Last updated : 08/01/2024 audience: ITPro +- must-keep description: How example organizations deploy and update using channels. |
| enterprise | Disable Access To Sway With Microsoft 365 Powershell | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/disable-access-to-sway-with-microsoft-365-powershell.md | Title: "Disable access to Sway with PowerShell for Microsoft 365" Previously updated : 07/17/2020 Last updated : 08/01/2024 audience: Admin search.appverid: - scotvorg - Ent_O365+- must-keep f1.keywords: - CSH description: "Learn where to download the ManageSway.ps1 PowerShell script that The ManageSway.ps1 PowerShell script lets you view and disable services in your Microsoft 365 organization, including Sway. This script automates the procedures that are described in the following topics: - [View licenses and services with PowerShell](view-licenses-and-services-with-microsoft-365-powershell.md)- + - [Disable access to services with PowerShell](disable-access-to-services-with-microsoft-365-powershell.md)- + You need to download the two files that are associated with the script: - The ManageSway.ps1 script at [https://go.microsoft.com/fwlink/p/?LinkId=785070](https://go.microsoft.com/fwlink/p/?LinkId=785070)- -- The help file for the script at [https://go.microsoft.com/fwlink/p/?LinkId=785072](https://go.microsoft.com/fwlink/p/?LinkId=785072)- +- The help file for the script at [https://go.microsoft.com/fwlink/p/?LinkId=785072](https://go.microsoft.com/fwlink/p/?LinkId=785072) |
| enterprise | Modern Page Call Optimization | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/modern-page-call-optimization.md | Title: "Optimize page calls in SharePoint modern and classic publishing site pages" + Title: "Optimize page calls in SharePoint in Microsoft 365 modern and classic publishing site pages" Previously updated : 03/11/2020 Last updated : 08/01/2024 audience: ITPro +- must-keep f1.keywords: - CSH search.appverid: - MET150-description: "Learn how to optimize modern and classic publishing site pages in SharePoint by limiting the number of calls to SharePoint service endpoints." +description: "Learn how to optimize modern and classic publishing site pages in SharePoint in Microsoft 365 by limiting the number of calls to SharePoint service endpoints." -# Optimize page calls in SharePoint modern and classic publishing site pages +# Optimize page calls in SharePoint in Microsoft 365 modern and classic publishing site pages -Both SharePoint modern and classic publishing sites contain links that load data from (or make calls to) SharePoint features and CDNs. The more calls made by a page, the longer the page takes to load. This is known as **end user perceived latency** or **EUPL**. +Both SharePoint in Microsoft 365 modern and classic publishing sites contain links that load data from (or make calls to) SharePoint features and CDNs. The more calls made by a page, the longer the page takes to load. This is known as **end user perceived latency** or **EUPL**. This article will help you understand how to determine the number and impact of calls to external endpoints from your modern and classic publishing site pages and how to limit their effect on end user perceived latency. This article will help you understand how to determine the number and impact of ## Use the Page Diagnostics for SharePoint tool to analyze page calls -The Page Diagnostics for SharePoint tool is a browser extension for the new Microsoft Edge (https://www.microsoft.com/edge) and Chrome browsers that analyzes both SharePoint modern portal and classic publishing site pages. The tool provides a report for each analyzed page showing how the page performs against a defined set of performance criteria. To install and learn about the Page Diagnostics for SharePoint tool, visit [Use the Page Diagnostics tool for SharePoint](page-diagnostics-for-spo.md). +The Page Diagnostics for SharePoint tool is a browser extension for Microsoft Edge and Chrome browsers that analyzes both SharePoint in Microsoft 365 modern portal and classic publishing site pages. The tool provides a report for each analyzed page showing how the page performs against a defined set of performance criteria. To install and learn about the Page Diagnostics for SharePoint tool, visit [Use the Page Diagnostics tool for SharePoint](page-diagnostics-for-spo.md). >[!NOTE]->The Page Diagnostics tool only works for SharePoint, and cannot be used on a SharePoint system page. +>The Page Diagnostics tool only works for SharePoint in Microsoft 365, and cannot be used on a SharePoint system page. When you analyze a SharePoint site page with the Page Diagnostics for SharePoint tool, you can see information about external calls in the **Requests to SharePoint** result in the _Diagnostic tests_ pane. The line will appear in green if the site page contains fewer than the baseline number of calls, and red if the page exceeds the baseline number. The baseline number is different for modern and classic pages because classic site pages use HTTP1.1 and modern pages use HTTP2.0: Before you make page revisions to remediate performance issues, make a note of t [Tune SharePoint performance](tune-sharepoint-online-performance.md) -[Tune Office 365 performance](tune-microsoft-365-performance.md) +[Tune Microsoft 365 performance](tune-microsoft-365-performance.md) [Performance in the modern SharePoint experience](/sharepoint/modern-experience-performance) [Content delivery networks](content-delivery-networks.md) -[Use the Office 365 Content Delivery Network (CDN) with SharePoint](use-microsoft-365-cdn-with-spo.md) +[Use the Microsoft 365 Content Delivery Network (CDN) with SharePoint](use-microsoft-365-cdn-with-spo.md) |
| enterprise | Using Content Search Web Part Instead Of Content Query Web Part To Improve Perfo | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/using-content-search-web-part-instead-of-content-query-web-part-to-improve-perfo.md | Title: "Using Content Search Web Part instead of Content Query Web Part to impro Previously updated : 4/20/2015 Last updated : 08/01/2024 audience: Admin +- must-keep f1.keywords: - CSH search.appverid: - MET150 - SPO160 ms.assetid: e8ce6b72-745b-464a-85c7-cbf6eb53391b-description: Learn how to increase performance by replacing the Content Query Web Part with the Content Search Web Part in SharePoint Server 2013 and SharePoint in Microsoft 365. +description: Learn how to increase performance by replacing the Content Query Web Part with the Content Search Web Part in SharePoint Server 2016 and SharePoint in Microsoft 365. # Using Content Search Web Part instead of Content Query Web Part to improve performance in SharePoint in Microsoft 365 -This article describes how to increase performance by replacing the Content Query Web Part with the Content Search Web Part in SharePoint Server 2013 and SharePoint in Microsoft 365. +This article describes how to increase performance by replacing the Content Query Web Part with the Content Search Web Part in SharePoint Server 2016 and SharePoint in Microsoft 365. -One of the most powerful new features of SharePoint Server 2013 and SharePoint in Microsoft 365 is the Content Search Web Part (CSWP). This Web Part uses the search index to quickly retrieve results, which are shown to the user. Use the Content Search Web Part instead of the Content Query Web Part (CQWP) in your pages to improve performance for your users. +One of the most powerful features of SharePoint Server 2016 and SharePoint in Microsoft 365 is the Content Search Web Part (CSWP). This Web Part uses the search index to quickly retrieve results, which are shown to the user. Use the Content Search Web Part instead of the Content Query Web Part (CQWP) in your pages to improve performance for your users. Using a Content Search Web Part over a Content Query Web Part will almost always result in better page load performance on SharePoint. There's a little additional configuration to get the right query, but the rewards are improved performance and happier users. The following examples show the relative performance gains you may receive when This example site has the following characteristics: - 8 levels of subsites.- + - Lists using a custom "fruit" content type.- + - In the Web Part, the content query is broad, returning all items with the content type of "fruit".- + - The example only uses 50 items across the 8 sites. The effects will be even more pronounced for sites with more content.- + Here's a screenshot of the results of the Content Query Web Part.  -In Internet Explorer, use the **Network** tab of the F12 developer tools to look at the details for the response header. In the following screenshot, the value for the **SPRequestDuration** for this page load is 924 milliseconds. +In Internet Explorer, use the **Network** tab of the F12 developer tools to look at the details for the response header. In the following screenshot, the value for the **SPRequestDuration** for this page load is 924 milliseconds.  - **SPRequestDuration** indicates the amount of work that is done on the server to prepare the page. Switching Content by Query Web Parts with Content by Search Web Parts dramatically reduces the time it takes to render the page. By contrast, a page with an equivalent Content Search Web Part, returning the same number of results has an **SPRequestDuration** value of 106 milliseconds as shown in this screenshot: + **SPRequestDuration** indicates the amount of work that is done on the server to prepare the page. Switching Content by Query Web Parts with Content by Search Web Parts dramatically reduces the time it takes to render the page. By contrast, a page with an equivalent Content Search Web Part, returning the same number of results has an **SPRequestDuration** value of 106 milliseconds as shown in this screenshot:  Once you've added a Content Search Web Part, you can refine the search and retur ## Query building and testing tool For a tool to build and test complex queries, see the [Search Query Tool](https://github.com/pnp/PnP-Tools/tree/master/Solutions/SharePoint.Search.QueryTool#download-the-tool).- - |