+3. Optional: Run this command if you want to disable creation of booking calendars for all other users in your organization.

+Depending on the billing frequency that you chose when you bought your subscription, you receive an invoice monthly, every three months, every six months, or annually. The amount of time since the last invoice date is called the *Billing Period* and is shown on page one of the invoice, above the Billing Summary section. This time period represents the date range during which charges accrue for the current invoice.

+Each new subscription purchase is billed the next day. Changes you make to an existing subscription will appear on the monthly invoice around the beginning of the following month.

+ Title: "Planning your portal launch roll-out plan in SharePoint in Microsoft 365"

+description: "This article describes how you can plan your portal launch in SharePoint in Microsoft 365 and what steps to take for a successful launch."

+# Planning your portal launch roll-out plan in SharePoint in Microsoft 365

+This article describes how to plan your deployment and roll-out plan to SharePoint in Microsoft 365. It also provides approaches to follow as traditional load testing isn't permitted on SharePoint in Microsoft 365. SharePoint in Microsoft 365 is a cloud service and the load capabilities, health, and overall balance of load in the service are managed by Microsoft.

+## Overview of capacity planning in SharePoint in Microsoft 365

+In order to efficiently use capacity and deal with unexpected growth, in any farm, we have automation that tracks certain usage scenarios. While exact growth is unpredictable for any one tenant in any one farm, the aggregated sum of requests is predictable over time. By identifying the growth trends in SharePoint in Microsoft 365, we can plan for future expansion. For more information, see [Capacity planning and load testing SharePoint](capacity-planning-and-load-testing-sharepoint-online.md).

+A key part of a successful launch is the "wave" or "phased roll-out" approach.

+## Can I load test SharePoint in Microsoft 365?

+SharePoint in Microsoft 365 is a shared multi-tenanted environment that is balanced across farms and scale is adjusted in an on-going basis. Load testing an environment, like SharePoint in Microsoft 365, whose scale changes continuously won't only give you unexpected results but it isn't permitted.

+Learn more: [Capacity planning and load testing SharePoint in Microsoft 365](capacity-planning-and-load-testing-sharepoint-online.md)

+Pages from an on-premises deployment shouldn't simply be moved as they are onto SharePoint without reviewing them against recommended guidelines for SharePoint. The best approach is to always optimize any home page for any site or portal in SharePoint, as this is where most users in your organization will access as the starting point for your sites.

+- For all site pages in SharePoint, use the [Page Diagnostics tool](./page-diagnostics-for-spo.md), which is a Chromium extension that assists with analyzing and providing guidance. This tool can be used by site owners, editors, administrators, and developers as it is designed to be a starting point for analysis and optimization.

+The traditional big bang approach for site launches won't allow verification that customizations, external sources, services, or processes have been tested at the right scale. This approach doesn't mean that it takes months to launch, but it's recommended over at least several days dependent on your organization size. Following a wave roll-out plan therefore gives you the option to pause and resolve issues before proceeding with the next phase and therefore lowers the potential number of users impacted by any issues. SharePoint as a service scales your capacity based on usage and predicted usage and while we don't need you to notify us of your launch, you should follow the guidelines to ensure success.

+As shown in the following image, often the number of users that are invited is higher than those that actually use the site. This image shows a strategy about how to roll out a release. This method helps identify ways to improve the SharePoint site before most the users see it.

+In the pilot phase, it's good to get feedback from users that the organization trusts and knows will be engaged. This way it's possible to gauge how the system is being used, and how it's performing.

+- As you plan each wave, try to start with a small user base (less than 5,000 users). Increase the group sizes as you proceed with each wave. By creating a staggered approach, it allows for easier pause opportunities as needed.

+### App setup and connecting to SharePoint in Microsoft 365

+1. [Download the latest SharePoint Management Shell](https://go.microsoft.com/fwlink/p/?LinkId=255251).

+ > If you installed a previous version of the SharePoint Management Shell, go to Add or remove programs and uninstall "SharePoint Management Shell."

+1. Connect to SharePoint as a [global admin or SharePoint admin](/sharepoint/sharepoint-admin-role) in Microsoft 365. To learn how, see [Getting started with SharePoint Management Shell](/powershell/sharepoint/sharepoint-online/connect-sharepoint-online).

+Bidirectional redirection involves launching a new modern SharePoint portal to replace an existing SharePoint classic or modern portal. Users in active waves are redirected to the new site regardless of whether they navigate to the old or new site. Users in a non-launched wave that try to access the new site are redirected back to the old site until their wave is launched.

+Temporary page redirection should be used when no existing SharePoint portal exists. Users are directed to a new modern SharePoint portal in a staged manner. If a user is in a wave that hasn't been launched, they're redirected to a temporary page (any URL).

+[Planning your portal launch roll-out plan in SharePoint](./planportallaunchroll-out.md)

+ Title: "How modern authentication works for Office 2016 and Office 2019 client apps"

+- must-keep

+description: Learn how Microsoft 365 modern authentication features work differently for Office 2016 and 2019 client apps.

+# How modern authentication works for Office 2016 and Office 2019 client apps

+Read this article to learn how Office 2016 and Office 2019 client apps use modern authentication features based on the authentication configuration on the Microsoft 365 tenant for Exchange Online, SharePoint Online, and Skype for Business Online.

+Select the links below to see how Office 2016 and Office 2019 client authentication works with the Microsoft 365 services depending on whether or not modern authentication is turned on.

+The following table describes the authentication behavior for Office 2016 and Office 2019 client apps when they connect to Exchange Online with or without modern authentication.

+The following table describes the authentication behavior for Office 2016 and Office 2019 client apps when they connect to SharePoint Online with or without modern authentication.

+The following table describes the authentication behavior for Office 2016 and Office 2019 client apps when they connect to Skype for Business Online with or without modern authentication.

+ Title: Use the Page Diagnostics tool for SharePoint in Microsoft 365

+description: "Use the Page Diagnostics for SharePoint tool to analyze SharePoint in Microsoft 365 modern portal and classic publishing pages against a predefined set of performance criteria."

+This article describes how to use the **Page Diagnostics for SharePoint tool** to analyze SharePoint in Microsoft 365 modern and classic site pages against a predefined set of performance criteria.

+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 in Microsoft 365 modern portal and classic publishing site pages.

+> This tool only works for SharePoint in Microsoft 365, and canΓÇÖt be used on a SharePoint system page or on a SharePoint App page. The App page type is designed to be used for specific business applications within SharePoint in Microsoft 365 and not for portals. The tool is designed to optimize portal pages and Teams site pages.

+The tool generates a report for each analyzed page showing how the page performs against a predefined set of rules and displays detailed information when results for a test fall outside the baseline value. SharePoint administrators and designers can use the tool to troubleshoot performance issues and to ensure that new pages are optimized prior to publishing.

+1. Navigate to the SharePoint site page on SharePoint that you would like to review. We've allowed for "delay loading" of items on pages; therefore, the tool won't stop automatically (this is by design to accommodate all page load scenarios). To stop collection, select **Stop**. Make sure that the page load has completed before you stop data collection or you'll only capture a partial trace.

+ - **SPIISLatency** is the time in milliseconds taken for SharePoint begin loading the page. This value doesn't include the time taken for the web application to respond.

+[Tune SharePoint performance](tune-sharepoint-online-performance.md)

+[Use the Office 365 Content Delivery Network (CDN) with SharePoint](use-microsoft-365-cdn-with-spo.md)

+> **Have a performance issue between your client and Office 365 right now?** Follow the steps outlined in the [Performance troubleshooting plan for Office 365](performance-troubleshooting-plan.md).

+Performance improvements never really stop in the cloud, so neither does experience with keeping the cloud healthy and quick. Should you have a performance issue connecting from your location to Office 365, it's best not to start with or wait on a Support case. Instead, you should begin investigating the problem from 'the inside out.' That is, start inside of your network, and work your way out to Office 365. Before you open a case with Support, you can gather data and take actions that will explore, and might resolve, the problem.

+> Be aware of capacity planning and limits in Office 365. That information will put you ahead of the curve when trying to resolve a performance issue. Here's a link to the [Microsoft 365 and Office 365 service descriptions](/office365/servicedescriptions/office-365-service-descriptions-technet-library). This is a central hub, and all the services offered by Office 365 have a link that goes to their own Service Descriptions from here. That means, should you need to see the standard limits for SharePoint, for example, you would click [SharePoint Service Description](/office365/servicedescriptions/sharepoint-online-service-description/sharepoint-online-service-description) and locate its [SharePoint Limits section](/office365/servicedescriptions/sharepoint-online-service-description/sharepoint-online-limits).

+Service Incidents happen when the Office 365 service itself is having issues. You might see red or yellow icons under **Current health** in the Microsoft 365 admin center. You might notice performance on client computers connecting to Office 365 is slow. For example, if Current health reports a red icon and you see **Investigating** beside Exchange, you might then also get calls from people in your organization who complain that client mailboxes using Exchange Online are slow. In that case, it's reasonable to assume that your Exchange Online performance was a victim of Service issues.

+- You can replicate the problem too, or know it happens if you do the right series of steps.

+- Uploading my files to SharePoint is taking forever. Why is it slow in the afternoon, but any other time, it's fast? Can't it just be fast?

+The admin and troubleshooter can't be aware of the *details* of the problem from general statements like these. For example, they don't know when the problem started happening. The troubleshooter might not know the user works from home and only ever sees slow switching while on their home network. Or that the user runs other RAM intensive applications on the local client. Admins might not know the user is running an older operating system or hasn't run recent updates.

+When users report a performance problem, there's much information to collect. Getting and recording information is called scoping the issue. Here's a basic scoping list you can use to collect information about performance issues. This list isn't exhaustive, but it's a place to start:

+Some of these questions are more obvious than others. Most everyone will understand a troubleshooter needs the exact steps to reproduce the issue. After all, how else can you record what's wrong, and how else can you test if the issue is fixed? Less obvious are things like "What date and time did you see the issue?", and "Where in the world are you located?", information that can be used in tandem. Depending on when the user was working, a few hours of time difference might mean maintenance is already underway on parts of your company's network. For instance, your company has a hybrid implementation, like a hybrid SharePoint Search, which can query search indexes in both SharePoint in Microsoft 365 and an On-premises SharePoint Server 2013 instance, updates might be underway in the on-premises farm. If your company is all in the cloud, system maintenance might include adding or removing network hardware, rolling out updates that are company-wide, or making changes to DNS, or other core infrastructure.

+When you're troubleshooting a performance problem, it's a bit like a crime scene, you need to be precise and observant to draw any conclusions from the evidence. In order to do this, you must get a good problem statement by gathering evidence. It should include the computer's context, the user's context, when the problem began, and the exact steps that exposed the performance issue. This problem statement should be, and stay, the topmost page in your notes. By walking through the problem statement again after you work on the resolution, you're taking the steps to test and prove whether the actions you take have resolved the issue. This is critical to knowing when your work, there, is done.

+What's missing here is a performance baseline.

+Baselines give you a context for your performance. You should take a baseline occasionally to frequently, depending on the needs of your company. If you're a larger company, your Operations team may take baselines for your on-premises environment already. For example, if you patch all the Exchange servers on the first Monday of the month, and all your SharePoint servers on the third Monday, your Operations team probably has a list of tasks and scenarios it runs post-patching, to prove that critical functions are operational. For example, opening the Inbox, clicking Send/Receive, and making sure the folders update, or, in SharePoint, browsing the main page of the site, going into the enterprise Search page, and doing a search that returns results.

+ - Proxy servers are common egress points, so you can check your web browser to see what proxy server it's set to use, if any.

+The options are listed as **Simple** and **Advanced** because of the amount of expertise you need in order to find the performance data. A network trace will take much time, compared to running command-line tools like PsPing and TraceTCP. These two command-line tools were chosen because they don't use ICMP packets, which will be blocked by Office 365, and because they give the time in milliseconds that it takes to leave the client computer, or proxy server (if you have access) and arrive at Office 365. Each individual hop from one computer to another will end up with a time value, and that's great for baselines! Just as importantly, these command-line tools allow you to add a port number onto the command, this is useful because Office 365 communicates over port 443, which is the port used by Secure Sockets Layer and Transport Layer Security (SSL and TLS). However, other third-party tools might be better solutions for your situation. Microsoft doesn't support all of these tools, so if, for some reason, you can't get PsPing and TraceTCP working, move on to a network trace with a tool like Netmon.

+You can take a baseline before business hours, again during heavy use, and then again after hours. This means you might have a folder structure that looks a bit like this in the end:

+There are lots of different ways to do this, but using the format **\<dateTime\>\<what's happening in the test\>** is a good place to start. Being diligent about this will help a lot when you're trying to troubleshoot issues later. Later, you'll be able to say "I took two traces on February 8, one showed good performance and one showed bad, so we can compare them". This is helpful for troubleshooting.

+You need to have an organized way to keep your historical baselines. In this example, the simple methods produced three command-line outputs and the results were collected as screenshots, but you might have network capture files instead. Use the method that works best for you. Store your historical baselines and refer to them at points where you notice changes in the behavior of online services.

+There is no better time to start making baselines than during a pilot of the Office 365 service. Your office might have thousands of users, hundreds of thousands, or it might have five, but even with a few users, you can perform tests to measure fluctuations in performance. In the case of a large company, a representative sample of several hundred users piloting Office 365 can be projected outward to several thousands so you know where issues might arise before they happen.

+In the case of a small company, where on-boarding means that all users go to the service at the same time and there's no pilot, keep performance measures so that you have data to show to anyone who might have to troubleshoot a badly performing operation. For example, if you notice that all of a sudden you can walk around your building in the time it takes to upload a medium-sized graphic where it used to happen quickly.

+The objective of these simple methods is to learn to take, understand, and properly store simple performance baselines over time so that you're informed about Office 365 performance. Here's the simple diagram for simple, as you've seen before:

+There are a few ways to deal with the egress point, in this case, the proxy server. You can either trace from 1 to 2 and then 2 to 3, and then add the numbers in milliseconds to get a final total to the edge of your network. Or, you can configure the connection to bypass the proxy for Office 365 addresses. In a larger network with a firewall, reverse proxy, or some combination of the two, you might need to make exceptions on the proxy server that will allow traffic to pass for a lot of URLs. For the list of endpoints used by Office 365, see [Office 365 URLs and IP address ranges](https://support.office.com/article/8548a211-3fe7-47cb-abb1-355ea5aa88a2). If you have an authenticating proxy, begin by testing exceptions for the following:

+To add these to your proxy bypass list in Internet Explorer, go to **Tools** \> **Internet Options** \> **Connections** \> **LAN settings** \> **Advanced**. The advanced tab is also where you'll find your proxy server and proxy server port. You might need to select the checkbox **Use a proxy server for your LAN**, to access the **Advanced** button. You'll want to make sure that **Bypass proxy server for local addresses** is checked. Once you select **Advanced**, you'll see a text box where you can enter exceptions. Separate the wildcard URLs listed above with semi-colons, for example:

+You have to use [PSPing](/sysinternals/downloads/psping) or another tool that doesn't use ICMP packets that are blocked by Office 365 in order to do this test.

+If you're not familiar with proxy bypass, and prefer to take things step by step, you need to first find out the name of your proxy server. In Internet Explorer, go to **Tools** \> **Internet Options** \> **Connections** \> **LAN settings** \> **Advanced**. The **Advanced** tab is where you'll see your proxy server listed. Ping that proxy server at a command prompt by completing this task:

+ Your command might look like any of these examples:

+3. When the trace stops sending test packets, you'll get a small summary that lists an average, in milliseconds, and that's the value you are after. Take a screenshot of the prompt and save it using your naming convention. At this point it might also help to fill in the diagram with the value.

+Maybe you've taken a trace in the early morning, and your client can get to the proxy (or whatever egress server exits to the Internet) quickly. In this case, your numbers might look like this:

+In terms of troubleshooting, you might find something interesting just from keeping these baselines. For example, if you find that you generally have about 40 milliseconds to 59 milliseconds of latency from the proxy or egress point to the Office 365 URL, and have a client to proxy or egress point latency of about 3 milliseconds to 7 milliseconds (depending on the amount network traffic you're seeing during that time of day) then you'll surely know something is problematic if your last three client to proxy or egress baselines show a latency of 45 milliseconds.

+If you really want to know what is happening with your Internet requests to Office 365, you need to become familiar with network traces. It doesn't matter which tools you prefer for these traces, HTTPWatch, Netmon, Message Analyzer, Wireshark, Fiddler, Developer Dashboard tool or any other will do as long as that tool can capture and filter network traffic. You'll see in this section that it's beneficial to run more than one of these tools to get a more complete picture of the problem. When you're testing, some of these tools also act as proxies in their own right. Tools used in the companion article, [Performance troubleshooting plan for Office 365](performance-troubleshooting-plan.md), include [Netmon 3.4](https://www.microsoft.com/download/details.aspx?id=4865), [HTTPWatch](https://www.httpwatch.com/download/), or [WireShark](https://www.wireshark.org/).

+Taking a performance baseline is the simple part of this method, and many of the steps are the same as when you troubleshoot a performance issue. The more advanced methods of creating baselines for performance require you to take and store network traces. Most of the examples in this article use SharePoint, but you should develop a list of common actions across the Office 365 services to which you subscribe to test and record. Here's a baseline example:

+- Baseline list for SPO - **Step 3:** Upload a large file to a SharePoint document library and do a network trace. Save the trace.

+This list should include the most important common actions that users take against SharePoint. Notice that the last step, to trace going to OneDrive, builds-in a comparison between the load of the SharePoint home page (which is often customized by companies) and OneDrive home page, which is seldom customized. This is a basic test when it comes to a slow-loading SharePoint site. You can build a record of this difference into your testing.

+To tackle a performance problem, *right now*, you need to be taking a trace at the time you're experiencing the performance issue. You need to have the proper tools available to gather logs, and you need an action plan, that is, a list of troubleshooting actions to take to gather the best information that you can. The first thing to do is record the date and time of the test so that the files can be saved in a folder that reflect the timing. Next, narrow down to the problem steps themselves. These are the exact steps you'll use for testing. Don't forget the basics: if the issue is only with Outlook, make sure to record that the problem behavior happens in only one Office 365 service. Narrowing down the scope of this issue will help you to focus on something you can resolve.

+When you synchronize your on-premises directory with Microsoft 365, you have to have a verified domain in Microsoft Entra ID. Only the User Principal Names (UPNs) that are associated with the on-premises Active Directory Domain Services (AD DS) domain are synchronized. However, any UPN that contains a nonroutable domain, such as `.local` (example: billa@contoso.local), is synchronized to an `.onmicrosoft.com` domain (example: billa@contoso.onmicrosoft.com).

+If you currently use a `.local` domain for your user accounts in AD DS, we recommend that you change them to use a verified domain. For example, billa@contoso.com, in order to properly synchronize with your Microsoft 365 domain.

+## What if I only have a `.local` on-premises domain?

+Microsoft Entra Connect synchronizes your users' UPN and password so that users can sign in with the same credentials they use on-premises. However, Microsoft Entra Connect only synchronizes users to domains that are verified by Microsoft 365. Microsoft Entra ID verifies the domain, as it manages Microsoft 365 identities. In other words, the domain has to be a valid Internet domain (such as, .com, .org, .NET, .us). If your internal AD DS only uses a nonroutable domain (for example, `.local`), this can't possibly match the verified domain you have for your Microsoft 365 tenant. You can fix this issue by either changing your primary domain in your on-premises AD DS, or by adding one or more UPN suffixes.

+Change your primary domain to a domain you've verified in Microsoft 365, for example, contoso.com. Every user that has the domain `contoso.local` is then updated to contoso.com. This is an involved process, however, and an easier solution is described in the following section.

+You can solve the `.local` problem by registering new UPN suffix or suffixes in AD DS to match the domain (or domains) you verified in Microsoft 365. After you register the new suffix, you update the user UPNs to replace the `.local` with the new domain name, for example, so that a user account looks like billa@contoso.com.

+This article describes how you can use remote Windows PowerShell for Exchange Online to connect to a single customer tenancy and retrieve a report. By default, Windows PowerShell doesn't support aggregating reporting data from multiple customer tenancies. The reports you retrieve with this procedure are only for the _DelegatedOrg_ that you connect to.

+There are many other reporting cmdlets available for Exchange Online, Lync Online, SharePoint, and other services for message tracing that you can use. To learn more about the available reporting cmdlets, see the articles listed in the following section.

+When users authenticate in any of the Microsoft 365 web apps or mobile apps, a session is established. For the duration of the session, users won't need to reauthenticate. Sessions can expire when users are inactive, when they close the browser or tab, or when their authentication token expires for other reasons such as when their password has been reset. The Microsoft 365 services have different session timeouts to correspond with the typical use of each service.

+|Microsoft 365 admin center <br/> |You're asked to provide credentials for the admin center every 8 hours. <br/> |

+|SharePoint <br/> |5 days of inactivity as long as the users chooses **Keep me signed in**. If the user accesses SharePoint again after 24 or more hours have passed from the previous sign-in, the timeout value is reset to five days. <br/> |

+|Outlook Web App <br/> |Six hours. <br/> You can change this value by using the _ActivityBasedAuthenticationTimeoutInterval_ parameter in the [Set-OrganizationConfig](/powershell/module/exchange/set-organizationconfig) cmdlet. <br/> |

+|Viva Engage with Microsoft 365 Sign-In <br/> |Lifetime of the browser. If users close the browser and access Viva Engage in a new browser, Viva Engage will reauthenticate them with Microsoft 365. If users use third-party browsers that cache cookies, they may not need to reauthenticate when they reopen the browser. <br/> > [!NOTE]> This is valid only for networks using Microsoft 365 Sign-In for Viva Engage. |

+- essentials-overview

+description: Learn about SharePoint storage quotas in multi-geo environments and how quotas can be managed by the SharePoint admin.

+With the SharePoint geo storage quota setting, you can manage the storage quota for each geo location. When you allocate a storage quota for a geo location, it becomes the maximum amount of storage available for that geo location, and is deducted from the available tenant storage quota. The remaining available tenant storage quota is then shared across the configured geo locations for which a specific storage quota hasn't been allocated.

+The SharePoint storage quota for any geo location is allocated by the SharePoint administrator by connecting to the central location. Geo administrators for satellite locations can view the storage quota but can't allocate it.

+Use the [Microsoft SharePoint Module](https://www.microsoft.com/download/details.aspx?id=35588) and connect to the central location to allocate the storage quota for a geo location.

+- **Use the mailbox move capabilities with an Exchange hybrid deployment.** With an Exchange hybrid deployment, offline mail (in the form of .OST files) doesn't require redownload when migrating to Exchange Online. This significantly reduces your download bandwidth requirements.

+- **Schedule mailbox moves to occur during periods of low Internet traffic and low on-premises Exchange use.** When scheduling moves, migration requests are submitted to the mailbox replication proxy and might not take place immediately.

+ Title: "Tune SharePoint in Microsoft 365 performance"

+description: "Contains links to other articles that tell you how to improve performance of page download times for SharePoint in Microsoft 365."

+# Tune SharePoint in Microsoft 365 performance

+This article contains links to other articles that tell you how to improve performance of page download times for SharePoint in Microsoft 365. This article is part of the [Network planning and performance tuning for Office 365](./network-planning-and-performance.md) project.

+## Articles about fine tuning SharePoint in Microsoft 365 performance

+Use these articles to fine tune SharePoint in Microsoft 365 performance.

+- [Introduction to performance tuning for SharePoint](introduction-to-performance-tuning-for-sharepoint-online.md)

+- [Use the Page Diagnostics tool for SharePoint](page-diagnostics-for-spo.md)

+- [Navigation options for SharePoint](navigation-options-for-sharepoint-online.md)

+- [Performance guidance for SharePoint portals](/sharepoint/dev/solution-guidance/portal-performance)

+- [Image optimization for SharePoint](image-optimization-for-sharepoint-online.md)

+- [Delay loading images and JavaScript in SharePoint](delay-loading-images-and-javascript-in-sharepoint-online.md)

+- [Minification and bundling in SharePoint](minification-and-bundling-in-sharepoint-online.md)

+- [Use the Office 365 Content Delivery Network (CDN) with SharePoint](use-microsoft-365-cdn-with-spo.md)

+- [Using Content Search Web Part instead of Content Query Web Part to improve performance in SharePoint](using-content-search-web-part-instead-of-content-query-web-part-to-improve-perfo.md)

+- [Capacity planning and load testing SharePoint](capacity-planning-and-load-testing-sharepoint-online.md)

+- [Diagnosing performance issues with SharePoint](diagnosing-performance-issues-with-sharepoint-online.md)

+- [Using the object cache with SharePoint](using-the-object-cache-with-sharepoint-online.md)

+- [How to: Avoid getting throttled or blocked in SharePoint](/sharepoint/dev/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online)

+- [Optimize iFrames in SharePoint modern portal pages](modern-iframe-optimization.md)

+- [Optimize web part performance in SharePoint modern portal pages](modern-web-part-optimization.md)

+- [Optimize page calls in SharePoint modern portal pages](modern-page-call-optimization.md)

+- [Optimize page weight in SharePoint modern portal pages](modern-page-weight-optimization.md)

+- [Optimize images in SharePoint modern portal pages](modern-image-optimization.md)

+- Reports for SharePoint:

+ - [Get started with SharePoint Management Shell](/powershell/sharepoint/sharepoint-online/connect-sharepoint-online)

+ Title: "Using Content Search Web Part instead of Content Query Web Part to improve performance in 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 2013 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.

+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.

+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.

+## Adding a Content Search Web Part in SharePoint in Microsoft 365

+ Title: "Using the object cache with SharePoint in Microsoft 365"

+description: "This article explains the difference between using the object cache in SharePoint Server 2013 on-premises and SharePoint in Microsoft 365."

+# Using the object cache with SharePoint

+This article explains the difference between using the object cache in SharePoint Server 2013 on-premises and SharePoint in Microsoft 365.

+There is significant negative impact of relying on the object cache in SharePoint deployment. Any dependency on object cache in SharePoint will reduce the reliability of your page.

+## How the SharePoint in Microsoft 365 and SharePoint Server 2013 object cache works

+In contrast, in SharePoint in Microsoft 365, there are many more servers but also many more sites. Each user may connect to a different front-end web server that doesn't have the cache populated. Or, perhaps the cache does get populated for a server, but the next user to that front-end web server requests a page from a different site. Or, even if the next user requests the same page as on their previous visit, they are load-balanced to a different front-end web server that doesn't have that page in its cache. In this last case, caching doesn't help the users at all.

+

+For all of these reasons, relying on users getting cached objects is not an effective way to ensure a quality user experience and page load times in SharePoint.

+## If we can't rely on the object cache to improve performance in SharePoint, what do we use instead?

+Since you shouldn't rely on caching in SharePoint, you should evaluate alternative design approaches for SharePoint customizations that use the object cache. This means using approaches for performance issues, which do not rely on the object caching in order to produce good results for users. This is described in some of the other articles in this series and includes:

+- [Navigation options for SharePoint](navigation-options-for-sharepoint-online.md)

+- [Minification and bundling in SharePoint](minification-and-bundling-in-sharepoint-online.md)

+- [Use the Office 365 Content Delivery Network (CDN) with SharePoint](use-microsoft-365-cdn-with-spo.md)

+- [Delay loading images and JavaScript in SharePoint](delay-loading-images-and-javascript-in-sharepoint-online.md)

+description: View the health status of Microsoft 365 services before you call support to see if there's an active service interruption.

+You can view the health of your Microsoft services, including Office on the web, Microsoft Teams, Exchange Online, and Microsoft Dynamics 365 on the **Service health** page in the [Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?linkid=2024339). If you're experiencing problems with a cloud service, you can check the service health to determine whether this is a known issue with a resolution in progress before you call support or spend time troubleshooting.

+If you're unable to sign in to the admin center, you can use the [service status page](https://status.cloud.microsoft) to check for known issues preventing you from logging into your tenant. Also, sign up to follow us at [@MSFT365status](https://twitter.com/MSFT365Status) on **X** (Twitter) to see information on certain events.

+2. To view service health, in the left-hand navigation of the admin center, go to **Health** > **Service health**, or select the **Service health** card on the **Home dashboard**. The dashboard card indicates whether there's an active service issue and links to the detailed **Service health** page.

+The **Issues for your organization to act on** section lists any issues detected in your environment that require your action. If there are no issues in your environment that need action, this section won't be visible.

+The **Issue history** tab shows all incidents and advisories that have been resolved within the last 7 or 30 days.

+||If a service has an advisory shown, we're aware of a problem that is affecting some users, but the service is still available. In an advisory, there's often a workaround to the problem and the problem might be intermittent or is limited in scope and user impact. |

+||If a service has an active incident shown, it's a critical issue and the service or a major function of the service is unavailable. For example, users might be unable to send and receive email or unable to sign-in. Incidents will have noticeable impact to users. When there's an incident in progress, we'll provide updates regarding the investigation, mitigation efforts, and confirmation of resolution in the Service health dashboard. |

+|**Service degradation** | We've confirmed that there's an issue that might affect use of a service or feature. You might see this status if a service is performing more slowly than usual, there are intermittent interruptions, or if a feature isn't working, for example. |

+Service health posts are written in English due to the timeliness of the information we're posting but can be automatically displayed in the language specified by your personal language settings for Microsoft 365. If you set your preferred language to anything other than English, you'll see an option in the Service health page to automatically translate posts. The messages are machine translated to your preferred language, meaning that a computer did the translation.

+Before you can choose your language settings, you have to set your preferred language. No translation options are shown when your language is set to English. You can't specify a preferred language for others; each person has to change this setting for themselves.

+Before you can choose your language settings, you have to set your preferred language. No translation options are shown when your language is set to English. You can't specify a preferred language for others; each person has to change this setting for themselves.

+## Related articles

+Team membership is automatically managed over time through the power of dynamic teams. As frontline workers are onboarded and offboarded, and as they change locations, their memberships in these teams are updated accordingly.

+- Users must have a Microsoft 365 F3, F1, E3, or E5 license. If a user doesn't have one of these licenses, they need a Microsoft Entra ID P1 add-on license to use dynamic teams. [Learn more about frontline licensing](flw-licensing-options.md).

+The [Teams frontline usage report](frontline-usage-report.md) on the usage dashboard of the Manage frontline teams page gives you an overview of usage activity in Teams for each of your frontline locations. You can view data, such as the number of active users and last activity date, to quickly see how many users at your frontline locations are using Teams to communicate and collaborate.

+- Create teams using prebuilt templates or your own custom templates.

+Create two CSV files for each batch of teams that you deploy:

+ |**Team Template ID**|If you're creating a team from a prebuilt or custom template, specify the team template ID. See [Get started with team templates in the Teams admin center](/microsoftteams/get-started-with-teams-templates-in-the-admin-console) for a list prebuilt team templates and IDs. If you want to use the standard default team template, leave this blank.|

+Use the following examples to help you create your CSV files. Here, we named the files, Teams.csv and Users.csv.

+Now that you created your CSV files and set up your environment, you're ready to deploy your teams.

+ The recipients will receive email notifications about deployment status. The email contains the orchestration ID for the batch you submitted and any errors that might have occurred.

+- Through the **App usage - Microsoft Teams** card. (Coming soon). This card shows the overall percentage of users across all your frontline teams that have been active on Teams in the last 30 days. Choose **View details** to go to the dashboard.

+Keep in mind that any custom [app setup policies](/microsoftteams/teams-app-setup-policies) assigned to users take precedence. This means that if a user already has a custom app setup policy assigned to them, the user gets the configuration defined in the custom app setup policy. To learn more about how the feature works with Teams app policies, including the global app setup policy, see the [Scenarios](#scenarios) section later in this article.

+Viva Connections is part of the tailored apps experience. Frontline users who see the tailored app experience have Viva Connections pinned in the first position on both mobile and desktop.

+- [Use app setup policies to pin and auto install apps for users](/microsoftteams/teams-app-setup-policies)

+- [Use app permission policies to control user access to apps](/microsoftteams/teams-app-permission-policies)