Forum Discussion
External Teams federation broken after Dunloe Dataplane Service provisioning failure
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.
Tenant ID: 58b3fa8e-4226-40ec-9424-7e3267c62187
1 Reply
Hi, since all external federation broke at once, I would check the Teams external access policy and domain allow/block list first, but this sounds more like a tenant-side provisioning or service issue than a user setting. Capture failed message timestamps, affected external domains, and any correlation IDs from Teams logs. If support already has a ticket, ask them to verify federation routing and provisioning state for the tenant, not just client cache.
