Skip to content

fix: exclude Deploy-SvcHealth-BuiltIn from base archetype to avoid AMBA Service Health duplication (#4210) - #2179

Open
pratyushverma63 wants to merge 1 commit into
mainfrom
fix/4210-exclude-svchealth-builtin-base-archetype
Open

fix: exclude Deploy-SvcHealth-BuiltIn from base archetype to avoid AMBA Service Health duplication (#4210)#2179
pratyushverma63 wants to merge 1 commit into
mainfrom
fix/4210-exclude-svchealth-builtin-base-archetype

Conversation

@pratyushverma63

@pratyushverma63 pratyushverma63 commented Jul 28, 2026

Copy link
Copy Markdown

Overview

Fixes #4210

Deploy-SvcHealth-BuiltIn (assigned by the ALZ root archetype) and AMBA's Deploy-AMBA-Res-SvcHlth initiative member ALZ_SHA_BuiltIn both reference the same built-in Service Health policy definition (98903777-a9f6-47f5-90a9-acaf62ab01a8). When both ALZ and AMBA are deployed to the same management-group hierarchy, each independently runs its own DINE remediation, producing duplicate action groups and duplicate Service Health alert rules (in rg-serviceHealthAlert and rg-amba-monitoring-001).

The Enterprise-Scale ARM/portal path already avoids this via the mutually-exclusive enableServiceHealth condition. However, the ALZ Library (Terraform) path loses that protection because platform/alz and platform/amba are generated from independent sources, so both assignments land together.

Change

Set enableServiceHealthBuiltIn to "No" in eslzArm/eslzArm.terraform-sync.param.json. This excludes Deploy-SvcHealth-BuiltIn from the generated ALZ root archetype in the Azure Landing Zones Library, so the built-in Service Health assignment no longer conflicts with AMBA's initiative.

     "enableServiceHealthBuiltIn": {
-          "value": "Yes"
+          "value": "No"

Validation

  • Library sync simulation: Ran Invoke-LibraryUpdatePolicyAssignmentArchetypes.ps1 against this change — confirmed Deploy-SvcHealth-BuiltIn is removed from the generated root.alz_archetype_definition.json.
  • Live deployment repro (test tenant):
    • Pre-fix: ALZ + AMBA assignments → 2 action groups + 2 identical Service Health alert rules (duplication reproduced).
    • Post-fix: only AMBA's assignment remains → 1 action group + 1 alert rule.
Action groups Alert rules
Pre-fix (ALZ + AMBA) 2 2
Post-fix (AMBA only) 1 1
image image image image image

Post fix validation
image
image
image
image
image

This removes the built-in Service Health assignment from the base archetype for all Library consumers, including non-AMBA deployments, which would lose the default Service Health alerting unless they re-enable it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant