{"id":110854,"date":"2017-06-29T10:00:00","date_gmt":"2017-06-29T17:00:00","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/tracking-deployments\/"},"modified":"2025-06-11T08:13:03","modified_gmt":"2025-06-11T15:13:03","slug":"tracking-deployments","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/tracking-deployments\/","title":{"rendered":"Flow of the Week: Tracking Deployments"},"content":{"rendered":"

Hello Flow Community!<\/p>\n

\u200bToday were bringing you a post from one of our internal Engineers. This post is about a Flow that we, the team use in our own environment and work day.<\/em><\/p>\n

The Microsoft Flow portal and the backend service are deployed to multiple Azure regions. New features and bug fixes are deployed by the team at a regular cadence. The deployment is done through a safe deployment sequence \u2013 an approach wherein deployment proceeds from regions with least usage to regions with highest usage. During a deployment, the team may get an incident through automated runners or through a customer report. At this point, the team must investigate the incident and make several decisions. This involves:<\/p>\n