Merge pull request #294297 from MicrosoftDocs/main

2/7/2025 PM Publish

Author: Taojunshen

.openpublishing.redirection.json

@@ -30,6 +30,46 @@
       "redirect_url": "/previous-versions/azure/partner-solutions/logzio/troubleshoot",
        "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/hdinsight-aks/index.yml",
+      "redirect_url": "/previous-versions/azure/hdinsight-aks",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/hdinsight-aks/flink/index.md",
+      "redirect_url": "/previous-versions/azure/hdinsight-aks/flink/flink-overview",
+      "redirect_document_id": false
+    },
+    {
+        "source_path_from_root": "/articles/hdinsight-aks/prerequisites-subscription.md",
+        "redirect_url": "/previous-versions/azure/hdinsight-aks/quickstart-prerequisites-subscription",
+        "redirect_document_id": false
+    },
+    {
+        "source_path_from_root": "/articles/hdinsight-aks/release-notes/index.md",
+        "redirect_url": "/previous-versions/azure/hdinsight-aks/release-notes/hdinsight-aks-release-notes",
+        "redirect_document_id": false
+    },
+    {
+        "source_path_from_root": "/articles/hdinsight-aks/prerequisites-resources.md",
+        "redirect_url": "/previous-versions/azure/hdinsight-aks/quickstart-prerequisites-resources",
+        "redirect_document_id": false
+    },    
+    {
+        "source_path_from_root": "/articles/hdinsight-aks/spark/index.md",
+        "redirect_url": "/previous-versions/azure/hdinsight-aks/spark/hdinsight-on-aks-spark-overview",
+        "redirect_document_id": false
+    },
+    {
+        "source_path_from_root": "/articles/hdinsight-aks/get-started.md",
+        "redirect_url": "/previous-versions/azure/hdinsight-aks/quickstart-get-started",
+        "redirect_document_id": false
+    },
+    {
+        "source_path_from_root": "/articles/hdinsight-aks/trino/index.md",
+        "redirect_url": "/previous-versions/azure/hdinsight-aks/trino/trino-overview ",
+        "redirect_document_id": false
+    },
     {
       "source_path": "articles/hdinsight-aks/cluster-storage.md",
       "redirect_url": "/previous-versions/azure/hdinsight-aks/cluster-storage",

articles/app-service/configure-ssl-app-service-certificate.md

@@ -139,6 +139,13 @@ By default, App Service certificates have a one-year validity period. Before the
 
 If you think your certificate's private key is compromised, you can rekey your certificate. This action rotates the certificate with a new certificate issued from the certificate authority.
 
+> [!NOTE]
+> Starting September 23 2021, if you haven't verified the domain in the last 395 days, App Service certificates require domain verification during a renew, auto-renew, or rekey process. The new certificate order remains in "pending issuance" mode during the renew, auto-renew, or rekey process until you complete the domain verification.
+> 
+> Unlike the free App Service managed certificate, purchased App Service certificates don't have automated domain re-verification. Failure to verify domain ownership results in failed renewals. For more information about how to verify your App Service certificate, review [Confirm domain ownership](#confirm-domain-ownership).
+>
+> The rekey process requires that the service principal for App Service has the required permissions on your key vault. These permissions are set up for you when you import an App Service certificate through the Azure portal. Make sure that you don't remove these permissions from your key vault.
+
 1. On the [App Service Certificates page](https://portal.azure.com/#blade/HubsExtension/Resources/resourceType/Microsoft.CertificateRegistration%2FcertificateOrders), select the certificate. From the left menu, select **Rekey and Sync**.
 
 1. To start the process, select **Rekey**. This process can take 1-10 minutes to complete.

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

@@ -1,36 +1,29 @@
 ---
-title: Tag resources, resource groups, and subscriptions for logical organization
-description: Describes the conditions and limitations for using tags with Azure resources.
+title: Use tags to organize your Azure resources and management hierarchy 
+description: Understand how to tag Azure resources, resource groups, and subscriptions for logical organization. Learn about the conditions and limitations of using tags with Azure resources.
 ms.topic: conceptual
-ms.date: 01/22/2025
+ms.date: 02/06/2025
 ---
 
 # Use tags to organize your Azure resources and management hierarchy
 
-Tags are metadata elements that you apply to your Azure resources. They're key-value pairs that help you identify resources based on settings that are relevant to your organization. If you want to track the deployment environment for your resources, add a key named `Environment`. To identify the resources deployed to production, give them a value of `Production`. The full key-value pair is `Environment = Production`.
+Tags are metadata elements that you apply to your Azure resources. They are key-value pairs that help you identify resources based on settings that are relevant to your organization. If you want to track the deployment environment for your resources, add a key named `Environment`. To identify the resources deployed to production, give them a value of `Production`. The full key-value pair is `Environment = Production`.
 
-This article describes the conditions and limitations for using tags. For steps on how to work with tags, see:
-
-* [Portal](tag-resources-portal.md)
-* [Azure CLI](tag-resources-cli.md)
-* [Azure PowerShell](tag-resources-powershell.md)
-* [Python](tag-resources-python.md)
-* [ARM templates](tag-resources-templates.md)
-* [Bicep](tag-resources-bicep.md)
+This article describes the conditions and limitations for using tags. 
 
 ## Tag usage and recommendations
 
-You can apply tags to your Azure resources, resource groups, and subscriptions, but not to management groups.
+You can apply tags to your Azure resources, resource groups, and subscriptions but not to management groups.
 
 For recommendations on how to implement a tagging strategy, see [Resource naming and tagging decision guide](/azure/cloud-adoption-framework/decision-guides/resource-tagging/?toc=/azure/azure-resource-manager/management/toc.json).
 
 Resource tags support all cost-accruing services. To ensure that cost-accruing services are provisioned with a tag, use one of the [tag policies](tag-policies.md).  
 
 > [!WARNING]
-> Tags are stored as plain text. Never add sensitive values to tags. Sensitive values could be exposed through many methods, including cost reports, commands that return existing tag definitions, deployment histories, exported templates, and monitoring logs.
+> Tags are stored as plain text. Do not add sensitive values to tags. Sensitive values could be exposed through many methods, including cost reports, commands that return existing tag definitions, deployment histories, exported templates, and monitoring logs.
 
 > [!WARNING]
-> Be careful when using non-English language in your tags. It can cause decoding progress failure while loading your VM's metadata from IMDS (Instance Metadata Service).
+> Be careful when using non-English language in your tags. It can cause decoding progress failure while loading your virtual machine's metadata from IMDS (Instance Metadata Service).
 
 > [!IMPORTANT]
 > Tag names are case-insensitive for operations. An operation updates or retrieves a tag with a tag name, regardless of the casing. However, the resource provider might keep the casing you provide for the tag name. You see that casing in cost reports.
@@ -41,66 +34,70 @@ Resource tags support all cost-accruing services. To ensure that cost-accruing s
 
 ## Required access
 
-There are two ways to get the required access to tag resources.
+There are two ways to get the required access to tag resources:
 
-* You can have write access to the `Microsoft.Resources/tags` resource type. This access lets you tag any resource, even if you don't have access to the resource itself. The [Tag Contributor](../../role-based-access-control/built-in-roles.md#tag-contributor) role grants this access. The tag contributor role, for example, can't apply tags to resources or resource groups through the portal. It can, however, apply tags to subscriptions through the portal. It supports all tag operations through Azure PowerShell and REST API.
+- You can have write access to the `Microsoft.Resources/tags` resource type. This access lets you tag any resource, even if you don't have access to the resource itself. The [Tag Contributor](../../role-based-access-control/built-in-roles.md#tag-contributor) role grants this access. For example, this role can't apply tags to resources or resource groups through the Azure portal. However, it can apply tags to subscriptions through the Azure portal. It supports all tag operations through Azure PowerShell and REST API.
 
-* You can have write access to the resource itself. The [Contributor](../../role-based-access-control/built-in-roles.md#contributor) role grants the required access to apply tags to any entity. To apply tags to only one resource type, use the contributor role for that resource. To apply tags to virtual machines, for example, use the [Virtual Machine Contributor](../../role-based-access-control/built-in-roles.md#virtual-machine-contributor).
+- You can have write access to the resource itself. The [Contributor](../../role-based-access-control/built-in-roles.md#contributor) role grants the required access to apply tags to any entity. To apply tags to only one resource type, use the Contributor role for that resource. To apply tags to virtual machines, use the [Virtual Machine Contributor](../../role-based-access-control/built-in-roles.md#virtual-machine-contributor) role.
 
 ## Inherit tags
 
-Resources don't inherit the tags you apply to a resource group or a subscription. To apply tags from a subscription or resource group to the resources, see [Azure Policies - tags](tag-policies.md).
+Resources don't inherit the tags you apply to a resource group or a subscription. To apply tags from a subscription or resource group to the resources, see [Assign policy definitions for tag compliance](tag-policies.md).
 
-You can group costs for an Azure resource by using the **cm-resource-parent** tag. This tag lets you review tagged costs in Microsoft Cost Management without having to use filters. The key for this tag is `cm-resource-parent` and its value is the resource ID of the Azure resource you want to group costs by. For example, to group costs by an Azure Virtual Desktop host pool, provide the resource ID of the host pool. For more information, see [Group related resources in the cost analysis](../../cost-management-billing/costs/group-filter.md#group-related-resources-in-the-resources-view).
+You can group costs for an Azure resource by using the **cm-resource-parent** tag. This tag lets you review tagged costs in Microsoft Cost Management without having to use filters. The key for this tag is `cm-resource-parent` and its value is the resource ID of the Azure resource you want to group costs by. For example, to group costs by an Azure Virtual Desktop host pool, provide the resource ID of the host pool. For more information, see [Group related resources in the Resources view](../../cost-management-billing/costs/group-filter.md#group-related-resources-in-the-resources-view).
 
 ## Tags and billing
 
-Use tags to group your billing data. For example, if you're running multiple VMs for different organizations, use the tags to group usage by cost center. You can also use tags to categorize costs by runtime environment, such as the billing usage for VMs running in the production environment.
+Use tags to group your billing data. For example, if you're running multiple virtual machines for different organizations, use the tags to group usage by cost center. You can also use tags to categorize costs by runtime environment, including the billing usage for virtual machines running in the production environment.
 
-To retrieve information about tags, download the usage file from the Azure portal. For more information, see [Download or view your Azure billing invoice and daily usage data](../../cost-management-billing/manage/download-azure-invoice-daily-usage-date.md). For services that support tags with billing, the tags appear in the **Tags** column.
+To retrieve information about tags, download the usage file from the Azure portal. For more information, see [Download or view your Azure billing invoice](../../cost-management-billing/manage/download-azure-invoice-daily-usage-date.md). For services that support tags with billing, the tags appear in the **Tags** column.
 
-For REST API operations, see [Azure Billing REST API Reference](/rest/api/billing/).
+For REST API operations, see the [Azure Billing REST API](/rest/api/billing/) overview.
 
 ## Unique tags pagination
 
-When you call the [Unique Tags API](/rest/api/resources/tags/list), there's a limit to the size of each API response page. A tag that has a large set of unique values requires the API to fetch the next page to retrieve the remaining set of values. When the results are divided over multiple pages, the API response shows the tag key again to indicate that the values are still under this key.  
+When you call the [Unique tags API](/rest/api/resources/tags/list), there's a limit to the size of each API response page. A tag that has a large set of unique values requires the API to fetch the next page to retrieve the remaining set of values. When the results are divided over multiple pages, the API response shows the tag key again to indicate that the values are still under this key.  
 
-This behavior can result in some tools, like the Azure portal, showing the tag key twice.
+This behavior can cause some tools like the Azure portal to show the tag key twice.
 
 ## Limitations
 
 The following limitations apply to tags:
 
 * Not all resource types support tags. To determine if you can apply a tag to a resource type, see [Tag support for Azure resources](tag-support.md).
-* Each resource type might have specific requirements when working with tags. For example, you can only update tags on virtual machine (VM) extensions when the VM is running. If you receive an error message while trying to update a tag, follow the instructions in the message.
+
+* Each resource type might have specific requirements when working with tags. For example, you can only update tags on virtual machine extensions when the virtual machine is running. If you receive an error message while trying to update a tag, follow the instructions in the message.
+
 * Each resource, resource group, and subscription can have a maximum of 50 tag name-value pairs. If you need to apply more tags than the maximum allowed number, use a JSON string for the tag value. The JSON string can contain many of the values that you apply to a single tag name. A resource group or subscription can contain many resources that each have 50 tag name-value pairs.
+
 * The tag name has a limit of 512 characters and the tag value has a limit of 256 characters. For storage accounts, the tag name has a limit of 128 characters and the tag value has a limit of 256 characters.
+
 * Classic resources such as Cloud Services don't support tags.
-* Azure IP Groups and Azure Firewall Policies don't support PATCH operations. PATCH API method operations, therefore, can't update tags through the 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#az-network-ip-group-update) 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?view=azure-cli-latest) command.
+
 * Tag names can't contain these characters: `<`, `>`, `%`, `&`, `\`, `?`, `/`
 
    > [!NOTE]
-   > * Azure Domain Name System (DNS) zones don't support the use of spaces or parentheses in the tag or a tag that starts with a number. Azure DNS tag names don't support special and Unicode characters. The value can contain all characters.
+   > * Azure DNS zones don't support the use of spaces or parentheses in the tag or a tag that starts with a number. Azure DNS tag names don't support special and Unicode characters. The value can contain all characters.
    >
    > * Traffic Manager doesn't support the use of spaces, `#`, or `:` in the tag name. The tag name can't start with a number.
    >
    > * Azure Front Door doesn't support the use of `#` or `:` in the tag name.
    >
    > * The following Azure resources only support 15 tags:
    >     * Azure Automation
-   >     * Azure Content Delivery Network (CDN)
+   >     * Azure Content Delivery Network
    >     * Azure DNS (Zone and A records)
-   >     * Azure Log Analytics Saved Search
+   >     * Azure Log Analytics saved search
 
 ## Next steps
 
-* Not all resource types support tags. To determine if you can apply a tag to a resource type, see [Tag support for Azure resources](tag-support.md).
-* For recommendations on how to implement a tagging strategy, see [Resource naming and tagging decision guide](/azure/cloud-adoption-framework/decision-guides/resource-tagging/?toc=/azure/azure-resource-manager/management/toc.json).
-* For steps on how to work with tags, see:
-
-  * [Portal](tag-resources-portal.md)
-  * [Azure CLI](tag-resources-cli.md)
-  * [Azure PowerShell](tag-resources-powershell.md)
-  * [Python](tag-resources-python.md)
-  * [ARM templates](tag-resources-templates.md)
-  * [Bicep](tag-resources-bicep.md)
+For more information on how to work with tags, see:
+
+* [Azure portal](tag-resources-portal.md)
+* [Azure CLI](tag-resources-cli.md)
+* [Azure PowerShell](tag-resources-powershell.md)
+* [Python](tag-resources-python.md)
+* [ARM templates](tag-resources-templates.md)
+* [Bicep](tag-resources-bicep.md)