Admin: Auto Shutdown Settings

Auto Shutdown settings govern virtual machine visibility, auto-enrollment tags, default power schedules, and the access role used for scheduling. This section also includes optional System Center Operations Manager (SCOM) maintenance hooks for scheduled power actions.

Core Auto Shutdown Controls

• Show All Virtual Machines: controls whether the scheduling experience lists all VMs visible to AZExecute.

• Custom VM Access Role Name: names the Azure custom role used to grant scheduling access.

• Auto Enrollment Enabled: allows matching resources to receive default scheduling behavior automatically.

• Enrollment Tag Name and Value: define which resources are picked up by auto-enrollment.

• Enforce Tag Name and Value: define the tag that prevents users from disabling enforced schedules.

• Owner tag key: maps tagged resource groups to owners when that metadata is available.

• Power On and Power Off: default times applied by the auto-enrollment configuration.

SCOM Integration Controls

The Auto Shutdown SCOM tab configures optional maintenance-mode runbooks for scheduled power workflows. It uses selected Azure Automation runbooks and optional Hybrid Worker Groups, not direct SCOM HTTP credentials.

• SCOM Integration: enables or disables auto-shutdown maintenance-mode hooks.

• SCOM Start Runbook: Azure Automation runbook used to start maintenance mode.

• SCOM Stop Runbook: Azure Automation runbook used to stop maintenance mode.

• RunOn selection: optional Hybrid Worker Group for the start and stop runbooks, or Default for Azure execution.

Auto-shutdown runbooks must expose a ServerName parameter before they can be selected. Built-in SCOM maintenance mode task steps are configured separately under Tenant Admin > Integrations > SCOM and run through a connected Windows agent with the OperationsManager PowerShell module.

Recommended Rollout

1. Confirm the custom VM access role and tenant access checks before broad rollout.

2. Pilot auto-enrollment with explicit enrollment tags on a non-critical resource group.

3. Validate Power On and Power Off behavior against the tenant's expected operating hours.

4. Add enforcement tags only after the schedule policy has been signed off.

5. If SCOM maintenance hooks are enabled, test both start and stop runbooks with the same ServerName input used by schedules.