A city operations lead wants nightly automation for non-production…

Question

A city operations lead wants nightly automation for non-production VMs but still needs a clickable place for one-off creates and reviews. How should the team think about the Azure portal?

Accepted Answer

Treat the portal as the interactive create-and-manage surface, and use CLI or PowerShell when the work should be automated. — The portal is great for hands-on creates and checks — like a dashboard you can click. Nightly start/stop loops belong in scripts, not in someone babysitting the mouse. Same Azure estate, different tools for different jobs.

Answer

Click the portal for every nightly job because automation tools cannot manage Azure.

Answer

Replace the portal with Conditional Access policies so resources create themselves.

Answer

Use the portal only to design Microsoft Sentinel analytics rules for AZ-500 depth.

A city operations lead wants nightly automation for non-production VMs but still needs a clickable place for one-off creates and reviews. How should the team think about the Azure portal?

Short Explanation

Full Explanation