Illustration of two secure systems exchanging data through an encrypted, shield-protected connection.
Azure's Network Security Perimeter (NSP) now has a public preview feature for joining two perimeters. Microsoft's Azure Updates listing for the feature is dated November 17, 2026. The listing itself carries almost no detail. The technical specifics below come from Microsoft Learn documentation, and that page was last updated July 13, 2026. It predates the Azure Updates item, so treat the details as the documented preview scope, not a verified change log.

Illustration of two secure systems exchanging data through an encrypted, shield-protected connection. What a perimeter link does​

A perimeter link, also called a cross-perimeter connection, is a secure connection that lets resources in different network security perimeters communicate without extra access rules. Until now, a key vault in one perimeter that needed to reach a storage account in another meant hand-writing inbound and outbound rules on both sides. Once you create a link, Azure generates those rules for you.

The baseline NSP model is a logical boundary for PaaS resources deployed outside virtual networks. In enforced mode, public traffic to associated resources is denied by default, and you open exceptions with access rules. The perimeter link is a way to approve one specific kind of exception, trusted traffic between two perimeters, without writing a rule for each case.

How it works​

  • A perimeter link joins two independent perimeters through a single connection.
  • It connects specific profiles. In Microsoft's example, a link connects Profile-A1 in perimeter A to Profile-B1 in perimeter B, establishing a trust relationship.
  • The selected profiles get extra inbound and outbound allow rules. The documentation says the source type of the generated rules is "Network security perimeter".
  • The link is symmetric. "Local" and "remote" only describe which perimeter you are configuring from.

Availability and access​

Microsoft says the preview is available across all NSP-supported Azure public and Azure Government cloud regions. It can be used through the Azure portal, CLI, PowerShell and API.

Setup also involves registration. The configuration guide says you register the Perimeter Link preview feature by using the Azure portal, Azure CLI, or Azure PowerShell before creating a link. The CLI exposes this through az network perimeter link create, and there are matching link list and link-reference list commands for inventory. The exact registration parameters are in Microsoft's configuration guide, so check them there before scripting anything.

Supported services​

The documented services for the preview are:

  • Azure SQL Database
  • Azure Storage
  • Azure Cosmos DB
  • Azure Key Vault
  • Azure Monitoring
  • Azure Service Bus

That list is not the same as the full NSP onboarding list. Services such as Event Hubs, AI Search and Event Grid are NSP-aware but are not listed for cross-perimeter links. Underlying NSP support also varies by service. Microsoft's concepts page marks SQL DB and Cosmos DB as public preview for NSP itself, so some of these links sit on preview-on-preview foundations.

Limits and requirements​

  • Managed Identity only. The documentation says other authentication methods aren't supported. Workloads that use keys, SAS tokens or connection strings will not benefit from a link. Audit them first.
  • 10 links per perimeter. The maximum number of perimeter links per network security perimeter is 10. A hub-and-spoke design with many spokes can run into this ceiling.
  • Same-subscription auto-approval only. Links across subscriptions need the initiating subscription owner to have Contributor access on the remote perimeter's subscription. The alternative is the Microsoft.Network/networkSecurityPerimeters/linkPerimeter/action permission there. Without one of these, the link can't be configured.

The removal risk​

Removal is the part most likely to cause an outage. Microsoft's documentation says removing a link ends the trust relationship and deletes the rules the link generated. Managed-identity service-to-service traffic that relied on the link is then denied, and enforcement falls back to the normal NSP rules.

Removal needs no consent from the other side. Per the documentation, an administrator of either perimeter can initiate link removal, even if mutual approval was used to create the link. That is a sensible design, because either team should be able to cut a connection it no longer trusts. It also means one team can break another team's workload without warning.

A third-party advisory from DSE Security recommends notifying both operational owners and recording the intended access outcome before removal. That is the vendor's own recommendation, not Microsoft guidance, but it is a reasonable process control.

Practical checklist before piloting​

  1. Confirm the workloads in both perimeters authenticate with managed identities.
  2. Check that every service involved is on the supported list.
  3. Review the subscription layout and the cross-subscription permissions.
  4. Register the preview feature and test in a non-production environment. Microsoft points to the Azure Preview Supplemental Terms, and Azure's own status definitions describe preview as non-production use and testing.
  5. Agree on an owner and a change process for link removal, and record which profiles each link connects.
  6. Track the 10-link limit as you design the topology.

Analysis​

The feature addresses a real problem. Organizations that segment PaaS resources into multiple perimeters, perhaps by business unit or environment, often find that manual rules between perimeters are tedious and easy to get wrong. Auto-generated rules scoped to chosen profiles should be cleaner than IP or subscription-based exceptions.

The caveats are the limited service list, the managed-identity requirement, the 10-link cap and preview status. For now, this is something to pilot, not to build production dependencies on. The documentation also doesn't say whether the generated rules appear in logs differently from hand-written ones. Verify that in a test before relying on it for audit evidence.

 

References

  1. (In preview) Public Preview: Perimeter link (cross perimeter) in network security perimeter Azure Updates 2026-11-17T20:51:13Z
  2. Perimeter link feature in Network Security Perimeter (Preview) - Azure Private Link learn.microsoft.com
  3. What is a network security perimeter? - Azure Private Link | Microsoft Learn learn.microsoft.com