Forum Discussion
External Teams federation broken after Dunloe Dataplane Service provisioning failure
Repost without tenantID
Since June 26, all external Teams chat/federation is broken for our organization. Messages to all external users fail with "Send failed".
In our Entra audit log we found the root cause: on June 26 at 05:57 UTC, Microsoft Azure AD Internal - Jit Provisioning failed to provision "Dunloe Dataplane Service" in our tenant (multiple SpnValidationException errors, only 1 of 6 succeeded).
We have verified all settings are correct:
- Get-CsTenantFederationConfiguration → AllowFederatedUsers: True, AllowedDomains: AllowAllKnownDomains
- Get-CsExternalAccessPolicy → EnableFederationAccess: True
- Entra Cross-tenant access settings → All B2B inbound/outbound: All allowed
This appears to be a Microsoft-side provisioning issue. We need Microsoft to re-provision the Dunloe Dataplane Service for our tenant.
This is not a support channel, open a support case via the admin center.
2 Replies
Hi, since this affects all external federation and you have an Entra audit event pointing to a provisioning failure, I would treat this as a tenant/service-side issue rather than a client problem.
I would check:
1. Teams admin center > External access settings.
2. Microsoft 365 admin center > Service health for Teams and Entra.
3. Whether newly created test users have the same external chat failure.
4. Any recent federation, cross-tenant access, or domain allow/block changes.
If everything is configured correctly, open or update a Microsoft support case and include the exact UTC timestamp, failing workload name, correlation/request IDs if available, and a fresh message trace/repro. This is the kind of issue support may need to repair on the backend.
This is not a support channel, open a support case via the admin center.
