Fixes MicrosoftDocs/azure-docs#40501 - Provide clarity around Disabled effect and enforcementMode

Author: DCtheGeek

articles/governance/policy/concepts/assignment-structure.md

@@ -58,8 +58,11 @@ characters and **description** a maximum length of _512_ characters.
 ## Enforcement Mode
 
 The **enforcementMode** property provides customers the ability to test the outcome of a policy on
-existing resources without initiating the policy effect or triggering entries in the [Azure Activity log](../../../azure-monitor/platform/activity-logs-overview.md).
-This scenario is commonly referred to as "What If" and aligns to safe deployment practices.
+existing resources without initiating the policy effect or triggering entries in the
+[Azure Activity log](../../../azure-monitor/platform/activity-logs-overview.md). This scenario is
+commonly referred to as "What If" and aligns to safe deployment practices. **enforcementMode** is
+different from the [Disabled](./effects.md#disabled) effect, as that effect prevents resource
+evaluation from happening at all.
 
 This property has the following values:
 

articles/governance/policy/concepts/effects.md

@@ -50,6 +50,11 @@ This effect is useful for testing situations or for when the policy definition h
 effect. This flexibility makes it possible to disable a single assignment instead of disabling all
 of that policy's assignments.
 
+An alternative to the Disabled effect is **enforcementMode** which is set on the policy assignment.
+When **enforcementMode** is _Disabled_, resources are still evaluated. Logging, such as Activity
+logs, and the policy effect don't occur. For more information, see
+[policy assignment - enforcement mode](./assignment-structure.md#enforcement-mode).
+
 ## Append
 
 Append is used to add additional fields to the requested resource during creation or update. A