Merge pull request #311889 from dlepow/grpc

[APIM] gRPC support in classic tiers

Author: Stacyrch140

articles/api-management/api-management-gateways-overview.md

@@ -8,7 +8,7 @@ ms.service: azure-api-management
 ms.custom:
   - build-2024
 ms.topic: concept-article
-ms.date: 02/11/2026
+ms.date: 02/17/2026
 ms.author: danlep
 ---
 
@@ -110,7 +110,7 @@ The following tables compare features available in the following API Management
 | [Pass-through GraphQL](graphql-apis-overview.md) |  ✔️ | ✔️ |✔️ | ✔️ | ✔️ |
 | [Synthetic GraphQL](graphql-apis-overview.md)|  ✔️ |  ✔️ | ✔️<sup>1</sup> | ✔️<sup>1</sup> | ❌ |
 | [Pass-through WebSocket](websocket-api.md) |  ✔️ |  ✔️ | ❌ | ✔️ | ✔️ |
-| [Pass-through gRPC](grpc-api.md)  |  ❌ | ❌ | ❌ | ✔️ | ❌ |
+| [Pass-through gRPC](grpc-api.md)  |  ✔️ | ❌ | ❌ | ✔️ | ❌ |
 | [OData](import-api-from-odata.md)  |  ✔️ |  ✔️ | ✔️ | ✔️ | ✔️ |
 | [Azure OpenAI in Microsoft Foundry models and LLMs](azure-ai-foundry-api.md) | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
 | [Pass-through MCP server](expose-existing-mcp-server.md) | ✔️  | ✔️ | ❌ | ✔️ | ❌ |

articles/api-management/grpc-api.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: how-to
-ms.date: 10/06/2025
+ms.date: 02/18/2026
 ms.author: danlep
 ms.custom:
   - devx-track-arm-template
@@ -17,7 +17,7 @@ ms.custom:
 ---
 # Import a gRPC API
 
-[!INCLUDE [api-management-availability-premium-dev](../../includes/api-management-availability-premium-dev.md)]
+[!INCLUDE [api-management-availability-premium-dev-standard-basic](../../includes/api-management-availability-premium-dev-standard-basic.md)]
 
 This article shows how to import a gRPC service definition as an API in API Management. You can then manage the API in API Management, secure access and apply other policies, and pass gRPC API requests through the gateway to the gRPC backend. 
 
@@ -30,21 +30,21 @@ To add a gRPC API to API Management, you need to:
 API Management supports pass-through with the following types of gRPC service methods: unary, server streaming, client streaming, and bidirectional streaming. To learn more about gRPC, see [Introduction to gRPC](https://grpc.io/docs/what-is-grpc/introduction/).
 
 > [!NOTE]
-> * Currently, gRPC APIs are only supported in the self-hosted gateway, not the managed gateway for your API Management instance.
+> * gRPC APIs are supported in the [self-hosted gateway](self-hosted-gateway-overview.md) and in the managed gateway for classic tier instances created starting January 2026 (preview). Contact support to enable gRPC API support in classic tier instances created before this date. gRPC APIs currently aren't supported in the v2 tiers.
 > * Currently, testing gRPC APIs isn't supported in the test console of the Azure portal or in the API Management developer portal.
-> * Import is limited to a single protobuf (*.proto*) file. 
+> * Import is limited to a single protobuf (*.proto*) file.  
 
 ## Prerequisites
 
 * An API Management instance. If you don't already have one, complete the following quickstart: [Create an Azure API Management instance](get-started-create-service-instance.md).
 
-* A gateway resource provisioned in your instance. If you don't already have one, see [Provision a self-hosted gateway in Azure API Management](api-management-howto-provision-self-hosted-gateway.md).
-
 * A gRPC protobuf (*.proto*) file available locally, and gRPC service that's accessible over HTTPS.
 
+* HTTP/2 protocol support enabled for client traffic. For more information, see [Manage protocols and ciphers in Azure API Management](api-management-howto-manage-protocols-ciphers.md).
+
 ## Add a gRPC API
 
-1. In the [Azure portal](https://portal.azure.com), navigate to your API Management instance.
+1. In the [Azure portal](https://portal.azure.com), go to your API Management instance.
 
 1. Under **APIs** in the sidebar menu, select **APIs**.
 
@@ -54,7 +54,7 @@ API Management supports pass-through with the following types of gRPC service me
 
 1. In the **Create a gRPC API window**, select **Full**.
 
-1. For a gRPC API, you must specify the following settings:
+1. For a gRPC API, specify the following settings:
 
     1. Enter a display name.
 
@@ -64,18 +64,15 @@ API Management supports pass-through with the following types of gRPC service me
 
     1. For **Gateways**, select the gateway resource that you want to use to expose the API. 
 
-        > [!IMPORTANT]
-        > In public preview, you can only select a self-hosted gateway. The **Managed** gateway isn't supported.
-
-1. Enter any remaining settings to configure your API. These settings are explained in the [Import and publish your first API](import-and-publish.md#import-and-publish-a-backend-api) tutorial.
+1. Enter any remaining settings to configure your API. The [Import and publish your first API](import-and-publish.md#import-and-publish-a-backend-api) tutorial explains these settings.
 
 1. Select **Create**.
 
-    The API is added to the **APIs** list. You can view update your settings by going to the **Settings** tab of the API.
+    The portal adds the API to the **APIs** list. You can view and update your settings by going to the **Settings** tab of the API.
 
-## Call gRPC services with .NET
+## Call gRPC services by using .NET
 
-For information about calling gRPC services with .NET, see the following articles:
+For information about calling gRPC services by using .NET, see the following articles:
 
 * [Tutorial: Create a gRPC client and server in ASP.NET Core](/aspnet/core/tutorials/grpc/grpc-start)
 * [Troubleshoot gRPC on .NET](/aspnet/core/grpc/troubleshoot#calling-grpc-services-hosted-in-a-sub-directory)

articles/api-management/migrate-amazon-api-gateway-to-api-management.md

@@ -142,7 +142,7 @@ As part of the assessment, consider whether to retain or replace existing servic
 - *OpenAPI specifications* exported from an Amazon API Gateway REST API contain details specific to the frontend implementation in Amazon API Gateway, not the backend service. You need to remove AWS-specific tags and configure details in the specification (such as the backend service URL) before import to Azure API Management or during the migration process. 
 - *Kubernetes microservices* backends, such as gRPC APIs, are handled differently:
   - Amazon API Gateway connects to the application load balancer in VPC, which in turn provides ingress to AWS EKS.
-  - Azure API Management supports gRPC APIs on Kubernetes clusters accessed only through the self-hosted gateway.
+  - Azure API Management typically supports gRPC and other microservice APIs on Kubernetes clusters through the self-hosted gateway.
   - Use of gRPC prevents the use of Application Gateway as a WAF.
 
 ### Compare API configurations