All templates
For cloud ops teams, platform engineers & IT managers

Know about Azure outages and maintenance before they hit you

Every morning, WebRun opens the Azure portal, reads Service Health for every subscription you watch, records which regions and resources are affected by active issues or scheduled maintenance in Google Sheets, and puts each maintenance window on your Google Calendar so deploys move off that date.

  • No credit card
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every day at 8:00 AM WebRun
1 Microsoft Azure read service health events
2 Google Sheets log issues and affected resources
3 Google Calendar block the maintenance windows
Run a sample
In short

How do I get told about Azure outages and planned maintenance early?

WebRun opens the Azure portal every morning and reads Service Health for each subscription you watch. It logs active issues and planned maintenance, with the regions and resources affected, into Google Sheets, then adds every maintenance window to Google Calendar so your team can move deploys off that date.

  • Maintenance windows land on the calendar before deploys are booked
  • One sheet shows which subscriptions and regions are affected today
  • Resolved events are marked resolved instead of lingering as noise

Built for cloud ops teams · platform engineers · IT managers · DevOps · managed service providers

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens portal.azure.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Microsoft Azure - read service health events
    azure.microsoft.com
    WebRun in Microsoft Azure: read service health events
    WebRun opens Microsoft Azure to read service health events.
    • Open the Azure portal and go to Service Health
    • Read the active service issues and the planned maintenance entries for every subscription you watch
    • Capture the event title, the regions and services involved, the impacted subscription and the start and end times
    • Open the affected resources view for each event and note which of your resources are named

    Done when Every open service issue and upcoming maintenance window touching your subscriptions is captured.

  3. 2
    Google Sheets - log issues and affected resources
    google.com How to Automate Google Sheets
    WebRun in Google Sheets: log issues and affected resources
    WebRun opens Google Sheets to log issues and affected resources.
    • Add one row per event to your Google Sheets tracker
    • Record the subscription, region, service, event type, window and the affected resources
    • Mark events that closed since yesterday as resolved rather than deleting them
    • Highlight anything touching a production subscription

    Done when The sheet shows today's open issues and upcoming maintenance, with yesterday's resolved ones marked.

  4. 3
    Google Calendar - block the maintenance windows
    calendar.google.com How to Automate Google Calendar
    WebRun in Google Calendar: block the maintenance windows
    WebRun opens Google Calendar to block the maintenance windows.
    • Create a calendar entry for each planned maintenance window on your team calendar
    • Title it with the service and region, and put the affected subscriptions and resources in the description
    • Update or remove an entry if Azure moves or cancels the window
    • Leave existing meetings and deploy slots untouched so a human decides what to reschedule

    Done when Every upcoming maintenance window sits on the team calendar at the right time.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
portal.azure.com
ScheduleRuns automatically on this cadence
Every day at 8:00 AM
DeliveryHow each run's result reaches you
Service health log · Google Sheets
OutputWhat each run produces - A daily list of Azure service issues and planned maintenance with the subscriptions, regions and resources affected, plus a calendar entry per window.
Text
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it change anything in my Azure subscription?

No. WebRun only reads Service Health. It never restarts a resource, changes a setting or acknowledges an event, and shell commands are blocked by policy.

Does it move my meetings or deploys?

No. It adds a calendar entry for each maintenance window and leaves your existing events alone, so a human decides what to reschedule around it.

What if an issue is resolved before the next run?

It reads the live Service Health status each morning and marks the closed event as resolved in the sheet instead of leaving it open.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.