RSS and Atom feeds

Follow Microsoft’s status in any feed reader, in Outlook, in a Teams or Slack RSS app, or in your own scripts. Every feed exists as RSS 2.0 (.xml) and Atom 1.0 (.atom). Free, no account.

FeedRSSAtom
Every Microsoft incident/feed.xml/feed.atom
One product family/status/microsoft-365/feed.xml/status/microsoft-365/feed.atom
One service/status/exchange-online/feed.xml/status/exchange-online/feed.atom
One Azure region/azure/regions/west-europe/feed.xml/azure/regions/west-europe/feed.atom
One incident, every version/incidents/{id}-{slug}/feed.xml/incidents/{id}-{slug}/feed.atom
Changes Microsoft announces (roadmap, Azure Updates …)/changes/feed.xml/changes/feed.atom

Any service or family id from the services list works in /status/{id}/feed.xml. Region ids are the Azure region names in lower case with hyphens (west-europe, east-us-2). Pages also announce their feeds with <link rel="alternate">, so most readers find them from the page address.

What an entry is

One entry per event, newest first: a new incident, every later version Microsoft published (a status change, an edit to the text, a resolution), and an incident a status page stopped listing without saying it was resolved. Each entry says what changed in our words, gives Microsoft’s status, the affected services and regions, the words Microsoft changed and, for the newest version, one short quote (at most 25 words). It links to the incident page and to the source. Entry ids are stable, so a reader shows each version once.

The change feed has new and edited items from the Microsoft 365 roadmap, Azure Updates and the other change sources. Items that already existed when we started reading a source are history, not news, so they appear only when Microsoft edits them.

Polling

Feeds can be cached for 60 seconds and carry ETag and Last-Modified, so a reader that sends them gets 304 Not Modified when nothing changed. Every five minutes is plenty for most readers. For alerts within a minute, use the API.

Last updated