Merge branch 'MicrosoftDocs:main' into master

Author: madhurinms

articles/active-directory-b2c/api-connectors-overview.md

@@ -85,7 +85,7 @@ Using Azure AD B2C, you can add your own business logic to a user journey by cal
 ![Diagram of a RESTful service claims exchange](media/api-connectors-overview/restful-service-claims-exchange.png)
 
 > [!NOTE]
-> If there is slow or no response from the RESTful service to Azure AD B2C, the timeout is 30 seconds and the retry count is two times (meaning there are 3 tries in total). Currently, you can't configure the timeout and retry count settings.
+> HTTP requests may be cancelled if there is a slow or no response from the RESTful service to Azure AD B2C. The default timeout is 10 seconds and the default retry count is one (meaning there are 2 tries in total).
 
 ## Calling a RESTful service
 

articles/api-center/synchronize-aws-gateway-apis.md

@@ -8,8 +8,9 @@ ms.date: 02/10/2025
 ms.author: danlep 
 ms.custom: 
   - devx-track-azurecli
-  - migration
-  - aws-to-azure
+ms.collection: 
+ - migration
+ - aws-to-azure
 # Customer intent: As an API program manager, I want to integrate my Azure API Management instance with my API center and synchronize API Management APIs to my inventory.
 ---
 

articles/app-service/environment/creation-terraform.md

@@ -0,0 +1,141 @@
+---
+title: 'Quickstart: Use Terraform to configure an Azure App Service Environment v3'
+description: In this quickstart, you learn how to configure an Azure App Service Environment v3. 
+ms.topic: quickstart
+ms.date: 04/08/2025
+ms.custom: devx-track-terraform
+ms.service: azure-app-service
+author: cephalin
+ms.author: cephalin
+#customer intent: As a Terraform user, I want to learn how to configure an Azure App Service Environment v3.
+content_well_notification: 
+  - AI-contribution
+---
+
+# Quickstart: Use Terraform to configure an Azure App Service Environment v3
+
+In this quickstart, you use [Terraform](/azure/developer/terraform) to create an App Service Environment, single-tenant deployment of Azure App Service. You use it with an Azure virtual network. You need one subnet for a deployment of App Service Environment, and this subnet can't be used for anything else. You create a resource group, virtual network, and a subnet to configure an Azure App Service Environment v3.
+
+In this article, you learn how to:
+
+> [!div class="checklist"]
+> * Create an Azure resource group with a unique name.
+> * Establish a virtual network with a specified name and address.
+> * Generate a random name for the subnet, and create a subnet in the virtual network.
+> * Delegate the subnet to the Microsoft.Web/hostingEnvironments service.
+> * Generate a random name for the App Service Environment v3, and create an App Service Environment v3 in the subnet.
+> * Set the internal load-balancing mode for the App Service Environment v3.
+> * Set cluster settings for the App Service Environment v3.
+> * Tag the App Service Environment v3.
+> * Output the names of the resource group, virtual network, subnet, and App Service Environment v3.
+
+## Prerequisites
+
+- An Azure account with an active subscription. You can [create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
+- Terraform. For more information, see [Install and configure Terraform](/azure/developer/terraform/quickstart-configure).
+
+> [!IMPORTANT]
+> If you're using the 4.x azurerm provider, you must [explicitly specify the Azure subscription ID](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/4.0-upgrade-guide#specifying-subscription-id-is-now-mandatory) to authenticate to Azure before running the Terraform commands.
+>
+> One way to specify the Azure subscription ID without putting it in the `providers` block is to specify the subscription ID in an environment variable named `ARM_SUBSCRIPTION_ID`.
+>
+> For more information, see the [Azure provider reference documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs#argument-reference).
+
+## Implement the Terraform code
+
+The sample code for this article is located in the [Azure Terraform GitHub repo](https://github.com/Azure/terraform/tree/master/quickstart/101-app-service-environment). You can view the log file containing the [test results from current and previous versions of Terraform](https://github.com/Azure/terraform/tree/master/quickstart/101-app-service-environment/TestRecord.md). See more [articles and sample code showing how to use Terraform to manage Azure resources](/azure/terraform).
+
+1. Create a directory in which to test and run the sample Terraform code, and make it the current directory.
+
+1. Create a file named `main.tf`, and insert the following code:
+    :::code language="Terraform" source="~/terraform_samples/quickstart/101-app-service-environment/main.tf":::
+
+1. Create a file named `outputs.tf`, and insert the following code:
+    :::code language="Terraform" source="~/terraform_samples/quickstart/101-app-service-environment/outputs.tf":::
+
+1. Create a file named `providers.tf`, and insert the following code:
+    :::code language="Terraform" source="~/terraform_samples/quickstart/101-app-service-environment/providers.tf":::
+
+1. Create a file named `variables.tf`, and insert the following code:
+    :::code language="Terraform" source="~/terraform_samples/quickstart/101-app-service-environment/variables.tf":::
+
+## Initialize Terraform
+
+[!INCLUDE [terraform-init.md](~/azure-dev-docs-pr/articles/terraform/includes/terraform-init.md)]
+
+## Create a Terraform execution plan
+
+[!INCLUDE [terraform-plan.md](~/azure-dev-docs-pr/articles/terraform/includes/terraform-plan.md)]
+
+## Apply a Terraform execution plan
+
+[!INCLUDE [terraform-apply-plan.md](~/azure-dev-docs-pr/articles/terraform/includes/terraform-apply-plan.md)]
+
+## Verify the results
+
+### [Azure CLI](#tab/azure-cli)
+
+1. Get the Azure resource group name.
+
+    ```console
+    resource_group_name=$(terraform output -raw resource_group_name)
+    ```
+
+1. Get the virtual network name.
+
+    ```console
+    virtual_network_name=$(terraform output -raw virtual_network_name)
+    ```
+
+1. Get the subnet name.
+
+    ```console
+    subnet_name=$(terraform output -raw subnet_name)
+    ```
+
+1. Run `az appservice ase show` to view the App Service Environment v3.
+
+    ```azurecli
+    az appservice ase show --name $app_service_environment_v3_name --resource-group $resource_group_name  
+    ```
+
+### [Azure PowerShell](#tab/azure-powershell)
+
+1. Get the Azure resource group name.
+
+    ```console
+    $resource_group_name=$(terraform output -raw resource_group_name)
+    ```
+
+1. Get the virtual network name.
+
+    ```console
+    $virtual_network_name=$(terraform output -virtual_network_name)
+    ```
+
+1. Get the subnet name.
+
+    ```console
+    $subnet_name=$(terraform output -subnet_name)
+    ```
+
+1. Run `Get-AzAppServiceEnvironment` to view the AKS cluster within the Azure Extended Zone.
+
+    ```azurepowershell
+    Get-AzAppServiceEnvironment -Name $app_service_environment_v3_name -ResourceGroupName $resource_group_name 
+    ```
+
+---
+
+## Clean up resources
+
+[!INCLUDE [terraform-plan-destroy.md](~/azure-dev-docs-pr/articles/terraform/includes/terraform-plan-destroy.md)]
+
+## Troubleshoot Terraform on Azure
+
+[Troubleshoot common problems when using Terraform on Azure](/azure/developer/terraform/troubleshoot).
+
+## Next steps
+
+> [!div class="nextstepaction"]
+> [See more articles about Azure app service environment v3.](/search/?terms=Azure%20app%20service%20environment%20v3%20and%20terraform)

articles/app-service/environment/toc.yml

@@ -11,6 +11,8 @@
   items:
   - name: Create App Service Environment in portal
     href: creation.md
+  - name: Create an App Service Environment using Terraform
+    href: creation-terraform.md
 - name: Tutorials
   items:
   - name: Integrate with Application Gateway

articles/application-gateway/application-gateway-probe-overview.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: azure-application-gateway
 ms.topic: concept-article
-ms.date: 09/14/2023
+ms.date: 04/09/2025
 ms.author: greglin 
 ms.custom: devx-track-azurepowershell
 ---
@@ -46,15 +46,15 @@ Once the probe detects a failed response, the counter for "Unhealthy threshold"
 
 An application gateway automatically configures a default health probe when you don't set up any custom probe configuration. The monitoring behavior works by making an HTTP GET request to the IP addresses or FQDN configured in the backend pool. For default probes if the backend http settings are configured for HTTPS, the probe uses HTTPS to test health of the backend servers.
 
-For example: You configure your application gateway to use backend servers A, B, and C to receive HTTP network traffic on port 80. The default health monitoring tests the three servers every 30 seconds for a healthy HTTP response with a 30-second-timeout for each request. A healthy HTTP response has a [status code](/troubleshoot/developer/webapps/iis/www-administration-management/http-status-code) between 200 and 399. In this case, the HTTP GET host header for the health probe looks like `http://127.0.0.1/`. Also see [HTTP response codes in Application Gateway](http-response-codes.md).
+For example: You configure your application gateway to use backend servers A, B, and C to receive HTTP network traffic on port 80. The default health monitoring tests the three servers every 30 seconds for a healthy HTTP response with a 30-second-timeout for each request. A healthy HTTP response has a [status code](/troubleshoot/developer/webapps/iis/www-administration-management/http-status-code) between 200 and 399. In this case, the HTTP GET Host header for the health probe appears as `http://127.0.0.1/`, unless a hostname is configured in the [Backend Settings](configuration-http-settings.md#configuring-the-host-name).
 
 If the default probe check fails for server A, the application gateway stops forwarding requests to this server. The default probe still continues to check for server A every 30 seconds. When server A responds successfully to one request from a default health probe, application gateway starts forwarding the requests to the server again.
 
 ### Default health probe settings
 
 | Probe property | Value | Description |
 | --- | --- | --- |
-| Probe URL |\<protocol\>://127.0.0.1:\<port\>/ |The protocol and port are inherited from the backend HTTP settings to which the probe is associated |
+| Probe URL |\<protocol\>://127.0.0.1:\<port\>/ |The protocol and port are inherited from the Backend Settings to which the probe is associated. The default host is 127.0.0.1 unless one is specified in the associated Backend Settings. |
 | Interval |30 |The amount of time in seconds to wait before the next health probe is sent.|
 | Time-out |30 |The amount of time in seconds the application gateway waits for a probe response before marking the probe as unhealthy. If a probe returns as healthy, the corresponding backend is immediately marked as healthy.|
 | Unhealthy threshold |3 |Governs how many probes to send in case there's a failure of the regular health probe. In v1 SKU, these additional health probes are sent in quick succession to determine the health of the backend quickly and don't wait for the probe interval. For v2 SKU, the health probes wait the interval. The backend server is marked down after the consecutive probe failure count reaches the unhealthy threshold. |

articles/azure-cache-for-redis/cache-migration-guide.md

@@ -1,14 +1,12 @@
 ---
 title: Migrate to Azure Cache for Redis
 description: Learn how to migrate your existing cache to Azure Cache for Redis
-
-
-
 ms.topic: conceptual
 ms.custom:
   - ignite-2024
-  - migration
-  - aws-to-azure
+ms.collection: 
+ - migration
+ - aws-to-azure
 ms.date: 11/17/2021
 appliesto:
   - ✅ Azure Cache for Redis

articles/azure-functions/durable/durable-functions-troubleshooting-guide.md

@@ -129,7 +129,7 @@ traces
 | extend status = customDimensions["prop__status"]
 | extend details = customDimensions["prop__Details"] 
 | extend reason = customDimensions["prop__reason"]
-| where severityLevel > 1 // to see all logs of  severity level "Information" or greater.
+| where severityLevel >= 1 // to see all logs of severity level "Information" or greater.
 | where instanceId == orchestrationInstanceID
 | sort by timestamp asc 
 ```

articles/azure-functions/migration/assess-lambda-workloads.md

@@ -4,6 +4,9 @@ description: Learn how to map AWS Lambda features to Azure Functions and develop
 author: MadhuraBharadwaj-MSFT
 ms.author: mabhar
 ms.service: azure-functions
+ms.collection: 
+ - migration
+ - aws-to-azure
 ms.topic: how-to
 ms.date: 03/18/2025
 #customer intent: As a developer, I want to ensure compatibility between features and create a detailed migration plan so that I can migrate serverless applications from AWS Lambda to Azure Functions efficiently.

articles/azure-functions/migration/discover-lambda-workloads.md

@@ -4,6 +4,9 @@ description: Learn how to conduct a detailed discovery process to inventory curr
 author: MadhuraBharadwaj-MSFT
 ms.author: mabhar
 ms.service: azure-functions
+ms.collection: 
+ - migration
+ - aws-to-azure
 ms.topic: how-to
 ms.date: 03/18/2025
 #customer intent: As a developer, I want to evaluate existing AWS Lambda workloads so that I can migrate serverless applications to Azure Functions efficiently.

articles/azure-functions/migration/migrate-lambda-workloads-overview.md

@@ -4,6 +4,9 @@ description: Learn about Azure Functions and the three stages that you need to c
 author: MadhuraBharadwaj-MSFT
 ms.author: mabhar
 ms.service: azure-functions
+ms.collection: 
+ - migration
+ - aws-to-azure
 ms.topic: how-to
 ms.date: 03/18/2025
 #customer intent: As a developer, I want to learn how to migrate serverless applications from AWS Lambda to Azure Functions so that I can make the transition efficiently.