{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-288-coordinate-both-owners-before-removing-a-preview-perimeter-link/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-288-coordinate-both-owners-before-removing-a-preview-perimeter-link/", "slug": "dse-20260909-288-coordinate-both-owners-before-removing-a-preview-perimeter-link", "url": "https://update.dsesecurity.com/updates/dse-20260909-288-coordinate-both-owners-before-removing-a-preview-perimeter-link/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-288-coordinate-both-owners-before-removing-a-preview-perimeter-link.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-288-coordinate-both-owners-before-removing-a-preview-perimeter-link/" }, "title": "Coordinate both owners before removing a preview perimeter link", "summary": "Either participating network security perimeter can initiate removal without the other administrator's consent.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "cybersecurity", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-10T00:27:08+00:00", "modified_at": "2026-09-10T01:23:49+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 235, "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.", "primary_source": { "name": "Configure a perimeter link between network security perimeters - Azure Private Link | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/private-link/configure-perimeter-link", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

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.

\n

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.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n

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

", "content_text": "Source facts\nAzure 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.\nAn 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.\nApplicability\nIdentify 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.\nDSE recommendation\nDSE 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.\nVerification\nIn 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.\nOfficial references\nMicrosoft Learn: Configure a perimeter link between network security perimeters. Source retrieved September 9, 2026.", "content_markdown": "## Source facts\n\nAzure 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.\n\nAn 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).\n\n## Applicability\n\nIdentify 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.\n\n## DSE recommendation\n\nDSE 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.\n\n## Verification\n\nIn 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.\n\n## Official references\n\n[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." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260909-288-coordinate-both-owners-before-removing-a-preview-perimeter-link/", "url": "https://update.dsesecurity.com/updates/dse-20260909-288-coordinate-both-owners-before-removing-a-preview-perimeter-link/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-288-coordinate-both-owners-before-removing-a-preview-perimeter-link/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Coordinate both owners before removing a preview perimeter link", "item": "https://update.dsesecurity.com/updates/dse-20260909-288-coordinate-both-owners-before-removing-a-preview-perimeter-link/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-288-coordinate-both-owners-before-removing-a-preview-perimeter-link/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-288-coordinate-both-owners-before-removing-a-preview-perimeter-link/", "url": "https://update.dsesecurity.com/updates/dse-20260909-288-coordinate-both-owners-before-removing-a-preview-perimeter-link/", "headline": "Coordinate both owners before removing a preview perimeter link", "description": "Either participating network security perimeter can initiate removal without the other administrator's consent.", "abstract": "Either participating network security perimeter can initiate removal without the other administrator's consent.", "articleBody": "Source facts\nAzure 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.\nAn 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.\nApplicability\nIdentify 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.\nDSE recommendation\nDSE 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.\nVerification\nIn 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.\nOfficial references\nMicrosoft Learn: Configure a perimeter link between network security perimeters. Source retrieved September 9, 2026.", "datePublished": "2026-09-10T00:27:08+00:00", "dateModified": "2026-09-10T01:23:49+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-288-coordinate-both-owners-before-removing-a-preview-perimeter-link/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260909-288-coordinate-both-owners-before-removing-a-preview-perimeter-link/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Coordinate both owners before removing a preview perimeter link" }, "articleSection": [ "Cybersecurity", "Networks & Infrastructure" ], "keywords": [ "Cybersecurity", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 235, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Configure a perimeter link between network security perimeters - Azure Private Link | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/private-link/configure-perimeter-link" } } ] } }