diff --git a/docs/content/accelerator/starter-terraform/options/amba.md b/docs/content/accelerator/starter-terraform/options/amba.md
index e6b22b7..7d3ecdc 100644
--- a/docs/content/accelerator/starter-terraform/options/amba.md
+++ b/docs/content/accelerator/starter-terraform/options/amba.md
@@ -41,6 +41,12 @@ management_groups:
     parent_id: null
 {{< / highlight >}}
 
+{{< hint type=warning >}}
+When deploying the `amba_root` archetype alongside the ALZ archetype, remove `Deploy-SvcHealth-BuiltIn` from the custom ALZ archetype override used by `root_custom`.
+
+AMBA already provides Service Health alerting through `Deploy-AMBA-Res-SvcHlth`. If both assignments remain enabled, they can create duplicate Service Health alert rules and action groups in separate resource groups.
+{{< /hint >}}
+
 3. Before deployment, there are a couple of pre-requisites that need to be completed, they include creating a managed identity in order to query Resource Graph for alerts and a resource group to store the alert/monitoring assets. Start by locating the `platform-landing-zone.tfvars` >`custom_replacements` > `names` block setting and add the following code:
 
 {{< highlight terraform "linenos=table" >}}
@@ -113,4 +119,4 @@ management_group_settings = {
 }
 {{< / highlight >}}
 
-The options for the policy default values and the policies they're used for, can be found in the [Azure Landing Zone AMBA Library](https://github.com/Azure/Azure-Landing-Zones-Library/blob/dae3d4cbcb32520f74bdeba144a95a6486517130/platform/amba/alz_policy_default_values.json).
\ No newline at end of file
+The options for the policy default values and the policies they're used for, can be found in the [Azure Landing Zone AMBA Library](https://github.com/Azure/Azure-Landing-Zones-Library/blob/dae3d4cbcb32520f74bdeba144a95a6486517130/platform/amba/alz_policy_default_values.json).