Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into monitoringDash

Author: siddomala

articles/azure-signalr/signalr-howto-use.md

@@ -152,7 +152,7 @@ You can increase this value to avoid client disconnect.
 
 - Default value: All transports are enabled.
 - This option defines a function to customize the transports that clients can use to send HTTP requests.
-- Use this options instead of [`HttpConnectionDispatcherOptions.Transports`](https://learn.microsoft.com/aspnet/core/signalr/configuration?&tabs=dotnet#advanced-http-configuration-options) to configure transports. 
+- Use this options instead of [`HttpConnectionDispatcherOptions.Transports`](/aspnet/core/signalr/configuration?&tabs=dotnet#advanced-http-configuration-options) to configure transports. 
 
 ### Sample
 

articles/azure-vmware/extended-security-updates-windows-sql-server.md

@@ -22,7 +22,7 @@ For SQL Server environments running in a VM in Azure VMware Solution, you can us
 
 First you'll need to Arc-enable VMware vShpere for Azure VMware Solution and have the Azure Extension for SQL Server installed onto the VM. The steps are: 
 
-1.	To Arc-enable the VMware vSphere in Azure VMware Solution, see [Deploy Arc-enabled VMware vSphere for Azure VMware Solution private cloud](https://learn.microsoft.com/azure/azure-vmware/deploy-arc-for-azure-vmware-solution?tabs=windows).  
+1.	To Arc-enable the VMware vSphere in Azure VMware Solution, see [Deploy Arc-enabled VMware vSphere for Azure VMware Solution private cloud](deploy-arc-for-azure-vmware-solution.md?tabs=windows).  
 
 2.	Enable guest management for the individual VMs running SQL Server and make sure the Azure Extension for SQL Server is installed. To validate the extension is installed see the section *View ESU subscription status*
 
@@ -35,7 +35,7 @@ To find the SQL Server Configuration from the Azure portal:
 
 1. In the Azure VMware Solution portal, go to **vCenter Server Inventory** and **Virtual Machines** clicking through one of the Arc-enabled VMs. Here you see the Machine-Azure Arc (AVS) page.
 2. In the left pane, expand Operations and you should see the SQL Server Configuration
-3. You should then follow the steps discussed in the section: [Subscribe to Extended Security Updates enabled by Azure Arc](https://learn.microsoft.com/sql/sql-server/end-of-support/sql-server-extended-security-updates?#subscribe-to-extended-security-updates-enabled-by-azure-arc), which also provides syntax to configure via Azure PowerShell or Azure CLI.
+3. You should then follow the steps discussed in the section: [Subscribe to Extended Security Updates enabled by Azure Arc](/sql/sql-server/end-of-support/sql-server-extended-security-updates?#subscribe-to-extended-security-updates-enabled-by-azure-arc), which also provides syntax to configure via Azure PowerShell or Azure CLI.
 
 #### View ESU subscription status
 For machines running SQL Server where guest management is enabled the Azure Extension for SQL Server should be registered. You can validate the extension is installed through the Azure portal or through Azure Resource Graph queries. 
@@ -45,7 +45,7 @@ For machines running SQL Server where guest management is enabled the Azure Exte
     2. As part of the **Overview** section of the left pane, there's a **Properties/Extensions** view that will list the WindowsAgent.SqlServer (Microsoft.HybridCompute/machines/extensions) if installed. Alternatively, you can expand **Settings** from the left pane and choose **Extensions** which should display the WindowsAgent.SqlServer name and type if configured.
 
 -	Through Azure Resource Graph queries
-    - You can use the following query [VM ESU subscription status](https://learn.microsoft.com/sql/sql-server/end-of-support/sql-server-extended-security-updates?#view-esu-subscriptions)  as an example to show you can view eligible SQL Server ESU instances and their ESU subscription status. 
+    - You can use the following query [VM ESU subscription status](/sql/sql-server/end-of-support/sql-server-extended-security-updates?#view-esu-subscriptions)  as an example to show you can view eligible SQL Server ESU instances and their ESU subscription status. 
 
 ### Windows Server 
 To enable ESUs for Windows Server environments running in VMs in Azure VMware Solution contact [Microsoft Support] for configuration assistance. 
@@ -61,11 +61,10 @@ When you contact support, the ticket should be raised under the category of Azur
 
 
 ## Related content
-- [What are Extended Security Updates - SQL Server](https://learn.microsoft.com/sql/sql-server/end-of-support/sql-server-extended-security-updates)
-- [Extend Security Updates for Windows Server overview](https://learn.microsoft.com/windows-server/get-started/extended-security-updates-overview)
+- [What are Extended Security Updates - SQL Server](/sql/sql-server/end-of-support/sql-server-extended-security-updates)
+- [Extend Security Updates for Windows Server overview](/windows-server/get-started/extended-security-updates-overview)
 - [Plan your Windows Server and SQL Server end of support](https://www.microsoft.com/windows-server/extended-security-updates)
 
 
 [Microsoft Support]: https://ms.portal.azure.com/#view/Microsoft_Azure_Support/NewSupportRequestV3Blade/assetId/%2Fsubscriptions%2F5a79c43b-b03d-4610-bc59-627d8a6744d1%2FresourceGroups%2FABM_CSS_Lab_Enviroment%2Fproviders%2FMicrosoft.AVS%2FprivateClouds%2FBareMetal_CSS_Lab/callerWorkflowId/a7ecc9f7-8578-4820-abdf-1db09a2bdb47/callerName/Microsoft_Azure_Support%2FAurora.ReactView/subscriptionId/5a79c43b-b03d-4610-bc59-627d8a6744d1/productId/e7b24d57-0431-7d60-a4bf-e28adc11d23e/summary/Issue/topicId/9e078285-e10f-0365-31e3-6b31e5871794/issueType/technical
-[Extended Security updates for SQL Server and Windows Server]: https://www.microsoft.com/en-us/windows-server/extended-security-updates
-
+[Extended Security updates for SQL Server and Windows Server]: https://www.microsoft.com/windows-server/extended-security-updates

articles/communication-services/how-tos/call-automation/teams-interop-call-automation.md

@@ -23,7 +23,7 @@ In this quickstart, we use the Azure Communication Services Call Automation APIs
 ## Prerequisites
 
 - An Azure account with an active subscription.
-- A Microsoft Teams phone license and a Teams tenant with administrative privileges. Teams phone license is a must in order to use this feature, learn more about Teams licenses [here](https://www.microsoft.com/microsoft-teams/compare-microsoft-teams-bundle-options). The Microsoft Teams user must also be `voice` enabled, see [setting-up-your-phone-system](https://learn.microsoft.com/microsoftteams/setting-up-your-phone-system).  Administrative privileges are required to authorize Communication Services resource to call Teams users, explained later in Step 1.  
+- A Microsoft Teams phone license and a Teams tenant with administrative privileges. Teams phone license is a must in order to use this feature, learn more about Teams licenses [here](https://www.microsoft.com/microsoft-teams/compare-microsoft-teams-bundle-options). The Microsoft Teams user must also be `voice` enabled, see [setting-up-your-phone-system](/microsoftteams/setting-up-your-phone-system).  Administrative privileges are required to authorize Communication Services resource to call Teams users, explained later in Step 1.  
 - A deployed [Communication Service resource](../../quickstarts/create-communication-resource.md) and valid connection string found by selecting Keys in left side menu on Azure portal.
 - [Acquire a PSTN phone number from the Communication Service resource](../../quickstarts/telephony/get-phone-number.md). Note the phone number you acquired to use in this quickstart. 
 - An Azure Event Grid subscription to receive the `IncomingCall` event.

articles/communication-services/quickstarts/call-automation/includes/quickstart-make-an-outbound-call-using-callautomation-csharp.md

@@ -19,7 +19,7 @@ ms.custom: mode-other
 - Create and host an Azure Dev Tunnel. Instructions [here](/azure/developer/dev-tunnels/get-started).
 - Create and connect [a Multi-service Azure AI services to your Azure Communication Services resource](../../../concepts/call-automation/azure-communication-services-azure-cognitive-services-integration.md).
 - Create a [custom subdomain](../../../../ai-services/cognitive-services-custom-subdomains.md) for your Azure AI services resource. 
-- (Optional) A Microsoft Teams user with a phone license that is `voice` enabled. Teams phone license is required to add Teams users to the call. Learn more about Teams licenses [here](https://www.microsoft.com/microsoft-teams/compare-microsoft-teams-bundle-options).  Learn about enabling phone system with `voice` [here](https://learn.microsoft.com/microsoftteams/setting-up-your-phone-system).
+- (Optional) A Microsoft Teams user with a phone license that is `voice` enabled. Teams phone license is required to add Teams users to the call. Learn more about Teams licenses [here](https://www.microsoft.com/microsoft-teams/compare-microsoft-teams-bundle-options).  Learn about enabling phone system with `voice` [here](/microsoftteams/setting-up-your-phone-system).
 
 ## Sample code
 

articles/search/search-howto-index-azure-data-lake-storage.md

@@ -5,7 +5,6 @@ description: Set up an Azure Data Lake Storage (ADLS) Gen2 indexer to automate i
 author: gmndrg
 ms.author: gimondra
 manager: nitinme
-
 ms.service: cognitive-search
 ms.custom:
   - ignite-2023
@@ -308,7 +307,7 @@ PUT /indexers/[indexer name]?api-version=2023-11-01
 
 ## Limitations
 
-1. Unlike blob indexers, ADLS Gen2 indexers cannot utilize container level SAS tokens for enumerating and indexing content from a storage account. This is because the indexer makes a check to determine if the storage account has hierarchical namespaces enabled by calling the [Filesystem - Get properties API](https://learn.microsoft.com/rest/api/storageservices/datalakestoragegen2/filesystem/get-properties). For storage accounts where hierarchical namespaces are not enabled, customers are instead recommended to utilize [blob indexers](search-howto-indexing-azure-blob-storage.md) to ensure performant enumeration of blobs.
+1. Unlike blob indexers, ADLS Gen2 indexers cannot utilize container level SAS tokens for enumerating and indexing content from a storage account. This is because the indexer makes a check to determine if the storage account has hierarchical namespaces enabled by calling the [Filesystem - Get properties API](/rest/api/storageservices/datalakestoragegen2/filesystem/get-properties). For storage accounts where hierarchical namespaces are not enabled, customers are instead recommended to utilize [blob indexers](search-howto-indexing-azure-blob-storage.md) to ensure performant enumeration of blobs.
 
 2. If the property `metadata_storage_path` is mapped to be the index key field, blobs are not guaranteed to get reindexed upon a directory rename. If you desire to reindex the blobs that are part of the renamed directories, update the `LastModified` timestamps for all of them.
 

articles/site-recovery/tutorial-shared-disk.md

@@ -36,7 +36,7 @@ If you don't have an Azure subscription, create a [free account](https://azure.m
 **Before you start, ensure you have:**
 
 - A recovery services vault. If you don't have one, [create recovery services vault](./azure-to-azure-tutorial-enable-replication.md#create-a-recovery-services-vault). 
-- A virtual machine as a part of the [Windows Server Failover Cluster](https://learn.microsoft.com/sql/sql-server/failover-clusters/windows/windows-server-failover-clustering-wsfc-with-sql-server?view=sql-server-ver16). 
+- A virtual machine as a part of the [Windows Server Failover Cluster](/sql/sql-server/failover-clusters/windows/windows-server-failover-clustering-wsfc-with-sql-server?view=sql-server-ver16). 
 
 
 ## Enable replication for shared disks