--- title: "Configuring Management operations tasks" slug: "configuring-management-operations-tasks" updated: 2026-09-07T18:32:16Z published: 2026-09-07T18:32:16Z canonical: "docs.turbo360.com/configuring-management-operations-tasks" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.turbo360.com/llms.txt > Use this file to discover all available pages before exploring further. # Configuring Management operations tasks ## Overview Management operations is an automated task type in Business Applications that updates the runtime state of associated Azure resources on a schedule. You can use it to start, stop, enable, or disable supported resource types automatically, without switching to the Azure portal. ### Business value Manually managing the state of Azure resources across environments is time-consuming and error-prone. Management operations let you automate scheduled state changes such as stopping non-production resources overnight or enabling resources before business hours, reducing operational overhead and Azure spend. ## How it works Management operations work by targeting one or more resources of a supported type and applying a specified state change (for example, stopping a Logic App or disabling a Service Bus Queue) at a scheduled time. You define the resource type, the desired target state, and the set of resources to act on. The task runs on the configured schedule and notifies you of the outcome. The following resource types support Management operations automated tasks: - API App - APIM Product - Azure Function - Azure Function App - Databricks Compute Cluster - Databricks Delta Live Table - Event Hub - Kubernetes Service - Logic App - Logic App (Standard) - Logic App Workflow - Service Bus Queue - Service Bus Topic - Service Bus Topic Subscription - Virtual Machine - Web App - Web Jobs ## Steps Use the following steps to configure a Management operations task. Navigate to **Business Applications** > **Automated tasks** > **New configuration** to get started. ### Configure the resource state change Configuring the resource state change defines which resources the task targets and what state it applies when it executes. 1. Select **Management operations** from the **New configuration** dropdown. 2. Select the **resource type** you want to manage. 3. Select the **state to be set** from the dropdown options. 4. Select the resources for which the state should be updated. Note: Enable **Run task once immediately after saving** if you want the task to execute once immediately at save time, in addition to running on its configured schedule. 1. Click **Next**. ### Schedule the task Scheduling controls when the automated task runs and whether it repeats. 1. Configure the recurrence schedule for the task. 2. Enable the task to activate it. 3. Click **Next**. ### Alert configuration Notification settings control which channels and recipients receive alerts when the task completes or fails. 1. Select the notification channels you want to use. 2. Enter one or more email addresses to receive notifications. 3. Under **Advanced settings**, enable either or both of the following options as required: - **Send alerts only when the automated task fails:** notifications are sent only when the task itself fails to execute. - **Send alerts only when the completed count is greater than 0:** notifications are sent only when at least one resource state was successfully updated. 4. Click **Save**. Note: When both Advanced settings options are enabled, you receive a notification if the task fails **or** if at least one resource state was successfully updated. ## Troubleshooting 1. **Resource state is not updated after the task runs** Cause: The resource type selected does not support the target state, or the resource is locked by another process. Fix: Verify the state is valid for the selected resource type. Check the Azure portal for any resource locks or policy restrictions that may prevent state changes. 2. **The task runs but notifications are not received** Cause: No notification channels are configured, or the Advanced settings filters exclude the current task result. Fix: Confirm at least one notification channel is selected. If Advanced settings are enabled, verify that the task outcome matches the configured filter conditions. 3. **The task does not run immediately after saving** Cause: The **Run task once immediately after saving** option was not enabled during configuration. Fix: Edit the task and enable **Run task once immediately after saving**. The immediate execution only occurs at save time and cannot be triggered retroactively. 4. **The desired resource type is not available in the dropdown** Cause: The resource has not been associated with the Business Application, or the resource type is not supported by Management operations. Fix: Verify that the resource is associated with the Business Application. Confirm the resource type appears in the supported resource types list above. 5. **The task completes but no resources are updated** Cause: The selected resources are already in the target state, or resource selection was not completed during configuration. Fix: Verify the current state of the targeted resources in the Azure portal. Edit the task to confirm the resource selection is complete and the target state differs from the current state. ## FAQs 1. **Can I target resources of different types in a single Management operations task?** No. Each Management operations task is scoped to one resource type. To manage multiple resource types on the same schedule, create a separate task configuration for each type. 2. **Can I schedule both a start and a stop operation for the same resource?** Yes. Create two separate Management operations tasks for the same resource: one configured to set the enabled or started state, and another to set the disabled or stopped state. Assign each task its own schedule to control the on and off windows. 3. **What happens if a resource is already in the target state when the task runs?** The task completes with a completion count of 0 and no error is recorded. Resources already in the target state are skipped. This is expected behavior and does not indicate a failure. ## Related articles - [What is an automated task?](https://docs.turbo360.com/docs/what-is-automated-task) - [Scheduling an automated task](https://docs.turbo360.com/docs/scheduling-an-automated-task) - [Task history](https://docs.turbo360.com/docs/task-history) - [Configuring Data Factory Pipeline automated tasks](https://docs.turbo360.com/docs/configuring-data-factory-pipeline-automated-tasks) - [Configuring Synapse Pipeline automated tasks](https://docs.turbo360.com/docs/configuring-synapse-pipeline-automated-tasks)