apply relative link, set date

Author: GitHubber17

articles/virtual-network/virtual-network-encryption-faq.yml

@@ -3,6 +3,7 @@ metadata:
   title: Virtual Network encryption frequently asked questions
   description: Answers to common questions about using Azure Virtual Network encryption.
   ms.topic: faq
+  ms.date: 05/13/2024
 
 title: Frequently asked questions for Azure Virtual Network encryption
 summary: |

articles/vpn-gateway/site-to-site-certificate-authentication-gateway-portal.md

@@ -42,7 +42,7 @@ This configuration requires a managed identity. For more information about manag
 
 ## <a name="enable"></a>Enable VPN Gateway for Key Vault and Managed Identity
 
-In this section, you enable the gateway for Azure Key Vault and the managed identity you created earlier. For more information about Azure Key Vault, see [About Azure Key Vault](https://learn.microsoft.com/azure/key-vault/general/overview).
+In this section, you enable the gateway for Azure Key Vault and the managed identity you created earlier. For more information about Azure Key Vault, see [About Azure Key Vault](/azure/key-vault/general/overview).
 
 1. In the portal, go to your virtual network gateway (VPN gateway).
 1. Go to **Settings -> Configuration**. On the Configuration page, specify the following authentication settings:
@@ -215,7 +215,7 @@ Export the public key data for the **root certificate**. Exported files must be
 
 ## Create a key vault
 
-This configuration requires Azure Key Vault. The following steps create a key vault. You add your certificate and Managed Identity to your key vault later. For more comprehensive steps, see [Quickstart - Create a key vault using the Azure portal](https://learn.microsoft.com/azure/key-vault/general/quick-create-portal).
+This configuration requires Azure Key Vault. The following steps create a key vault. You add your certificate and Managed Identity to your key vault later. For more comprehensive steps, see [Quickstart - Create a key vault using the Azure portal](/azure/key-vault/general/quick-create-portal).
 
 1. In the Azure portal, search for **Key Vaults**. On the **Key vaults** page, select **+Create**.
 1. On the **Create a key vault** page, fill out the required information. The resource group doesn't have to be the same as the resource group that you used for your VPN gateway.

articles/vpn-gateway/vpn-gateway-classic-resource-manager-migration.md

@@ -26,7 +26,7 @@ Once the VNet migration is completed, Azure will attempt to complete the remaind
 The Resource Manager model is different from the classic model and is composed of virtual network gateways, local network gateways and connection resources. These represent the VPN gateway itself, the local-site representing on premises address space and connectivity between the two respectively. Once migration is completed, your gateways won't be available in the classic model and all management operations on virtual network gateways, local network gateways, and connection objects must be performed using the Resource Manager model.
 
 ## Locating a classic VPN gateway 
-To locate a classic VPN gateway via PowerShell, you will need to install the Azure PowerShell Service Management module. Start here: [Installing the Azure PowerShell Service Management module](https://learn.microsoft.com/powershell/azure/servicemanagement/install-azure-ps). To view classic resources, you will need co-admin or owner permissions. You can't use Az cmdlets to access classic resources. 
+To locate a classic VPN gateway via PowerShell, you will need to install the Azure PowerShell Service Management module. Start here: [Installing the Azure PowerShell Service Management module](/powershell/azure/servicemanagement/install-azure-ps). To view classic resources, you will need co-admin or owner permissions. You can't use Az cmdlets to access classic resources. 
 
 
 To locate a classic VPN gateway via Azure portal, open the portal and search for "Virtual network(classic)". Select your classic virtual network and navigate to the gateway blade to find your classic virtual network gateway. 

includes/vpn-gateway-vwan-openvpn-conditional.md

@@ -8,7 +8,7 @@ ms.topic: include
  # this file is used for both virtual wan and vpn gateway. When modifying, make sure that your changes work for both environments.
 ---
 
-Conditional Access allows for fine-grained access control on a per-application basis. In order to use Conditional Access, you should have Microsoft Entra ID P1 or P2 or greater licensing applied to the users that will be subject to the Conditional Access rules. For more information, see [What is Conditional Access](https://learn.microsoft.com/entra/identity/conditional-access/overview)?
+Conditional Access allows for fine-grained access control on a per-application basis. In order to use Conditional Access, you should have Microsoft Entra ID P1 or P2 or greater licensing applied to the users that will be subject to the Conditional Access rules. For more information, see [What is Conditional Access](/entra/identity/conditional-access/overview)?
 
 1. Go to the **Microsoft Entra ID - Enterprise applications - All applications** page and click **Azure VPN**.
 

includes/vpn-gateway-vwan-openvpn-enable-mfa-overview.md

@@ -11,4 +11,4 @@ ms.topic: include
 If you want users to be prompted for a second factor of authentication before granting access, you can configure Microsoft Entra multifactor authentication (MFA). You can configure MFA on a per user basis, or you can leverage MFA via [Conditional Access](/azure/active-directory/conditional-access/overview).
 
 * MFA per user can be enabled at no-additional cost. When you enable MFA per user, the user is prompted for second factor authentication against all applications tied to the Microsoft Entra tenant. See [Option 1](#peruser) for steps.
-* Conditional Access allows for finer-grained control over how a second factor should be promoted. It can allow assignment of MFA to only VPN, and exclude other applications tied to the Microsoft Entra tenant. See [Option 2](#conditional) for configuration steps. For more information about Conditional Access, see [What is Conditional Access](https://learn.microsoft.com/entra/identity/conditional-access/overview)?
+* Conditional Access allows for finer-grained control over how a second factor should be promoted. It can allow assignment of MFA to only VPN, and exclude other applications tied to the Microsoft Entra tenant. See [Option 2](#conditional) for configuration steps. For more information about Conditional Access, see [What is Conditional Access](/entra/identity/conditional-access/overview)?