Merge pull request #2691 from MicrosoftDocs/main

learn-build-service-prod[bot] · web-flow · commit 46188f10d4f4 · 2026-02-14T06:02:37.000Z
Auto Publish – main to live - 2026-02-14 06:00 UTC
diff --git a/articles/aks/best-practices-storage-nvme.md b/articles/aks/best-practices-storage-nvme.md
@@ -182,7 +182,7 @@ For more information, see [Azure Container Storage documentation](/azure/storage
 
 ### `emptyDir` Volumes
 
-`[emptyDir](https://kubernetes.io/docs/concepts/storage/volumes/#emptydir)` is a Kubernetes volume type that uses the node's local storage. By default, it uses the kubelet storage path on the OS disk, but you can configure it to use local NVMe disks for higher throughput and lower latency with temporary data.
+[emptyDir](https://kubernetes.io/docs/concepts/storage/volumes/#emptydir) is a Kubernetes volume type that uses the node's local storage. By default, it uses the kubelet storage path on the OS disk, but you can configure it to use local NVMe disks for higher throughput and lower latency with temporary data.
 
 To back `emptyDir` volumes with local NVMe disks, you must configure the kubelet storage path to point to an NVMe mount point during node initialization. This requires custom node bootstrap scripting and careful planning, as the configuration is immutable after node provisioning.
 
diff --git a/articles/aks/node-auto-provisioning.md b/articles/aks/node-auto-provisioning.md
@@ -4,7 +4,7 @@ description: Learn about node auto-provisioning in AKS, including how it works,
 ms.topic: overview
 ms.service: azure-kubernetes-service
 ms.custom: devx-track-azurecli
-ms.date: 09/29/2025
+ms.date: 2/15/2026
 ms.author: wilsondarko
 author: wdarko1
 # Customer intent: As a cluster operator or developer, I want to automatically provision and manage the optimal VM configuration for my AKS workloads, so that I can efficiently scale my cluster while minimizing resource costs and complexities.
@@ -57,9 +57,7 @@ The following limitations and unsupported features apply to node auto-provisioni
 - Windows node pools aren't supported.
 - IPv6 clusters aren't supported.
 - [Service principals](./kubernetes-service-principal.md) aren't supported. You can use either a system-assigned or user-assigned managed identity.
-- [Custom certificate authority (CA) certificates](./custom-certificate-authority.md) aren't supported.
 - You can't [stop a cluster](./start-stop-cluster.md) enabled with NAP.
-- [HTTP proxy](./http-proxy.md) isn't supported.
 - You can't change the [cluster egress outbound type](./egress-outboundtype.md) after you create a cluster enabled with NAP.
 - When creating a NAP cluster in a custom virtual network (VNet), you must use a [Standard Load Balancer](./load-balancer-standard.md). The Basic Load Balancer isn't supported.
 
diff --git a/articles/kubernetes-fleet/concepts-fleet-arc-integration.md b/articles/kubernetes-fleet/concepts-fleet-arc-integration.md
@@ -1,19 +1,19 @@
 ---
 title: "Azure Kubernetes Fleet Manager with Arc-enabled Kubernetes clusters"
 description: This article provides a conceptual overview of Azure Kubernetes Fleet Manager integration with Azure Arc-enabled Kubernetes clusters.
-ms.date: 10/16/2025
+ms.date: 02/13/2026
 author: ealianis
 ms.author: sehobbs
 ms.service: azure-kubernetes-fleet-manager
 ms.topic: concept-article
-# Customer intent: "As a platform administrator managing hybrid and multi-cloud Kubernetes infrastructure, I want to understand how Azure Kubernetes Fleet Manager integrates with Arc-enabled Kubernetes clusters, so that I can centrally manage my entire fleet regardless of where clusters are running."
+# Customer intent: "As a platform administrator managing hybrid and multicloud Kubernetes infrastructure, I want to understand how Azure Kubernetes Fleet Manager integrates with Arc-enabled Kubernetes clusters, so that I can centrally manage my entire fleet regardless of where clusters are running."
 ---
 
 # Azure Kubernetes Fleet Manager with Arc-enabled Kubernetes clusters (preview)
 
-This article provides a conceptual overview of how Azure Kubernetes Fleet Manager integrates with Azure Arc-enabled Kubernetes clusters to enable unified multi-cluster management across hybrid and multi-cloud environments.
+This article provides a conceptual overview of how Azure Kubernetes Fleet Manager integrates with Azure Arc-enabled Kubernetes clusters to enable unified multi-cluster management across hybrid and multicloud environments.
 
-If you are unfamiliar with Azure Kubernetes Fleet Manager, start with the [Azure Kubernetes Fleet Manager overview](./overview.md).
+If you're unfamiliar with Azure Kubernetes Fleet Manager, start with the [Azure Kubernetes Fleet Manager overview](./overview.md).
 
 > [!IMPORTANT]
 > Azure Kubernetes Fleet Manager's support for Arc-enabled Kubernetes clusters is currently in public preview.
@@ -26,41 +26,53 @@ The integration between Azure Kubernetes Fleet Manager and Azure Arc-enabled Kub
 
 ## Key benefits and capabilities
 
-Azure Kubernetes Fleet Manager integration with Arc-enabled Kubernetes clusters enables unified, intelligent, policy-driven multi-cluster resource management across hybrid and multi-cloud environments.
+Azure Kubernetes Fleet Manager integration with Arc-enabled Kubernetes clusters enables unified, intelligent, policy-driven multi-cluster resource management across hybrid and multicloud environments.
 
 ### Centralized policy-driven fleet governance
 
-Azure Kubernetes Fleet Manager utilizes a hub-spoke architecture that creates a single control plane for the fleet. It allows fleet administrators to apply uniform cloud native policies on every member cluster, whether they reside in public clouds, private data centers, or edge locations. This greatly simplifies governance across large, geographically distributed fleets spanning hybrid and multi-cloud environments.
+Azure Kubernetes Fleet Manager utilizes a hub-spoke architecture that creates a single control plane for the fleet. It allows fleet administrators to apply uniform cloud native policies on every member cluster, whether they reside in public clouds, private data centers, or edge locations. The hub-spoke architecture greatly simplifies governance across large, geographically distributed fleets spanning hybrid and multicloud environments.
 
 ### Progressive Rollouts with Safeguards
 
-Azure Kubernetes Fleet Manager provides a cloud native progressive rollout plans sequence updates across the entire fleet with health verification at each step. The application owner can stop a rollout or rollback to any previous versions when they observe failures, limiting blast radius. This keeps multi-cluster application deployments reliable and predictable spanning edge, on-premises, and cloud environments.
+Azure Kubernetes Fleet Manager provides a cloud native progressive rollout plans sequence updates across the entire fleet with health verification at each step. The application owner can stop a rollout or rollback to any previous versions when they observe failures, limiting blast radius. Progressive rollouts keep multi-cluster application deployments reliable and predictable spanning edge, on-premises, and cloud environments.
 
 ### Powerful Multi-Cluster Scheduling
 
-Azure Kubernetes Fleet Manager scheduler evaluates member cluster properties, available capacity, and declarative placement policies to select optimal destinations for workloads. It supports cluster affinity and anti-affinity rules, topology spread constraints to distribute workloads across failure domains, and resource-based placement to ensure sufficient compute, memory, and storage. The scheduler continuously reconciles as fleet conditions change, automatically adapting to cluster additions, removals, or capacity shifts across edge, on-premises, and cloud environments. For more details on the various scheduling capabilities, please see the multi-cluster workload management section.
+Azure Kubernetes Fleet Manager scheduler evaluates member cluster properties, available capacity, and declarative placement policies to select optimal destinations for workloads. It supports cluster affinity and anti-affinity rules, topology spread constraints to distribute workloads across failure domains, and resource-based placement to ensure sufficient compute, memory, and storage. The scheduler continuously reconciles as fleet conditions change, automatically adapting to cluster additions, removals, or capacity shifts across edge, on-premises, and cloud environments. For more details on the various scheduling capabilities see the multi-cluster workload management section.
 
-## Supported capabilities, prerequisites and considerations
+## Supported capabilities, prerequisites, and considerations
 
-Before integrating Arc-enabled Kubernetes clusters with Fleet Manager, review these important considerations
-noted within the [member cluster types documentation](./concepts-member-cluster-types.md).
+Before integrating Arc-enabled Kubernetes clusters with Fleet Manager, review these important considerations noted within the [member cluster types documentation](./concepts-member-cluster-types.md).
 
 ## Architecture overview
 
-The Fleet Manager and Arc integration follows the same hub-and-spoke architecture used for AKS clusters:
+The Fleet Manager and Azure Arc integration uses the same hub-and-spoke architecture as AKS clusters:
 
-When you join an Arc-enabled Kubernetes cluster to a Fleet, the Fleet Arc Extension is installed on your Arc-Enabled Kubernetes cluster, deploying the Fleet's member agents onto your underlying cluster. These agents will communicate directly with the Fleet's hub cluster. 
+When you join an Arc-enabled Kubernetes cluster to a Fleet Manager, the Fleet Manager Arc extension is installed on your Arc-Enabled Kubernetes cluster, deploying the Fleet's member agents onto your underlying cluster. These agents communicate directly with the Fleet's hub cluster. 
 
 **Key components:**
 
-- **Hub cluster**: Centralized control plane for managing the entire fleet
+- **Hub cluster**: Centralized control plane for managing the entire fleet.
 - **Fleet extension**: Deployed to Arc-enabled clusters to enable Fleet Manager integration via the Fleet Arc Extension.
-- **Member cluster representation**: Arc-enabled clusters appear as `MemberCluster` resources in the hub
+- **Member cluster representation**: Arc-enabled clusters appear as `MemberCluster` resources in the hub.
 
 ## Getting started 
 
 To begin using Fleet Manager with Arc-enabled Kubernetes clusters:
 
 1. **Connect clusters to Azure Arc**: Connect your Kubernetes clusters to Azure Arc. For instructions, see [Connect an existing Kubernetes cluster to Azure Arc](/azure/azure-arc/kubernetes/quickstart-connect-cluster).
 2. **Create or upgrade your fleet**: Create (or upgrade) a fleet resource with a hub cluster, then join your Arc-enabled clusters. For instructions, see [Create a fleet and join member clusters](./quickstart-create-fleet-and-members.md).
-3. **Configure workload placement**: Create `ClusterResourcePlacement` resources for your applications. For guidance, see [Kubernetes resource propagation concepts](./concepts-resource-propagation.md).
+3. **Configure workload placement**: Create `ClusterResourcePlacement` resources for your applications. For guidance, see [Kubernetes resource propagation concepts](./concepts-resource-propagation.md).
+
+## Public region limitation
+
+Fleet Manager Arc-enabled Kubernetes cluster support is only currently available in Azure public cloud regions.
+
+If you attempt to create an Arc-enabled member cluster in a non-public cloud region, an error of type `FeatureNotAvailableInCloud` with the message `The feature 'Arc Member Cluster' is not available in cloud environment` is returned.
+
+When Azure Arc Gateway is available in Azure non-public cloud regions the restriction will be lifted.
+
+You can track the status of Azure Arc Gateway via its [official documentation][azure-arc-gateway].
+
+<!-- LINKS -->
+[azure-arc-gateway]: /azure/azure-arc/kubernetes/arc-gateway-simplify-networking
diff --git a/articles/kubernetes-fleet/concepts-member-cluster-types.md b/articles/kubernetes-fleet/concepts-member-cluster-types.md
@@ -16,35 +16,48 @@ Azure Kubernetes Fleet Manager supports two types of member clusters:
 - [Arc-enabled Kubernetes clusters](/azure/azure-arc/kubernetes/overview) (Preview).
 
 > [!IMPORTANT]
-> Azure Kubernetes Fleet Manager's support for Arc-enabled Kubernetes clusters is currently in Preview. [See below for limitations and requirements](#arc-enabled-kubernetes-clusters-important-considerations).
+> Azure Kubernetes Fleet Manager's support for Arc-enabled Kubernetes clusters is currently in Preview.
 
 The following table outlines which Azure Kubernetes Fleet Manager capabilities are supported for each member cluster type.
 
 | Capability | AKS cluster | Arc-enabled Kubernetes cluster |
-|-----|----|-----------|
-| Kubernetes and node image updates |✅ GA | ❌ Unsupported|
-| Workload placement |✅ GA| ✅ Preview|
+|------------|-------------|--------------------------------|
+| Kubernetes and node image updates |✅ GA | ❌ Unsupported |
+| Workload placement |✅ GA| ✅ Preview |
 | DNS load balancing | ✅ GA| ❌ Unsupported|
 | Managed Namespaces | ✅ Preview  | ✅ Preview  |
-| Managed Namespace RBAC | ✅ Preview  | ❌ Unsupported  |
+| Managed Namespace RBAC | ✅ Preview  | ❌ Unsupported |
+| Non-public Azure regions | ✅ GA  | ❌ Unsupported |
 
 ## Arc-enabled Kubernetes Clusters important considerations
 
 Depending on your environment and configuration, certain limitations may apply when connecting an Arc-enabled Kubernetes cluster to an Azure Kubernetes Fleet Manager hub. Review the following considerations:
 
-### Private Fleet
+### Cluster resource requirements
 
-- For **Private Fleets**, your Arc-enabled Kubernetes cluster **must** be configured to use [Azure Arc Gateway](/azure/azure-arc/servers/arc-gateway).
+When you add an Arc-enabled Kubernetes cluster to Fleet Manager, the following conditions apply on the member cluster:
 
-### Cluster resource requirements
+- At least **210 MB** memory and **2%** of one CPU core available.
+- The cluster should reserve **3 pods** for the Azure Kubernetes Fleet Manager Arc extension agents.
+- The **fleet-system** namespace is created for Fleet-related components and shouldn't be directly modified.
 
-When adding an Arc-enabled Kubernetes cluster to Fleet Manager, the following conditions apply:
-- At least **210 MB** memory and **2%** of one CPU core available
-- The cluster should reserve **3 pods** for the Azure Kubernetes Fleet Manager Arc extension agents
-- The namespace **fleet-system** will be created for related components.
-  - Do **not delete or modify** this namespace, it is required for core functionality.
+### Private Fleet
+
+For **Private Fleets**, your Arc-enabled Kubernetes cluster **must** be configured to use [Azure Arc Gateway](/azure/azure-arc/servers/arc-gateway).
 
 ### Networking
 
-- **TLS-terminating proxies are not supported.**  
-- If using a **passthrough proxy**, your Arc-enabled Kubernetes cluster **must** also be configured to use [Azure Arc Gateway](/azure/azure-arc/servers/arc-gateway).
+**TLS-terminating proxies are not supported.**  If using a **passthrough proxy**, your Arc-enabled Kubernetes cluster **must** also be configured to use [Azure Arc Gateway](/azure/azure-arc/servers/arc-gateway).
+
+## Non-public region limitation
+
+Fleet Manager Arc-enabled Kubernetes cluster support is only currently available in Azure public cloud regions.
+
+If you attempt to create an Arc-enabled member cluster in a non-public cloud region, an error of type `FeatureNotAvailableInCloud` with the message `The feature 'Arc Member Cluster' is not available in cloud environment` is returned.
+
+When Azure Arc Gateway is available in Azure non-public cloud regions the restriction will be lifted.
+
+You can track the status of Azure Arc Gateway via its [official documentation][azure-arc-gateway].
+
+<!-- LINKS -->
+[azure-arc-gateway]: /azure/azure-arc/kubernetes/arc-gateway-simplify-networking
