[AzureAD] Update links for TechNet Gallery scripts to Azure samples

Author: iainfoulds

articles/active-directory/authentication/howto-mfa-nps-extension-errors.md

@@ -95,7 +95,7 @@ If your users are [Having trouble with two-step verification](../user-help/multi
 
 ### Health check script
 
-The [Azure MFA NPS Extension health check script](https://gallery.technet.microsoft.com/Azure-MFA-NPS-Extension-648de6bb) is available on the TechNet Gallery to perform a basic health check when troubleshooting the NPS extension. Run the script and choose option 3.
+The [Azure MFA NPS Extension health check script](https://docs.microsoft.com/samples/azure-samples/azure-mfa-nps-extension-health-check/azure-mfa-nps-extension-health-check/) performs a basic health check when troubleshooting the NPS extension. Run the script and choose option 3.
 
 ### Contact Microsoft support
 

articles/active-directory/authentication/howto-mfa-nps-extension.md

@@ -26,7 +26,7 @@ When using the NPS extension for Azure MFA, the authentication flow includes the
 1. **NAS/VPN Server** receives requests from VPN clients and converts them into RADIUS requests to NPS servers. 
 2. **NPS Server** connects to Active Directory to perform the primary authentication for the RADIUS requests and, upon success, passes the request to any installed extensions.  
 3. **NPS Extension** triggers a request to Azure MFA for the secondary authentication. Once the extension receives the response, and if the MFA challenge succeeds, it completes the authentication request by providing the NPS server with security tokens that include an MFA claim, issued by Azure STS.  
-4. **Azure MFA** communicates with Azure Active Directory to retrieve the user’s details and performs the secondary authentication using a verification method configured to the user.
+4. **Azure MFA** communicates with Azure Active Directory to retrieve the user's details and performs the secondary authentication using a verification method configured to the user.
 
 The following diagram illustrates this high-level authentication request flow: 
 
@@ -165,7 +165,7 @@ The installer creates a PowerShell script in this location: `C:\Program Files\Mi
 - Create a self-signed certificate.
 - Associate the public key of the certificate to the service principal on Azure AD.
 - Store the cert in the local machine cert store.
-- Grant access to the certificate’s private key to Network User.
+- Grant access to the certificate's private key to Network User.
 - Restart the NPS.
 
 Unless you want to use your own certificates (instead of the self-signed certificates that the PowerShell script generates), run the PowerShell Script to complete the installation. If you install the extension on multiple servers, each one should have its own certificate.
@@ -247,9 +247,9 @@ You can choose to create this key and set it to FALSE while your users are onboa
 
 ### NPS extension health check script
 
-The following script is available on the TechNet Gallery to perform basic health check steps when troubleshooting the NPS extension.
+The following script is available to perform basic health check steps when troubleshooting the NPS extension.
 
-[MFA_NPS_Troubleshooter.ps1](https://gallery.technet.microsoft.com/Azure-MFA-NPS-Extension-648de6bb)
+[MFA_NPS_Troubleshooter.ps1](https://docs.microsoft.com/samples/azure-samples/azure-mfa-nps-extension-health-check/azure-mfa-nps-extension-health-check/)
 
 ---