Merge pull request #293912 from MicrosoftDocs/main

01/31/2025 AM Publishing

Author: v-alje

.openpublishing.redirection.json

@@ -5223,6 +5223,11 @@
       "source_path_from_root": "/articles/reliability/cross-region-replication-azure-no-pair.md",
       "redirect_url": "/azure/reliability/regions-multi-region-nonpaired",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/reliability/reliability-hdinsight-on-aks.md",
+      "redirect_url": "/azure/reliability/overview-reliability-guidance",
+      "redirect_document_id": false
     }
   ]
 }

articles/active-directory-b2c/identity-provider-generic-saml-options.md

@@ -422,7 +422,7 @@ Upon an application sign-out request, Azure AD B2C attempts to sign out from you
 
 ## Debug SAML protocol
 
-To help configure and debug federation with a SAML identity provider, you can use a browser extension for the SAML protocol, such as [SAML DevTools extension](https://chrome.google.com/webstore/detail/saml-devtools-extension/jndllhgbinhiiddokbeoeepbppdnhhio) for Chrome, [SAML-tracer](https://addons.mozilla.org/es/firefox/addon/saml-tracer/) for FireFox, or [Microsoft Edge or Internet Explorer developer tools](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/gathering-a-saml-token-using-edge-or-ie-developer-tools/ba-p/320957).
+To help configure and debug federation with a SAML identity provider, you can use a browser extension for the SAML protocol, such as [SAML DevTools extension](https://chrome.google.com/webstore/detail/saml-devtools-extension/jndllhgbinhiiddokbeoeepbppdnhhio) for Chrome, [SAML-tracer](https://addons.mozilla.org/es/firefox/addon/saml-tracer/) for Firefox, or [Microsoft Edge or Internet Explorer developer tools](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/gathering-a-saml-token-using-edge-or-ie-developer-tools/ba-p/320957).
 
 Using these tools, you can check the integration between Azure AD B2C and your SAML identity provider. For example:
 

articles/active-directory-b2c/troubleshoot.md

@@ -165,7 +165,7 @@ Use **Run now** and `https://jwt.ms` to test your policies independently of your
 
 ## Troubleshoot SAML protocol
 
-To help configure and debug the integration with your service provider, you can use a browser extension for the SAML protocol, for example, [SAML DevTools extension](https://chrome.google.com/webstore/detail/saml-devtools-extension/jndllhgbinhiiddokbeoeepbppdnhhio) for Chrome, [SAML-tracer](https://addons.mozilla.org/es/firefox/addon/saml-tracer/) for FireFox, or [Edge or Internet Explorer developer tools](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/gathering-a-saml-token-using-edge-or-ie-developer-tools/ba-p/320957).
+To help configure and debug the integration with your service provider, you can use a browser extension for the SAML protocol, for example, [SAML DevTools extension](https://chrome.google.com/webstore/detail/saml-devtools-extension/jndllhgbinhiiddokbeoeepbppdnhhio) for Chrome, [SAML-tracer](https://addons.mozilla.org/es/firefox/addon/saml-tracer/) for Firefox, or [Edge or Internet Explorer developer tools](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/gathering-a-saml-token-using-edge-or-ie-developer-tools/ba-p/320957).
 
 The following screenshot demonstrates how the SAML DevTools extension presents the SAML request Azure AD B2C sends to the identity provider, and the SAML response.
 

articles/app-service/environment/networking.md

@@ -141,7 +141,7 @@ For more information about Private Endpoint and Web App, see [Azure Web App Priv
 
 ## DNS
 
-The following sections describe the DNS considerations and configuration that apply inbound to and outbound from your App Service Environment. The examples use the domain suffix `appserviceenvironment.net` from Azure Public Cloud. If you're using other clouds like Azure Government, you need to use their respective domain suffix. For App Service Environment domains, the site name is truncated at 40 characters because of DNS limits. If you have a slot, the slot name is truncated at 19 characters.
+The following sections describe the DNS considerations and configuration that apply inbound to and outbound from your App Service Environment. The examples use the domain suffix `appserviceenvironment.net` from Azure Public Cloud. If you're using other clouds like Azure Government, you need to use their respective domain suffix. For App Service Environment domains, the site name is truncated at 59 characters because of DNS limits. For App Service Environment domains with slots, the site name is truncated at 40 characters and the slot name is truncated at 19 characters because of DNS limits.
 
 ### DNS configuration to your App Service Environment
 

articles/app-service/wordpress-faq.md

@@ -90,7 +90,7 @@ Key tools for debugging and monitoring WordPress sites include:
 - **[SSH Access](configure-linux-open-ssh-session.md?pivots=container-linux)**
 
 ### PhpMyAdmin
-WordPress on App Service utilizes an Azure Database for MySQL flexible server, which is integrated into a VNET. This setup restricts database access to within the VNET. WordPress on App Service includes phpMyAdmin by default. You can access it at: https://`<your-site-link>`/phpmyadmin. 
+WordPress on App Service utilizes an Azure Database for MySQL Flexible Server, which is integrated into a VNET. This setup restricts database access to within the VNET. WordPress on App Service includes phpMyAdmin by default. You can access it at: https://`<your-site-link>`/phpmyadmin. 
 
 If you are using Managed Identities, you can log in to phpMyAdmin by using the value from DATABASE_USERNAME environment variable as the username and the token as the password. To find the token use your Kudu SSH to run the following command: 
 

articles/azure-resource-manager/templates/template-specs-create-portal-forms.md

@@ -1,9 +1,9 @@
 ---
 title: Create portal forms for template spec
-description: Learn how to create forms that are displayed in the Azure portal forms. Use the form to deploying a template spec
+description: Learn how to create forms that are displayed in the Azure portal forms. Use the form to deploy a template spec.
 ms.topic: tutorial
 ms.custom: devx-track-azurepowershell, devx-track-azurecli
-ms.date: 03/20/2024
+ms.date: 01/30/2025
 ---
 
 # Tutorial: Create Azure portal forms for a template spec
@@ -24,9 +24,9 @@ For Azure PowerShell, use [version 6.0.0 or later](/powershell/azure/install-azu
 
 ## Create template
 
-To show the different portal elements that are available in a form, you'll use an ARM template with several parameters. The following template creates a key vault, configures permissions to key vault for a user, and adds a secret.
+To show the different portal elements that are available in a form, use an ARM template with several parameters. The following template creates a key vault, configures permissions to key vault for a user, and adds a secret.
 
-Copy this file and save it locally. This tutorial assumes you've named it **keyvault.json** but you can give it any name.
+Copy this file and save it locally. This tutorial assumes you named it **keyvault.json** but you can give it any name.
 
 ```json
 {
@@ -182,15 +182,15 @@ Copy this file and save it locally. This tutorial assumes you've named it **keyv
 
 ## Create default form
 
-The Azure portal provides a sandbox for creating and previewing forms. This sandbox can render a form from an existing ARM template. You'll use this default form to get started with creating a form for your template spec. For more information about the form structure, see [FormViewType](https://github.com/Azure/portaldocs/blob/main/portal-sdk/generated/dx-view-formViewType.md).
+The Azure portal provides a sandbox for creating and previewing forms. This sandbox can render a form from an existing ARM template. Use this default form to get started with creating a form for your template spec. For more information about the form structure, see [FormViewType](https://github.com/Azure/portaldocs/blob/main/portal-sdk/generated/dx-view-formViewType.md).
 
-1. Open the [Form view sandbox](https://aka.ms/form/sandbox).
+1. Open the [Form view sandbox](https://also known as.ms/form/sandbox).
 
     :::image type="content" source="./media/template-specs-create-portal-forms/deploy-template-spec-config.png" alt-text="Screenshot of Azure portal form view sandbox interface.":::
 
-1. In **Package Type**, select **CustomTemplate**. Make sure you select the package type before specify deployment template.
-1. In **Deployment template (optional)**, select the key vault template you saved locally. When prompted if you want to overwrite current changes, select **Yes**. The autogenerated form is displayed in the code window. The form is editable from the portal. To customize the form, see [customize form](#customize-form).
-    If you look closely into the autogenerated form, the default title is called **Test Form View**, and there's only one step called **basics** defined.
+1. In **Package Type**, select **CustomTemplate**. Make sure you select the package type before specifying deployment template.
+1. In **Deployment template (optional)**, select the key vault template you saved locally. When prompted if you want to overwrite current changes, select **Yes**. The autogenerated form is displayed in the code window. You can edit the form from the portal. To customize the form, see [customize form](#customize-form).
+    If you look closely at the autogenerated form, the default title is **Test Form View**. There's only one step called **basics** defined.
 
     ```json
     {
@@ -216,43 +216,43 @@ The Azure portal provides a sandbox for creating and previewing forms. This sand
     }
     ```
 
-1. To see that works it without any modifications, select **Preview**.
+1. To see that it works without any modifications, select **Preview**.
 
     :::image type="content" source="./media/template-specs-create-portal-forms/view-portal-basic.png" alt-text="Screenshot of the generated basic Azure portal form.":::
 
-    The sandbox displays the form. It has fields for selecting a subscription, resource group, and region. It also fields for all of the parameters from the template.
+    The sandbox displays the form. It has fields for selecting a subscription, resource group, and region. It also has fields for all of the parameters from the template.
 
-    Most of the fields are text boxes, but some fields are specific for the type of parameter. When your template includes allowed values for a parameter, the autogenerated form uses a drop-down element. The drop-down element is pre-populated with the allowed values.
+    Most of the fields are text boxes, but some fields are specific for the type of parameter. When your template includes allowed values for a parameter, the autogenerated form uses a drop-down element. The drop-down element is prepopulated with the allowed values.
 
-    In between the title and **Project details**, there are no tabs because the default form only has one step defined.  In the **Customize form** section, you'll break the parameters into multiple tabs.
+    Between the title and **Project details**, there are no tabs because the default form only has one step defined. In the **Customize form** section, you break the parameters into multiple tabs.
 
     > [!WARNING]
-    > Don't select **Create** as it will launch a real deployment. You'll have a chance to deploy the template spec later in this tutorial.
+    > Don't select **Create** as it launches a real deployment. You have a chance to deploy the template spec later in this tutorial.
 
 1. To exit from the preview, select **Cancel**.
 
 ## Customize form
 
-The default form is a good starting point for understanding forms but usually you'll want to customize it. You can edit it in the sandbox or in Visual Studio Code. The preview option is only available in the sandbox.
+The default form is a good starting point for understanding forms but usually you want to customize it. You can edit it in the sandbox or in Visual Studio Code. The preview option is only available in the sandbox.
 
 1. Give the form a **title** that describes its use.
 
     ::: code language="json" source="~/azure-docs-json-samples/azure-resource-manager/ui-forms/keyvaultform.json" range="1-6" highlight="6" :::
 
-1. Your default form had all of the fields for your template combined into one step called **Basics**. To help users to understand the values they're providing, divide the form into steps. Each step contains fields related to a logical part of the solution to deploy.
+1. Your default form had all of the fields for your template combined into one step called **Basics**. To help users understand the values they're providing, divide the form into steps. Each step contains fields related to a logical part of the solution to deploy.
 
-    Find the step labeled **Basics**. You'll keep this step but add steps below it. The new steps will focus on configuring the key vault, setting user permissions, and specifying the secret. Make sure you add a comma after the basics step.
+    Find the step labeled **Basics**. Keep this step but add steps that focus on configuring the key vault, setting user permissions, and specifying the secret. Add a comma after the basics step.
 
     ::: code language="json" source="~/azure-docs-json-samples/azure-resource-manager/ui-forms/steps.json" highlight="15-32" :::
 
     > [!IMPORTANT]
     > Properties in the form are case-sensitive. Make sure you use the casing shown in the examples.
 
-1. Select **Preview**. You'll see the steps, but most of them don't have any elements.
+1. Select **Preview**. You see the steps, but most of them don't have any elements.
 
     :::image type="content" source="./media/template-specs-create-portal-forms/view-steps.png" alt-text="Screenshot of Azure portal form with multiple steps.":::
 
-1. Now, move elements to the appropriate steps. Start with the elements labeled **Secret Name** and **Secret Value**. Remove these elements from the **Basics** step and add them to the **Secret** step.
+1. Move elements to the appropriate steps. Start with the elements labeled **Secret Name** and **Secret Value**. Remove these elements from the **Basics** step and add them to the **Secret** step.
 
     ```json
     {
@@ -294,7 +294,7 @@ The default form is a good starting point for understanding forms but usually yo
     }
     ```
 
-1. When you move elements, you need to fix the `outputs` section. Currently, the outputs section references those elements as if they were still in the basics step. Fix the syntax so it references the elements in the `secret` step.
+1. When you move elements, fix the `outputs` section. Currently, the outputs section references those elements as if they were still in the basics step. Fix the syntax so it references the elements in the `secret` step.
 
     ```json
     "outputs": {
@@ -305,7 +305,7 @@ The default form is a good starting point for understanding forms but usually yo
       }
     ```
 
-1. Continue moving elements to the appropriate steps. Rather than go through each one, take a look at the updated form.
+1. Continue moving elements to the appropriate steps. Rather than go through each one, look at the updated form.
 
     ::: code language="json" source="~/azure-docs-json-samples/azure-resource-manager/ui-forms/keyvaultform.json" :::
 
@@ -345,19 +345,19 @@ To test the form, go to the portal and navigate to your template spec. Select **
 
 :::image type="content" source="./media/template-specs-create-portal-forms/deploy-template-spec.png" alt-text="Screenshot of Azure template spec overview with deploy option highlighted.":::
 
-You'll see the form you created. Go through the steps and provide values for the fields.
+You see the form you created. Go through the steps and provide values for the fields.
 
-On the **Basics** step, you'll see a field for **Region**. This field is used for the location of the resource group. On the **Key Vault** step, you'll see a field for **Location**. This field is used for the location of the key vault.
+On the **Basics** step, you see a field for **Region**. This field is for the location of the resource group. On the **Key Vault** step, you see a field for **Location**. This field is for the location of the key vault.
 
-On the **Permissions** step, you can provide your own user ID for the object ID. Use the default value (`["list"]`) for key and secret permissions. You'll improve that option in the next section.
+On the **Permissions** step, provide your user ID for the object ID. Use the default value (`["list"]`) for key and secret permissions. You improve that option in the next section.
 
-When you have finished providing values, select **Create** to deploy the template spec.
+When you finish providing values, select **Create** to deploy the template spec.
 
 ## Improve the form
 
-In the previous section, you added steps and moved elements, but you didn't change any of the default behaviors. In this section, you'll make changes that improve the experience for users of your template spec.
+In the previous section, you added steps and moved elements, but you didn't change any of the default behaviors. In this section, you make changes that improve the experience for users of your template spec.
 
-Previously, the two permissions fields were text boxes. Now, you'll use a drop-down. Set the type to `Microsoft.Common.DropDown`.
+Previously, the two permissions fields were text boxes. Now, you use a drop-down. Set the type to `Microsoft.Common.DropDown`.
 
 Update `keysPermissions`:
 
@@ -367,13 +367,13 @@ And `secretsPermissions`:
 
 ::: code language="json" source="~/azure-docs-json-samples/azure-resource-manager/ui-forms/keyvaultform2.json" range="253-255" highlight="3" :::
 
-These fields need to pass an array to the template. A regular drop-down won't work because it only lets you select one value. To select more than one value and pass them as an array, add the `multiselect` field and set to `true`.
+These fields need to pass an array to the template. A regular drop-down doesn't work because it only lets you select one value. To select more than one value and pass them as an array, add the `multiselect` field and set it to `true`.
 
 ::: code language="json" source="~/azure-docs-json-samples/azure-resource-manager/ui-forms/keyvaultform2.json" range="169-173" highlight="5" :::
 
 ::: code language="json" source="~/azure-docs-json-samples/azure-resource-manager/ui-forms/keyvaultform2.json" range="253-257" highlight="5" :::
 
-Finally, you must specify the allowed values for the drop-down and a default value.
+Finally, specify the allowed values for the drop-down and a default value.
 
 ::: code language="json" source="~/azure-docs-json-samples/azure-resource-manager/ui-forms/keyvaultform2.json" range="169-304" highlight="6-8,12-81,90-92,96-133" :::
 
@@ -407,7 +407,7 @@ Redeploy your template spec with the improved portal form.
 
 :::image type="content" source="./media/template-specs-create-portal-forms/view-portal.png" alt-text="Screenshot of Azure portal form for providing values to a template spec.":::
 
-Notice that your permission fields are now drop-down that allow multiple values.
+Notice that your permission fields are now drop-downs that allow multiple values.
 
 ## Next steps