Merge pull request #313757 from craigshoemaker/aca/mcp-aks

[Container Apps] Update MCP service comparison to include AKS

Author: v-regandowner

articles/container-apps/mcp-choosing-azure-service.md

@@ -1,12 +1,12 @@
 ---
 title: Choose an Azure service for your MCP server
-description: Compare Azure Container Apps, App Service, and Azure Functions for hosting MCP servers and pick the best fit for your workload.
+description: Compare Azure Container Apps, App Service, Azure Functions, and Azure Kubernetes Service (AKS) for hosting MCP servers and pick the best fit for your workload.
 #customer intent: As a developer, I want to understand how Azure hosting options compare for MCP servers so that I can pick the right service for my workload.
 ms.topic: product-comparison
 ms.service: azure-container-apps
 ms.collection: ce-skilling-ai-copilot
 ms.custom: cross-service
-ms.date: 02/19/2026
+ms.date: 03/26/2026
 author: craigshoemaker
 ms.author: cshoe
 ms.reviewer: cshoe
@@ -21,7 +21,7 @@ You can use several Azure services to host Model Context Protocol (MCP) servers.
 
 ## Hosting options overview
 
-Azure provides four ways to host an MCP server. Each option targets a different mix of flexibility, simplicity, and isolation.
+Azure provides five ways to host an MCP server. Each option targets a different mix of flexibility, simplicity, and isolation.
 
 ### Azure Container Apps (standalone)
 
@@ -39,22 +39,29 @@ Add an MCP endpoint to an existing or new web app. App Service supports code-bas
 
 Map function triggers to MCP tools by using the [Azure Functions MCP extension](/azure/azure-functions/scenario-custom-remote-mcp-server). Azure Functions is optimized for stateless, event-driven tool execution with per-invocation pricing.
 
+### Azure Kubernetes Service (AKS)
+
+Deploy MCP servers as standard Kubernetes Deployments with HTTP ingress. AKS gives you full access to the Kubernetes API, so you can use Helm charts, custom networking (CNI, network policies), service mesh, GPU node pools, and [KEDA](/azure/aks/keda-about)-based autoscaling. Choose AKS when your team already manages a Kubernetes cluster or needs capabilities that go beyond what a managed container platform provides.
+
+> [!NOTE]
+> Container Apps is built on Kubernetes and provides a managed experience with less operational overhead. If you need direct Kubernetes API access, custom operators, or have an existing AKS investment, use AKS directly. For a broader comparison between these services, see [Comparing Container Apps with other Azure container options](compare-options.md).
+
 ## Compare hosting options
 
 The following table summarizes the key differences between hosting options.
 
-| Consideration | Container Apps (standalone) | Container Apps (sessions) | App Service | Azure Functions |
-|---|---|---|---|---|
-| **Custom tools** | Yes | No (platform-defined only) | Yes | Yes |
-| **Language support** | Any (containerized) | Python and shell only | .NET, Python, Node.js, Java | .NET, Python, Node.js, Java |
-| **MCP transport** | Streamable HTTP | JSON-RPC over HTTP | Streamable HTTP | MCP extension or self-hosted |
-| **Authentication** | Built-in auth (Microsoft Entra ID) or custom | API key (`x-ms-apikey`) | App Service auth (Microsoft Entra ID) | Function keys or Microsoft Entra ID |
-| **Isolation** | Container-level | Hyper-V per session | App-level | Function-level |
-| **Scaling** | Revision autoscale, scale-to-zero | Per-session, pool-managed | App Service Plan | Consumption or Premium plan |
-| **Cold start** | Yes (mitigate with min replicas) | Subsecond (prewarmed pool) | Depends on plan | Yes (Consumption plan) |
-| **Microservices** | Native (environments, Dapr) | No | Limited | Limited |
-| **Operational overhead** | Medium (Dockerfile, registry) | Low (platform-managed) | Low (code deployment) | Low (function deployment) |
-| **Pricing model** | Per vCPU-second, per GiB-second | Per session (consumption) | App Service Plan | Per execution |
+| Consideration | Container Apps (standalone) | Container Apps (sessions) | App Service | Azure Functions | AKS |
+|---|---|---|---|---|---|
+| **Custom tools** | Yes | No (platform-defined only) | Yes | Yes | Yes |
+| **Language support** | Any (containerized) | Python and shell only | .NET, Python, Node.js, Java | .NET, Python, Node.js, Java | Any (containerized) |
+| **MCP transport** | Streamable HTTP | JSON-RPC over HTTP | Streamable HTTP | MCP extension or self-hosted | Streamable HTTP |
+| **Authentication** | Built-in auth (Microsoft Entra ID) or custom | API key (`x-ms-apikey`) | App Service auth (Microsoft Entra ID) | Function keys or Microsoft Entra ID | Microsoft Entra Workload Identity or custom |
+| **Isolation** | Container-level | Hyper-V per session | App-level | Function-level | Pod and namespace-level |
+| **Scaling** | Revision autoscale, scale-to-zero | Per-session, pool-managed | App Service Plan | Consumption or Premium plan | HPA, KEDA, Cluster Autoscaler |
+| **Cold start** | Yes (mitigate with min replicas) | Subsecond (prewarmed pool) | Depends on plan | Yes (Consumption plan) | No (pods always running), or Yes with KEDA scale-to-zero |
+| **Microservices** | Native (environments, Dapr) | No | Limited | Limited | Native (Kubernetes service discovery, service mesh) |
+| **Operational overhead** | Medium (Dockerfile, registry) | Low (platform-managed) | Low (code deployment) | Low (function deployment) | High (cluster management, upgrades, networking) |
+| **Pricing model** | Per vCPU-second, per GiB-second | Per session (consumption) | App Service Plan | Per execution | Per node (VM cost) + managed cluster fee |
 
 ## Choose by scenario
 
@@ -122,6 +129,21 @@ For interactive MCP clients, use a Functions Premium plan to avoid cold-start la
 
 Container Apps environments support internal service discovery, Dapr sidecars, and managed identities for service-to-service calls. Deploy multiple MCP servers as separate container apps within the same environment and let them communicate securely without exposing internal endpoints to the internet. Container Apps gives you full control over the runtime and dependencies for each server, but you manage a Dockerfile and container images for each one.
 
+### Host MCP servers on an existing AKS cluster
+
+**Recommended: Azure Kubernetes Service (AKS)**
+
+If your team already manages an AKS cluster, deploy MCP servers as Kubernetes Deployments with a Service and Ingress resource. AKS is a good fit when:
+
+- You already run AI workloads on AKS and want to colocate MCP servers on the same cluster.
+- You need GPU node pools for AI models running alongside your MCP servers.
+- You require custom Kubernetes networking, such as Azure CNI, network policies, or a service mesh.
+- You want [KEDA](/azure/aks/keda-about)-based autoscaling with fine-grained control over scaling triggers.
+
+Use a standard Kubernetes Ingress controller (such as NGINX, Azure Application Gateway Ingress Controller, or Istio gateway) to expose your MCP server's streamable HTTP endpoint. Secure the endpoint with [Microsoft Entra Workload Identity](/azure/aks/workload-identity-overview) for service-to-service calls or custom authentication middleware.
+
+For a hybrid scenario where you want the Container Apps managed experience on your own Kubernetes infrastructure, see [Azure Container Apps on Azure Arc](azure-arc-overview.md).
+
 ## Quick decision guide
 
 Use these questions to narrow your choice:
@@ -130,6 +152,7 @@ Use these questions to narrow your choice:
 1. **Do you already have a web app running on App Service?** Add MCP to your existing Azure App Service app.
 1. **Do you need event-driven, per-invocation tool execution?** Use Azure Functions.
 1. **Do you need full container control, custom languages, or a microservices architecture?** Use Azure Container Apps (standalone).
+1. **Do you already run workloads on AKS and need full Kubernetes API access?** Use Azure Kubernetes Service (AKS).
 1. **Not sure where to start?** Begin with Azure Container Apps (standalone), which is the most flexible default.
 
 ## Related content
@@ -140,3 +163,6 @@ Use these questions to narrow your choice:
 - [Azure App Service overview](/azure/app-service/overview)
 - [Azure Functions overview](/azure/azure-functions/functions-overview)
 - [Connect an MCP server on Azure Functions to a Foundry Agent Service agent](/azure/azure-functions/functions-mcp-foundry-tools)
+- [Azure Kubernetes Service (AKS) overview](/azure/aks/intro-kubernetes)
+- [KEDA add-on for AKS](/azure/aks/keda-about)
+- [Microsoft Entra Workload Identity on AKS](/azure/aks/workload-identity-overview)