Skip to content

Commit 08a9430

Browse files
TaojunshenTaojunshen
authored
Merge pull request #297935 from MicrosoftDocs/main
4/9/2025 AM Publish
2 parents 1f9c0dc + d4be933 commit 08a9430

File tree

70 files changed

+501
-109
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

70 files changed

+501
-109
lines changed

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

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,9 @@ ms.date: 02/10/2025
88
ms.author: danlep
99
ms.custom:
1010
- devx-track-azurecli
11-
- migration
12-
- aws-to-azure
11+
ms.collection:
12+
- migration
13+
- aws-to-azure
1314
# 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.
1415
---
1516

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

Lines changed: 141 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,141 @@
1+
---
2+
title: 'Quickstart: Use Terraform to configure an Azure App Service Environment v3'
3+
description: In this quickstart, you learn how to configure an Azure App Service Environment v3.
4+
ms.topic: quickstart
5+
ms.date: 04/08/2025
6+
ms.custom: devx-track-terraform
7+
ms.service: azure-app-service
8+
author: cephalin
9+
ms.author: cephalin
10+
#customer intent: As a Terraform user, I want to learn how to configure an Azure App Service Environment v3.
11+
content_well_notification:
12+
- AI-contribution
13+
---
14+
15+
# Quickstart: Use Terraform to configure an Azure App Service Environment v3
16+
17+
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.
18+
19+
In this article, you learn how to:
20+
21+
> [!div class="checklist"]
22+
> * Create an Azure resource group with a unique name.
23+
> * Establish a virtual network with a specified name and address.
24+
> * Generate a random name for the subnet, and create a subnet in the virtual network.
25+
> * Delegate the subnet to the Microsoft.Web/hostingEnvironments service.
26+
> * Generate a random name for the App Service Environment v3, and create an App Service Environment v3 in the subnet.
27+
> * Set the internal load-balancing mode for the App Service Environment v3.
28+
> * Set cluster settings for the App Service Environment v3.
29+
> * Tag the App Service Environment v3.
30+
> * Output the names of the resource group, virtual network, subnet, and App Service Environment v3.
31+
32+
## Prerequisites
33+
34+
- An Azure account with an active subscription. You can [create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
35+
- Terraform. For more information, see [Install and configure Terraform](/azure/developer/terraform/quickstart-configure).
36+
37+
> [!IMPORTANT]
38+
> 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.
39+
>
40+
> 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`.
41+
>
42+
> For more information, see the [Azure provider reference documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs#argument-reference).
43+
44+
## Implement the Terraform code
45+
46+
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).
47+
48+
1. Create a directory in which to test and run the sample Terraform code, and make it the current directory.
49+
50+
1. Create a file named `main.tf`, and insert the following code:
51+
:::code language="Terraform" source="~/terraform_samples/quickstart/101-app-service-environment/main.tf":::
52+
53+
1. Create a file named `outputs.tf`, and insert the following code:
54+
:::code language="Terraform" source="~/terraform_samples/quickstart/101-app-service-environment/outputs.tf":::
55+
56+
1. Create a file named `providers.tf`, and insert the following code:
57+
:::code language="Terraform" source="~/terraform_samples/quickstart/101-app-service-environment/providers.tf":::
58+
59+
1. Create a file named `variables.tf`, and insert the following code:
60+
:::code language="Terraform" source="~/terraform_samples/quickstart/101-app-service-environment/variables.tf":::
61+
62+
## Initialize Terraform
63+
64+
[!INCLUDE [terraform-init.md](~/azure-dev-docs-pr/articles/terraform/includes/terraform-init.md)]
65+
66+
## Create a Terraform execution plan
67+
68+
[!INCLUDE [terraform-plan.md](~/azure-dev-docs-pr/articles/terraform/includes/terraform-plan.md)]
69+
70+
## Apply a Terraform execution plan
71+
72+
[!INCLUDE [terraform-apply-plan.md](~/azure-dev-docs-pr/articles/terraform/includes/terraform-apply-plan.md)]
73+
74+
## Verify the results
75+
76+
### [Azure CLI](#tab/azure-cli)
77+
78+
1. Get the Azure resource group name.
79+
80+
```console
81+
resource_group_name=$(terraform output -raw resource_group_name)
82+
```
83+
84+
1. Get the virtual network name.
85+
86+
```console
87+
virtual_network_name=$(terraform output -raw virtual_network_name)
88+
```
89+
90+
1. Get the subnet name.
91+
92+
```console
93+
subnet_name=$(terraform output -raw subnet_name)
94+
```
95+
96+
1. Run `az appservice ase show` to view the App Service Environment v3.
97+
98+
```azurecli
99+
az appservice ase show --name $app_service_environment_v3_name --resource-group $resource_group_name
100+
```
101+
102+
### [Azure PowerShell](#tab/azure-powershell)
103+
104+
1. Get the Azure resource group name.
105+
106+
```console
107+
$resource_group_name=$(terraform output -raw resource_group_name)
108+
```
109+
110+
1. Get the virtual network name.
111+
112+
```console
113+
$virtual_network_name=$(terraform output -virtual_network_name)
114+
```
115+
116+
1. Get the subnet name.
117+
118+
```console
119+
$subnet_name=$(terraform output -subnet_name)
120+
```
121+
122+
1. Run `Get-AzAppServiceEnvironment` to view the AKS cluster within the Azure Extended Zone.
123+
124+
```azurepowershell
125+
Get-AzAppServiceEnvironment -Name $app_service_environment_v3_name -ResourceGroupName $resource_group_name
126+
```
127+
128+
---
129+
130+
## Clean up resources
131+
132+
[!INCLUDE [terraform-plan-destroy.md](~/azure-dev-docs-pr/articles/terraform/includes/terraform-plan-destroy.md)]
133+
134+
## Troubleshoot Terraform on Azure
135+
136+
[Troubleshoot common problems when using Terraform on Azure](/azure/developer/terraform/troubleshoot).
137+
138+
## Next steps
139+
140+
> [!div class="nextstepaction"]
141+
> [See more articles about Azure app service environment v3.](/search/?terms=Azure%20app%20service%20environment%20v3%20and%20terraform)

‎articles/app-service/environment/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,8 @@
1111
items:
1212
- name: Create App Service Environment in portal
1313
href: creation.md
14+
- name: Create an App Service Environment using Terraform
15+
href: creation-terraform.md
1416
- name: Tutorials
1517
items:
1618
- name: Integrate with Application Gateway

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

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,12 @@
11
---
22
title: Migrate to Azure Cache for Redis
33
description: Learn how to migrate your existing cache to Azure Cache for Redis
4-
5-
6-
74
ms.topic: conceptual
85
ms.custom:
96
- ignite-2024
10-
- migration
11-
- aws-to-azure
7+
ms.collection:
8+
- migration
9+
- aws-to-azure
1210
ms.date: 11/17/2021
1311
appliesto:
1412
- ✅ Azure Cache for Redis

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,7 @@ traces
129129
| extend status = customDimensions["prop__status"]
130130
| extend details = customDimensions["prop__Details"]
131131
| extend reason = customDimensions["prop__reason"]
132-
| where severityLevel > 1 // to see all logs of severity level "Information" or greater.
132+
| where severityLevel >= 1 // to see all logs of severity level "Information" or greater.
133133
| where instanceId == orchestrationInstanceID
134134
| sort by timestamp asc
135135
```

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,9 @@ description: Learn how to map AWS Lambda features to Azure Functions and develop
44
author: MadhuraBharadwaj-MSFT
55
ms.author: mabhar
66
ms.service: azure-functions
7+
ms.collection:
8+
- migration
9+
- aws-to-azure
710
ms.topic: how-to
811
ms.date: 03/18/2025
912
#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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,9 @@ description: Learn how to conduct a detailed discovery process to inventory curr
44
author: MadhuraBharadwaj-MSFT
55
ms.author: mabhar
66
ms.service: azure-functions
7+
ms.collection:
8+
- migration
9+
- aws-to-azure
710
ms.topic: how-to
811
ms.date: 03/18/2025
912
#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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,9 @@ description: Learn about Azure Functions and the three stages that you need to c
44
author: MadhuraBharadwaj-MSFT
55
ms.author: mabhar
66
ms.service: azure-functions
7+
ms.collection:
8+
- migration
9+
- aws-to-azure
710
ms.topic: how-to
811
ms.date: 03/18/2025
912
#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.

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,9 @@ description: Learn about the steps to complete your AWS Lambda to Azure Function
44
author: MadhuraBharadwaj-MSFT
55
ms.author: mabhar
66
ms.service: azure-functions
7+
ms.collection:
8+
- migration
9+
- aws-to-azure
710
ms.topic: how-to
811
ms.date: 03/18/2025
912
#customer intent: As a developer, I want to adapt function code for compatibility and best practices so that I can migrate serverless applications from AWS Lambda to Azure Functions efficiently.

‎articles/azure-maps/migrate-get-traffic-incidents.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -69,22 +69,22 @@ The following table lists the fields that can appear in the HTTP response when r
6969

7070
| Bing Maps response field | Azure Maps response field | Description |
7171
|--------------------------|---------------------------|-------------|
72-
| Description (Json)<br>Description (XML)  | `d`  | This output is in the [tm] response element of Azure Maps.  |
73-
| End (Json)<br>EndTimeUTC (XML)  | `ed`  | This output is in the [tm] response element of Azure Maps. The date is described in the ISO8601 format and includes time in UTC.  |
74-
| eventList (Json)<br>EventList (XML)  | Not supported | |
75-
| icon (Json)<br>Icon (XML)  | `ic`  | This output is in the [tm] response element of Azure Maps. See [IconCategory] (`ic`) for more info.  |
76-
| incidentId (Json)<br>IncidentId (XML)  | `id` | This output is in the [tm] response element of Azure Maps.  |
77-
| isEndTimeBackfilled (Json)<br>IsEndTimeBackfilled (XML)  | Not supported | |
78-
| isJamcident (Json)<br>IsJamcident (XML)  | Not supported |
79-
| lastModified (Json)<br>LastModifiedUTC (XML)  | Not supported | |
80-
| point (Json)<br>Point (XML)  | `p`  | This output is in the [tm] response element of Azure Maps. See [point] (`p`) for more info.  |
81-
| roadClosed (Json)<br>RoadClosed (XML)  | See description | The [IconCategory] output of the [tm] response element of Azure Maps can be used to indicate a road closure.   |
82-
| severity (Json)<br>Severity (XML)  | `ty`  | This output is in the [tm] response element. See [DelayMagnitude]:  (`ty`) for more info.  |
83-
| severityScore (Json)<br>SeverityScore (XML)              | Not supported | |
84-
| Start (Json)<br>StartTimeUTC (XML)  | `sd`  | This output is in the [tm] response element of Azure Maps. The date is described in the ISO8601 format and includes time in UTC.  |
85-
| title (Json)<br>Title (XML)  | See description | The `f` output in the [tm] response element of Azure Maps provides the name of the intersection or location where the traffic caused by the the incident starts and can serve as an alternative to the Bing Maps `title` output.  |
86-
| toPoint (Json)<br>ToPoint (XML)  | See description | The `t` output in the [tm] response element of Azure Maps provides the name of the intersection or location where the traffic due to the incident ends and can serve as an alternative to the Bing Maps `toPoint` output.  |
87-
| type (Json)<br>Type (XML)  | `c`  | The `c` output in the [tm] response element of Azure Maps provides the cause of the incident, if available.  |
72+
| Description (JSON)<br>Description (XML)  | `d`  | This output is in the [tm] response element of Azure Maps.  |
73+
| End (JSON)<br>EndTimeUTC (XML)  | `ed`  | This output is in the [tm] response element of Azure Maps. The date is described in the ISO8601 format and includes time in UTC.  |
74+
| eventList (JSON)<br>EventList (XML)  | Not supported | |
75+
| icon (JSON)<br>Icon (XML)  | `ic`  | This output is in the [tm] response element of Azure Maps. See [IconCategory] (`ic`) for more info.  |
76+
| incidentId (JSON)<br>IncidentId (XML)  | `id` | This output is in the [tm] response element of Azure Maps.  |
77+
| isEndTimeBackfilled (JSON)<br>IsEndTimeBackfilled (XML)  | Not supported | |
78+
| isJamcident (JSON)<br>IsJamcident (XML)  | Not supported |
79+
| lastModified (JSON)<br>LastModifiedUTC (XML)  | Not supported | |
80+
| point (JSON)<br>Point (XML)  | `p`  | This output is in the [tm] response element of Azure Maps. See [point] (`p`) for more info.  |
81+
| roadClosed (JSON)<br>RoadClosed (XML)  | See description | The [IconCategory] output of the [tm] response element of Azure Maps can be used to indicate a road closure.   |
82+
| severity (JSON)<br>Severity (XML)  | `ty`  | This output is in the [tm] response element. See [DelayMagnitude]:  (`ty`) for more info.  |
83+
| severityScore (JSON)<br>SeverityScore (XML)              | Not supported | |
84+
| Start (JSON)<br>StartTimeUTC (XML)  | `sd`  | This output is in the [tm] response element of Azure Maps. The date is described in the ISO8601 format and includes time in UTC.  |
85+
| title (JSON)<br>Title (XML)  | See description | The `f` output in the [tm] response element of Azure Maps provides the name of the intersection or location where the traffic caused by the the incident starts and can serve as an alternative to the Bing Maps `title` output.  |
86+
| toPoint (JSON)<br>ToPoint (XML)  | See description | The `t` output in the [tm] response element of Azure Maps provides the name of the intersection or location where the traffic due to the incident ends and can serve as an alternative to the Bing Maps `toPoint` output.  |
87+
| type (JSON)<br>Type (XML)  | `c`  | The `c` output in the [tm] response element of Azure Maps provides the cause of the incident, if available.  |
8888

8989
For more information about the Azure Maps Get Traffic Incident Detail API response fields, see [Responses].
9090

0 commit comments

Comments
 (0)