Here's a number most Teams voice deployments never look at until someone asks for last spring's call data: 150. That's how many days of Direct Routing call detail records Microsoft keeps in the Teams admin center for a US tenant. Calling Plan records in the same report get 365. After that, the export window is closed.
Nobody chose that retention policy for your business. It came with the phone system. And it's the clearest symptom of a bigger design fact that gets lost in every "move your phones into Teams" project: Teams is a very good calling client and a very thin calling record.
What Direct Routing actually is
Strip away the licensing slides and Direct Routing is a SIP trunk with strict manners. Microsoft's own planning guide lays out the requirements: a certified Session Border Controller, an SBC FQDN on a verified tenant domain (not *.onmicrosoft.com), a public certificate signed by a CA in the Microsoft Trusted Root Program, SIP over TLS to port 5061, and media firewall rules for Microsoft's processor ranges. The SBC tries sip.pstnhub.microsoft.com first, then sip2, then sip3, each mapping to a different regional datacenter.
That's solid engineering. It's also a list of things that fail on a schedule. Certificates expire. Root programs change. A firewall rule gets "cleaned up." When that happens, your Teams users don't see a SIP error. They see a phone that doesn't ring.
My opinion: if your organization runs its own SBC for Direct Routing, it owns a piece of carrier infrastructure, whether or not anyone's job description says so. Most mid-size companies are better off letting a provider own that edge.
What the Teams record contains
The Teams PSTN usage report's Direct Routing tab is built for one job: diagnosing signaling between your SBC and Microsoft's SIP proxy. It's good at that. You get invite time, start and end time, final SIP code and phrase, call type, and a visual SIP call flow. Microsoft also states that the report "usually reflect[s] a 24 to 48 hour latency from time of activity."
Now list what isn't in it. You won't find the campaign that made the phone ring, the tracking number or keyword behind it, or what was actually said. There's no sentiment, no outcome, nothing about whether a quote was given or a cancellation was threatened. Transfers show up as separate rows. They only tie back to the original call through a Shared Correlation ID, and that ID exists only in the exported CSV.
None of this is a criticism of Microsoft. A PSTN usage report is a carrier-grade billing and diagnostics artifact, and that's exactly what this one is. The trouble starts when a company retires its old phone system, moves every external call into Teams, and quietly assumes the "phone data" moved too. What moved is a 150-day log of SIP transactions. The business meaning of those calls was never in it.
Where the analytics layer has to live
The architectural point is simple once you draw it. In a Direct Routing deployment, every PSTN call crosses one boundary: the trunk between the carrier network and Microsoft's SIP proxy. Teams-to-Teams calls never touch that boundary. External calls always do. So the trunk is the one place where you can see every customer call, from any Teams client, with full caller information, in real time, before Microsoft's reporting latency or retention rules apply.
If you want call data that answers business questions, it has to be captured there and written to a record you control. Three properties matter:
- Retention you set. Your record-keeping policy should follow your legal and business needs, not a default that differs by license type.
- Same-record enrichment. Attribution, transcript, and sentiment belong on the call row itself, not in a second system joined later by timestamp and luck.
- Continuity across transport changes. If you move users from desk phones to Teams next year, your call-volume time series shouldn't reset.
The Dial800 angle
This is the reason we built Teams Direct Routing the way we did. The customer doesn't stand up an SBC. You authorize Dial800 through the standard Microsoft 365 tenant consent flow, assign DIDs user by user from the Dial800 dashboard, and E911 is handled per user. Because every external Teams call crosses our trunk, it gets the same treatment as any other Dial800 call. That includes AI transcription with speaker separation, sentiment and keyword tagging, and source attribution, all on the same record. It also shows up in the same reporting as calls that land on a desk phone, a softphone, or a contact-center queue. It's $15 per seat per month.
There are limits. Teams-to-Teams calls between your own employees stay inside Microsoft's cloud, and we don't see them. That's how Direct Routing is designed, and I'd be skeptical of any provider who claims otherwise. Your Teams client experience, meetings, and chat are still Microsoft's. What changes is where the customer-call record lives, and who decides how long it lives.
Before your next renewal
Pull up the Teams admin center and export your Direct Routing usage for the longest window it allows. Then try to answer one question from that file: which marketing source produced the calls that turned into revenue last quarter?
If the file can't answer it, Teams didn't break anything. Your phone system just stopped being your system of record, and nobody wrote that down.