Cosmos DB | Policy | Fix link warnings

Author: Patrick El-Azem

articles/cosmos-db/policy.md

@@ -11,17 +11,17 @@ ms.date: 05/20/2020
 
 # Use Azure Policy to implement governance and controls for Azure Cosmos DB resources
 
-[Azure Policy](../governance/policy/overview) helps to enforce organizational governance standards, assess resource compliance, and implement automatic remediation. Common use cases include security, cost management, and configuration consistency.
+[Azure Policy](../governance/policy/overview.md) helps to enforce organizational governance standards, assess resource compliance, and implement automatic remediation. Common use cases include security, cost management, and configuration consistency.
 
-Azure Policy provides built-in policy definitions. You can create custom policy definitions for scenarios that are not addressed by the built-in policy definitions. See the [Azure Policy documentation](../governance/policy/overview) for more details.
+Azure Policy provides built-in policy definitions. You can create custom policy definitions for scenarios that are not addressed by the built-in policy definitions. See the [Azure Policy documentation](../governance/policy/overview.md) for more details.
 
 ## Assign a built-in policy definition
 
 Policy definitions describe resource compliance conditions and the effect to take if a condition is met. Policy _assignments_ are created from policy _definitions_. You can use built-in or custom policy definitions for your Azure Cosmos DB resources. Policy assignments are scoped to an Azure management group, an Azure subscription, or a resource group and they are applied to the resources within the selected scope. Optionally, you can exclude specific resources from the scope.
 
-You can create policy assignments with the [Azure portal](../governance/policy/assign-policy-portal), [Azure PowerShell](../governance/policy/assign-policy-powershell), [Azure CLI](../governance/policy/assign-policy-azurecli), or [ARM template](../governance/policy/assign-policy-template).
+You can create policy assignments with the [Azure portal](../governance/policy/assign-policy-portal.md), [Azure PowerShell](../governance/policy/assign-policy-powershell.md), [Azure CLI](../governance/policy/assign-policy-azurecli.md), or [ARM template](../governance/policy/assign-policy-template.md).
 
-To create a policy assignment from a built-in policy definition for Azure Cosmos DB, use the steps in [create a policy assignment with the Azure portal](../governance/policy/assign-policy-portal) article.
+To create a policy assignment from a built-in policy definition for Azure Cosmos DB, use the steps in [create a policy assignment with the Azure portal](../governance/policy/assign-policy-portal.md) article.
 
 At the step to select a policy definition, enter `Cosmos DB` in the Search field to filter the list of available built-in policy definitions. Select one of the available built-in policy definitions, and then choose **Select** to continue creating the policy assignment.
 
@@ -32,11 +32,11 @@ At the step to select a policy definition, enter `Cosmos DB` in the Search field
 
 ## Create a custom policy definition
 
-For specific scenarios that are not addressed by built-in policies, you can create [a custom policy definition](../governance/policy/tutorials/create-custom-policy-definition). Later you create a Policy _assignment_ from your custom policy _definition_.
+For specific scenarios that are not addressed by built-in policies, you can create [a custom policy definition](../governance/policy/tutorials/create-custom-policy-definition.md). Later you create a Policy _assignment_ from your custom policy _definition_.
 
 ### Property types and property aliases in policy rules
 
-Use the [custom policy definition steps](../governance/policy/tutorials/create-custom-policy-definition) to identify the resource properties and property aliases, which are required to create policy rules.
+Use the [custom policy definition steps](../governance/policy/tutorials/create-custom-policy-definition.md) to identify the resource properties and property aliases, which are required to create policy rules.
 
 To identify Azure Cosmos DB specific property aliases, use the namespace `Microsoft.DocumentDB` with one of the methods shown in the custom policy definition steps article.
 
@@ -73,7 +73,7 @@ These commands output the list of property alias names for Azure Cosmos DB prope
 ]
 ```
 
-You can use any of these property alias names in the [custom policy definition rules](../governance/policy/tutorials/create-custom-policy-definition#policy-rule).
+You can use any of these property alias names in the [custom policy definition rules](../governance/policy/tutorials/create-custom-policy-definition.md#policy-rule).
 
 The following is an example policy definition that checks if an Azure Cosmos DB SQL database's provisioned throughput is greater than a maximum allowed limit of 400 RU/s. A custom policy definition includes two rules: one to check for the specific type of property alias, and the second one for the specific property of the type. Both rules use the alias names.
 
@@ -100,7 +100,7 @@ Custom policy definitions can be used to create policy assignments just like the
 
 After the policy assignments are created, Azure Policy evaluates the resources in the assignment's scope. Each resource's _compliance_ with the policy is assessed. The _effect_ specified in the policy is then applied to non-compliant resources.
 
-You can review the compliance results and remediation details in the [Azure portal](../governance/policy/how-to/get-compliance-data#portal) or via the [Azure CLI](../governance/policy/how-to/get-compliance-data#command-line) or the [Azure Monitor logs](../governance/policy/how-to/get-compliance-data#azure-monitor-logs).
+You can review the compliance results and remediation details in the [Azure portal](../governance/policy/how-to/get-compliance-data.md#portal) or via the [Azure CLI](../governance/policy/how-to/get-compliance-data.md#command-line) or the [Azure Monitor logs](../governance/policy/how-to/get-compliance-data.md#azure-monitor-logs).
 
 The following screenshot shows two example policy assignments. One assignment is based on a built-in policy definition, which checks that the Azure Cosmos DB resources are deployed only to the allowed Azure regions. The other assignment is based on a custom policy definition. This assignment checks that the provisioned throughput on Azure Cosmos DB resources does not exceed a specified maximum limit.
 
@@ -113,10 +113,10 @@ The screenshot shows the following compliance evaluation results:
 
 :::image type="content" source="./media/policy/compliance.png" alt-text="Search for Cosmos DB built-in policy definitions":::
 
-To remediate the non-compliant resources, see the [remediated with Azure Policy](../governance/policy/how-to/remediate-resources) article.
+To remediate the non-compliant resources, see the [remediated with Azure Policy](../governance/policy/how-to/remediate-resources.md) article.
 
 ## Next Steps
 
 - [Review sample custom policy definitions for Azure Cosmos DB](https://github.com/Azure/azure-policy/tree/master/samples/CosmosDB)
-- [Create a policy assignment in the Azure portal](../governance/policy/assign-policy-portal)
-- [Review Azure Policy built-in policy definitions for Azure Cosmos DB](./policy-samples)
+- [Create a policy assignment in the Azure portal](../governance/policy/assign-policy-portal.md)
+- [Review Azure Policy built-in policy definitions for Azure Cosmos DB](./policy-samples.md)