Merge pull request #188843 from v-rajagt/gwallace

Link fixed.

Author: PRMerger15

articles/governance/blueprints/samples/ism-protected/control-mapping.md

@@ -28,7 +28,7 @@ to support audit requirements** built-in policy initiative.
 > compliance in Azure Policy is only a partial view of your overall compliance status. The
 > associations between controls and Azure Policy definitions for this compliance blueprint sample
 > may change over time. To view the change history, see the
-> [GitHub Commit History](https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/governance/blueprints/samples/ism-protected/control-mapping.md).
+> [GitHub Commit History](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/samples/ism-protected/control-mapping.md).
 
 ## Location Constraints
 

articles/governance/blueprints/samples/iso27001-ase-sql-workload/control-mapping.md

@@ -26,7 +26,7 @@ specific VM Extensions to support audit requirements** built-in policy initiativ
 > compliance in Azure Policy is only a partial view of your overall compliance status. The
 > associations between controls and Azure Policy definitions for this compliance blueprint sample
 > may change over time. To view the change history, see the
-> [GitHub Commit History](https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/governance/blueprints/samples/iso27001-ase-sql-workload/control-mapping.md).
+> [GitHub Commit History](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/samples/iso27001-ase-sql-workload/control-mapping.md).
 
 ## A.6.1.2 Segregation of duties
 

articles/governance/blueprints/samples/iso27001-shared/control-mapping.md

@@ -28,7 +28,7 @@ requirements** built-in policy initiative.
 > compliance in Azure Policy is only a partial view of your overall compliance status. The
 > associations between controls and Azure Policy definitions for this compliance blueprint sample
 > may change over time. To view the change history, see the
-> [GitHub Commit History](https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/governance/blueprints/samples/iso27001-shared/control-mapping.md).
+> [GitHub Commit History](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/samples/iso27001-shared/control-mapping.md).
 
 ## A.6.1.2 Segregation of duties
 

articles/governance/blueprints/samples/media/control-mapping.md

@@ -27,7 +27,7 @@ directly to a specific control mapping. Many of the mapped controls are implemen
 > compliance in Azure Policy is only a partial view of your overall compliance status. The
 > associations between controls and Azure Policy definitions for this compliance blueprint sample
 > may change over time. To view the change history, see the
-> [GitHub Commit History](https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/governance/blueprints/samples/media/control-mapping.md).
+> [GitHub Commit History](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/samples/media/control-mapping.md).
 
 ## Access Control
 

articles/governance/blueprints/samples/pci-dss-3.2.1/control-mapping.md

@@ -27,7 +27,7 @@ v3.2.1:2018** built-in policy initiative.
 > compliance in Azure Policy is only a partial view of your overall compliance status. The
 > associations between controls and Azure Policy definitions for this compliance blueprint sample
 > may change over time. To view the change history, see the
-> [GitHub Commit History](https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/governance/blueprints/samples/pci-dss-3.2.1/control-mapping.md).
+> [GitHub Commit History](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/samples/pci-dss-3.2.1/control-mapping.md).
 
 ## 1.3.2 and 1.3.4 Boundary Protection
 

articles/governance/blueprints/samples/swift-2020/control-mapping.md

@@ -28,7 +28,7 @@ audit requirements** built-in policy initiative.
 > compliance in Azure Policy is only a partial view of your overall compliance status. The
 > associations between controls and Azure Policy definitions for this compliance blueprint sample
 > may change over time. To view the change history, see the
-> [GitHub Commit History](https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/governance/blueprints/samples/swift-2020/control-mapping.md).
+> [GitHub Commit History](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/samples/swift-2020/control-mapping.md).
 
 ## 1.2 and 5.1 Account Management
 

articles/governance/policy/how-to/guest-configuration-desired-state-configuration-extension-migration.md

@@ -94,11 +94,11 @@ before you can create a guest configuration package.
 #### Update deployment templates
 
 If your deployment templates include the DSC extension
-(see [examples](/virtual-machines/extensions/dsc-template.md)),
+(see [examples](/azure/virtual-machines/extensions/dsc-template)),
 there are two changes required.
 
 First, replace the DSC extension with the
-[extension for the guest configuration feature](/virtual-machines/extensions/guest-configuration.md).
+[extension for the guest configuration feature](/azure/virtual-machines/extensions/guest-configuration).
 
 Then, add a
 [guest configuration assignment](../concepts/guest-configuration-assignments.md)