Service issues › MV1269743

Users may be unable to load the Data Quality page in Microsoft Viva Insights and receive an error

Resolved Microsoft Viva Organizational Insights advisory
Started
02 Apr 2026 02:37 UTC
Resolved
03 Apr 2026 22:40 UTC
Status
serviceRestored
Origin
microsoft

Timeline & resolution

03 Apr 2026 23:51 UTC · regular

Title: Users may be unable to load the Data Quality page in Microsoft Viva Insights and receive an error User impact: Users may have been unable to load the Data Quality page in Microsoft Viva Insights and received an error. More info: Users received an error stating “Something went wrong” when attempting to load the Data Quality page. Final status: The deployment of the code fix completed, and after a period of monitoring, we've confirmed impact is remediated. Scope of impact: Any user attempting to load the Data Quality page may have been impacted. Start time: Thursday, April 2, 2026, at 2:37 AM UTC End time: Friday, April 3, 2026, at 10:40 PM UTC Root cause: A recent code change switched the underlying data source for the Data Quality page in Microsoft Viva Insights, introducing a temporary service API issue that resulted in impact. Next steps: - To help prevent similar impact in the future, we're further reviewing our code change release procedures to identify issues before being deployed. This is the final update for the event.

03 Apr 2026 21:30 UTC · regular

Title: Users may be unable to load the Data Quality page in Microsoft Viva Insights and receive an error User impact: Users may be unable to load the Data Quality page in Microsoft Viva Insights and receive an error. More info: Users receive an error stating “Something went wrong” when attempting to load the Data Quality page. Current status: We've validated the code fix and started deploying it to all impacted users. We expect this will complete and remediate impact by our next scheduled update. Scope of impact: Any user attempting to load the Data Quality page may be impacted. Start time: Thursday, April 2, 2026, at 2:37 AM UTC Root cause: A recent code change switched the underlying data source for certain pages in Microsoft Viva Insights, introducing a temporary service API issue that resulted in impact. Next update by: Saturday, April 4, 2026, at 1:00 AM UTC

03 Apr 2026 20:28 UTC · regular

Title: Users may be unable to load the Data Quality page in Microsoft Viva Insights and receive an error User impact: Users may be unable to load the Data Quality page in Microsoft Viva Insights and receive an error. More info: Users receive an error stating “Something went wrong” when attempting to load the Data Quality page. Current status: We're continuing to validate the code fix that we expect will remediate impact. Once this validation completes we'll deploy the code fix to the affected environment and provide a timeline for remediation. Scope of impact: Any user attempting to load the Data Quality page may be impacted. Start time: Thursday, April 2, 2026, at 2:37 AM UTC Root cause: A recent code change switched the underlying data source for certain pages in Microsoft Viva Insights, introducing a temporary service API issue that resulted in impact. Next update by: Friday, April 3, 2026, at 10:30 PM UTC

03 Apr 2026 18:22 UTC · regular

Title: Users may be unable to load the Data Quality page in Microsoft Viva Insights and receive an error User impact: Users may be unable to load the Data Quality page in Microsoft Viva Insights and receive an error. More info: Users receive an error stating “Something went wrong” when attempting to load the Data Quality page. Current status: We've identified that a recent code change switched the underlying data source for certain pages in Microsoft Viva Insights, introducing a temporary service API issue that resulted in impact. We're validating a code fix to potentially remediate impact. Once this validation completes we'll deploy the code fix to the affected environment. Scope of impact: Any user attempting to load the Data Quality page may be impacted. Next update by: Friday, April 3, 2026, at 8:30 PM UTC

Source: Microsoft 365 service health.