fixing the links for powershell and az module

Author: microsoftshawarma

articles/trusted-signing/how-to-sign-ci-policy.md

@@ -17,8 +17,8 @@ To sign new CI policies with the service first install several prerequisites.
 Prerequisites: 
 * A Trusted Signing account, Identity Validation, and Certificate Profile.
 * Ensure there are proper individual or group role assignments for signing (“Trusted Signing Certificate Profile Signer” role).
-* [Azure PowerShell on Windows](https://learn.microsoft.com/en-us/powershell/azure/install-azps-windows?view=azps-9.7.1&tabs=powershell&pivots=windows-msi) installed 
-* [Az.CodeSigning](https://learn.microsoft.com/en-us/powershell/module/az.codesigning/?view=azps-11.4.0) module downloaded
+* [Azure PowerShell on Windows](https://learn.microsoft.com/powershell/azure/install-azps-windows) installed 
+* [Az.CodeSigning](https://learn.microsoft.com/powershell/module/az.codesigning/) module downloaded
 
 Overview of steps:
 1. ⁠Unzip the Az.CodeSigning module to a folder
@@ -32,7 +32,7 @@ Endpoint "https://scus.codesigning.azure.net/"
 CodeSigningAccountName "youracsaccount" 
 CertificateProfileName "youracscertprofile" 
 ```
-5. [Get the root certificate](https://learn.microsoft.com/en-us/powershell/module/az.codesigning/get-azcodesigningrootcert?view=azps-11.4.0) to be added to the trust store
+5. [Get the root certificate](https://learn.microsoft.com/en-us/powershell/module/az.codesigning/get-azcodesigningrootcert) to be added to the trust store
 ```
 Get-AzCodeSigningRootCert -AccountName TestAccount -ProfileName TestCertProfile -EndpointUrl https://xxx.codesigning.azure.net/ -Destination c:\temp\root.cer
 ```
@@ -63,6 +63,6 @@ Invoke-AzCodeSigningCIPolicySigning -MetadataFilePath C:\temp\metadata.sample.sc
 ## Creating and Deploying a CI Policy
 
 For steps on creating and deploying your CI policy refer to:
-* [Use signed policies to protect Windows Defender Application Control against tampering](https://learn.microsoft.com/en-us/windows/security/application-security/application-control/windows-defender-application-control/deployment/use-signed-policies-to-protect-wdac-against-tampering)
-* [Windows Defender Application Control design guide](https://learn.microsoft.com/en-us/windows/security/application-security/application-control/windows-defender-application-control/design/wdac-design-guide)
+* [Use signed policies to protect Windows Defender Application Control against tampering](https://learn.microsoft.com/windows/security/application-security/application-control/windows-defender-application-control/deployment/use-signed-policies-to-protect-wdac-against-tampering)
+* [Windows Defender Application Control design guide](https://learn.microsoft.com/windows/security/application-security/application-control/windows-defender-application-control/design/wdac-design-guide)
 

articles/trusted-signing/how-to-signing-integrations.md

@@ -120,6 +120,6 @@ This section explains how to set up other not [SignTool](#set-up-signtool-with-t
 
 * PowerShell for Authenticode – To use PowerShell for Trusted Signing, visit [PowerShell Gallery | Trusted Signing 0.3.8](https://www.powershellgallery.com/packages/TrustedSigning/0.3.8) to install the PowerShell module. 
 
-* Azure PowerShell: App Control for Business CI Policy – To use Trusted Signing for CI policy signing follow the instructions at [Signing a New CI policy](./how-to-sign-ci-policy.md) and visit the [Az.CodeSigning PowerShell Module](https://learn.microsoft.com/en-us/powershell/module/az.codesigning/?view=azps-11.4.0).
+* Azure PowerShell: App Control for Business CI Policy – To use Trusted Signing for CI policy signing follow the instructions at [Signing a New CI policy](./how-to-sign-ci-policy.md) and visit the [Az.CodeSigning PowerShell Module](https://learn.microsoft.com/en-us/powershell/azure/install-azps-windows).
 
 * Trusted Signing SDK – To create your own signing integration our [Trusted Signing SDK](https://www.nuget.org/packages/Azure.CodeSigning.Sdk) is publicly available.