VERSICH

Power BI and Microsoft 365: What Breaks During a Tenant Outage

power bi and microsoft 365: what breaks during a tenant outage

Microsoft 365 was down for about 24 hours on 12 and 13 November 2026. Outlook could not reach mailboxes and email delivery stalled worldwide, as covered in our live coverage of the Microsoft 365 outage. The Power BI service itself stayed online, yet many teams still lived through a Power BI outage, because the pieces that connect Power BI to Microsoft 365 broke around it. 

This guide covers what Microsoft reported during the Power BI outage, where the Power BI Microsoft 365 dependency failed, what to check now and how to reduce the risk next time. 

What Microsoft Reported for Power BI 

Microsoft’s service health notices listed two related problems: 

  • Power BI: exporting reports with Microsoft Purview sensitivity labels to PDF failed intermittently. 

  • Microsoft Fabric: exporting labelled reports to PDF or PowerPoint, updating labelled items and opening labelled .pbix files in Power BI Desktop failed. Microsoft’s workaround was to remove the sensitivity label where company policy allowed it. 

Both problems trace back to Microsoft Purview, which was one of the affected services. Any board pack or finance report exported as a labelled PDF failed with it. 

Where the Power BI Microsoft 365 Dependency Broke 

Email Subscriptions and Data Alerts 

Power BI email subscriptions come from no-reply-powerbi@microsoft.com, but they land in Outlook. With Exchange Online down, morning sales snapshots, scheduled report emails and data alert emails reached nobody on time. Teams that run on emailed reports went a full day without numbers. 

Refresh Failure Notifications 

Power BI emails semantic model owners when a scheduled refresh fails. Those emails were delayed too, so a Power BI refresh failed message from Thursday surfaced only when someone opened a report and noticed old figures. 

Data That Lives in Exchange 

Microsoft reported that Microsoft Graph requests for Exchange data, including mail, calendars and contacts, timed out. Reports built on mailbox or calendar data, such as shared inbox response times or meeting-load dashboards, failed to refresh and showed stale figures. 

Files in SharePoint and OneDrive 

Microsoft reported that files stored directly in SharePoint stayed accessible, so reports built on Excel or CSV files in SharePoint and OneDrive kept refreshing. Workbooks that someone updates from emailed attachments stayed out of date, because the attachments never arrived. 

Power BI Refresh Failed? What to Check Now 

  1. Review refresh history: Open the refresh history for each semantic model and list every failure between 12 and 14 November. 

  1. Refresh the failed models: Run a manual refresh, starting with finance and sales models. 

  1. Re-send key subscriptions: Trigger the important subscriptions again so recipients get current numbers. 

  1. Redo labelled exports: Re-export the PDF and PowerPoint reports that failed during the outage. 

  1. Check email-fed sources: Confirm that workbooks updated from emailed files contain the outage days. 

How to Cut Power BI’s Dependency on One Tenant 

  • Show the last refresh time on every report page: Readers spot stale data immediately instead of acting on it. 

  • Send refresh failure alerts to a second channel: Route them to a tool outside Microsoft 365 so failures surface even when Outlook is down. 

  • Pull finance data from the source system: Connect your ERP directly to Power BI instead of passing spreadsheets through email. Our NetSuite and Power BI integration services remove the inbox from that chain entirely. 

  • Keep offline copies of critical reports: Store a PDF of board and finance reports after each month-end close in a location outside Microsoft 365. 

  • Agree a label workaround in advance: Decide with your compliance team who may remove a sensitivity label for an urgent export, and who approves it. 

Our Power BI services team reviews semantic models, refresh schedules, subscriptions, and data sources for exactly these weak points, then fixes them. 

Conclusion 

Power BI kept running through the Microsoft 365 outage, but the emails, alerts and Exchange data around it failed quietly. A short dependency review now keeps the next Power BI outage from reaching your decision-makers. Talk to our Power BI team and we will review your refreshes, subscriptions and data sources for single points of failure.

Frequently Asked Questions

Was Power BI down during the Microsoft 365 outage?

No. The Power BI service stayed online. Microsoft reported one Power BI problem: exporting reports with Microsoft Purview sensitivity labels to PDF failed intermittently. The wider damage came from email subscriptions, refresh alerts and Exchange data that Power BI depends on.

Why did my Power BI refresh fail during the outage?

Reports that read mail, calendar or contact data through Microsoft Graph failed because Microsoft reported those requests timing out. Reports built on files updated from email attachments refreshed successfully but missed the outage days, because the attachments never arrived.

Where do Power BI email subscriptions come from?

Power BI email subscriptions come from no-reply-powerbi@microsoft.com and land in each recipient’s mailbox. When Exchange Online is down, they arrive late. Add the address to your approved senders so they never land in spam once delivery resumes.

How do I know if a Power BI report shows stale data?

Open the semantic model’s refresh history to see the last successful refresh. Better still, show the last refresh date and time on every report page so readers see it without asking.

How do I export a labelled report when Microsoft Purview is unavailable?

Microsoft’s workaround during the outage was to remove the sensitivity label where company policy allowed it. Agree in advance who may remove a label for an urgent export and who approves it, so nobody makes that call under pressure.