Azure

What This Skill Does

The Azure skill for OpenClaw provides an intelligent interface to deploy, monitor, and optimize your Microsoft Azure cloud footprint. Built on a foundation of "battle-tested" production rules, this skill acts as your architectural advisor, ensuring that your infrastructure adheres to best practices regarding cost optimization, security boundaries, and performance tuning. It helps navigate complex Azure configurations by automating the enforcement of naming conventions, networking isolation (via NSGs and Private Endpoints), and resource lifecycle management. Whether you are managing serverless functions, Cosmos DB instances, or networking topologies, this skill prevents common pitfalls like runaway billing, insecure identities, and performance bottlenecks.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/ivangdavila/azure Ensure that you have your Azure CLI credentials configured in your environment, as the skill utilizes these to perform authenticated operations within your subscription.

Use Cases

• Cost Governance: Automating the identification and deallocation of idle VMs to prevent storage and IP address costs, and identifying over-provisioned SSDs.
• Security Hardening: Implementing Managed Identities to replace legacy service principal secrets and configuring Private DNS zones for Private Endpoints.
• Cloud Architecture: Managing Hub-and-Spoke networking topologies and providing guidance on selecting the correct SKU for App Service plans or Redis caches.
• Performance Tuning: Advising on Cosmos DB partition key selection and identifying cold-start latency issues in consumption-plan Azure Functions.

Example Prompts

1. "OpenClaw, audit my current Azure resource group and identify any VMs that are currently stopped but still incurring costs for attached disks or static IPs."
2. "I need to deploy a new App Service. Can you recommend a tier that supports 10 slots and guide me through configuring it with a Managed Identity instead of client secrets?"
3. "Analyze my current Cosmos DB configuration. I am seeing high latency; how can I determine if my partition key choice is the culprit and what would the migration path look like?"

Tips & Limitations

Always remember that Azure Resource Groups are for management, not security isolation; for true network isolation, ensure you are utilizing NSGs and Private Endpoints. Be cautious with Key Vault names, as the 90-day soft-delete policy prevents immediate reuse of purged names. When scaling, note that VNet peering is non-transitive, so if you are building a complex mesh, consider Azure Virtual WAN. Finally, always verify the region pairing to avoid unexpected bandwidth egress charges, which are billed in both directions.