What is Microsoft Power Automate current status?

Microsoft Power Automate is currently operational. You can check Microsoft Power Automate status and current incidents and outages on the top of the page. The status is updated in almost real-time, and you can see the issues affecting customers.

Is Microsoft Power Automate down today?

Microsoft Power Automate had 1 know outages in the last 24 hours. IsDown continuously monitors the Microsoft 365 status page, looking for the latest outages and issues affecting customers. Check all recent outages in the section 'Latest Microsoft Power Automate outages, issues and problems' at the top of the page.

When was the last Microsoft Power Automate outage?

We don't have a record of Microsoft Power Automate last outage

How to monitor or check Microsoft Power Automate status?

You can use IsDown service or go to Microsoft 365 official status page. Some accounts also use Twitter to communicate the status.

How can I be notified when Microsoft Power Automate is having issues?

You can create an account in IsDown and monitor multiple services or subscribe for updates on the official status page. IsDown will send you a notification in real-time when Microsoft Power Automate has issues. Microsoft 365 official status page might also offer notification options such as email, SMS, or Slack.

Is Microsoft Power Automate Down? Check Microsoft Power Automate status and current outages

Microsoft Power Automate incident history

IsDown has tracked 0 incidents for Microsoft Power Automate since started monitoring Microsoft 365 downtimes in June 2023. We are also collecting data from 4000+ services, and normalize the data to give you a clear picture of the impact of the outage.

No outages registered

Microsoft Power Automate user-reported issues in the last 24 hours

This chart displays the number of user-reported Microsoft Power Automate problems over the past 24 hours, grouped into 20-minute intervals. It's normal to see occasional reports, which may be due to individual user issues rather than a broader problem.

Third-party monitoring

Stop Juggling Dozens of Status Pages – Monitor Them All in One Place

Monitoring 4000+ third-party services in real-time

Get custom alerts via Slack, Teams, Datadog, etc.

Create public or private status pages

Start Free Trial

14-day free trial · No credit card required

Trusted by thousands of teams

Monitor Microsoft Power Automate and all your dependencies

Latest user comments about Microsoft Power Automate issues

J

Joe

5 days ago

Generic something went wrong on Power apps and power automate just is stuck on create text with gpt using promtp
D

dave

6 days ago

My flow is back up! Hopefully, everyone else is running again.
C

Casey

6 days ago

Excel related flows are taking 10 times longer to run than they should.
K

Kelly

6 days ago

Bad Gateway/Timeout. Excel connectors
A

Amber

6 days ago

My excel flows run for a very long time and then finally give me a gateway error.
B

Bell

6 days ago

getting Bad Gateway related to Excel Connection
B

Bourbaki

6 days ago

Excel connectors are down. None work or are able to get the dynamic values for tables or rows
D

dave

6 days ago

excel branch is not working. If I move the file into another sharepoint folder, rename, then move back, the flow is fixed. Weird
A

Aiden

6 days ago

My connections from microsoft forms to excel that are being processed through microsoft power automate flows are not working.
D

David

6 days ago

My cloud flows are taking over 30 minutes to run. They have been fine for months and I'm not running anything extensive.
B

Bethany

6 days ago

Hello. My flows are having a “gateway” error. I have been getting this on error on flows that have excel connections.
K

kap

6 days ago

Excel connector not working - bad gateway. Continues to time out.
S

Sam

6 days ago

Keep getting Gateway Runtime Errors when flow eaches excel task
M

Matthew

6 days ago

My flows are just spinning without any error. None will complete.
W

Wes

6 days ago

None of my Automations/Flows, which incorporate Excel, are completing. The Flow runs until that step, then just spins.
G

Guy

6 days ago

Excel connector not working - bad gateway. Continues to time out.
S

Sree

6 days ago

Flow cannot run for Excel connector. Cannot get a row and hence cannot go to the next actions
B

Bill

6 days ago

Excel connectors not working - BadGateway error.
S

Sharon

6 days ago

Excel Connector is not working Flow Failed
M

Maia

6 days ago

Scheduled flows failing but no error message showing. Flow checker showing no errors in build.
A

Ariana

6 days ago

Excel connections aren't working
B

Bob

6 days ago

Gateway issues with linked SharePoint files
L

Loren

6 days ago

Flows not loading into the excel spreadsheets!
P

Paige

6 days ago

""Graph API request failed. Error code is 'InvalidSession'. Error message is 'The target session is invalid.'.\r\nclientRequestId: 9830122f-8329-41d6-92d7-adf0d711a461", "error": {
R

Richard

6 days ago

Bad Gateway 504 error. Only for some Excel connections to Teams files. No issue with flows using other Excel connections.
I

Isley

6 days ago

Bad Gateway 504 error. Only for excel connections. Won't even let me save any new changes.
N

Nathan

6 days ago

Our flows are not working. Specifically those that deal with excel connections.
N

Nick

6 days ago

Not connecting to sharepoint in a timely manner
J

Jiao

6 days ago

Bad gateway in excel connector
A

Andrew

6 days ago

Experiencing GatewayTimeout for "Excel Online [Business]" connector - example actions "List rows present in a table" or "Get table" actions
S

Steven

6 days ago

Everything is not loading and my flows are all timing out
C

Chuy

6 days ago

Multiple recurrence flows not working, "Multiple errors occurred: 'GatewayTimeout,GatewayTimeout'."
J

Jim

7 days ago

Power Automate: Multiple automated cloud flows not running significant delay in running.
C

CSuwan

10 days ago

Flow save failed with code 'MultipleErrorsOccurred' and message 'The dynamic operation request to API 'excelonlinebusiness' operation 'GetTable' failed with status code 'GatewayTimeout'. Error response: { "error": { "code": 504, "source": "default-74105ed9-72ff-4685-9154-75f7408b6f67.03.common.as...
J

J

10 days ago

getting a Gateway Error - timeout "Request to Graph API has timed out"
S

Shawna

10 days ago

Cannot read properties of undefined (reading 'outputs')
R

Rawan

11 days ago

This is the issue I get if i tried to rerun a flow  Request to Azure Resource Manager failed with error: '{"error":{"code":"ResourceNotFound","message":"The Resource 'Microsoft.Logic/workflows/17bb8f1f-31b8-4e06-906c-5903e7b2fdfb' under resource group 'AF8E89A3D9AC422FAD06CC4EB4214314-DEFAUL...
C

Costin

14 days ago

Hmmm… can't reach this page Check if there is a typo in make.powerautomate.com
J

jacques

14 days ago

Getting "make.powerautomate.com’s server IP address could not be found." when I try to go log in.
J

Jack

15 days ago

Website took too long to respond, doesnt load
S

Stephen

15 days ago

Unable to connect getting. The connection for this site is not secure make.powerautomate.com uses an unsupported protocol.
M

Matthew

15 days ago

Unable to access make.powerautomate.com
A

Aashna

17 days ago

Unable to access the make.powerautomate.com website.
T

Tinoby

17 days ago

Unable to access the make.powerautomate.com website.
F

Frank

17 days ago

This site can’t be reached when opening power automate
A

Adam

18 days ago

power apps and power automate connections aren't stable. SQL Stored Procedure steps are taking too long to respond
J

Jake

27 days ago

Internal azure resource manager errors. Cant load or edit flows.
J

J

28 days ago

Won't run past trigger step, even for Trigger>initialize variable testing.
D

Dominic

about 1 month ago

emails not being sent per flow
J

Jean

about 1 month ago

Buggiest interface with json validator scheme
T

Tomek

about 1 month ago

In my flows: "Multiple errors occurred: 'InternalServerError,InternalServerError,InternalServerError'. Please see details."
A

Arpad

about 1 month ago

Not loading any flows (cannot see them)
R

Roger

about 1 month ago

Power Automate not responding.
C

Chris

about 1 month ago

Time: "2025-04-02T11:13:37.715Z" Session ID: 737649e0-0fb3-11f0-9a3a-ff9823b31a11 x-ms-client-request-id (Client->Backend Request Header): 8c9fdff9-ef60-4912-80fb-d3a70c6ac7a0 x-ms-correlation-request-id (Backend Response Header): f9cef215-40a8-41ae-84e3-bb0d206218bc Error: Encountered int...
T

Tom

about 1 month ago

Internal Server Error - no flows loading
P

Peter

about 1 month ago

In my flows: "Multiple errors occurred: 'InternalServerError,InternalServerError,InternalServerError'. Please see details."
M

Mario

about 1 month ago

41 / 5.000 Cloud flows does not appear in my environment
P

Palen

about 1 month ago

Unable to load all created flows under "My Flows". "Multiple errors occurred: 'InternalServorError'.
T

thor

about 1 month ago

Constant errors when listing flows and working with a flow in all environments.
M

M

about 1 month ago

Cant list or open Flows. Error: Encountered internal server error from Azure Resource Manager.

Microsoft Power Automate outages in the last 30 days

Number of Incidents

0 issues

Last incident

0 days ago

Seamless Integrations

Get Microsoft 365 outage alerts and updates in your favorite tools

Receive vendor outage notifications where your team already works. Compatible with Slack, Microsoft Teams, PagerDuty, Datadog, Better Stack, Rootly, Incident.io, Statuspage.io, and more.

Never miss an outage

Easy setup · No coding required

Works with your existing stack

Having problems with Microsoft Power Automate? What can you do?

First, stay calm.
- We know it's stressful when Microsoft Power Automate is down, but running around is not going to fix it.
- Remember that it's normal for services to go down sometimes. It can be for a number of reasons, from maintenance to unexpected issues.
Make a quick evaluation of the impact of the Microsoft Power Automate outage
- Try to evaluate the impact of the outage on your business. Is it impacting a majority of your users or just a few?
- Did Microsoft Power Automate already acknowledge the issue? And published a status update? (You can find it in the top of the page or in Microsoft Power Automate status page)
- If not, understand if other users are also experiencing issues. You can also check this information on the top of the page.
Communicate with your team and users quickly
- If Microsoft Power Automate is having problems and impacting your business, it's important to keep your team and users informed.
- Share this page with your team, so you can start incident response procedures. No need for everyone to go around searching for information. Create a post or a specific channel in your internal communication tools (Slack, Teams, Google Chat, etc.) so you can aggregate all the information in one place.
- If you have a status page, create a status update to inform your users about the issue. This way they know what's going on and you can avoid a flow of support requests overburding your team.
Understand the root cause
- After the first communication, let's move on to the next step. Do a more thorough investigation to understand the root cause of the issue and impact.
- Reach out to the service provider to understand if they are aware of the issue and if they are already working on it. You can reach them in their support channels, or their social media channels if they have any.
Is there any mitigation for the issue?
- Understand if there are workarounds or mitigations for the issue. Can you use a different provider? Is the switch easy to do? Talk with your team to understand the best course of action.
- Need to wait on the service provider to fix the issue? Understand if there is a timeline for the fix. Adapt your communication with your team and users to the situation. It's very important to keep everyone informed.
Did Microsoft Power Automate recover?
- Continue to monitor the situation. A lot of times, the service can see a brief recovery and declare the issue as resolved, but it can come back. Keep monitor for some time to make sure it's really resolved.
Post-incident analysis
- Once the issue is resolved, it's important to do a post-incident analysis. Understand what went wrong and if it's possible or needed to do something to prevent it from happening again.
- Sometimes if it's a critical dependency, you might need to have a backup plan in place to avoid a similar issue.
- Vendors usually publish post-mortem analysis reports, so keep an eye on their social media channels and website for more information.
Prepare for the next incident, because it will happen again
- Start monitoring your dependencies. Sign up to IsDown and aggregate all your dependencies status in one place.
- Nowadays, it's very common to have a lot of dependencies, and keeping an eye on them is not an easy task. IsDown can help you with that, by aggregating and monitoring all dependencies status and alerting you if they are having issues. Create status pages to communicate with your team and users.
- For a complete overview of all Microsoft 365 services, visit the Microsoft 365 Status Page on IsDown

Related Services Dashboard

Services commonly monitored together with Microsoft 365

Create your own dashboard

Azure

AWS

MINOR

Google Workspace

Google Cloud

Cloudflare

MINOR

GitHub

Adobe

Zoom

Salesforce

MINOR

Slack

Figma

Microsoft Office 365

HubSpot

Datadog US1

Airtable

Want to be informed about Microsoft 365 status changes?

IsDown offers an easy way to monitor Microsoft 365 with maximum flexibility

Major Outages Notifications

IsDown monitors Microsoft Power Automate for major outages. A major outage is when Microsoft Power Automate experiences a critical issue that severely affects one or more services/regions. When Microsoft 365 marks an incident as a major outage, IsDown updates its internal status, the customer status page and dashboard. Depending on the customer settings, IsDown will also send notifications.

Minor Outages Notifications

IsDown monitors Microsoft 365 status page for minor outages. A minor outage is when Microsoft Power Automate experiences a small issue affecting a small percentage of its customer's applications. An example is the performance degradation of an application. When a minor outage occurs, IsDown updates its internal status and shares that information on the customer status page. Depending on the customer settings, IsDown will also send notifications.

Outage Details

IsDown collects all information from the outages published in Microsoft 365 status page to provide the most accurate information. If available, we gather the title, description, time of the outage, status, and outage updates. Another important piece of information is the affected services/regions which we use to filter the notifications that impact your business.

Component Filtering

IsDown monitors Microsoft 365 and all their 19 components that can be affected by an outage. IsDown allows you to filter the notifications and status page alerts based on the components you care about. For example, you can choose which components or regions affect your business and filter out all other outages. This way you avoid alert fatigue in your team.

Early Outage Indicators

Microsoft 365 and other vendors don't always report outages on time. Our crowdsourced status platform helps you stay ahead of outages. Users report issues and outages, sharing details on what problems they are facing. We use that info to provide early signs of outages. This way, even without an official update, you can stay ahead of possible problems.