Merge pull request #301572 from JustPies/jpvalidation-6-19

Bulk - Fix Validation issues

Author: prmerger-automator[bot]

articles/azure-compute-fleet/quickstart-create-azure-cli.md

@@ -80,7 +80,7 @@ export MY_SUBNET_ID="$(az network vnet subnet show \
 
 ## Set up the admin password
 
-Set up a password that meets the [password requirements for Azure VMs](https://learn.microsoft.com/azure/virtual-machines/windows/faq#what-are-the-password-requirements-when-creating-a-vm-).
+Set up a password that meets the [password requirements for Azure VMs](/azure/virtual-machines/windows/faq#what-are-the-password-requirements-when-creating-a-vm-).
 
 ```bash
 export ADMIN_PASSWORD="Azure compliant password"

articles/cost-management-billing/manage/ea-pricing-overview.md

@@ -45,7 +45,7 @@ Microsoft might drop the current Enterprise Agreement price for individual Azure
 
 Enterprise Agreement (EA) customers are billed in their designated billing currency as per the terms of their agreement. Therefore, foreign exchange (FX) rates do not apply and are not available for EA customers.
 
-As a result, the *cost in pricing currency* field is not included in EA usage report. For more information see, [Understand cost details field](https://learn.microsoft.com/azure/cost-management-billing/automate/understand-usage-details-fields#list-of-fields-and-descriptions) 
+As a result, the *cost in pricing currency* field is not included in EA usage report. For more information see, [Understand cost details field](/azure/cost-management-billing/automate/understand-usage-details-fields#list-of-fields-and-descriptions) 
 
 If Microsoft anticipates any pricing changes due to currency exchange rate fluctuations, customers are notified in advance before those changes take effect.
 

articles/migrate/best-practices-security.md

@@ -48,7 +48,7 @@ We recommend joining the appliance machine to the domain.
 
 - The Migrate appliance can be deployed on the supported version of Windows Servers either using a PowerShell installation script or OVA/VHD template.  
 
-- **Security baseline** - We recommend hardening the OS image of Migrate appliance using [security baselines](https://learn.microsoft.com/windows/security/operating-system-security/device-management/windows-security-configuration-framework/windows-security-baselines). Download the [security compliance toolkit](https://www.microsoft.com/en-us/download/details.aspx?id=55319) to apply security baselines on Migrate Appliance machine. Using the toolkit, administrators can compare their current GPOs with Microsoft-recommended GPO baselines or other baselines, edit them, store them in GPO backup file format, and apply them via a domain controller or inject them directly into testbed hosts to test their effects.  
+- **Security baseline** - We recommend hardening the OS image of Migrate appliance using [security baselines](/windows/security/operating-system-security/device-management/windows-security-configuration-framework/windows-security-baselines). Download the [security compliance toolkit](https://www.microsoft.com/en-us/download/details.aspx?id=55319) to apply security baselines on Migrate Appliance machine. Using the toolkit, administrators can compare their current GPOs with Microsoft-recommended GPO baselines or other baselines, edit them, store them in GPO backup file format, and apply them via a domain controller or inject them directly into testbed hosts to test their effects.  
 
 ## Credentials handling best practices
 

articles/planetary-computer/get-started-planetary-computer.md

@@ -110,7 +110,7 @@ Planetary Computer Pro supports [connecting collections to ESRI's ArcGIS Pro Ser
 ## Get help
 
 1. Review the [rest of the documentation](/azure/planetary-computer) for relevant articles
-2. [Check out Microsoft Q&A](https://learn.microsoft.com/answers/tags/133/azure) to ask a question or find answers from others
+2. [Check out Microsoft Q&A](/answers/tags/133/azure) to ask a question or find answers from others
 3. [File a Support Ticket](https://azure.microsoft.com/support/create-ticket)
 
 

articles/storage/elastic-san/elastic-san-troubleshoot.md

@@ -30,15 +30,15 @@ This article lists common issues related to Azure Elastic SAN. It also provides
 
 ***Unable to connect to your Elastic SAN via service endpoints***
 
-- [Enable](https://learn.microsoft.com/azure/storage/elastic-san/elastic-san-networking?tabs=azure-powershell#configure-public-network-access) Public Network Access on the SAN 
+- [Enable](/azure/storage/elastic-san/elastic-san-networking?tabs=azure-powershell#configure-public-network-access) Public Network Access on the SAN 
 ```powershell
 # Set the variable values.
 $RgName       = "<ResourceGroupName>"
 $EsanName     = "<ElasticSanName>"
 # Update the Elastic San.
 Update-AzElasticSan -Name $EsanName -ResourceGroupName $RgName -PublicNetworkAccess Enabled
 ```
-- [Configure](https://learn.microsoft.com/azure/storage/elastic-san/elastic-san-networking?tabs=azure-powershell#configure-an-azure-storage-service-endpoint) service endpoints on the volume group 
+- [Configure](/azure/storage/elastic-san/elastic-san-networking?tabs=azure-powershell#configure-an-azure-storage-service-endpoint) service endpoints on the volume group 
 ```powershell
 # Define some variables
 $RgName = "<ResourceGroupName>" 
@@ -54,7 +54,7 @@ $Vnet | Set-AzVirtualNetworkSubnetConfig -Name $SubnetName -AddressPrefix $Subne
 
 - Check your SAN size and configuration via portal (SAN homepage -> Configuration blade) and ensure that the I/O per second (IOPS) and throughput numbers can handle the requirements of the workload
 -  Check your VM throughput and IOPS limits and ensure that the VM can handle the workload requirements
-- Ensure that you're following the best practices outlined in this [document](https://learn.microsoft.com/azure/storage/elastic-san/elastic-san-best-practices). 
+- Ensure that you're following the best practices outlined in this [document](/azure/storage/elastic-san/elastic-san-best-practices). 
 
 
 ***Unable to establish connectivity from new nodes in a cluster***
@@ -73,8 +73,8 @@ $Vnet | Set-AzVirtualNetworkSubnetConfig -Name $SubnetName -AddressPrefix $Subne
 - Run the script on your VM. These values can also be entered during runtime of the script.
 
 ## Next steps
-- [Deploy an Elastic SAN](https://learn.microsoft.com/azure/storage/elastic-san/elastic-san-create)
-- [Connect to Windows](https://learn.microsoft.com/azure/storage/elastic-san/elastic-san-connect-windows)
-- [Connect to Linux](https://learn.microsoft.com/azure/storage/elastic-san/elastic-san-connect-linux)
-- [Connect to Azure VMware Solution](https://learn.microsoft.com/azure/azure-vmware/configure-azure-elastic-san?toc=/azure/storage/elastic-san/toc.json)
+- [Deploy an Elastic SAN](/azure/storage/elastic-san/elastic-san-create)
+- [Connect to Windows](/azure/storage/elastic-san/elastic-san-connect-windows)
+- [Connect to Linux](/azure/storage/elastic-san/elastic-san-connect-linux)
+- [Connect to Azure VMware Solution](/azure/azure-vmware/configure-azure-elastic-san?toc=/azure/storage/elastic-san/toc.json)