Proposed Pull Request Change

📄 Document Links

View on GitHub View on Microsoft Learn

--- title: Azure billing and cost management budget scenario description: Learn how to use Azure Automation to shut down VMs based on specific budget thresholds. author: vikramdesai01 ms.reviewer: vikdesai ms.service: cost-management-billing ms.subservice: cost-management ms.topic: how-to ms.date: 06/26/2025 ms.author: vikdesai ms.custom: sfi-image-nochange --- # Manage costs with budgets Cost control is a critical component to maximizing the value of your investment in the cloud. There are several scenarios where cost visibility, reporting, and cost-based orchestration are critical to continued business operations. [Cost Management APIs](/rest/api/consumption/) provide a set of APIs to support each of these scenarios. The APIs provide usage details, allowing you to view granular instance level costs. Budgets are commonly used as part of cost control. Budgets can be scoped in Azure. For instance, you could narrow your budget view based on subscription, resource groups, or a collection of resources. Besides using the budgets API to send email notifications when a budget threshold is reached, you can also use [Azure Monitor action groups](/azure/azure-monitor/alerts/action-groups). Action groups trigger a coordinated set of actions in response to a budget event. A typical budget scenario for a customer running a noncritical workload is to manage spending against a budget and achieve predictable costs when reviewing the monthly invoice. This scenario requires some cost-based orchestration of resources that are part of the Azure environment. In this scenario, a monthly budget of $1,000 for the subscription is set. Also, notification thresholds are set to trigger a few orchestrations. This scenario starts with an 80% cost threshold, which stops all virtual machines (VM) in the resource group **Optional**. Then, at the 100% cost threshold, all VM instances are stopped. To configure this scenario, you complete the following actions by using the steps provided in each section of this tutorial. These actions included in this tutorial allow you to: - Create an Azure Automation Runbook to stop VMs by using webhooks. - Create an Azure Logic App to be triggered based on the budget threshold value and call the runbook with the right parameters. - Create an Azure Monitor Action Group that is configured to trigger the Azure Logic App when the budget threshold is met. - Create the budget with the wanted thresholds and wire it to the action group. ## Create an Azure Automation Runbook [Azure Automation](../../automation/automation-intro.md) is a service that enables you to script most of your resource management tasks and run those tasks as either scheduled or on-demand. As part of this scenario, you create an [Azure Automation runbook](../../automation/automation-runbook-types.md) that stops VMs. You use the [Stop Azure V2 VMs](https://github.com/azureautomation/stop-azure-v2-vms) graphical runbook from the [Azure Automation gallery](https://github.com/azureautomation) to build this scenario. By importing this runbook into your Azure account and publishing it, you can stop VMs when a budget threshold is reached. > [!NOTE] > You can create a budget in Azure Cost Management and link it to an Azure Automation runbook to automatically stop resources when a specified threshold is reached. ### Create an Azure Automation account 1. Sign in to the [Azure portal](https://portal.azure.com/) with your Azure account credentials. 2. Select the **Create a resource** button found on the upper left corner of Azure. 3. Select **Management Tools** > **Automation**. > [!NOTE] > If you don't have an Azure account, you can create a [free account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn). 4. Enter your account information. For **Create Azure Run As account**, choose **Yes** to automatically enable the settings needed to simplify authentication to Azure. 5. When complete, select **Create**, to start the Automation account deployment. ### Import the Stop Azure V2 VMs runbook Using an [Azure Automation runbook](../../automation/automation-runbook-types.md), import the [Stop Azure V2 VMs](https://github.com/azureautomation/stop-azure-v2-vms) graphical runbook from the gallery. 1. Sign in to the [Azure portal](https://portal.azure.com/) with your Azure account credentials. 1. Open your Automation account by selecting **All services** > **Automation Accounts**. Then, select your Automation Account. 1. Select **Runbooks gallery** from the **Process Automation** section. 1. Set the **Gallery Source** to **Script Center** and select **OK**. 1. Locate and select the [Stop Azure V2 VMs](https://github.com/azureautomation/stop-azure-v2-vms) gallery item within the Azure portal. 1. Select **Import** to display the **Import** area and select **OK**. The runbook overview area gets displayed. 1. Once the runbook completes the import process, select **Edit** to display the graphical runbook editor and publishing option. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-01.png" alt-text="Screenshot showing Edit graphical runbook."::: 1. Select **Publish** to publish the runbook and then select **Yes** when prompted. When you publish a runbook, you override any existing published version with the draft version. In this case, you have no published version because you created the runbook. For more information about publishing a runbook, see [Create a graphical runbook](../../automation/learn/powershell-runbook-managed-identity.md). ## Create webhooks for the runbook Using the [Stop Azure V2 VMs](https://github.com/azureautomation/stop-azure-v2-vms) graphical runbook, you create two Webhooks to start the runbook in Azure Automation through a single HTTP request. The first webhook invokes the runbook at an 80% budget threshold with the resource group name as a parameter, allowing the optional VMs to be stopped. Then, the second webhook invokes the runbook with no parameters (at 100%), which stops all remaining VM instances. 1. From the **Runbooks** page in the [Azure portal](https://portal.azure.com/), select the **StopAzureV2Vm** runbook that displays the runbook's overview area. 1. Select **Webhook** at the top of the page to open the **Add Webhook** area. 1. Select **Create new webhook** to open the **Create a new webhook** area. 1. Set the **Name** of the Webhook to **Optional**. The **Enabled** property must be **Yes**. You don't need to change the **Expires** value. For more information about Webhook properties, see [Webhook properties](../../automation/automation-webhooks.md#webhook-properties). 1. Next to the URL value, select the copy icon to copy the URL of the webhook. > [!IMPORTANT] > Save the URL of the webhook named **Optional** in a safe place. You'll use the URL later in this tutorial. For security reasons, once you create the webhook, you cannot view or retrieve the URL again. 1. Select **OK** to create the new webhook. 1. Select **Configure parameters and run settings** to view parameter values for the runbook. > [!NOTE] > If the runbook has mandatory parameters, then you are not able to create the webhook unless values are provided. 1. Select **OK** to accept the webhook parameter values. 1. Select **Create** to create the webhook. 1. Next, follow the preceding steps to create a second webhook named **Complete**. > [!IMPORTANT] > Be sure to save both webhook URLs to use later in this tutorial. For security reasons, once you create the webhook, you cannot view or retrieve the URL again. You should now have two configured webhooks that are each available using the URLs that you saved. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-02.png" alt-text="Screenshot showing Webhooks."::: You completed the Azure Automation setup. You can test the webhooks with a simple API test to validate that the webhook works. Some popular ways to query the API are: - [Visual Studio](/aspnet/core/test/http-files) - [Insomnia](https://insomnia.rest/) - [Bruno](https://www.usebruno.com/) - PowerShell’s [Invoke-RestMethod](https://powershellcookbook.com/recipe/Vlhv/interact-with-rest-based-web-apis) - [Curl](https://curl.se/docs/httpscripting.html) Next, you must create the Logic App for orchestration. ## Create an Azure Logic App for orchestration Logic Apps helps you build, schedule, and automate processes as workflows so you can integrate apps, data, systems, and services across enterprises or organizations. In this scenario, the [Logic App](../../logic-apps/index.yml) you create does a little more than just call the automation webhook you created. Budgets can be set up to trigger a notification when a specified threshold is met. You can provide multiple thresholds to be notified at and the Logic App demonstrates the ability for you to perform different actions based on the threshold met. In this example, you set up a scenario where you get a couple of notifications. The first notification is for when 80% of the budget is reached. The second notification is when 100% of the budget is reached. The logic app is used to shut down all VMs in the resource group. First, the **Optional** threshold is reached at 80%, then the second threshold is reached where all VMs in the subscription get shutdown. Logic apps allow you to provide a sample schema for the HTTP trigger, but require you to set the **Content-Type** header. Because the action group doesn't have custom headers for the webhook, you must parse out the payload in a separate step. You use the **Parse** action and provide it with a sample payload. ### Create the logic app The logic app performs several actions. The following list provides a high-level set of actions that the logic app performs: - Recognizes when an HTTP request is received - Parse the passed in JSON data to determine the threshold value that is reached - Use a conditional statement to check whether the threshold amount reached 80% or more of the budget range, but not greater than or equal to 100%. - If this threshold amount is reached, send an HTTP POST using the webhook named **Optional**. This action shuts down the VMs in the "Optional" group. - Use a conditional statement to check whether the threshold amount reached or exceeded 100% of the budget value. - If the threshold amount is reached, send an HTTP POST using the webhook named **Complete**. This action shuts down all remaining VMs. The following steps are needed to create the logic app that performs the preceding steps: 1. In the [Azure portal](https://portal.azure.com/), select **Create a resource** > **Integration** > **Logic App**. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-03.png" alt-text="Screenshot showing Select the Logic App resource."::: 1. In the **Create logic app** area, provide the details need to create your logic app, select **Pin to dashboard**, and select **Create**. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-03a.png" alt-text="Screenshot showing Create a Logic App."::: After Azure deploys your logic app, the **Logic Apps Designer** opens and shows an area with an introduction video and commonly used triggers. ### Add a trigger Every logic app must start with a trigger, which fires when a specific event happens or when a specific condition is met. Each time the trigger fires, the Logic Apps engine creates a logic app instance that starts and runs your workflow. Actions are all the steps that happen after the trigger. 1. Under **Templates** of the **Logic Apps Designer** area, choose **Blank Logic App**. 1. Add a [trigger](../../logic-apps/logic-apps-overview.md#logic-app-concepts) by entering "http request" in the **Logic Apps Designer** search box to find and select the trigger named **Request – When an HTTP request is received**. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-04.png" alt-text="Screenshot showing the When an HTTP request is received trigger."::: 1. Select **New step** > **Add an action**. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-05.png" alt-text="Screenshot showing New step - Add an action."::: 1. Search for "parse JSON" in the **Logic Apps Designer** search box to find and select the **Data Operations - Parse JSON** [action](../../logic-apps/logic-apps-overview.md#logic-app-concepts). :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-06.png" alt-text="Screenshot showing data operations - parse JSON."::: 1. Enter "Payload" as the **Content** name for the Parse JSON payload or use the "Body" tag from dynamic content. 1. Select the **Use sample payload to generate schema** option in the **Parse JSON** box. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-07.png" alt-text="Screenshot showing Use sample JSON data to generate schema payload."::: 1. Paste the following JSON sample payload into the textbox: `{"schemaId":"AIP Budget Notification","data":{"SubscriptionName":"CCM - Microsoft Azure Enterprise - 1","SubscriptionId":"<GUID>","SpendingAmount":"100","BudgetStartDate":"6/1/2018","Budget":"50","Unit":"USD","BudgetCreator":"email@contoso.com","BudgetName":"BudgetName","BudgetType":"Cost","ResourceGroup":"","NotificationThresholdAmount":"0.8"}}` The textbox appears as: :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-08.png" alt-text="Screenshot showing sample JSON payload."::: 1. Select **Done**. ### Add the first conditional action Use a conditional statement to check whether the threshold amount reached 80% or more of the budget range, but not greater than or equal to 100%. If this threshold amount is reached, send an HTTP POST using the webhook named **Optional**. This action shuts down the VMs in the **Optional** group. 1. Select **New step** > **Add a condition**. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-09.png" alt-text="Screenshot showing Add a condition."::: 1. In the **Condition** box, select the textbox containing `Choose a value` to display a list of available values. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-10.png" alt-text="Screenshot showing Choose a value condition."::: 1. Select **Expression** at the top of the list and enter the following expression in the expression editor: `float()` :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-11.png" alt-text="Screenshot showing the Float expression."::: 1. Select **Dynamic content**, place the cursor inside the parenthesis (), and select **NotificationThresholdAmount** from the list to populate the complete expression. The expression is:<br> `float(body('Parse_JSON')?['data']?['NotificationThresholdAmount'])` 1. Select **OK** to set the expression. 1. Select **is greater than or equal to** in the dropdown box of the **Condition**. 1. In the **Choose a value** box of the condition, enter `.8`. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-12.png" alt-text="Screenshot showing the Condition dialog box with values selected."::: 1. Select **Add** > **Add row** within the Condition box to add another part of the condition. 1. In the **Condition** box, select the textbox containing `Choose a value`. 1. Select **Expression** at the top of the list and enter the following expression in the expression editor: `float()` 1. Select **Dynamic content**, place the cursor inside the parenthesis (), and select **NotificationThresholdAmount** from the list to populate the complete expression. 1. Select **OK** to set the expression. 1. Select **is less than** in the dropdown box of the **Condition**. 1. In the **Choose a value** box of the condition, enter `1`. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-13.png" alt-text="Screenshot showing the Condition dialog box with two conditions."::: 1. In the **If true** box, select **Add an action**. You add an HTTP POST action that shuts down optional VMs. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-14.png" alt-text="Screenshot showing Add an action."::: 1. Enter **HTTP** to search for the HTTP action and select the **HTTP – HTTP** action. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-15.png" alt-text="Screenshot showing Add HTTP action."::: 1. Select **Post** for the **Method** value. 1. Enter the URL for the webhook named **Optional** that you created earlier in this tutorial as the **Uri** value. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-16.png" alt-text="Screenshot showing the HTTP action URI."::: 1. Select **Add an action** in the **If true** box. You add an email action that sends an email notifying the recipient that the optional VMs were shut down. 1. Search for "send email" and select a *send email* action based on the email service you use. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-17.png" alt-text="Screenshot showing the Send email action."::: For personal Microsoft accounts, select **Outlook.com**. For Azure work or school accounts, select **Office 365 Outlook**. If you don't already have a connection, you get asked to sign in to your email account. Logic Apps creates a connection to your email account. You need to allow the Logic App to access your email information. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-18.png" alt-text="Screenshot showing the access notice."::: 1. Add the **To**, **Subject**, and **Body** text for the email that notifies the recipient that the optional VMs were shut down. Use the **BudgetName** and the **NotificationThresholdAmount** dynamic content to populate the subject and body fields. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-19.png" alt-text="Screenshot showing Email details."::: ### Add the second conditional action Use a conditional statement to check whether the threshold amount reached or exceeded 100% of the budget value. If the threshold amount is reached, send an HTTP POST using the webhook named **Complete**. This action shuts down all remaining VMs. 1. Select **New step** > **Add a Condition**. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-20.png" alt-text="Screenshot showing the If true dialog box with Add an action called out."::: 1. In the **Condition** box, select the textbox containing `Choose a value` to display a list of available values. 1. Select **Expression** at the top of the list and enter the following expression in the expression editor: `float()` 1. Select **Dynamic content**, place the cursor inside the parenthesis (), and select **NotificationThresholdAmount** from the list to populate the complete expression. The expression resembles:<br> `float(body('Parse_JSON')?['data']?['NotificationThresholdAmount'])` 1. Select **OK** to set the expression. 1. Select **is greater than or equal to** in the dropdown box of the **Condition**. 1. In the **Choose a value box** for the condition, enter `1`. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-21.png" alt-text="Screenshot showing the Set condition value."::: 1. In the **If true** box, select **Add an action**. You add an HTTP POST action that shuts down all the remaining VMs. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-22.png" alt-text="Screenshot showing the If true dialog box with where you can add an H T T P POST action."::: 1. Enter **HTTP** to search for the HTTP action and select the **HTTP – HTTP** action. 1. Select **Post** as the **Method** value. 1. Enter the URL for the webhook named **Complete** that you created earlier in this tutorial as the **Uri** value. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-23.png" alt-text="Screenshot showing the H T T P dialog box where you can enter the U R L value."::: 1. Select **Add an action** in the **If true** box. You add an email action that sends an email notifying the recipient that the remaining VMs were shut down. 1. Search for "send email" and select a *send email* action based on the email service you use. 1. Add the **To**, **Subject**, and **Body** text for the email that notifies the recipient that the optional VMs were shut down. Use the **BudgetName** and the **NotificationThresholdAmount** dynamic content to populate the subject and body fields. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-24.png" alt-text="Screenshot showing the email details that you configured."::: 1. Select **Save** at the top of the **Logic App Designer** area. ### Logic App summary Here's what your Logic App looks like when done. In the most basic of scenarios where you don't need any threshold-based orchestration, you could directly call the automation script from **Monitor** and skip the **Logic App** step. :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-25.png" alt-text="Screenshot showing the Logic app - complete view."::: When you saved your logic app, a URL was generated that you can call. You use this URL in the next section of this tutorial. ## Create an Azure Monitor Action Group An action group is a collection of notification preferences that you define. When an alert is triggered, a specific action group can receive the alert by being notified. An Azure alert proactively raises a notification based on specific conditions and provides the opportunity to take action. An alert can use data from multiple sources, including metrics and logs. Action groups are the only endpoint that you integrate with your budget. You can set up notifications in many channels, but for this scenario you focus on the Logic App you created earlier in this tutorial. ### Create an action group in Azure Monitor When you create the action group, you point to the Logic App that you created earlier in this tutorial. 1. If you aren't already signed-in to the [Azure portal](https://portal.azure.com/), sign in and select **All services** > **Monitor**. 1. Select **Alerts** then select **Manage actions**. 1. Select **Add an action group** from the **Action groups** area. 1. Add and verify the following items: - Action group name - Short name - Subscription - Resource group :::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-26.png" alt-text="Screenshot showing Add an action group."::: 1. Within the **Add action group** pane, add a LogicApp action. Name the action **Budget-BudgetLA**. In the **Logic App** pane, select the **Subscription** and the **Resource group**. Then, select the **Logic app** that you created earlier in this tutorial. 1. Select **OK** to set the Logic App. Then, select **OK** in the **Add action group** pane to create the action group. You completed all the supporting components that are needed to effectively orchestrate your budget. Now all you need to do is create the budget and configure it to use the action group you created. ## Create the budget You can create a budget in the Azure portal using the [Budget feature](../costs/tutorial-acm-create-budgets.md) in Cost Management. Or, you can create a budget using REST APIs, PowerShell cmdlets, or use the CLI. The following procedure uses the REST API. Before calling the REST API, you need an authorization token. To create an authorization token, you can use the [ARMClient](https://github.com/projectkudu/ARMClient) project. The **ARMClient** allows you to authenticate yourself to the Azure Resource Manager and get a token to call the APIs. ### Create an authentication token 1. Navigate to the [ARMClient](https://github.com/projectkudu/ARMClient) project on GitHub. 1. Clone the repo to get a local copy. 1. Open the project in Visual Studio and build it. 1. Once the build is successful, the executable should be in the *\bin\debug* folder. 1. Run the ARMClient. Open a command prompt and navigate to the *\bin\debug* folder from the project root. 1. To sign in and authenticate, enter the following command at the command prompt:<br> `ARMClient login prod` 1. Copy the **subscription guid** from the output. 1. To copy an authorization token to your clipboard, enter the following command at the command prompt, but sure to use the copied subscription ID from the preceding step: <br> `ARMClient token <subscription GUID from previous step>` When you complete the preceding step, you see:<br> **Token copied to clipboard successfully.** 1. Save the token to be used for steps in the next section of this tutorial. ### Create the Budget Next, you create a budget by calling the Azure Consumption REST APIs. You need a way to interact with APIs. Some popular ways to query the API are: - [Visual Studio](/aspnet/core/test/http-files) - [Insomnia](https://insomnia.rest/) - [Bruno](https://www.usebruno.com/) - PowerShell’s [Invoke-RestMethod](https://powershellcookbook.com/recipe/Vlhv/interact-with-rest-based-web-apis) - [Curl](https://curl.se/docs/httpscripting.html) You need to import both environment and collection files into your API client. The collection contains grouped definitions of HTTP requests that call Azure Consumption REST APIs. The environment file contains variables that are used by the collection. 1. In your API client, create a new request. 1. Save the new request so that it has nothing in it. 1. Change the request from a `Get` to a `Put` action. 1. Modify the following URL by replacing `{subscriptionId}` with the **Subscription ID** that you used in the previous section of this tutorial. Also, modify the URL to include "SampleBudget" as the value for `{budgetName}`: `https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.Consumption/budgets/{budgetName}?api-version=2018-03-31` 1. Select Headers in your API client. 1. Add a new **Key** named "Authorization". 1. Set the **Value** to the token that was created using the ArmClient at the end of the last section. 1. Select Body in your API client. 1. Select the **raw** option in your API client. 1. In the text area in your API client, paste the following sample budget definition. You must replace the `subscriptionID`, `resourcegroupname`, and `actiongroupname` parameters with your subscription ID, a unique name for your resource group, and the action group name you created in both the URL and the request body: ``` { "properties": { "category": "Cost", "amount": 100.00, "timeGrain": "Monthly", "timePeriod": { "startDate": "2018-06-01T00:00:00Z", "endDate": "2018-10-31T00:00:00Z" }, "filters": {}, "notifications": { "Actual_GreaterThan_80_Percent": { "enabled": true, "operator": "GreaterThan", "threshold": 80, "contactEmails": [], "contactRoles": [], "contactGroups": [ "/subscriptions/{subscriptionid}/resourceGroups/{resourcegroupname}/providers/microsoft.insights/actionGroups/{actiongroupname}" ] }, "Actual_EqualTo_100_Percent": { "operator": "EqualTo", "threshold": 100, "contactGroups": [ "/subscriptions/{subscriptionid}/resourceGroups/{resourcegroupname}/providers/microsoft.insights/actionGroups/{actiongroupname}" ] } } } } ``` 1. Send the request. You now have all the pieces you need to call the [budgets API](/rest/api/consumption/budgets). The budgets API reference has more details on the specific requests, including: - **budgetName** - Multiple budgets are supported. Budget names must be unique. - **category** - Must be either **Cost** or **Usage**. The API supports both cost and usage budgets. - **timeGrain** - A monthly, quarterly, or yearly budget. The amount resets at the end of the period. - **filters** - Filters allow you to narrow the budget to a specific set of resources within the selected scope. For example, a filter could be a collection of resource groups for a subscription level budget. - **notifications** – Determines the notification details and thresholds. You can set up multiple thresholds and provide an email address or an action group to receive a notification. ## Summary By using this tutorial, you learned: - How to create an Azure Automation Runbook to stop VMs. - How to create an Azure Logic App that is triggered based on the budget threshold values and call the related runbook with the right parameters. - How to create an Azure Monitor Action Group that was configured to trigger the Azure Logic App when the budget threshold is met. - How to create the budget with the desired thresholds and wire it to the action group. You now have a fully functional budget for your subscription that shuts down your VMs when you reach your configured budget thresholds. ## Next steps - For more information about Azure billing scenarios, see [Billing and cost management automation scenarios](cost-management-automation-scenarios.md).