Azure-docs: Setting Pricing Tier to Standard via REST API

[cananac]

Hi,

What is the way to set pricing tier as Standard for the subscription via REST API? It used to be by setting "name" as "default". But now it expects a specific resource name and does not accept default as value any more.
"The name 'default' is not a valid name. Possible pricing bundle names: VirtualMachines, SqlServers, AppServices, StorageAccounts, SqlServerVirtualMachines, KubernetesService, ContainerRegistry, KeyVaults."

Does that mean it can not be configured at subscription level any more and should be done for each resource type?

Thanks,
Canan

---

Document Details

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

• ID: f8e2ed68-8901-d002-a00a-e1d702cc1638
• Version Independent ID: 32c32bf8-8492-e8c6-c05f-3b0845b06913
• Content: Pricing of Azure Security Center tiers
• Content Source: articles/security-center/security-center-pricing.md
• Service: security-center
• GitHub Login: @memildin
• Microsoft Alias: memildin

[SaurabhSharma-MSFT]

@cananac Thanks for your feedback! We will investigate and update as appropriate.

[SaurabhSharma-MSFT]

@cananac You can use the below Rest API endpoint to update the security center pricing
https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.Security/pricings/{pricingName}?api-version=2018-06-01
Please refer to the Pricings - Update documentation.

[cananac]

Thanks @SaurabhSharma-MSFT . My question is more about at what level this should be configured. To be more clear, if I want to set Standard pricing Tier at subscription level, what should be the pricing name?

[SaurabhSharma-MSFT]

@cananac ok. I get you. I am checking this internally with the products team and update you on my findings.

[SaurabhSharma-MSFT]

@cananac I have got the confirmation from the products team that the naming indeed changed, the “default” pricing from the older API was changed to “VirtualMachines” and support for more types were added to support more granular resource type protection. Each bundle represents standard protection for the bundle’s resource types across the entire subscription. So, if you wants to upgrade all bundles for a subscription, then all bundles should be updated via “Pricing and settings “ blade in UI or Multiple REST API calls to upgrade each individual bundles.

[cananac]

Thanks @SaurabhSharma-MSFT