---
title: "Azure Integration: Administration"
slug: "azure-integration-administration"
updated: 2025-07-02T16:32:36Z
published: 2025-07-02T16:32:36Z
canonical: "support.controlup.com/azure-integration-administration"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.controlup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Azure Integration: Administration

The Azure integration makes it easy to run machine actions on your Azure VMs. We defined a preset of 5 different machine actions that you can run on one or more Azure VMs at the same time. This article describes different machine actions and shows how to run a machine action on a specific machine.

## Machine Actions Overview

| Action Name | Description |
| --- | --- |
| Power Off (Stop) | Powers off the Azure VM and you can restart the VM with the same provisioned resources. You will be charged for this VM even when the VM is stopped. To avoid being charged for the VM, use the Stop (Deallocate) machine action. |
| Reapply | Reapplies the Azure VM's state. |
| Restart | Restarts the Azure VM. |
| Start | Starts the Azure VM. |
| Stop (Deallocate) | Shuts down the Azure VM and releases the computer's resources of this VM. Once the VM is in the stopped (deallocate) state, you will not be charged for the VM resources. Note that you are still charged for storage costs if you want the disk to persist. |

## Run a Machine Action

**To run a machine action on an Azure VM:**

1. Open your Real-Time Console and connect to your Azure subscription.
2. Under the **Machines** tab, right-click the Azure VM > **Cloud Management** > select the action you want to run on the machine.  
![Right-click action menu. The Cloud Management action are highlighted: Power Off, Reapply Azure Machine, Restart, Start, Stop](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/001_AzureMachineActions(1).jpg)You can run a machine action on multiple Azure virtual machines. While holding the Shift key, mark the VMs and run Step 2.

## New Security Policy Actions

The [Security Policy Pane](/tim-reorg/docs/security-policy-pane) in the Real-Time Console introduces new security permissions for [machine actions.](/docs/azure-integration-administration) The table below shows the default permission set for each pre-defined ControlUp user role. By default, **Organization Members** and **ControlUp Admins** are allowed to perform Azure machine actions.

|  | Local Admins | Organization Members | ControlUp Monitors | Automation Admins | ControlUp Admins | Helpdesk | New roles |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Reboot | N/A | Allow | N/A | Not set | Allow | Not set | Not set |
| Start | N/A | Allow | N/A | Not set | Allow | Not set | Not set |
| Power Off (Stop) | N/A | Allow | N/A | Not set | Allow | Not set | Not set |
| Reapply Azure Machine State | N/A | Allow | N/A | Not set | Allow | Not set | Not set |
| Stop (Deallocate) VM | N/A | Allow | N/A | Not set | Allow | Not set | Not set |