Azure-docs: API Management: Switching between Consumption Tier and Basic/Standard/Premium Plans

[tiwari-abhishek]

Is switching between Consumption and Basic/Standard/Premium tiers possible?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 7232dd1a-d250-1304-14ec-db25f04cff48
• Version Independent ID: 29250085-defe-18ac-1ca9-2155b778127b
• Content: Upgrade and scale an Azure API Management instance
• Content Source: articles/api-management/upgrade-and-scale.md
• Service: api-management
• GitHub Login: @mikebudzynski
• Microsoft Alias: apimpm

[mike-urnun-msft]

@tiwari-abhishek Thank you for your question. I'm pretty sure the process is manual for now as in that you have to recreate your APIs and config objects onto the tier/plan that you're switching to.

@miaojiang could you confirm?

[mike-urnun-msft]

@tiwari-abhishek While switching automatically via Portal isn't supported at this time (see screenshot below), you may achieve greater automation by using Azure API Management DevOps Resource Kit as well.

We will now proceed to close this thread for now. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

[sopelt]

@mike-urnun-msft could you please try to get information if this use-case will be supported in the future and possibly improve the documentation by adding this restriction?

I checked and this scenario seems to be unsupported via ARM/Powershell right now so I am not sure what you mean with your link to the APIM DevOps Resource Kit.

PS Azure:\> $apim.Sku = "Premium"
Azure:/
PS Azure:\> Set-AzApiManagement -InputObject $apim
Set-AzApiManagement : Changing SkuType from 'Consumption' to 'Premium' is not Supported.

Having to recreate the whole APIM environment defeats the purpose in terms of having a stable URI/API/Keys/... and significantly limits the consumption tier as a starting point that can grow into more advanced scenarios.