Merge pull request #10585 from MicrosoftDocs/main

Auto Publish – main to live - 2026-01-23 18:00 UTC

Author: learn-build-service-prod[bot]

.openpublishing.redirection.json

@@ -14167,6 +14167,10 @@
     {
       "source_path": "support/developer/visualstudio/cpp/libraries/use-setfind-stl-function.md",
       "redirect_url": "/cpp/standard-library/set-class#example-of-setfind"
+    },
+    {
+      "source_path": "support/power-platform/ai-builder/power-automate/prevent-users-from-creating-ai-builder-custom-models.md",
+      "redirect_url": "/troubleshoot/power-platform/ai-builder/welcome-ai-builder"
     }
   ]
 }

support/azure/azure-kubernetes/create-upgrade-delete/troubleshoot-pods-remain-pending-state-scenario.md

@@ -0,0 +1,36 @@
+---
+title: Troubleshoot Pods Remain in a Pending State Scenario
+description: This article helps you troubleshoot a scenario in which pods remain in a pending state.
+ms.date: 01/12/2026
+ms.author: jarrettr
+ms.editor: v-jsitser
+ms.reviewer: chiragpa, rorylen, v-ryanberg 
+ms.service: azure-kubernetes-service
+keywords:
+#Customer intent: As an Azure Kubernetes user, I want to troubleshoot a scenario in which pods remain in the Pending state in Azure Kubernetes Service (AKS).
+ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
+---
+
+# Troubleshoot pods that remain in the Pending state
+
+This article helps you troubleshoot a scenario in which pods remain in the **Pending** state.
+
+## Symptoms
+
+You run `kubectl describe pod` for a pod, and the pod remains in the **Pending** state. When this issue occurs, the **Event** section displays **pod didn't trigger scale-up (it wouldn't fit if a new node is added)**. Additionally, the cluster-autoscaler doesn’t scale up the node count.
+
+## Cause
+
+These symptoms indicate one or more of the following situations:
+
+- Even if the cluster-autoscaler adds a node, the pod can’t be put onto the new node. This condition occurs because the pod's resource requests exceed the maximum resources that are available on the node.
+
+- The node is missing a resource that the pod requires (such as a Graphics Processing Unit (GPU)).
+
+- The pod has affinity or topology constraints, and the new nodes don’t meet these requirements.
+
+## Resolution
+
+Review the pod resource request configuration (for example CPU, memory, or GPU), and compare it with the node size. To make sure that pod placement can occur, you might have to adjust the node size or type, or adjust the resource request configuration for the pod.
+
+If you rule out a resource constraint, make sure that affinity or taints aren't preventing scheduling.

support/azure/azure-kubernetes/toc.yml

@@ -25,6 +25,8 @@ items:
       href: create-upgrade-delete/upgrading-or-scaling-does-not-succeed.md
     - name: Node count isn't in autoscaler min and max range
       href: create-upgrade-delete/node-count-is-not-in-autoscaler-min-max-range.md
+    - name: Troubleshoot pods remain in a Pending state scenario
+      href: create-upgrade-delete/troubleshoot-pods-remain-pending-state-scenario.md 
   - name: Start operations
     items:
     - name: Basic troubleshooting

support/azure/kubernetes-fleet/toc.yml

@@ -1,5 +1,9 @@
+items:
 - name: Welcome
   href: welcome-azure-kubernetes-fleet.yml
+- name: Unable to connect to Azure Fleet Manager
+  href: unable-connect-azure-fleet-manager.md
+- name: Cluster Resource Placement
 
 - name: Resource Placement
   items:

support/azure/kubernetes-fleet/unable-connect-azure-fleet-manager.md

@@ -0,0 +1,50 @@
+---
+title: Can't connect to Azure Fleet Manager
+description: This article provides guidance for actions to take when you can't connect to Azure Fleet Manager.
+ms.date: 01/13/2026
+ms.author: jarrettr
+ms.reviewer: chiragpa, v-ryanberg 
+ms.service: azure-kubernetes-fleet-manager
+ms.custom: sap:Other issue or questions related to Fleet manager
+---
+# Unable to connect to Azure Fleet Manager
+
+This article helps you resolve an issue that prevents you from connecting to Azure Fleet Manager.
+
+## Symptoms
+
+You try to connect to Azure Fleet Manager by retrieving the kubeconfig file for the Fleet Manager hub cluster. You initially run the following command: 
+
+```powershell
+az fleet get-credentials --resource-group \${GROUP} --name
+```
+
+Then, you run the following command:
+
+```powershell
+kubectl get pods
+```
+
+On the Fleet Manager API server, you're prompted to enter a device code in another browser to authenticate your identity.
+
+If your organization enforces Conditional Access policies that block device code flows, you might receive a message that resembles the following message:
+
+> Your sign-in was successful but does not meet the criteria to access this resource. For example, you might be signing in from a browser, app, location, or an authentication flow that is restricted by your admin.
+
+The following screenshot shows an example of this kind of message.
+
+:::image type="content" source="../media/unable-connect-azure-fleet-manager/no-access-message.png" alt-text="Example of Conditional Access blocking device code flow." lightbox="../media/unable-connect-azure-fleet-manager/no-access-message.png":::
+
+## Cause
+
+The kubeconfig file that's generated by the `az fleet get-credentials` command defaults to device code authentication. Conditional Access policies can block this flow and prevent access to the Fleet Manager API server.
+
+## Resolution
+
+To resolve this issue, modify kubeconfig to use Azure CLI authentication instead of device code authentication. To make this change, run the following command:
+
+```powershell
+kubelogin convert-kubeconfig -l azurecli
+```
+
+This command updates the kubeconfig file so that it authenticates by using your existing Azure CLI sign-in session. This action bypasses the device code prompt.

support/azure/media/unable-connect-azure-fleet-manager/no-access-message.png

@@ -10,8 +10,6 @@
       href: power-automate/all-ai-builder-credits-have-been-consumed.md
     - name: Current environment doesn't meet the minimum requirements
       href: power-automate/the-current-environment-donot-meet-the-minimum-requirements-error-message.md
-    - name: Prevent users from creating AI Builder custom models
-      href: power-automate/prevent-users-from-creating-ai-builder-custom-models.md
 - name: Use in Power Automate
   items:
     - name: AI models fail to be imported in a new environment

support/power-platform/ai-builder/power-automate/prevent-users-from-creating-ai-builder-custom-models.md

@@ -28,8 +28,6 @@ landingContent:
             url: power-automate/all-ai-builder-credits-have-been-consumed.md
           - text: Current environment doesn't meet the minimum requirements error
             url: power-automate/the-current-environment-donot-meet-the-minimum-requirements-error-message.md
-          - text: Prevent users from creating AI Builder custom models
-            url: power-automate/prevent-users-from-creating-ai-builder-custom-models.md
   # Card
   - title: Use in Power Automate
     linkLists: