Merge pull request #115619 from mlearned/mdl-1720605-uptime-sla-build-day

uptime sla broken link

Author: PRMerger6

articles/aks/faq.md

@@ -123,9 +123,7 @@ Windows Server support for node pool includes some limitations that are part of
 
 ## Does AKS offer a service-level agreement?
 
-AKS offers an optional [uptime SLA add-on][uptime-sla] for the Kubernetes API server. Customers who choose the SLA add-on are guaranteed 99.95% availability for clusters which are spread across availability zones and 99.9% availability for those which are not. For clusters without the SLA add-on, AKS maintaines a service-level objective of 99.5% availability. 
-
-It is important to recognize the distinction between AKS service availability which refers to uptime of the Kubernetes control plane and the availability of your specific workload which is running on Azure Virtual Machines and therefore covered by the [VM SLA][vm-sla]. In the event that the Kubernetes control plane is unavailable, your applications will continue to function. However, you will be unable to deploy new applications, scale or upgrade existing applications, or perform other management operations on the cluster.
+AKS provides SLA guarantees as an optional add on feature with [Uptime SLA][uptime-sla].
 
 ## Can I apply Azure reservation discounts to my AKS agent nodes?
 

articles/aks/private-clusters.md

@@ -98,13 +98,13 @@ As mentioned, VNet peering is one way to access your private cluster. To use VNe
 * IP authorized ranges cannot be applied to the private api server endpoint, they only apply to the public API server
 * Availability Zones are currently supported for certain regions, see the beginning of this document 
 * [Azure Private Link service limitations][private-link-service] apply to private clusters.
-* No support for virtual nodes in a private cluster to spin private Azure Container Instances (ACI) in a private Azure virtual network
 * No support for Azure DevOps integration out of the box with private clusters
 * For customers that need to enable Azure Container Registry to work with private AKS, the Container Registry virtual network must be peered with the agent cluster virtual network.
 * No current support for Azure Dev Spaces
 * No support for converting existing AKS clusters into private clusters
 * Deleting or modifying the private endpoint in the customer subnet will cause the cluster to stop functioning. 
 * Azure Monitor for containers Live Data isn't currently supported.
+* Uptime SLA isn't currently supported.
 
 
 <!-- LINKS - internal -->