Power BI Outage and Service Status

Power BI may be experiencing an outage if Microsoft reports an active incident, but local sign-in, browser, network, permission, or regional problems can produce similar symptoms.

How to Check Power BI Service Status

For official Power BI service status, start with Microsoft’s service-health information rather than an unverified outage report. Open the company’s official website and look for Support, Service status, or Service health.

Organizations that use Microsoft 365 can also check Service health in the Microsoft 365 admin center. Access may require an administrator or another account with permission to view health notices.

1. Sign in with the account used by your organization.
2. Open the service-health area and locate Power BI or the related Microsoft Fabric service entry.
3. Look for an active advisory or incident that matches your location, feature, and error.
4. Read the latest update, affected services, and any guidance provided by Microsoft.
5. Check again later for a resolution notice instead of relying on an estimated time remembered from an earlier update.

An active incident should come from Microsoft and describe an affected service or function. Do not assume that an old notice or a report for another Microsoft product explains the current Power BI problem.

Is Power BI Down Right Now?

To answer “is Power BI down” or “is PowerBI down,” compare the official Power BI status with what other authorized users experience. A widespread power bi outage usually affects multiple people, devices, or networks and may appear in an official incident notice.

The problem is more likely isolated when:

• Only one account cannot sign in.
• Power BI works in another supported browser or a private browsing window.
• Another network or device can reach the service.
• Only one report, dataset, workspace, or gateway is affected.
• Other users can open the same content with the expected permissions.
• The issue occurs in one location while authorized users elsewhere have normal access.

These checks do not prove that Microsoft has no regional or limited incident. They help narrow the scope while you wait for verified Power BI service status information.

What Do Power BI Status Messages Mean?

Service-health wording can vary, so read the incident details rather than relying only on a label. Common states generally mean:

• Normal operation: Microsoft is not reporting a known service problem in the status information you can access.
• Degraded performance: The service remains available, but some actions may be slow, delayed, or unreliable.
• Partial disruption: A particular feature, region, or group of users may be affected while other Power BI functions continue working.
• Service interruption: An affected function may be unavailable for some or all users covered by the incident.
• Investigating or mitigation in progress: Microsoft has acknowledged the issue and is still diagnosing it or applying measures to reduce its effect.
• Resolved: Microsoft reports that service has been restored, although users may still need to retry an operation or confirm that delayed work completed.

A powerbi status message may be updated as Microsoft learns more. Use the newest timestamp and scope shown in the official notice.

What Should You Do During a Power BI Outage?

1. Check the official Power BI outage notice and record its incident reference, scope, and latest update.
2. Save the exact error text, time, time zone, affected workspace or report, and a screenshot that does not expose private data.
3. Ask another authorized user whether the same action fails, if organizational policy allows that check.
4. Avoid repeatedly changing passwords, permissions, gateway settings, refresh schedules, or data-source credentials during a confirmed outage.
5. Preserve unsaved source work outside Power BI when possible, and do not assume a failed-looking submission completed.
6. Wait for Microsoft to confirm resolution, then test the affected action once.

Repeated configuration changes can make recovery harder to verify. Follow only recovery instructions included in the official incident or provided by authorized support.

How Do You Troubleshoot Power BI When No Outage Is Reported?

1. Confirm that you are using the intended work or school account and that the account can complete sign-in.
2. Open a private browsing window or sign out and start a fresh browser session. This helps identify a stale session, which is an expired or outdated sign-in state retained by the browser.
3. Clear Power BI site data only if a fresh session works or support recommends it. Clearing all browser data may sign you out of unrelated services.
4. Try another supported browser, device, or trusted network to separate a device problem from a connectivity problem.
5. Check whether the account still has permission to the affected workspace, report, semantic model, or data source.
6. If refreshes fail, review the refresh history, credentials, and gateway status. A gateway is software that connects the online service to data stored on another network.
7. For the Power BI application, install approved updates through your organization’s normal process, restart the application, and test the same item in the browser when available.

Do not disable security controls or use an unknown network merely to test access. Ask the organization’s administrator when permissions, gateways, or managed-device rules may be involved.

How Do You Contact Power BI Support?

Use the official support option shown on the Power BI or Microsoft support site. Business users may need to contact their Microsoft 365 administrator first because support requests and service-health details can require administrator access.

Prepare the following information before requesting help:

• Your account type and organization, without sharing the password.
• The exact error message and the time it occurred, including the time zone.
• The affected feature, workspace, report, semantic model, refresh, or gateway.
• Browsers, devices, networks, and troubleshooting steps already tested.
• Whether other authorized users have the same problem.
• Relevant activity, request, correlation, or incident identifiers shown in the error.
• Screenshots with confidential data removed or obscured.

Never send passwords, verification codes, private report data, or data-source secrets in an ordinary support message.

What Should You Check After Power BI Service Is Restored?

1. Confirm that sign-in and navigation work with the normal account and network.
2. Open the reports and workspaces that failed during the PowerBI outage.
3. Refresh important reports or semantic models and verify that current data appears.
4. Review scheduled refresh history for failures or missed runs; retry only when appropriate for the data source and workload.
5. Check gateway connectivity and data-source credentials if gateway-dependent refreshes still fail.
6. Confirm that workspace access, sharing, subscriptions, and other affected functions operate as expected.
7. Keep the recorded error details until Microsoft marks the incident resolved and normal operation is confirmed.

If problems continue after the official resolution, treat them as a separate issue and give support the earlier incident reference along with the new test results.