A glowing infographic depicts secure cloud computing, linking protected servers to cloud storage and distributed services.
Azure API Management's Applications feature has moved from a gated trial to an open public preview. Microsoft's Azure Updates entry is titled "Public Preview: Azure API Management Application" and went up on November 17, 2026. If you publish APIs to partners or internal teams, this is worth a look in a test environment.

A glowing infographic depicts secure cloud computing, linking protected servers to cloud storage and distributed services. What changed​

API Management supports built-in OAuth 2.0 application-based access to product APIs using the client credentials flow. API managers register Microsoft Entra ID applications, which streamlines secure API access for developers through OAuth 2.0 authorization.

The earlier preview was restricted. In 2025, Microsoft's Tech Community announcement called it a limited-access feature. The Microsoft Learn article, as indexed in search, still said Applications are currently in limited preview.

The new update reportedly removes that gate. The 365Fanatic changelog mirror reproduces Microsoft's text. It says the feature is available to all customers, with no sign-up or registration required. I couldn't load the Azure Updates page's own item text, so that wording comes from the mirror. Treat the mirror's reported November 30 start date the same way and confirm it against the live Microsoft entry.

How it works​

The Learn documentation describes the flow in four parts:

  • API managers register client applications in Microsoft Entra ID to limit access to specific products.
  • Developers can get client application credentials from the API Management developer portal.
  • Developers or apps use the OAuth 2.0 client credentials flow to obtain tokens and include them in API requests.
  • The API Management gateway validates the tokens and authorizes access to the product's APIs.

The docs give some specifics:

  • Each client application has a single user (owner) in the API Management instance.
  • A client secret must be generated for the application to use the client credentials flow.
  • A developer who owns an application can see its Client ID, Client secret, and Scope in the developer portal. Those values are needed to generate a token to call the product APIs.

Why it matters​

Subscription keys are the traditional way to gate APIM access. Applications adds identity-based access at the application level, backed by Entra ID tokens. That gives you a tidier model for machine-to-machine consumers such as daemons, CLIs and backend services. Microsoft's OAuth documentation describes client credentials as the flow that authenticates and authorizes an app rather than a user.

Nothing I found says Applications replaces subscriptions. The sources don't explain how the two interact, so treat Applications as an additional option until Microsoft says otherwise.

Troubleshooting from the docs​

The Azure China documentation mirror lists a common failure and its fixes. If you get an internal server error when registering applications in the portal, check these:

  1. The Application Administrator role is assigned to the API Management instance's managed identity in Microsoft Entra ID.
  2. You're signed in through the custom portal URL that the applications feature required.

That URL requirement appears in the documentation from the limited-preview period. Check whether it still applies now that the preview is open to everyone.

Before you adopt it​

  • Preview status: Microsoft defines "In preview" as available for non-production use and testing per its Azure Updates status legend. Keep this out of production for now.
  • Documentation lag: The Learn page still referred to limited preview and a sign-up form when indexed. Expect the docs to change.
  • Unconfirmed details: I found no verified information on supported APIM tiers, regions, quotas, pricing, SLA or migration guidance for existing subscription-based setups. Don't assume any of these.
  • Secret handling: Client secrets are issued per application. Plan for storage and rotation the way you would for any other credential.

Suggested pilot​

  1. Pick a non-production APIM instance.
  2. Make sure the instance's managed identity has the Application Administrator role in Entra ID.
  3. Register a test client application and assign it a product.
  4. Generate its secret, request a token with the client credentials flow, and call the product's API.
  5. Check that an application without the product assignment is refused.

The change here is that a feature once gated by a request form is now open to everyone. Whether it's right for production has to wait until Microsoft publishes the limits.

 

References

  1. (In preview) Public Preview: Azure API Management Application Azure Updates 2026-11-17T20:15:03Z
  2. Securely Access Products and APIs - Microsoft Entra Applications - Azure API Management docs.azure.cn
  3. Announcing the Public Preview of the Applications feature in Azure API management techcommunity.microsoft.com