Why it matters
Teams often create their own plan per subscription without knowing it can be shared, so the same protection is paid for several times.How nOps finds it
nOps reads your pay-as-you-go DDoS Protection billing. It looks for two or more plans billed on all of the last 14 complete days and keeps the one that costs the most. A plan includes 100 public IPs and bills each extra one. nOps takes the highest number of public IPs billed on any of the last 7 days across all subscriptions, and subtracts the most extra IP cost the kept plan could add from the saving. The saving is the removed plan’s cost over the last 7 days, scaled to a month, less that amount, and must be at least $5 a month.Before you start
All plans must be in the same Microsoft Entra tenant. Permission to change virtual network settings and delete DDoS plans (for example Network Contributor).How to implement
- Confirm the plans are in the same Microsoft Entra tenant and that no policy requires a separate plan.
- For each virtual network on the plan being removed, open it in the Azure portal, go to DDoS protection and select the plan you keep, or run
az network vnet update --resource-group MY_RG --name MY_VNET --ddos-protection-plan KEPT_PLAN_ID --ddos-protection true. - When no virtual network uses the old plan, delete it, or run
az network ddos-protection delete --resource-group MY_RG --name OLD_PLAN. - Update Azure Policy assignments or templates that point at the old plan.
Risks and considerations
- nOps cannot see the tenant from billing. A plan in another tenant cannot protect your virtual networks.
- Protection continues if you move each virtual network to the kept plan before deleting the old one.
- If you protect more than 100 public IPs in total, the kept plan bills the extra IPs. nOps already takes this into account.
FAQs
Can one plan cover several subscriptions?
Can one plan cover several subscriptions?
Yes. A DDoS Network Protection plan can protect virtual networks in any subscription in the same Microsoft Entra tenant.