Enterprise VM telemetry with
Azure Monitor
For corporate agencies and IT teams managing client WordPress workloads on Microsoft Azure Virtual Machines. Clockwork Control authenticates via Entra ID (Azure AD) Service Principals and queries Azure Monitor metrics without installing OS agents.
Entra ID SP Auth
Uses OAuth2 Service Principal credentials (Tenant ID, App ID, Secret) with strict least-privilege Reader role permissions.
Azure Monitor Metrics
Directly queries ARM metric endpoints for Percentage CPU and Available Memory Bytes.
Multi-Subscription
Supports enterprise Azure subscriptions with multiple resource groups and cross-region virtual machines.
Zero OS Agent
Reads telemetry directly from the Azure hypervisor plane without installing agents or extensions inside guest operating systems.
Help us test Azure Monitor with live enterprise VMs
The Azure Monitor module is verified in sandbox with Entra ID Service Principals — but we haven’t polled live production Azure virtual machines yet. Run client workloads on Azure? Check out our Contributing Guide to test endpoints for your agency, vibe code any fixes with Claude, and submit a pull request!
Microsoft Azure VM metrics without complex Log Analytics setup
Enterprise Azure accounts often involve separate resource groups and complicated Log Analytics workspaces. Clockwork Control simplifies VM visibility by talking directly to Azure Monitor REST APIs using standard OAuth2 client credentials.
# Authenticating via Entra ID Service Principal & polling ARM:
$ php artisan clockwork:poll-azure-metrics
• Requesting OAuth2 bearer token from login.microsoftonline.com...
• Authenticated as Service Principal (Tenant: agency-corp.onmicrosoft.com)
• Scanning Resource Group: rg-client-production (Subscription: sub-881a)
• VM vm-wordpress-eastus (Standard_D4s_v5): CPU 16.2% • RAM: 11.4GB Avail
• Matched IP 20.121.45.109 to client host
• Telemetry saved to time-series store
• Polling complete: Azure VM telemetry healthy • Status: OK
Azure standalone vs. Azure + Clockwork Control
Clockwork Control gives agency CTOs high-level oversight across Azure VMs alongside the rest of their hosting fleet.
| Capability | Azure Standalone | With Clockwork Control Panel |
|---|---|---|
| Virtual Machine Metrics | Azure Portal Metric Explorer & Log Analytics workspaces | ✓Direct Azure Monitor polling every 5 minutes integrated with your WordPress site health |
| Enterprise Authentication | Azure Role-Based Access Control (RBAC) & Entra ID | ✓OAuth2 Service Principal flow (Tenant ID, Client ID, Client Secret, Subscription ID) |
| Non-Invasive Hypervisor Metrics | Requires Azure Monitor Agent (AMA) extension on VMs for detailed OS stats | ✓Pulls Percentage CPU and Available Memory Bytes directly from host hypervisor plane without agents |
| Agency Fleet Integration | Isolated Azure subscription view | ✓View Azure VMs right alongside DigitalOcean, Hetzner, Vultr, Linode, and managed hosts |
| Application-to-VM Linkage | Manual resource group tagging | ✓Automated IP reconciliation mapping client WordPress domains to Azure VM public IPs |
| Monitoring Cost | Log Analytics data ingestion and metric retention fees | ✓100% Free & Open-Source (MIT) — unmetered VMs and unmetered sites |
Help test the Azure Monitor module
The Azure Monitor module is verified in sandbox environments. We are actively seeking enterprise agency testers running multi-VM Azure workloads to validate live production polling.
# Set Azure Service Principal credentials in .env:
AZURE_TENANT_ID=your_tenant_id_here
AZURE_CLIENT_ID=your_client_id_here
AZURE_CLIENT_SECRET=your_client_secret_here
AZURE_SUBSCRIPTION_ID=your_subscription_id_here
# Test Azure connection and poll telemetry:
$ php artisan clockwork:poll-azure-metrics
