Skip to content

Commit 6d8f5e4

Browse files
authored
Merge pull request #296652 from MicrosoftDocs/main
Merge main to live, 4 AM
2 parents e1c9ef0 + 35f5adc commit 6d8f5e4

File tree

72 files changed

+2492
-1325
lines changed

Some content is hidden

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

72 files changed

+2492
-1325
lines changed

articles/automation/delete-account.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: This article tells how to delete and your Automation account across
44
services: automation
55
ms.service: azure-automation
66
ms.subservice: process-automation
7-
ms.date: 12/28/2024
7+
ms.date: 03/20/2025
88
ms.topic: how-to
99
---
1010

@@ -93,6 +93,9 @@ While it attempts to unlink the Automation account, you can track the progress u
9393

9494
After the Automation account is successfully unlinked from the workspace, perform the steps in the [standalone Automation account](#delete-a-standalone-automation-account) section to delete the account.
9595

96+
> [!NOTE]
97+
> A previously soft-deleted Log Analytics workspace can't be unlinked from the Automation account successfully. In this scenario, first recover and permanently delete it to forcefully remove the link. Learn [how to recover a workspace in a soft-delete state](/azure/azure-monitor/logs/delete-workspace#recover-a-workspace-in-a-soft-delete-state) and [delete it permanently](/azure/azure-monitor/logs/delete-workspace#delete-a-workspace-permanently).
98+
9699
## Delete a shared capability Automation account
97100

98101
To delete your Automation account linked to a Log Analytics workspace in support of Update Management, Change Tracking and Inventory, and/or Start/Stop VMs during off-hours, perform the following steps.

articles/azure-functions/functions-create-first-function-bicep.md

Lines changed: 75 additions & 46 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,24 @@
11
---
22
title: Create your function app resources in Azure using Bicep
33
description: Create and deploy to Azure a simple HTTP triggered serverless function using Bicep.
4-
author: mijacobs
5-
ms.author: mijacobs
6-
ms.date: 06/12/2022
4+
author: ggailey777
5+
ms.author: glenga
6+
ms.date: 03/17/2025
77
ms.topic: quickstart
88
ms.service: azure-functions
9+
zone_pivot_groups: programming-languages-set-functions
910
ms.custom: subject-armqs, mode-arm, devx-track-bicep
1011
---
1112

1213
# Quickstart: Create and deploy Azure Functions resources using Bicep
1314

14-
In this article, you use Azure Functions with Bicep to create a function app and related resources in Azure. The function app provides an execution context for your function code executions.
15+
In this article, you use Bicep to create a function app in a Flex Consumption plan in Azure, along with its required Azure resources. The function app provides a serverless execution context for your function code executions. The app uses Microsoft Entra ID with managed identities to connect to other Azure resources.
1516

1617
Completing this quickstart incurs a small cost of a few USD cents or less in your Azure account.
1718

1819
[!INCLUDE [About Bicep](~/reusable-content/ce-skilling/azure/includes/resource-manager-quickstart-bicep-introduction.md)]
1920

20-
After you create the function app, you can deploy Azure Functions project code to that app.
21+
After you create the function app, you can deploy your Azure Functions project code to that app. A final code deployment step is outside the scope of this quickstart article.
2122

2223
## Prerequisites
2324

@@ -27,56 +28,103 @@ Before you begin, you must have an Azure account with an active subscription. [C
2728

2829
## Review the Bicep file
2930

30-
The Bicep file used in this quickstart is from [Azure Quickstart Templates](https://azure.microsoft.com/resources/templates/function-app-create-dynamic/).
31+
The Bicep file used in this quickstart is from an [Azure Quickstart Template](https://azure.microsoft.com/resources/templates/function-app-create-dynamic/).
3132

32-
:::code language="bicep" source="~/quickstart-templates/quickstarts/microsoft.web/function-app-create-dynamic/main.bicep":::
33+
:::code language="bicep" source="~/quickstart-templates/quickstarts/microsoft.web/function-app-flex-managed-identities/main.bicep":::
3334

34-
The following four Azure resources are created by this Bicep file:
35+
This deployment file creates these Azure resources needed by a function app that securely connects to Azure services:
3536

36-
+ [**Microsoft.Storage/storageAccounts**](/azure/templates/microsoft.storage/storageaccounts): create an Azure Storage account, which is required by Functions.
37-
+ [**Microsoft.Web/serverfarms**](/azure/templates/microsoft.web/serverfarms): create a serverless Consumption hosting plan for the function app.
38-
+ [**Microsoft.Web/sites**](/azure/templates/microsoft.web/sites): create a function app.
39-
+ [**microsoft.insights/components**](/azure/templates/microsoft.insights/components): create an Application Insights instance for monitoring.
37+
[!INCLUDE [functions-azure-resources-list](../../includes/functions-azure-resources-list.md)]
4038

41-
[!INCLUDE [functions-storage-access-note](../../includes/functions-storage-access-note.md)]
39+
[!INCLUDE [functions-deployment-considerations-infra](../../includes/functions-deployment-considerations-infra.md)]
4240

4341
## Deploy the Bicep file
4442

4543
1. Save the Bicep file as **main.bicep** to your local computer.
46-
1. Deploy the Bicep file using either Azure CLI or Azure PowerShell.
4744

48-
# [CLI](#tab/CLI)
45+
1. Deploy the Bicep file using either Azure CLI or Azure PowerShell.
4946

47+
### [Azure CLI](#tab/azure-cli)
48+
::: zone pivot="programming-language-csharp"
5049
```azurecli
51-
az group create --name exampleRG --location eastus
52-
az deployment group create --resource-group exampleRG --template-file main.bicep --parameters appInsightsLocation=<app-location>
50+
az group create --name exampleRG --location <SUPPORTED_REGION>
51+
az deployment group create --resource-group exampleRG --template-file main.bicep --parameters functionAppRuntime=dotnet-isolated functionAppRuntimeVersion=8.0
5352
```
53+
::: zone-end
54+
::: zone pivot="programming-language-java"
55+
```azurecli
56+
az group create --name exampleRG --location <SUPPORTED_REGION>
57+
az deployment group create --resource-group exampleRG --template-file main.bicep --parameters functionAppRuntime=java functionAppRuntimeVersion=17
58+
```
59+
::: zone-end
60+
::: zone pivot="programming-language-javascript,programming-language-typescript"
61+
```azurecli
62+
az group create --name exampleRG --location <SUPPORTED_REGION>
63+
az deployment group create --resource-group exampleRG --template-file main.bicep --parameters functionAppRuntime=node functionAppRuntimeVersion=20
64+
```
65+
::: zone-end
66+
::: zone pivot="programming-language-python"
67+
```azurecli
68+
az group create --name exampleRG --location <SUPPORTED_REGION>
69+
az deployment group create --resource-group exampleRG --template-file main.bicep --parameters functionAppRuntime=python functionAppRuntimeVersion=3.11
70+
```
71+
::: zone-end
72+
::: zone pivot="programming-language-powershell"
73+
```azurecli
74+
az group create --name exampleRG --location <SUPPORTED_REGION>
75+
az deployment group create --resource-group exampleRG --template-file main.bicep --parameters functionAppRuntime=powerShell functionAppRuntimeVersion=7.4
76+
```
77+
::: zone-end
78+
### [Azure PowerShell](#tab/azure-powershell)
5479
55-
# [PowerShell](#tab/PowerShell)
56-
80+
::: zone pivot="programming-language-csharp"
81+
```azurepowershell
82+
New-AzResourceGroup -Name exampleRG -Location <SUPPORTED_REGION>
83+
New-AzResourceGroupDeployment -ResourceGroupName exampleRG -TemplateFile ./main.bicep -functionAppRuntime "dotnet-isolated" -functionAppRuntimeVersion "8.0"
84+
```
85+
::: zone-end
86+
::: zone pivot="programming-language-java"
5787
```azurepowershell
58-
New-AzResourceGroup -Name exampleRG -Location eastus
59-
New-AzResourceGroupDeployment -ResourceGroupName exampleRG -TemplateFile ./main.bicep -appInsightsLocation "<app-location>"
88+
New-AzResourceGroup -Name exampleRG -Location <SUPPORTED_REGION>
89+
New-AzResourceGroupDeployment -ResourceGroupName exampleRG -TemplateFile ./main.bicep -functionAppRuntime "java" -functionAppRuntimeVersion "17"
6090
```
91+
::: zone-end
92+
::: zone pivot="programming-language-javascript,programming-language-typescript"
93+
```azurepowershell
94+
New-AzResourceGroup -Name exampleRG -Location <SUPPORTED_REGION>
95+
New-AzResourceGroupDeployment -ResourceGroupName exampleRG -TemplateFile ./main.bicep -functionAppRuntime "node" -functionAppRuntimeVersion "20"
96+
```
97+
::: zone-end
98+
::: zone pivot="programming-language-python"
99+
```azurepowershell
100+
New-AzResourceGroup -Name exampleRG -Location <SUPPORTED_REGION>
101+
New-AzResourceGroupDeployment -ResourceGroupName exampleRG -TemplateFile ./main.bicep -functionAppRuntime "python" -functionAppRuntimeVersion "3.11"
102+
```
103+
::: zone-end
104+
::: zone pivot="programming-language-powershell"
105+
```azurepowershell
106+
New-AzResourceGroup -Name exampleRG -Location <SUPPORTED_REGION>
107+
New-AzResourceGroupDeployment -ResourceGroupName exampleRG -TemplateFile ./main.bicep -functionAppRuntime "powershell" -functionAppRuntimeVersion "7.4"
108+
```
109+
::: zone-end
61110
62111
---
63112
64-
> [!NOTE]
65-
> Replace **\<app-location\>** with the region for Application Insights, which is usually the same as the resource group.
113+
In this example, replace `<SUPPORTED_REGION>` with a region that [supports the Flex Consumption plan](./flex-consumption-how-to.md#view-currently-supported-regions).
66114
67115
When the deployment finishes, you should see a message indicating the deployment succeeded.
68116
69117
## Validate the deployment
70118
71119
Use Azure CLI or Azure PowerShell to validate the deployment.
72120
73-
# [CLI](#tab/CLI)
121+
### [Azure CLI](#tab/azure-cli)
74122
75123
```azurecli-interactive
76124
az resource list --resource-group exampleRG
77125
```
78126

79-
# [PowerShell](#tab/PowerShell)
127+
### [Azure PowerShell](#tab/azure-powershell)
80128

81129
```azurepowershell-interactive
82130
Get-AzResource -ResourceGroupName exampleRG
@@ -88,28 +136,9 @@ Get-AzResource -ResourceGroupName exampleRG
88136

89137
## Clean up resources
90138

91-
If you continue to the next step and add an Azure Storage queue output binding, keep all your resources in place as you'll build on what you've already done.
92-
93-
Otherwise, if you no longer need the resources, use Azure CLI, PowerShell, or Azure portal to delete the resource group and its resources.
94-
95-
# [CLI](#tab/CLI)
96-
97-
```azurecli-interactive
98-
az group delete --name exampleRG
99-
```
100-
101-
# [PowerShell](#tab/PowerShell)
102-
103-
```azurepowershell-interactive
104-
Remove-AzResourceGroup -Name exampleRG
105-
```
106-
107-
---
139+
[!INCLUDE [functions-cleanup-resources-infra](../../includes/functions-cleanup-resources-infra.md)]
108140

109141
## Next steps
110142

111-
Now that you've created your function app resources in Azure, you can deploy your code to the existing app by using one of the following tools:
143+
[!INCLUDE [functions-quickstarts-infra-next-steps](../../includes/functions-quickstarts-infra-next-steps.md)]
112144

113-
* [Visual Studio Code](functions-develop-vs-code.md#republish-project-files)
114-
* [Visual Studio](functions-develop-vs.md#publish-to-azure)
115-
* [Azure Functions Core Tools](functions-run-local.md#publish)

0 commit comments

Comments
 (0)