Merge remote-tracking branch 'upstream/main' into AB#9354-Top-articles--Add-Summary-section

Author: v-tappelgate

support/azure/app-service/troubleshoot-dotnet-visual-studio.md

@@ -38,8 +38,8 @@ Azure uses different endpoints for Key Management Services (KMS) activation depe
 
 To troubleshoot a Windows activation issue, follow these steps:
 
-> [!Important]
-> If you're experiencing Azure virtual machine (VM) Windows activation issues, see [Troubleshooting tools for Windows activation issues on Azure virtual machines](windows-activation-troubleshoot-tools).
+> [!IMPORTANT]  
+> If you're experiencing Azure virtual machine (VM) Windows activation issues, see [Troubleshooting tools for Windows activation issues on Azure virtual machines](windows-activation-troubleshoot-tools.md).
 
 1. Get the error message and the error code:
 

support/azure/virtual-machines/windows/troubleshoot-activation-problems.md

@@ -111,19 +111,19 @@ The following table lists the current checks and findings together with any pote
 | Check for binaries | Verifies that the guest agent .exe files (WindowsAzureGuestAgent.exe and WaAppAgent.exe) exist and is also used to help determine that the Guest Agent was installed.<br><br>If this check doesn't exist, it's likely that the guest agent has to be installed. |
 | Status of agent services | Verifies that the guest agent services (WindowsAzureGuestAgent and RdAgent) exist. Also used to help determine whether the guest agent was installed.<br><br>If this check doesn't exist, it's likely that the guest agent has to be installed. If it is installed, make sure that it's set to `Running` and that the StartType is `Automatic`. |
 | Status of `winmgmt` service | Verifies that the winmgmt service is running. |
-| Status of `KeyIso` service | Verifies that the `KeyIso (CNG Key Isolation)` service is running.<br><br>See [Solution: Start the CNG Key Isolation service](windows-azure-guest-agent#solution-start-the-cng-key-isolation-service). |
+| Status of `KeyIso` service | Verifies that the `KeyIso (CNG Key Isolation)` service is running.<br><br>See [Solution: Start the CNG Key Isolation service](windows-azure-guest-agent.md#solution-start-the-cng-key-isolation-service). |
 | Check if agent services/processes have crashed | This checks whether the Guest Agent services and processes have failed during the past day. If the incident is only a one-time event, it might not be important unless it occurs at the time when the issue is reported. However, if the services constantly fail, the incident must be investigated.<br><br>Start the investigation by looking in the WaAppAgent.log and system and application event logs. |
-| Checks if `stdregprov` is working | The VM agent MSI uses WMI StdRegProv to access the registry. If WMI isn't working correctly, the MSI can't set the RdAgent service path from the registry, and the MSI installation fails. <br><br> See [Guest Agent installation fails because of faulty WMI](windows-azure-guest-agent#guest-agent-installation-fails-because-of-faulty-wmi). |
+| Checks if `stdregprov` is working | The VM agent MSI uses WMI StdRegProv to access the registry. If WMI isn't working correctly, the MSI can't set the RdAgent service path from the registry, and the MSI installation fails. <br><br> See [Guest Agent installation fails because of faulty WMI](windows-azure-guest-agent.md#guest-agent-installation-fails-because-of-faulty-wmi). |
 | Agent is installed | Returns True if the guest agent is installed. Otherwise, the guest agent has to be installed. |
 | Installed by PA or MSI | This check determines whether the guest agent was installed by the provisioning agent or manually through .MSI. Neither of these options are `wrong`. However, it's included for information. |
 | Supported version | Checks whether the Azure Guest Agent version is up to date and supported. |
 | Proxy | Checks for netsh proxies. This check doesn't look for the existence of *all* types of proxy on the system. For example, it doesn't check whether a `3rd party proxy application` is installed. <br><br>If wireserver connectivity issues exist, you can start troubleshooting by using [Troubleshooting 168.63.129.16](/azure/virtual-network/what-is-ip-address-168-63-129-16#troubleshoot-connectivity). |
 | CRP cert exists and is valid | Checks whether the CRP "Windows Azure CRP Certificate Generator" certificate exists. This certificate secures the communication with the host, and transfers protected settings that are used by extensions.<br><br> See [Troubleshoot extension certificate issues on a Windows VM in Azure](troubleshoot-extension-certificates-issues-windows-vm.md). |
-| WCF debugging | This check might run if Windows Communication Framework (WCF) profiling is enabled. WCF profiling should be enabled only while debugging a WCF issue. It should not be left enabled while running a production workload.<br><br> See [Windows Azure Guest Agent service or the RdAgent service stops responding on startup (WCF)](windows-azure-guest-agent#windows-azure-guest-agent-service-or-the-rdagent-service-stops-responding-on-startup). |
+| WCF debugging | This check might run if Windows Communication Framework (WCF) profiling is enabled. WCF profiling should be enabled only while debugging a WCF issue. It should not be left enabled while running a production workload.<br><br> See [Windows Azure Guest Agent service or the RdAgent service stops responding on startup (WCF)](windows-azure-guest-agent.md#windows-azure-guest-agent-service-or-the-rdagent-service-stops-responding-on-startup). |
 | Wireserver (168.63.129.16) connectivity on 80, 32526, and REST API | If wireserver connectivity issues exist, you can start troubleshooting by using [Troubleshooting 168.63.129.16](/azure/virtual-network/what-is-ip-address-168-63-129-16#troubleshoot-connectivity). |
 | IMDS connectivity | IMDS connectivity isn't required for the guest agent to work, but the guest agent does try to connect. Therefore, you might see error entries in the logs. Additionally, VM assist itself gets information about the VM from IMDS to populate some sections of the .HTML file.<br><br>Not having connectivity to IMDS doesn't break the Guest Agent. See [Troubleshooting tool for Azure VM Instance Metadata Service issues](windows-vm-imds-tool.md). |
 | Third-party modules in WaAppAgent and WindowsAzureGuestAgent | Other applications occasionally inject their DLLs into the Guest Agent process. Usually, this behavior doesn't cause the guest agent to fail. However, DLLs might cause unexpected failures in the Guest Agent that are difficult to debug. Although DLLs rarely cause an issue, if any of them are from unexpectedly injected applications, consider removing or reconfiguring the application so that it no longer injects its .dlls into the guest agent processes. |
-| Checks permissions on machineKeys folder | Checks whether the default permissions exist on `C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys`. If improper permissions are that block access are applied, extensions that use protected settings won't work even if the guest agent is in a 'Ready' state.<br><br> See [PInvoke PFXImportCertStore failed and null handle is returned. Error Code: 86](windows-azure-guest-agent#pinvoke-pfximportcertstore-failed-and-null-handle-is-returned-error-code-86). |
+| Checks permissions on machineKeys folder | Checks whether the default permissions exist on `C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys`. If improper permissions are that block access are applied, extensions that use protected settings won't work even if the guest agent is in a 'Ready' state.<br><br> See [PInvoke PFXImportCertStore failed and null handle is returned. Error Code: 86](windows-azure-guest-agent.md#pinvoke-pfximportcertstore-failed-and-null-handle-is-returned-error-code-86). |
 | Checks permissions on `C:\WindowsAzure` and `C:\Packages` | Verifies that the System account has access to these directories. These directories are what the guest agent and extensions use for their binaries, configuration files, and log files. Therefore, it's important that the System account has access. |
 | Sufficient disk space |This check looks for available disk space. If the disk space is filled, the guest agent might not be able to write its status file, update, install extensions, and so on. In this situation, you must either delete files or expand the disk capacity. |
 | DHCP IP | If one private IP exists on the VM's network adapter, we highly recommend that you have DHCP enabled on the guest VM. If a static private IP address is needed, [configure it through the Azure portal or PowerShell](/azure/virtual-network/ip-services/virtual-networks-static-private-ip-arm-ps). Make sure that the DHCP option inside the VM is enabled. This setting makes sure that the IP configuration always matches the VM configuration in Azure.<br><br>If multiple private IPs are assigned to the VM's network adapter, make sure that you follow these steps to [statically assign the IPs correctly](/azure/virtual-network/ip-services/virtual-network-multiple-ip-addresses-portal#os-config). After you perform this procedure, if the guest agent can't communicate with 168.63.129.16, check whether the primary IP in Windows [matches the primary IP in the VM's network adapter in Azure](no-internet-access-multi-ip.md). |

support/azure/virtual-machines/windows/windows-azure-guest-agent-tools-vmassist.md

@@ -1,8 +1,6 @@
 ---
 title: Troubleshoot unification output tables
 description: Provides troubleshooting steps for unification output tables in Microsoft Dynamics 365 Customer Insights - Data.
-author: wu-allison
-ms.author: allisonwu
 ms.date: 06/20/2024
 ms.reviewer: mhart
 ms.custom: sap:Data Unification

support/dynamics-365/customer-insights/data/profile-unification/troubleshoot-unification-output-tables.md

@@ -1,8 +1,6 @@
 ---
 title: Troubleshoot unification results
 description: Provides troubleshooting steps for unexpected deduplication, match, or merge results in Microsoft Dynamics 365 Customer Insights - Data.
-author: wu-allison
-ms.author: allisonwu
 ms.date: 06/20/2024
 ms.reviewer: mhart
 ms.custom: sap:Data Unification

support/dynamics-365/customer-insights/data/profile-unification/troubleshoot-unification-results.md

@@ -1,11 +1,9 @@
 ---
 title: All AI Builder credits have been consumed
 description: Provides a resolution for the issue that all AI Builder credits have been consumed in Microsoft Power Platform.
-ms.reviewer: chplanty, cdbellar
-ms.date: 09/18/2023
+ms.reviewer: antode, chplanty, cdbellar, v-shaywood
+ms.date: 01/19/2026
 ms.custom: sap:AI Builder\Administration and Licensing
-ms.author: antode
-author: Antoine2F
 ---
 # All AI Builder credits have been consumed
 
@@ -21,8 +19,7 @@ Here are the different symptoms of this issue:
 
 1. A banner shows the "Some environments have consumed all or almost all AI Builder credits" message on the **Capacity** page in the Power Platform admin center.
 1. A banner shows the "You've consumed all your AI Builder credits" message on the AI Builder page.
-1. Maker actions (Model creation, Model edit, and Quick test) are blocked on the AI Builder page.
-1. A flow stops with the "All AI Builder credits in this environment have been consumed" error.
+1. A flow stops and returns the error message "All AI Builder credits in this environment have been consumed" or "Missing Copilot Credit or AI Builder credit capacity".
 
    > [!NOTE]
    > This error is displayed in the **Error** panel on the flow run page.
@@ -33,28 +30,32 @@ Here are the different symptoms of this issue:
    - Code="QuotaExceeded"
    - Message="Credit usage exceeds allocation."
 
-1. In Power Apps, a banner shows the "You need an AI Builder license to use this component" message when you try to perform an AI Builder action.
+1. In Power Apps, a banner shows the message "You need an AI Builder license to use this component" or "Missing Copilot Credit or AI Builder credit capacity" when you try to perform an AI Builder action.
 
 ## Cause
 
-This issue occurs because AI Builder actions consume AI Builder credits. These credits come from tenant-level or environment-level allocations.
+This issue occurs because AI Builder actions consume AI Builder credits or Copilot Credits, depending on the context. These credits come from tenant-level or environment-level allocations.
 
-The environment's consumption is computed each day from the beginning of the month.  
+- _Power Apps_ or _Power Automate_: AI Builder actions consume AI Builder credits first. If those credits are exhausted or unavailable, the actions consume Copilot Credits instead.
+- _Microsoft Copilot Studio_ (agents and agent flows): AI Builder actions consume Copilot Credits only.
 
-- When the consumption is close to the allocated credits, a banner is displayed on the **Capacity** page in the Power Platform admin center, and a notification email is sent to the administrator.
-- When the consumption starts exceeding the tenant-level or environment-level credits ("simple overage"), a banner is displayed on the AI Builder page, and Maker actions are blocked. In "simple overage", AI Builder actions in flows and apps are still allowed and continue consuming credits.
-- When the consumption is much higher than the tenant-level or environment-level credits ("important overage"), AI Builder actions in flows and apps are blocked, and an error might occur in flows and apps.
+The environment's consumption is calculated regularly and resets at the beginning of the month.
+
+- When the calculated consumption is close to the allocated credits, a banner appears on the **Capacity** page in the Power Platform admin center, and a notification email is sent to the administrator.
+- When the calculated consumption exceeds the tenant-level or environment-level credits (125%), AI Builder actions in flows and apps are blocked, and an error message appears.
+
+Sometimes the environment's consumption calculation is delayed (up to five days). In this case, the system uses the last known calculated consumption. This delay can lead to significant consumption beyond your capacity before AI Builder actions are blocked or fall back to Copilot Credits. This overage isn't billed to you and doesn't affect other environments.
 
 ## Resolution
 
-To solve this issue, add more credits to your environment.
+To solve this issue, add more AI Builder credits or Copilot Credits to your environment.
 
 If credits come from the tenant level (unassigned credits), you need to add credits at the tenant level. This can be done by deallocating credits from other environments or by purchasing more.
 
 If credits come from the environment level, you need to allocate more credits to your environment. This can be done by using the existing tenant-level environment or by adding credits at the tenant level first (using purchase or environment deallocation).
 
 > [!NOTE]
-> If the **Allow users to consume unassigned credit** setting is disabled, the unassigned credits can't be used. You can go to the Power Platform admin center, select **Settings**, and then open the **AI Builder credit** page to enable this setting.
+> For AI Builder credits, if the **Allow users to consume unassigned credit** setting is disabled, the unassigned credits can't be used. You can go to the Power Platform admin center, select **Settings**, and then open the **AI Builder credit** page to enable this setting.
 
 #### How to determine the source and number of allocated, unassigned, and owned credits
 
@@ -69,7 +70,7 @@ You need to be the administrator of your environment to perform these actions.
     1. On the right pane, select **Summary**.
     1. At the bottom of the pane, in the **Add-ons** section, the **AI Builder credits** indicates the total number of credits allocated to environments among the total of owned credits. The amount of tenant-level credits (unassigned credits) is the difference between these numbers.
 
-#### How to change the number of environment-allocated credits
+#### How to change the number of environment-allocated AI Builder credits
 
 You need to be the administrator of your environment to perform these actions.
 
@@ -81,7 +82,7 @@ You need to be the administrator of your environment to perform these actions.
 1. In the right-side panel, select your environment.
 1. Modify the number of AI Builder credits. If the remaining credits aren't enough, you can deallocate credits from other environments or purchase more.
 
-#### How to change the number of tenant-level credits (unassigned credits) by deallocating credits from environments
+#### How to change the number of tenant-level AI Builder credits (unassigned credits) by deallocating credits from environments
 
 You need to be the administrator of your environment to perform these actions.
 
@@ -96,21 +97,24 @@ You need to be the administrator of your environment to perform these actions.
 > [!NOTE]
 > If the **Allow users to consume unassigned credit** setting is disabled, the unassigned credits can't be used. You can go to the Power Platform admin center, select **Settings**, and then open the **AI Builder credit** page to enable this setting.
 
-#### How to change the number of tenant-level credits (unassigned credits) by purchasing more AI Builder credits
+#### How to change the number of tenant-level AI Builder credits (unassigned credits) by purchasing more AI Builder credits
 
-You need to be the billing administrator of your tenant to perform these actions.
+> [!IMPORTANT]
+> AI Builder Capacity Add-ons are in "End of Sales" state. You can only purchase more if you already have active AI Builder Add-ons.
+
+You must be the billing administrator of your tenant to perform these steps.
 
 1. Sign in to the [Microsoft 365 admin center](https://admin.microsoft.com/).
 1. On the left pane, select **Billing** > **Purchase services**.
 1. Search for AI Builder.
 1. Select **AI Builder Capacity Add-on T1**, **AI Builder Capacity Add-on T2 (min 10 packs)**, or **AI Builder Capacity Add-on T3 (min 50 packs)**, depending on how many packs you need. Each pack provides 1 million AI Builder credits.
 1. Follow the purchase process.
-1. Once purchased, follow the steps in [How to change the number of environment-allocated credits](#how-to-change-the-number-of-environment-allocated-credits) if the credits come from the environment level.
+1. Once purchased, follow the steps in [How to change the number of environment-allocated AI Builder credits](#how-to-change-the-number-of-environment-allocated-ai-builder-credits) if the credits come from the environment level.
 
 > [!NOTE]
 > If the **Allow users to consume unassigned credit** setting is disabled, the unassigned credits can't be used. You can go to the Power Platform admin center, select **Settings**, and then open the **AI Builder credit** page to enable this setting.
 
-#### How to evaluate the amount of credits to add
+#### How to evaluate the amount of AI Builder credits to add
 
 You need to be the administrator of your environment to perform these actions.
 
@@ -124,20 +128,6 @@ You need to be the administrator of your environment to perform these actions.
 1. Open the .csv file in Excel. It contains the AI Builder credit consumption per day, user, and environment.
 1. By adding all your environment's consumption for the current month, you can evaluate how many credits this environment needs for the entire month.
 
-## AI Builder purchase takes time, and I urgently need to unblock my flow or app. What can I do?
-
-You can find the **Request extension** button to add 200,000 extension credits for the current month.
-
-- On the AI Builder page, you might find the **Request extension** button in the "You've consumed all your AI Builder credits" overage banner.
-- In the Power Platform admin center, you might find the **Request extension** button in the "Some environments have consumed all or almost all AI Builder credits" banner.
-
-> [!NOTE]
->
-> - These credits can't be allocated or assigned and can be used directly by any environment in overage.
-> - The number of extension requests per month and per year is limited.
-> - Each extension request sends a notification email to the Power Platform admin informing that extension credits have been requested and granted.
-> - If the **Allow users to consume unassigned credit** setting is disabled in the Power Platform admin center, the environment without assigned credits is blocked, and extension credits won't help. You can go to the Power Platform admin center, select **Settings**, and then open the **AI Builder credit** page to enable this setting.
-
 ## Resources
 
 For more information, see [AI Builder licensing](/ai-builder/administer-licensing).