Skip to main content
The API Management Developer tier has the same features as Premium for building and testing APIs, at a fraction of the price, but no SLA and a single unit. nOps finds non-production API Management instances on Standard or Premium (classic or v2) and estimates the saving from moving them to Developer.

Why it matters

Development and test API gateways are often created on the same tier as production, which is far more than they need.

How nOps finds it

nOps reads the last 14 days of API Management billing. An instance is flagged when its Standard or Premium units were billed on at least 7 of those days and in the last 2 days, and at least 90% of its cost is non-production (from its environment tag, then the environment nOps assigns, then the resource group name). The saving is its 7-day pay-as-you-go unit cost, scaled to a month, times (1 minus the Developer unit list price divided by the current unit list price), using regional list prices where available. Services mostly paid with credits and savings under $25 a month are left out.

Before you start

Confirm the instance serves no production traffic, and plan for downtime during the tier change.

How to implement

  1. Confirm with the owner that the instance is used only for development or test.
  2. For a classic Standard or Premium instance, open it in the Azure portal, go to Pricing tier, choose Developer and save. Or use az apim update --resource-group RESOURCE_GROUP --name APIM_NAME --sku-name Developer.
  3. For a v2 tier instance, create a new Developer instance and move the APIs to it (export and import, or your API deployment pipeline), then delete the old one.
  4. Update Terraform, Bicep or ARM templates (sku_name) so a later deployment does not change it back.

Risks and considerations

  • Changing tier in place causes downtime of up to about 45 minutes.
  • Developer has no SLA, one unit, and no multi-region or availability zone support.
  • If the instance runs several units today, the real saving is larger than the estimate.
  • To roll back, change the tier back; it causes downtime again.

FAQs

From its environment tag first, then the environment nOps assigns, then words like dev, test or staging in the resource group name. At least 90% of its cost must be non-production.