Merge pull request #263226 from KrishnaG-MSFT/patch-368

(AzureCXP) MicrosoftDocs/azure-docs#118861

Author: prmerger-automator[bot]

articles/governance/machine-configuration/migrate-from-azure-automation.md

@@ -292,7 +292,7 @@ configuration to a MOF file and create a machine configuration package.
 
 Some modules might have compatibility issues with machine configuration. The most common
 problems are related to .NET framework vs .NET core. Detailed technical information is available on
-the page, [Differences between Windows PowerShell 5.1 and PowerShell 7.x][https://learn.microsoft.com/powershell/scripting/whats-new/differences-from-windows-powershell?view=powershell-7.4].
+the page, [Differences between Windows PowerShell 5.1 and PowerShell 7.x][07].
 
 One option to resolve compatibility issues is to run commands in Windows PowerShell from within a
 module that's imported in PowerShell 7, by running `powershell.exe`. You can review a sample module
@@ -394,7 +394,7 @@ configuration stored in Azure Automation by making a REST request to the service
 [04]: /powershell/gallery/how-to/working-with-local-psrepositories
 [05]: ./how-to-create-package.md
 [06]: ./how-to-create-package.md#author-a-configuration
-[07]: /powershell/gallery/how-to/working-with-local-psrepositories
+[07]: https://learn.microsoft.com/powershell/scripting/whats-new/differences-from-windows-powershell?view=powershell-7.4
 [08]: https://github.com/Azure/azure-policy/blob/bbfc60104c2c5b7fa6dd5b784b5d4713ddd55218/samples/GuestConfiguration/package-samples/resource-modules/WindowsDscConfiguration/DscResources/WindowsDscConfiguration/WindowsDscConfiguration.psm1#L97
 [09]: ./dsc-in-machine-configuration.md#special-requirements-for-get
 [10]: ../../azure-resource-manager/management/overview.md#terminology