Merge pull request #9084 from MicrosoftDocs/main

Auto push to live 2025-06-09 10:01:57

Author: Deland-Han

support/entra/entra-id/toc.yml

@@ -291,18 +291,20 @@
       href: mfa/cannot-verify-account-reset-pwd.md
 - name: Microsoft Graph Users, Groups, and Entra APIs
   items: 
-   - name: Handling errors in Graph API requests with Invoke-RestMethod
-     href: app-integration/graph-api-error-handling-invoke-restmethod.md
-   - name: Troubleshoot Authorization RequestDenied error
-     href: app-integration/troubleshoot-authorization-requestdenied-graph-api.md
    - name: 403 error when adding a user to a group
      href: users-groups-entra-apis/authorization-requestdenied-403-error-add-user-group.md
    - name: 404 error when managing objects
      href: app-integration/404-not-found-error-manage-objects-microsoft-graph.md
-   - name: Use managed identities to call Graph APIs in VB.Net and C#
-     href: users-groups-entra-apis/call-graph-api-using-managed-dentities.md
+   - name: Change enumeration is not supported for requested tenant
+     href: users-groups-entra-apis/delta-query-not-supported-for-aad-b2c-tenant.md
+   - name: Handling errors in Graph API requests with Invoke-RestMethod
+     href: app-integration/graph-api-error-handling-invoke-restmethod.md
+   - name: Troubleshoot Authorization RequestDenied error
+     href: app-integration/troubleshoot-authorization-requestdenied-graph-api.md
    - name: The memberOf API returns null values for properties
      href: users-groups-entra-apis/memberof-api-returns-null-properties.md
+   - name: Use managed identities to call Graph APIs in VB.Net and C#
+     href: users-groups-entra-apis/call-graph-api-using-managed-dentities.md
    - name: Getting access denied errors (Authorization)
      items:
       - name: Add an owner to an application

support/entra/entra-id/users-groups-entra-apis/delta-query-not-supported-for-aad-b2c-tenant.md

@@ -0,0 +1,36 @@
+---
+title: Change Enumeration Is Not Supported for Requested Tenant
+description: Describes an issue in which you receive the Request_UnsupportedQuery error code when you run a Microsoft Graph delta query.
+ms.date: 06/09/2025
+ms.service: entra-id
+ms.custom: sap:Problem with querying or provisioning resources
+ms.reviewer: bachoang, v-weizhu
+---
+# Error "Change enumeration is not supported for requested tenant" when running a Microsoft Graph delta query
+
+This article provides a solution to an error that occurs when you run a Microsoft Graph delta query.
+
+## Symptoms
+
+When executing a [Microsoft Graph delta query](/graph/delta-query-overview), such as `GET https://graph.microsoft.com/beta/users/delta`, you might receive the following error response:
+
+```output
+'error': {
+'code': 'Request_UnsupportedQuery',
+'message': 'Change enumeration is not supported for requested tenant.',
+'innerError': {
+'request-id': '<request-id>',
+'date': '2020-05-22T13:17:45'
+    }
+}
+```
+
+## Cause
+
+This issue occurs when your tenant is an [Azure Active Directory (AD) B2C](/azure/active-directory-b2c/overview) tenant. Currently, differential or delta queries aren't supported in Azure AD B2C tenants.
+
+## Solution
+
+Run a delta query in a regular Microsoft Entra tenant.
+
+[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/sql/database-engine/performance/troubleshoot-high-cpu-usage-issues.md

@@ -1,7 +1,7 @@
 ---
 title: Troubleshoot high-CPU-usage issues in SQL Server
 description: This article provides a procedure to help you fix high-CPU-usage issues on a server that is running SQL Server.
-ms.date: 01/10/2025
+ms.date: 06/09/2025
 ms.custom: sap:SQL resource usage and configuration (CPU, Memory, Storage)
 ms.topic: troubleshooting
 ms.reviewer: jopilov, v-jayaramanp, v-sidong
@@ -59,7 +59,7 @@ Use one of the following tools to check whether the SQL Server process is actual
 
 ## Step 2: Identify queries contributing to CPU usage
 
-If the `Sqlservr.exe` process is causing high CPU usage, by far, the most common reason is SQL Server queries that perform table or index scans, followed by sort, hash operations and loops (nested loop operator or WHILE (T-SQL)). To get an idea of how much CPU the queries are currently using, out of overall CPU capacity, run the following statement:
+If the `Sqlservr.exe` process is causing high CPU usage, by far, the most common reason is SQL Server queries that perform table or index scans, followed by sort and hash operations and loops (nested loop operator or WHILE (T-SQL)). To get an idea of how much CPU the queries are currently using, out of overall CPU capacity, run the following statement:
 
 ```sql
 DECLARE @init_sum_cpu_time int,
@@ -203,11 +203,15 @@ If your SQL Server instance experiences a high CPU scenario caused by spinlock c
 > [!NOTE]
 > High CPU usage may result from spinlock contention on many other spinlock types. For more information on spinlocks, see [Diagnose and resolve spinlock contention on SQL Server](/sql/relational-databases/diagnose-resolve-spinlock-contention).
 
-## Step 9: Configure your virtual machine
+## Step 9: Check your power plan settings at the OS level
+
+SQL Server workloads may experience reduced performance and cause high CPU on the system when Windows is configured with the default **Balanced** power plan. The **Balanced** power plan setting might lower the CPU clock speed to conserve energy. For example, a processor rated at 3.00 GHz may throttle down to 1.2 GHz. As a result, workloads that typically consume around 30% CPU may reach 100% utilization due to the reduced clock speed. To maintain consistent and optimal performance for compute-intensive SQL Server workloads, we recommend that you configure the system to use the **High Performance** power plan. This setting ensures the CPU operates at its full rated speed, helping to avoid performance bottlenecks. For more information, see [Slow performance on Windows Server when using the Balanced power plan](/troubleshoot/windows-server/performance/slow-performance-when-using-power-plan).  
+
+## Step 10: Configure your virtual machine
 
 If you're using a virtual machine, ensure that you aren't overprovisioning CPUs and that they're configured correctly. For more information, see [Troubleshooting ESX/ESXi virtual machine performance issues (2001003)](https://kb.vmware.com/s/article/2001003#CPU%20constraints).
 
-## Step 10: Scale up system to use more CPUs
+## Step 11: Scale up system to use more CPUs
 
 If individual query instances are using little CPU capacity, but the overall workload of all queries together causes high CPU consumption, consider scaling up your computer by adding more CPUs. Use the following query to find the number of queries that have exceeded a certain threshold of average and maximum CPU consumption per execution and have run many times on the system (make sure that you modify the values of the two variables to match your environment):