Merge pull request #297080 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Albertyang0

articles/azure-resource-manager/bicep/add-template-to-azure-pipelines.md

@@ -81,7 +81,6 @@ You can use an Azure Resource Group deployment task or an Azure CLI task to depl
     - task: AzureResourceManagerTemplateDeployment@3
       inputs:
         deploymentScope: 'Resource Group'
-        azureSubscription: '${{ parameters.azureServiceConnection }}'
         action: 'Create Or Update Resource Group'
         resourceGroupName: '$(resourceGroupName)'
         location: '$(location)'
@@ -91,6 +90,7 @@ You can use an Azure Resource Group deployment task or an Azure CLI task to depl
         overrideParameters: '-storageAccountType Standard_LRS'
         deploymentMode: 'Incremental'
         deploymentName: 'DeployPipelineTemplate'
+        connectedServiceName: '${{ parameters.azureServiceConnection }}'
     ```
 
 1. Update the values of `azureServiceConnection` and `location`.

articles/azure-resource-manager/management/tag-resources.md

@@ -74,7 +74,7 @@ The following limitations apply to tags:
 
 * Classic resources such as Cloud Services don't support tags.
 
-* Azure IP Groups and Azure Firewall policies don't support PATCH operations. Therefore, PATCH API method operations can't update tags through the Azure portal. Instead, use the update commands for those resources. For example, you can update tags for an IP group with the [`az network ip-group update`](/cli/azure/network/ip-group?view=azure-cli-latest) command.
+* Azure IP Groups and Azure Firewall policies don't support PATCH operations. Therefore, PATCH API method operations can't update tags through the Azure portal. Instead, use the update commands for those resources. For example, you can update tags for an IP group with the [`az network ip-group update`](/cli/azure/network/ip-group) command.
 
 * Tag names can't contain these characters: `<`, `>`, `%`, `&`, `\`, `?`, `/`
 
@@ -88,7 +88,8 @@ The following limitations apply to tags:
    > * The following Azure resources only support 15 tags:
    >     * Azure Automation
    >     * Azure Content Delivery Network
-   >     * Azure DNS (Zone and A records)
+   >     * Azure Public DNS (Zone and A records)
+   >     * Azure Private DNS (Zone and A records)
    >     * Azure Log Analytics saved search
 
 ## Next steps
@@ -100,4 +101,4 @@ For more information on how to work with tags, see:
 * [Azure PowerShell](tag-resources-powershell.md)
 * [Python](tag-resources-python.md)
 * [ARM templates](tag-resources-templates.md)
-* [Bicep](tag-resources-bicep.md)
+* [Bicep](tag-resources-bicep.md)

articles/cost-management-billing/scope-level/overview-azure-hybrid-benefit-scope.md

@@ -1,13 +1,14 @@
 ---
 title: What is centrally managed Azure Hybrid Benefit for SQL Server?
 description: Azure Hybrid Benefit an Azure discount that lets you allocate your on-premises core-based Windows Server and SQL Server licenses with active Software Assurance (or subscription) to Azure.
-author: bandersmsft
-ms.author: banders
+author: pri-mittal
+ms.author: primittal
 ms.date: 11/21/2024
 ms.topic: overview
 ms.service: cost-management-billing
 ms.subservice: ahb
-ms.reviewer: chrisrin
+ms.reviewer: primittal
+ms.custom: cpx
 ---
 
 # What is centrally managed Azure Hybrid Benefit for SQL Server?
@@ -132,4 +133,4 @@ We recommend that you establish a proactive rhythm when centrally managing Azure
 
 - Follow the [Manage and optimize Azure Hybrid Benefit for SQL Server](tutorial-azure-hybrid-benefits-sql.md) tutorial.
 - Learn about how to [transition to centrally managed Azure Hybrid Benefit](transition-existing.md).
-- Review the [Centrally managed Azure Hybrid Benefit FAQ](faq-azure-hybrid-benefit-scope.yml).
+- Review the [Centrally managed Azure Hybrid Benefit FAQ](faq-azure-hybrid-benefit-scope.yml).