Container v2.12.0

[Tom Kerkhove (tomkerkhove)]

Getting started

You can easily install the self-hosted gateway with Docker:

docker run -d -p 8080:8080 -p 8081:8081 --name <gateway-name> --env config.service.endpoint=<instance-name>.configuration.azure-api.net
config.service.auth=<auth-token> mcr.microsoft.com/azure-api-management/gateway:2.12.0

Learn how you can install it on other container platforms:

• Deploy self-hosted gateway on Kubernetes with Helm
• Deploy self-hosted gateway on Kubernetes with Azure Arc (Preview)
• Deploy self-hosted gateway on Kubernetes with YAML

Here are other relevant resources:

• Authenticate self-hosted gateway with Azure AD
• Self-hosted gateway on Microsoft Artifact Registry
• Our image tagging strategy

What is new?

Features

• Enhanced Service Bus policy support: The send-service-bus-message policy now supports additional Service Bus capabilities, including message-id, session-id, time-to-live, sent-message output variables, and optional continuation on failure with ignore-error.

• Outbound policy requests logged as Application Insights dependencies: Outbound HTTP calls made by policies such as send-request, authentication-managed-identity, and validate-jwt key fetches now appear as dependency telemetry in Application Insights, including URL, duration, status code, and operation ID. Learn more

• Improved policy validation and cache behavior: llm-token-limit policy validation now supports global and product scopes with clearer errors. llm-semantic-cache-store now caches only 200 responses by default, matching cache-store behavior, and cache-remove-value no longer surfaces an error when the value cannot be removed, unless it is explicitly configured to do so.

• Various improvements from our June release

Fixes / Changes

None.

Breaking Changes

None.

Removal

None.

---

This discussion was created from the release Container v2.12.0.