Source record · tier 2 current vendor documentation
Microsoft Teams PSTN usage report
- Publisher
- Microsoft
- URL
- https://learn.microsoft.com/en-us/microsoftteams/teams-analytics-and-reports/pstn-usage-report
- Published
- 2026-04-26
- Updated
- unknown
- Accessed
- 2026-09-24
- HTTP status
- 200
- License
- Microsoft Learn terms of use; no-redistribution; short excerpts and locators only
Source notes citing this source
- In the Direct Routing tab of the Teams PSTN usage report, the Correlation ID is the unique call identifier Microsoft tells admins to use when contacting Microsoft Support. in context
- Direct Routing usage data can be exported for up to 150 days from the current date unless country or region rules prohibit retaining it that long. in context
- Direct Routing report timestamps (Invite, Start, Failure and End time) are shown in UTC, and all dates in the exported CSV are UTC in ISO 8601 format. in context
- For failed Direct Routing calls the report gives Final SIP code, Final Microsoft subcode and Final SIP phrase as the reasons the call failed. in context
- Direct Routing Invite time is when the initial INVITE was sent to the SBC on an outbound call or received from the SBC by the Direct Routing SIP Proxy on an inbound call. in context
- In some countries the Teams PSTN and Direct Routing reports mask the last three or four digits of external phone numbers, for example three digits for Germany and four for France. in context
- Microsoft documentation gives differing freshness for Direct Routing call data: the PSTN usage report page says reports usually reflect 24 to 48 hours latency, while the SIP call flow page says to allow up to 30 minutes for SIP call data. disputed in context
- The Shared Correlation ID exists only in the exported Direct Routing CSV, not in the portal, and links two or more related calls such as the original call and a transfer leg. in context
- The Direct Routing tab of the PSTN usage report shows, per call, the SBC FQDN, media bypass, Azure regions for media and signaling, final SIP code, final Microsoft subcode and SIP phrase, and links to a SIP call flow view. in context
- The PSTN and Direct Routing reports obfuscate the last three or four digits of external phone numbers for organizations in listed European countries such as Germany, France and Switzerland, show full numbers elsewhere, and note that CQD and Call Analytics may use different obfuscation rules. in context
- The Teams PSTN usage report usually lags activity by 24 to 48 hours. in context
- PSTN usage detail records are kept for 365 days for Calling Plans and 150 days for Direct Routing by default, with country-specific periods such as 730 days in Italy and Mexico and 450 days in the United Kingdom, based on the user's country. in context
- Calls on Telstra calling plans do not appear in the Teams PSTN usage report or in the Graph getPstnCalls API. in context
Cite this source record
APA
WarmTransfer. (2026, April 26). Microsoft Teams PSTN usage report. WarmTransfer. https://warmtransfer.net/knowledge/sources/ms-learn-pstn-usage-report
BibTeX
@misc{warmtransfer-ms-learn-pstn-usage-report,
title = {Microsoft Teams PSTN usage report},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/sources/ms-learn-pstn-usage-report},
note = {Microsoft, accessed 2026-09-24}
}