Coordinate both owners before removing a preview perimeter link

Source facts

Azure network security perimeter links and cross-perimeter connectivity are in preview. An existing link can cover one or more profiles and represents a trust relationship between the two participating perimeters.

An administrator of either perimeter can initiate link removal. Microsoft explicitly says that remote-administrator consent is unnecessary, even when creation of the original link used mutual approval. Microsoft Learn.

Applicability

Identify both perimeters, the exact link and reference, associated profiles and dependent test workloads. Confirm that the preview feature is appropriate for the environment before planning changes.

DSE recommendation

DSE recommends notifying both operational owners and recording the intended access outcome before removal. Ask each owner to identify connections that depend on the link and an approved recovery plan. Distinguish the application’s change approval from the permissions that let an administrator execute the operation. Do not assume the remote team will receive or exercise a product-enforced veto merely because the initial connection was mutually approved.

Verification

In an approved test, inspect link and reference state from the relevant administrative scopes and exercise the intended dependent connections. Record what remains permitted and what no longer works without inferring every result from the portal operation alone. Confirm that both owners have received the outcome. Leave any unexpected surviving access or unexplained failure open for investigation before declaring the change complete.

Official references

Microsoft Learn: Configure a perimeter link between network security perimeters. Source retrieved September 9, 2026.