You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/automation/delete-account.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: This article tells how to delete and your Automation account across
4
4
services: automation
5
5
ms.service: azure-automation
6
6
ms.subservice: process-automation
7
-
ms.date: 12/28/2024
7
+
ms.date: 03/20/2025
8
8
ms.topic: how-to
9
9
---
10
10
@@ -93,6 +93,9 @@ While it attempts to unlink the Automation account, you can track the progress u
93
93
94
94
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.
95
95
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
+
96
99
## Delete a shared capability Automation account
97
100
98
101
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.
# Quickstart: Create and deploy Azure Functions resources using Bicep
13
14
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.
15
16
16
17
Completing this quickstart incurs a small cost of a few USD cents or less in your Azure account.
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.
21
22
22
23
## Prerequisites
23
24
@@ -27,56 +28,103 @@ Before you begin, you must have an Azure account with an active subscription. [C
27
28
28
29
## Review the Bicep file
29
30
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/).
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:
35
36
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.
> 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).
66
114
67
115
When the deployment finishes, you should see a message indicating the deployment succeeded.
68
116
69
117
## Validate the deployment
70
118
71
119
Use Azure CLI or Azure PowerShell to validate the deployment.
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.
0 commit comments