3rd Party: Some Microsoft Advertising connectors are failing with a "Report processing failed: (StreamProcessing)" error

Update timeline

1. identified Jun 07, 2026, 08:50 AM UTC

   We have identified an issue where Microsoft Advertising connectors are failing with a "Report processing failed: (StreamProcessing)" exception. We are currently investigating in more detail. Next Expected Update:

2. identified Jun 07, 2026, 10:53 AM UTC

   We have performed an initial analysis and identified that the issue appears to be related to an incident with the Bing Ads Reporting API affecting the "GeographicPerformanceReport" report Next Expected Update:

3. monitoring Jun 07, 2026, 01:30 PM UTC

   The issue appears to have been resolved on the Microsoft end, and the affected connections are recovering. We will continue to monitor all affected connectors until they resume their normal sync functionality. Next Expected Update:

4. resolved Jun 07, 2026, 02:08 PM UTC

   This incident has been resolved. We have observed that instance rates are returning to normal levels, and affected connectors are syncing successfully. Incident Summary Description: We identified an issue with the Microsoft Advertising connections, which resulted in syncs failing with a "Report processing failed: (StreamProcessing)" error. Timeline: This issue began on June 7, 2026, at 05:00 UTC and was resolved on June 7, 2026, at 13:00 UTC. Cause: The connectors that were syncing Geographic Performance report tables in Microsoft Ads started failing consistently due to an issue with the Microsoft Ads API on Microsoft's end. Resolution: This has been automatically resolved on the Microsoft Ads API affecting the GeographicPerformanceReport, and the connectors are succeeding now.