Zeeshan

In Part 1 we made the case for an operations copilot that runs inside your own tenant. In Part 2, the Azure Support Agent’s war room of specialist agents root-caused a live 5xx in about ninety seconds. But every one of those specialists had to be pointed at something first — and defining that “something” is the problem this post solves. Welcome to the second pillar: Map.

Turning non-production VMs off at night is the easiest Azure saving there is. Doing it without causing an outage is the part nobody writes about. This is an open-source scheduler that takes that saving as an application, in ordered rings, with two independent safety gates between you and a real power action — and it runs entirely in your own subscription.