Data Integration Flows Failing Due to Authentication Issue

The issue affecting Data Integration flows has been resolved.

The root cause was an expired authentication credential used for Microsoft Entra ID access. This occurred due to a manual error during the credential renewal process, resulting in authentication failures for affected integration flows.

The authentication credential has been renewed and Data Integration services are operating normally. New messages are being processed successfully.

To prevent similar incidents in the future, we are implementing a new version that uses Microsoft-managed keyless authentication, eliminating the need for manual credential renewals.

We apologize for the inconvenience and thank you for your patience.

Due to platform security restrictions, our Data Integration team is unable to restart all previously failed messages on behalf of customers.

Customers are advised to review any failed integration messages and restart them where necessary.

The authentication issue affecting Data Integration flows has been resolved:

The required authentication credentials have been renewed and new integration messages are being processed successfully. Our Data Integration team is currently restarting and processing messages that were impacted during the outage.

We continue to monitor the service and will provide a further update once all backlog processing has been completed.

We are currently investigating an issue affecting Data Integration flows. Some customers may experience failures when integrations attempt to connect to Microsoft Entra ID (Azure AD). As a result, affected integrations may not process data as expected and could return authentication-related errors.

Our team has identified that the issue is related to expired authentication credentials used by the integration service and is working on restoring normal operation as quickly as possible.