{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-012-review-parent-deletion-even-when-an-arm-resource-type-is-marked-nondeleting/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260917-012-review-parent-deletion-even-when-an-arm-resource-type-is-marked-nondeleting/", "slug": "dse-20260917-012-review-parent-deletion-even-when-an-arm-resource-type-is-marked-nondeleting", "url": "https://update.dsesecurity.com/updates/dse-20260917-012-review-parent-deletion-even-when-an-arm-resource-type-is-marked-nondeleting/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260917-012-review-parent-deletion-even-when-an-arm-resource-type-is-marked-nondeleting.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-012-review-parent-deletion-even-when-an-arm-resource-type-is-marked-nondeleting/" }, "title": "Review parent deletion even when an ARM resource type is marked nondeleting", "summary": "Read the complete-mode deletion table together with resource parentage.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "cyber-defense", "label": "Cyber defense", "alt": "Layered glass and metal cyber-defense structure with controlled blue and gold signal paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "cybersecurity", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "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-17T16:34:48+00:00", "modified_at": "2026-09-17T16:35:03+00:00", "reviewed_on": "2026-09-17", "reading_minutes": 1, "word_count": 206, "potentially_affected": "Apply this review to an existing proposal for an ARM complete-mode deployment. Identify the exact resource types and their parent resources. This article explains the deletion reference; it does not recommend choosing complete mode for a new deployment process.", "dse_recommendation": "DSE recommends listing the children of every parent proposed for removal before approving the deployment.", "primary_source": { "name": "Complete mode deletion - Azure Resource Manager | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-complete-mode-deletion", "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

Microsoft’s complete-mode deletion reference says resource types marked No are not automatically removed solely because they are absent from the template. However, they are removed when their parent resource is deleted. The table’s individual entry therefore has to be read with the resource hierarchy. Microsoft Learn.

\n

Applicability

\n

Apply this review to an existing proposal for an ARM complete-mode deployment. Identify the exact resource types and their parent resources. This article explains the deletion reference; it does not recommend choosing complete mode for a new deployment process.

\n

DSE recommendation

\n

DSE recommends listing the children of every parent proposed for removal before approving the deployment. Have the responsible service owner classify the consequences and the available recovery route. Review the current deployment guidance and inspect what-if output against that inventory. Hold the change if a dependent resource has no agreed disposition or recovery evidence.

\n

Verification

\n

In a disposable representative environment, compare the proposed template, resource hierarchy and predicted deletions. If an approved rehearsal is appropriate, inspect both parents and children afterward and compare their state with the prediction. Keep the hierarchy and prediction in the change record; a surviving independent resource does not prove that dependent children were protected.

\n

Official references

\n

Microsoft Learn: Complete mode deletion.

", "content_text": "Source facts\nMicrosoft’s complete-mode deletion reference says resource types marked No are not automatically removed solely because they are absent from the template. However, they are removed when their parent resource is deleted. The table’s individual entry therefore has to be read with the resource hierarchy. Microsoft Learn.\nApplicability\nApply this review to an existing proposal for an ARM complete-mode deployment. Identify the exact resource types and their parent resources. This article explains the deletion reference; it does not recommend choosing complete mode for a new deployment process.\nDSE recommendation\nDSE recommends listing the children of every parent proposed for removal before approving the deployment. Have the responsible service owner classify the consequences and the available recovery route. Review the current deployment guidance and inspect what-if output against that inventory. Hold the change if a dependent resource has no agreed disposition or recovery evidence.\nVerification\nIn a disposable representative environment, compare the proposed template, resource hierarchy and predicted deletions. If an approved rehearsal is appropriate, inspect both parents and children afterward and compare their state with the prediction. Keep the hierarchy and prediction in the change record; a surviving independent resource does not prove that dependent children were protected.\nOfficial references\nMicrosoft Learn: Complete mode deletion.", "content_markdown": "## Source facts\n\nMicrosoft’s complete-mode deletion reference says resource types marked No are not automatically removed solely because they are absent from the template. However, they are removed when their parent resource is deleted. The table’s individual entry therefore has to be read with the resource hierarchy. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-complete-mode-deletion).\n\n## Applicability\n\nApply this review to an existing proposal for an ARM complete-mode deployment. Identify the exact resource types and their parent resources. This article explains the deletion reference; it does not recommend choosing complete mode for a new deployment process.\n\n## DSE recommendation\n\nDSE recommends listing the children of every parent proposed for removal before approving the deployment. Have the responsible service owner classify the consequences and the available recovery route. Review the current deployment guidance and inspect what-if output against that inventory. Hold the change if a dependent resource has no agreed disposition or recovery evidence.\n\n## Verification\n\nIn a disposable representative environment, compare the proposed template, resource hierarchy and predicted deletions. If an approved rehearsal is appropriate, inspect both parents and children afterward and compare their state with the prediction. Keep the hierarchy and prediction in the change record; a surviving independent resource does not prove that dependent children were protected.\n\n## Official references\n\n[Microsoft Learn: Complete mode deletion](https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-complete-mode-deletion)." }, "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-20260917-012-review-parent-deletion-even-when-an-arm-resource-type-is-marked-nondeleting/", "url": "https://update.dsesecurity.com/updates/dse-20260917-012-review-parent-deletion-even-when-an-arm-resource-type-is-marked-nondeleting/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-17" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260917-012-review-parent-deletion-even-when-an-arm-resource-type-is-marked-nondeleting/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Review parent deletion even when an ARM resource type is marked nondeleting", "item": "https://update.dsesecurity.com/updates/dse-20260917-012-review-parent-deletion-even-when-an-arm-resource-type-is-marked-nondeleting/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260917-012-review-parent-deletion-even-when-an-arm-resource-type-is-marked-nondeleting/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260917-012-review-parent-deletion-even-when-an-arm-resource-type-is-marked-nondeleting/", "url": "https://update.dsesecurity.com/updates/dse-20260917-012-review-parent-deletion-even-when-an-arm-resource-type-is-marked-nondeleting/", "headline": "Review parent deletion even when an ARM resource type is marked nondeleting", "description": "Read the complete-mode deletion table together with resource parentage.", "abstract": "Read the complete-mode deletion table together with resource parentage.", "articleBody": "Source facts\nMicrosoft’s complete-mode deletion reference says resource types marked No are not automatically removed solely because they are absent from the template. However, they are removed when their parent resource is deleted. The table’s individual entry therefore has to be read with the resource hierarchy. Microsoft Learn.\nApplicability\nApply this review to an existing proposal for an ARM complete-mode deployment. Identify the exact resource types and their parent resources. This article explains the deletion reference; it does not recommend choosing complete mode for a new deployment process.\nDSE recommendation\nDSE recommends listing the children of every parent proposed for removal before approving the deployment. Have the responsible service owner classify the consequences and the available recovery route. Review the current deployment guidance and inspect what-if output against that inventory. Hold the change if a dependent resource has no agreed disposition or recovery evidence.\nVerification\nIn a disposable representative environment, compare the proposed template, resource hierarchy and predicted deletions. If an approved rehearsal is appropriate, inspect both parents and children afterward and compare their state with the prediction. Keep the hierarchy and prediction in the change record; a surviving independent resource does not prove that dependent children were protected.\nOfficial references\nMicrosoft Learn: Complete mode deletion.", "datePublished": "2026-09-17T16:34:48+00:00", "dateModified": "2026-09-17T16:35:03+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260917-012-review-parent-deletion-even-when-an-arm-resource-type-is-marked-nondeleting/" }, "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-20260917-012-review-parent-deletion-even-when-an-arm-resource-type-is-marked-nondeleting/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Review parent deletion even when an ARM resource type is marked nondeleting" }, "articleSection": [ "Cybersecurity", "IT" ], "keywords": [ "Cybersecurity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 206, "timeRequired": "PT1M", "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": "Complete mode deletion - Azure Resource Manager | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-complete-mode-deletion" } } ] } }