updates effect links

Author: davidsmatlak

articles/governance/policy/assign-policy-portal.md

@@ -58,7 +58,7 @@ In this quickstart, you create a policy assignment with a built-in policy defini
    | Tab name | Options |
    | ---- | ---- |
    | **Parameters** | If the policy definition you selected on the **Basics** tab has parameters, you configure them on the **Parameters** tab. This example doesn't use parameters. |
-   | **Remediation** | You can create a managed identity. For this example, **Create a Managed Identity** is unchecked. <br><br> This box _must_ be checked when a policy or initiative includes a policy with either the [deployIfNotExists](./concepts/effects.md#deployifnotexists) or [modify](./concepts/effects.md#modify) effect. For more information, go to [managed identities](../../active-directory/managed-identities-azure-resources/overview.md) and [how remediation access control works](./how-to/remediate-resources.md#how-remediation-access-control-works). |
+   | **Remediation** | You can create a managed identity. For this example, **Create a Managed Identity** is unchecked. <br><br> This box _must_ be checked when a policy or initiative includes a policy with either the [deployIfNotExists](./concepts/effect-deploy-if-not-exists.md) or [modify](./concepts/effect-modify.md) effect. For more information, go to [managed identities](../../active-directory/managed-identities-azure-resources/overview.md) and [how remediation access control works](./how-to/remediate-resources.md#how-remediation-access-control-works). |
 
 1. Select **Next** and on the **Non-compliance messages** tab create a **Non-compliance message** like _Virtual machines should use managed disks_.
 

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

@@ -275,7 +275,7 @@ One override can be used to replace the effect of many policies by specifying mu
 
 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/azure-monitor/essentials/platform-logs-overview).
 
-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 scenario is commonly referred to as _What If_ and aligns to safe deployment practices. `enforcementMode` is different from the [Disabled](./effect-disabled.md) effect, as that effect prevents resource evaluation from happening at all.
 
 This property has the following values:
 
@@ -284,7 +284,7 @@ This property has the following values:
 |Enabled |Default |string |Yes |Yes |The policy effect is enforced during resource creation or update. |
 |Disabled |DoNotEnforce |string |Yes |No | The policy effect isn't enforced during resource creation or update. |
 
-If `enforcementMode` isn't specified in a policy or initiative definition, the value _Default_ is used. [Remediation tasks](../how-to/remediate-resources.md) can be started for [deployIfNotExists](./effects.md#deployifnotexists) policies, even when `enforcementMode` is set to _DoNotEnforce_.
+If `enforcementMode` isn't specified in a policy or initiative definition, the value _Default_ is used. [Remediation tasks](../how-to/remediate-resources.md) can be started for [deployIfNotExists](./effect-deploy-if-not-exists.md) policies, even when `enforcementMode` is set to _DoNotEnforce_.
 
 ## Excluded scopes
 

articles/governance/policy/concepts/definition-structure-alias.md

@@ -30,7 +30,7 @@ The list of aliases is always growing. To find which aliases Azure Policy suppor
   ```
 
   > [!NOTE]
-  > To find aliases that can be used with the [modify](./effects.md#modify) effect, use the
+  > To find aliases that can be used with the [modify](./effect-modify.md) effect, use the
   > following command in Azure PowerShell **4.6.0** or higher:
   >
   > ```azurepowershell-interactive
@@ -83,7 +83,7 @@ For more information and examples, see [Referencing array resource properties](.
 - For more information about policy definition structure, go to [basics](./definition-structure-basics.md), [parameters](./definition-structure-parameters.md), and [policy rule](./definition-structure-policy-rule.md).
 - For initiatives, go to [initiative definition structure](./initiative-definition-structure.md).
 - Review examples at [Azure Policy samples](../samples/index.md).
-- Review [Understanding policy effects](effects.md).
+- Review [Understanding policy effects](effect-basics.md).
 - Understand how to [programmatically create policies](../how-to/programmatically-create.md).
 - Learn how to [get compliance data](../how-to/get-compliance-data.md).
 - Learn how to [remediate non-compliant resources](../how-to/remediate-resources.md).

articles/governance/policy/concepts/definition-structure-parameters.md

@@ -193,7 +193,7 @@ The non _resource type_ allowed values for `strongType` are:
 - For more information about policy definition structure, go to [basics](./definition-structure-basics.md), [policy rule](./definition-structure-policy-rule.md), and [alias](./definition-structure-alias.md).
 - For initiatives, go to [initiative definition structure](./initiative-definition-structure.md).
 - Review examples at [Azure Policy samples](../samples/index.md).
-- Review [Understanding policy effects](effects.md).
+- Review [Understanding policy effects](effect-basics.md).
 - Understand how to [programmatically create policies](../how-to/programmatically-create.md).
 - Learn how to [get compliance data](../how-to/get-compliance-data.md).
 - Learn how to [remediate non-compliant resources](../how-to/remediate-resources.md).

articles/governance/policy/concepts/definition-structure-policy-rule.md

@@ -633,7 +633,7 @@ The following functions are only available in policy rules:
 - `field(fieldName)`
   - `fieldName`: [Required] string - Name of the [field](./definition-structure-policy-rule.md#fields) to retrieve
   - Returns the value of that field from the resource that is being evaluated by the If condition.
-  - `field` is primarily used with `auditIfNotExists` and `deployIfNotExists` to reference fields on the resource that are being evaluated. An example of this use can be seen in the [DeployIfNotExists example](effects.md#deployifnotexists-example).
+  - `field` is primarily used with `auditIfNotExists` and `deployIfNotExists` to reference fields on the resource that are being evaluated. An example of this use can be seen in the [DeployIfNotExists example](effect-deploy-if-not-exists.md-example).
 
 - `requestContext().apiVersion`
   - Returns the API version of the request that triggered policy evaluation (example: `2021-09-01`). This value is the API version that was used in the PUT/PATCH request for evaluations on resource creation/update. The latest API version is always used during compliance evaluation on existing resources.
@@ -727,7 +727,7 @@ The length of the string created by the `concat()` function depends on the value
 - For more information about policy definition structure, go to [basics](./definition-structure-basics.md), [parameters](./definition-structure-parameters.md), and [alias](./definition-structure-alias.md).
 - For initiatives, go to [initiative definition structure](./initiative-definition-structure.md).
 - Review examples at [Azure Policy samples](../samples/index.md).
-- Review [Understanding policy effects](effects.md).
+- Review [Understanding policy effects](effect-basics.md).
 - Understand how to [programmatically create policies](../how-to/programmatically-create.md).
 - Learn how to [get compliance data](../how-to/get-compliance-data.md).
 - Learn how to [remediate non-compliant resources](../how-to/remediate-resources.md).

articles/governance/policy/concepts/initiative-definition-structure.md

@@ -392,7 +392,7 @@ Below is an example of the **policyMetadata** object. This example metadata belo
 
 - See the [definition structure](./definition-structure.md)
 - Review examples at [Azure Policy samples](../samples/index.md).
-- Review [Understanding policy effects](effects.md).
+- Review [Understanding policy effects](effect-basics.md).
 - Understand how to [programmatically create policies](../how-to/programmatically-create.md).
 - Learn how to [get compliance data](../how-to/get-compliance-data.md).
 - Learn how to [remediate non-compliant resources](../how-to/remediate-resources.md).

articles/governance/policy/concepts/policy-as-code.md

@@ -43,7 +43,7 @@ The file names correspond with certain portions of policy or initiative definiti
 | `policyset-v#.parameters.json`   | The `properties.parameters` portion of the initiative definition           |
 | `policy-v#.rules.json`           | The `properties.policyRule` portion of the policy definition               |
 | `policyset-v#.definitions.json`  | The `properties.policyDefinitions` portion of the initiative definition    |
-| `exemptionName.json`          | The policy exemption that targets a particular resource or scope  | 
+| `exemptionName.json`          | The policy exemption that targets a particular resource or scope  |
 
 
 ## Workflow overview
@@ -56,7 +56,7 @@ The recommended general workflow of Azure Policy as Code looks like this diagram
 
 ### Source control
 
-Existing [policy and initiative definitions can be exported](../how-to/export-resources.md) different ways such as through PowerShell, CLI, or [Azure Resource Graph (ARG)](../../resource-graph/overview.md) queries. The source control management environment of choice to store these definitions can be one of many options, including a [GitHub](https://www.github.com) or [Azure DevOps](/azure/devops/user-guide/what-is-azure-devops). 
+Existing [policy and initiative definitions can be exported](../how-to/export-resources.md) different ways such as through PowerShell, CLI, or [Azure Resource Graph (ARG)](../../resource-graph/overview.md) queries. The source control management environment of choice to store these definitions can be one of many options, including a [GitHub](https://www.github.com) or [Azure DevOps](/azure/devops/user-guide/what-is-azure-devops).
 
 ### Create and update policy definitions
 
@@ -146,7 +146,7 @@ the update to the object in Azure, it's time to test the changes that were made.
 or the initiative(s) it's part of should then be assigned to resources in the environment farthest
 from production. This environment is typically _Dev_.
 
->[!NOTE] 
+>[!NOTE]
 > In this step, we are conducting integration testing of the policy definition within your Azure environment, this is seperate from [verfying the functionality of the policy definition](./evaluate-impact.md#test-your-policys-effectiveness) which should occur during the definition creation process.
 
 The assignment should use [enforcementMode](./assignment-structure.md#enforcement-mode) of
@@ -171,8 +171,8 @@ may be unexpected and unidentified impact from the policy. For more information,
 ### Enable remediation tasks
 
 If validation of the assignment meets expectations, the next step is to validate remediation.
-Policies that use either [deployIfNotExists](./effects.md#deployifnotexists) or
-[modify](./effects.md#modify) can have an associated remediation task triggered to correct resources from a non-compliant state and bring them into compliance.
+Policies that use either [deployIfNotExists](./effect-deploy-if-not-exists.md) or
+[modify](./effect-modify.md) can have an associated remediation task triggered to correct resources from a non-compliant state and bring them into compliance.
 
 The first step to remediating resources is to grant the policy assignment the role assignment
 defined in the policy definition. This role assignment gives the policy assignment managed identity
@@ -227,4 +227,3 @@ supports scripted steps and automation based on triggers.
 - Learn how to [get compliance data](../how-to/get-compliance-data.md).
 - Learn how to [remediate non-compliant resources](../how-to/remediate-resources.md).
 - Under how to [follow policy safe deployment practices](../how-to/policy-safe-deployment-practices.md)
-  

articles/governance/policy/concepts/regulatory-compliance.md

@@ -94,5 +94,5 @@ The following code is an example of added results from a `summarize` call:
 
 - See the [initiative definition structure](./initiative-definition-structure.md)
 - Review examples at [Azure Policy samples](../samples/index.md).
-- Review [Understanding policy effects](./effects.md).
+- Review [Understanding policy effects](./effect-basics.md).
 - Learn how to [remediate non-compliant resources](../how-to/remediate-resources.md).

articles/governance/policy/how-to/author-policies-for-arrays.md

@@ -617,7 +617,7 @@ For useful examples, see [Field count examples](../concepts/definition-structure
 
 ## Modifying arrays
 
-The [append](../concepts/effects.md#append) and [modify](../concepts/effects.md#modify) alter properties on a resource during creation or update. When you work with array properties, the behavior of these effects depends on whether the operation is trying to modify the `[*]` alias or not:
+The [append](../concepts/effect-append.md) and [modify](../concepts/effect-modify.md) alter properties on a resource during creation or update. When you work with array properties, the behavior of these effects depends on whether the operation is trying to modify the `[*]` alias or not:
 
 > [!NOTE]
 > Using the `modify` effect with aliases is currently in **preview**.
@@ -634,7 +634,7 @@ The [append](../concepts/effects.md#append) and [modify](../concepts/effects.md#
 | `Microsoft.Storage/storageAccounts/networkAcls.ipRules[*].action` | `modify` with `add` operation | Azure Policy appends a value to the `action` property of each array member. |
 | `Microsoft.Storage/storageAccounts/networkAcls.ipRules[*].action` | `modify` with `addOrReplace` operation | Azure Policy appends or replaces the existing `action` property of each array member. |
 
-For more information, see the [append examples](../concepts/effects.md#append-examples).
+For more information, see the [append examples](../concepts/effect-append.md#append-examples).
 
 ## More alias examples
 

articles/governance/policy/how-to/determine-non-compliance.md

@@ -54,8 +54,8 @@ To view the compliance details, follow these steps:
 
    For an `auditIfNotExists` or `deployIfNotExists` policy definition, the details include the
    **details.type** property and any optional properties. For a list, see [auditIfNotExists
-   properties](../concepts/effects.md#auditifnotexists-properties) and [deployIfNotExists
-   properties](../concepts/effects.md#deployifnotexists-properties). **Last evaluated resource** is
+   properties](../concepts/effect-audit-if-not-exists.md#auditifnotexists-properties) and [deployIfNotExists
+   properties](../concepts/effect-deploy-if-not-exists.md#deployifnotexists-properties). **Last evaluated resource** is
    a related resource from the **details** section of the definition.
 
    Example partial `deployIfNotExists` definition:
@@ -253,7 +253,7 @@ query this information outside of the Azure portal, see [Get resource changes](.
 
 - Review examples at [Azure Policy samples](../samples/index.md).
 - Review the [Azure Policy definition structure](../concepts/definition-structure.md).
-- Review [Understanding policy effects](../concepts/effects.md).
+- Review [Understanding policy effects](../concepts/effect-basics.md).
 - Understand how to [programmatically create policies](programmatically-create.md).
 - Learn how to [get compliance data](get-compliance-data.md).
 - Learn how to [remediate non-compliant resources](remediate-resources.md).