Back to Archive

Azure News - 2026-08-01

2026-08-01
最終更新: 2026-08-27 21:13:49 JST

Azure Updates

[In preview] Public Preview: Azure SQL updates for late-July

In late-July 2026, the following update and enhancement was made to Azure SQL: Regex-based dynamic data masking (DDM) extends the built-in DDM feature with pattern‑based masking to hide sensitive data like emails, phone numbers, and identifiers—centrally

[In preview] Public Preview: Route-Maps for Azure Route Server

Route maps for Azure Route Server are now available in public preview, providing fine-grained control over inbound and outbound routing across hybrid connections. Customers can manage routes advertised to and from Azure Route Server BGP peerings with Netw

[Launched] Generally Available: Single-click purchase for public SaaS offers

Eligible SaaS products on Microsoft Marketplace now support a simplified purchase experience in Azure portal. Customers can review plan, billing, resource group, contact details, and terms information on a single page for completing the purchase. This exp

Azure Networking Blog

Scale limits in network security perimeter

詳細を表示

Presently, network security perimeter functionality can be used to support deployments of PaaS resources with common public network controls with following scale limitations:

LimitationDescription
Number of network security perimetersSupported up to 100 as recommended limit per subscription.
Profiles per network security perimetersSupported up to 200 as recommended limit.
Number of rule elements per profileSupported up to 200 for inbound and outbound each as hard limit.
Number of PaaS resources across subscriptions associated with the same network security perimeterSupported up to 1000 as recommended limit.

These limits were deployed as soft limits. The updated limits will be as given in the table below and will now be implemented as hard limits

LimitationDescription
Number of network security perimetersSupported up to 1000 as hard limit per subscription.
Profiles per network security perimetersSupported up to 200 as hard limit.
Number of rule elements per profileSupported up to 200 for inbound and outbound each as hard limit.
Number of PaaS resources across subscriptions associated with the same network security perimeterSupported up to 2500 as hard limit.

What do the changes mean to users?

  1. Rule elements' creation limit will be capped at 200 for new customers. (presently at 500)
  2. Existing customers who have rule elements >200 per profile, will be allowed to continue above 200 with an option to replace/edit, decrease/reduce but not increase/add the current rule elements without any service interruption till 10/31/26.
    1. For example, scenario(s): A user has a profile with rule elements = 400 
      1. They cannot increase/add new rule elements and try to go above 400.
      2. They can replace/edit existing rule elements and continue at 400.
      3. They can decrease/reduce rule elements to anything till 200 and that will be their upper ceiling i.e. if they reduce to 250, that will be their new upper ceiling.
      4. If they decrease/reduce to <200, say 150, they can go till 200 but not back to the 400.
  3. After 10/31/26, profiles with rule elements above 200 will be allowed to continue above 200 but only with an option to reduce. There will be no replace/edit and increase options.
    1. For example, scenario(s): A user has a profile with rule elements = 400
      1. They cannot increase/add new rule elements and try to go above 400.
      2. They cannot replace/edit existing rule elements but can continue at 400 without touch the rule-elements.
      3. They can decrease/reduce rule elements to anything till 200 but cannot stop above 200 or maintain above 200.
      4. If they decrease/reduce to <200, say 150, they can go till 200 but not back to the 400.

For questions or clarifications, please reach out to nsppmvteam@microsoft.com

前日
Archive
翌日