update definition links

Author: davidsmatlak

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](effect-deploy-if-not-exists.md-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#deployifnotexists-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.

articles/governance/policy/concepts/effect-add-to-network-group.md

@@ -7,7 +7,7 @@ ms.topic: conceptual
 
 # Azure Policy definitions addToNetworkGroup effect
 
-The `addToNetworkGroup` effect is used in Azure Virtual Network Manager to define dynamic network group membership. This effect is specific to `Microsoft.Network.Data` [policy mode](./definition-structure.md#resource-provider-modes) definitions only.
+The `addToNetworkGroup` effect is used in Azure Virtual Network Manager to define dynamic network group membership. This effect is specific to `Microsoft.Network.Data` [policy mode](./definition-structure-basics.md#resource-provider-modes) definitions only.
 
 With network groups, your policy definition includes your conditional expression for matching virtual networks meeting your criteria, and specifies the destination network group where any matching resources are placed. The `addToNetworkGroup` effect is used to place resources in the destination network group.
 

articles/governance/policy/concepts/effect-basics.md

@@ -36,7 +36,7 @@ The following list is some general guidance around interchangeable effects:
 
 ## Order of evaluation
 
-Azure Policy's first evaluation is for requests to create or update a resource. Azure Policy creates a list of all assignments that apply to the resource and then evaluates the resource against each definition. For a [Resource Manager mode](./definition-structure.md#resource-manager-modes), Azure Policy processes several of the effects before handing the request to the appropriate Resource Provider. This order prevents unnecessary processing by a Resource Provider when a resource doesn't meet the designed governance controls of Azure Policy. With a [Resource Provider mode](./definition-structure.md#resource-provider-modes), the Resource Provider manages the evaluation and outcome and reports the results back to Azure Policy.
+Azure Policy's first evaluation is for requests to create or update a resource. Azure Policy creates a list of all assignments that apply to the resource and then evaluates the resource against each definition. For a [Resource Manager mode](./definition-structure-basics.md#resource-manager-modes), Azure Policy processes several of the effects before handing the request to the appropriate Resource Provider. This order prevents unnecessary processing by a Resource Provider when a resource doesn't meet the designed governance controls of Azure Policy. With a [Resource Provider mode](./definition-structure-basics.md#resource-provider-modes), the Resource Provider manages the evaluation and outcome and reports the results back to Azure Policy.
 
 - `disabled` is checked first to determine whether the policy rule should be evaluated.
 - `append` and `modify` are then evaluated. Since either could alter the request, a change made might prevent an audit or deny effect from triggering. These effects are only available with a Resource Manager mode.

articles/governance/policy/concepts/effect-deny-action.md

@@ -38,7 +38,7 @@ The `details` property of the `denyAction` effect has all the subproperties that
   - Supported action names are: `delete`.
 - `cascadeBehaviors` (optional)
   - An _object_ that defines which behavior is followed when a resource is implicitly deleted when a resource group is removed.
-  - Only supported in policy definitions with [mode](./definition-structure.md#resource-manager-modes) set to `indexed`.
+  - Only supported in policy definitions with [mode](./definition-structure-basics.md#resource-manager-modes) set to `indexed`.
   - Allowed values are `allow` or `deny`.
   - Default value is `deny`.
 

articles/governance/policy/concepts/effect-modify.md

@@ -7,13 +7,13 @@ ms.topic: conceptual
 
 # Azure Policy definitions modify effect
 
-The `modify` effect is used to add, update, or remove properties or tags on a subscription or resource during creation or update. Existing non-compliant resources can also be remediated with a [remediation task](../how-to/remediate-resources.md). Policy assignments with effect set as Modify require a [managed identity](../how-to/remediate-resources.md) to do remediation. A common example using `modify` effect is updating tags on resources such as 'costCenter'. 
+The `modify` effect is used to add, update, or remove properties or tags on a subscription or resource during creation or update. Existing non-compliant resources can also be remediated with a [remediation task](../how-to/remediate-resources.md). Policy assignments with effect set as Modify require a [managed identity](../how-to/remediate-resources.md) to do remediation. A common example using `modify` effect is updating tags on resources such as 'costCenter'.
 
 There are some nuances in modification behavior for resource properties. Learn more about scenarios when modification is [skipped](#skipped-modification).
 
 A single `modify` rule can have any number of operations. Supported operations are:
 
-- _Add_, _replace_, or _remove_ resource tags. Only tags can be removed. For tags, a Modify policy should have [mode](./definition-structure.md#resource-manager-modes) set to `indexed` unless the target resource is a resource group.
+- _Add_, _replace_, or _remove_ resource tags. Only tags can be removed. For tags, a Modify policy should have [mode](./definition-structure-basics.md#resource-manager-modes) set to `indexed` unless the target resource is a resource group.
 - _Add_ or _replace_ the value of managed identity type (`identity.type`) of virtual machines and Virtual Machine Scale Sets. You can only modify the `identity.type` for virtual machines or Virtual Machine Scale Sets.
 - _Add_ or _replace_ the values of certain aliases.
   - Use `Get-AzPolicyAlias | Select-Object -ExpandProperty 'Aliases' | Where-Object { $_.DefaultMetadata.Attributes -eq 'Modifiable' }` in Azure PowerShell **4.6.0** or higher to get a list of aliases that can be used with `modify`.
@@ -26,7 +26,7 @@ A single `modify` rule can have any number of operations. Supported operations a
 
 ## Modify evaluation
 
-Modify evaluates before the request gets processed by a Resource Provider during the creation or updating of a resource. The `modify` operations are applied to the request content when the `if` condition of the policy rule is met. Each `modify` operation can specify a condition that determines when it's applied. 
+Modify evaluates before the request gets processed by a Resource Provider during the creation or updating of a resource. The `modify` operations are applied to the request content when the `if` condition of the policy rule is met. Each `modify` operation can specify a condition that determines when it's applied.
 
 When an alias is specified, more checks are performed to ensure that the `modify` operation doesn't change the request content in a way that causes the resource provider to reject it:
 
@@ -55,7 +55,7 @@ Modification of resource properties depends on the API request and the updated r
 
 Imagine you apply a policy that modifies tags on a virtual machine (VM). Every time the VM is updated, such as during resizing or disk changes, the tags are updated accordingly regardless of the contents of the VM payload. This is because tags are independent of the VM properties.
 
-However, if you apply a policy that modifies properties on a VM, modification is dependent on the resource payload. If you attempt to modify properties that are not included in the update payload, the modification will not take place. For instance, this can happen when patching the `assessmentMode` property of a VM (alias `Microsoft.Compute/virtualMachines/osProfile.windowsConfiguration.patchSettings.assessmentMode`). The property is "nested", so if its parent properties are not included in the request, this omission is assumed to be intentional and modification is skipped. For modification to take place, the resource payload should contain this context. 
+However, if you apply a policy that modifies properties on a VM, modification is dependent on the resource payload. If you attempt to modify properties that are not included in the update payload, the modification will not take place. For instance, this can happen when patching the `assessmentMode` property of a VM (alias `Microsoft.Compute/virtualMachines/osProfile.windowsConfiguration.patchSettings.assessmentMode`). The property is "nested", so if its parent properties are not included in the request, this omission is assumed to be intentional and modification is skipped. For modification to take place, the resource payload should contain this context.
 
 ## Modify properties
 
@@ -75,7 +75,7 @@ The `details` property of the `modify` effect has all the subproperties that def
   - An array of all tag operations to be completed on matching resources.
   - Properties:
     - `operation` (required)
-      - Defines what action to take on a matching resource. Options are: `addOrReplace`, `Add`, and `Remove`. 
+      - Defines what action to take on a matching resource. Options are: `addOrReplace`, `Add`, and `Remove`.
       - `Add` behaves similar to the [append](./effect-append.md) effect.
       - `Remove` is only supported for resource tags.
     - `field` (required)
@@ -84,7 +84,7 @@ The `details` property of the `modify` effect has all the subproperties that def
       - The value to set the tag to.
       - This property is required if `operation` is _addOrReplace_ or _Add_.
     - `condition` (optional)
-      - A string containing an Azure Policy language expression with [Policy functions](./definition-structure.md#policy-functions) that evaluates to _true_ or _false_.
+      - A string containing an Azure Policy language expression with [Policy functions](./definition-structure-policy-rule.md#policy-functions) that evaluates to _true_ or _false_.
       - Doesn't support the following Policy functions: `field()`, `resourceGroup()`,
         `subscription()`.
 
@@ -202,4 +202,4 @@ Example 3: Ensure that a storage account doesn't allow blob public access, the `
 - 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).
-- Review [Azure management groups](../../management-groups/overview.md).
+- Review [Azure management groups](../../management-groups/overview.md).

articles/governance/policy/concepts/effect-mutate.md

@@ -7,7 +7,7 @@ ms.topic: conceptual
 
 # Azure Policy definitions mutate (preview) effect
 
-Mutation is used in Azure Policy for Kubernetes to remediate Azure Kubernetes Service (AKS) cluster components, like pods. This effect is specific to _Microsoft.Kubernetes.Data_ [policy mode](./definition-structure.md#resource-provider-modes) definitions only.
+Mutation is used in Azure Policy for Kubernetes to remediate Azure Kubernetes Service (AKS) cluster components, like pods. This effect is specific to _Microsoft.Kubernetes.Data_ [policy mode](./definition-structure-basics.md#resource-provider-modes) definitions only.
 
 To learn more, go to [Understand Azure Policy for Kubernetes clusters](./policy-for-kubernetes.md).
 

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

@@ -7,7 +7,7 @@ ms.topic: conceptual
 
 # Azure Policy exemption structure
 
-The Azure Policy exemptions feature is used to _exempt_ a resource hierarchy or an individual resource from evaluation of initiatives or definitions. Resources that are _exempt_ count toward overall compliance, but can't be evaluated or have a temporary waiver. For more information, see [Understand applicability in Azure Policy](./policy-applicability.md). Azure Policy exemptions also work with the following [Resource Manager modes](./definition-structure.md#resource-manager-modes): `Microsoft.Kubernetes.Data`, `Microsoft.KeyVault.Data`, and `Microsoft.Network.Data`.
+The Azure Policy exemptions feature is used to _exempt_ a resource hierarchy or an individual resource from evaluation of initiatives or definitions. Resources that are _exempt_ count toward overall compliance, but can't be evaluated or have a temporary waiver. For more information, see [Understand applicability in Azure Policy](./policy-applicability.md). Azure Policy exemptions also work with the following [Resource Manager modes](./definition-structure-basics.md#resource-manager-modes): `Microsoft.Kubernetes.Data`, `Microsoft.KeyVault.Data`, and `Microsoft.Network.Data`.
 
 You use JavaScript Object Notation (JSON) to create a policy exemption. The policy exemption contains elements for:
 

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

@@ -390,7 +390,7 @@ Below is an example of the **policyMetadata** object. This example metadata belo
 
 ## Next steps
 
-- See the [definition structure](./definition-structure.md)
+- See the [definition structure](./definition-structure-basics.md)
 - Review examples at [Azure Policy samples](../samples/index.md).
 - Review [Understanding policy effects](effect-basics.md).
 - Understand how to [programmatically create policies](../how-to/programmatically-create.md).

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

@@ -29,7 +29,7 @@ before it's too late and they're attempting to deploy in production.
 
 Before getting into the details of Azure Policy as Code workflow, it's important to understand some fundamental concepts, like how to author policy definitions and initiative definitions, and how to leverage exemptions on assignments of those definitions:
 
-- [Policy definition](./definition-structure.md)
+- [Policy definition](./definition-structure-basics.md)
 - [Initiative definition](./initiative-definition-structure.md)
 - [Policy exemption](./exemption-structure.md)
 
@@ -221,7 +221,7 @@ supports scripted steps and automation based on triggers.
 
 ## Next steps
 
-- Learn about the [policy definition structure](./definition-structure.md).
+- Learn about the [policy definition structure](./definition-structure-basics.md).
 - Learn about the [policy assignment structure](./assignment-structure.md).
 - Understand how to [programmatically create policies](../how-to/programmatically-create.md).
 - Learn how to [get compliance data](../how-to/get-compliance-data.md).

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

@@ -11,7 +11,7 @@ Regulatory Compliance in Azure Policy provides built-in initiative definitions t
 **controls** and **compliance domains** based on responsibility (_Customer_, _Microsoft_, _Shared_).
 For Microsoft-responsible controls, we provide additional details of our audit results based on
 third-party attestation and our implementation details to achieve that compliance.
-Microsoft-responsible controls are of `policyType` [static](./definition-structure.md#policy-type).
+Microsoft-responsible controls are of `policyType` [static](./definition-structure-basics.md#policy-type).
 
 > [!NOTE]
 > Regulatory Compliance is a Preview feature. For updated built-ins, the initiatives
@@ -60,7 +60,7 @@ compliance** tab provides a granular view of each resource that's evaluated by a
 the currently viewed **control**.
 
 > [!NOTE]
-> An evaluation type of **Microsoft managed** is for a [static](./definition-structure.md#policy-type) policy definition `policyType`.
+> An evaluation type of **Microsoft managed** is for a [static](./definition-structure-basics.md#policy-type) policy definition `policyType`.
 
 :::image type="content" source="../media/regulatory-compliance/regulatory-compliance-policies.png" alt-text="Screenshot of the Regulatory Compliance details for the Boundary Protection control of the NIST SP 800-53 R4 built-in definition.":::