After our recent post Introducing more control over Direct Send in Exchange Online, there have been more questions about scenarios that are not actually Direct Send such as senders being able to igno...
Updated Nov 11, 2025
Version 8.0
Blog Post
Does an Inbound Connector force TERRL counting for direct sends to other tenants?
If I configure an Inbound Connector (OnPremises) restricted to my dedicated public IP to secure internal traffic: Does this force Global Tenant Attribution for that IP, meaning all traffic coming from it is attributed to my tenant?
Specifically, if my server sends email to other Exchange Online tenants (via direct MX lookup), are those messages now classified as "Outbound" from my organization and counted against my TERRL quota?
I observed a significant spike in my Tenant Outbound External Recipients report immediately after creating the connector, even though the traffic volume didn't change. I want to confirm if this is the expected behavior.