# Coordinate both owners before removing a preview perimeter link

> Either participating network security perimeter can initiate removal without the other administrator's consent.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-288-coordinate-both-owners-before-removing-a-preview-perimeter-link/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:27:08+00:00
- Modified: 2026-09-10T01:23:49+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Cybersecurity, Networks & Infrastructure
- Reading time: 2 minutes

## What you need to know

Either participating network security perimeter can initiate removal without the other administrator's consent.

## Potentially affected

Azure network security perimeters participating in preview cross-perimeter links.

## DSE recommendation

Treat remote-owner coordination as an operational requirement, not an approval step the product necessarily enforces.

## Article

## 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](https://learn.microsoft.com/en-us/azure/private-link/configure-perimeter-link).

## 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](https://learn.microsoft.com/en-us/azure/private-link/configure-perimeter-link). Source retrieved September 9, 2026.

## Primary reference

- Name: Configure a perimeter link between network security perimeters - Azure Private Link | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/private-link/configure-perimeter-link
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Coordinate both owners before removing a preview perimeter link,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-288-coordinate-both-owners-before-removing-a-preview-perimeter-link/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.