Can You Pull Call Logs From Microsoft Teams?

If your team runs its phones through Microsoft Teams, sooner or later someone asks a reasonable question: where did all our calls go, and can I get them out in a spreadsheet? Maybe you are reconciling a phone bill, checking whether the sales team is actually calling leads, or trying to figure out which marketing campaign drove the busy afternoon last Tuesday.

Here is the short answer: yes, you can pull call logs from Microsoft Teams. The data lives in a few different places depending on whether you want individual call history, tenant-wide records, or analytics reporting, and you can export most of it to CSV. What you cannot easily get from raw Teams logs is the marketing context behind each call, which is where the logs stop being enough for anyone measuring campaigns. This guide covers where the logs are, how to get them out, and what to do when a call log is not the same thing as call analytics.

Where Does Microsoft Teams Store Call Logs?

Teams does not keep everything in one tidy place. Call data is scattered across three layers, and knowing which one you need saves a lot of clicking.

1. Individual call history. Every user has a personal call log inside the Teams client. It shows inbound, outbound, and missed calls with names, numbers, timestamps, and duration. This is the view most people mean when they say “call log”, it is fast to check but limited to one person and a rolling window of recent activity.

2. The Teams admin center. Administrators can see call analytics per user and access broader usage reports. This is where you look when you need data across the whole organization rather than a single account.

3. Call Quality Dashboard (CQD) and PSTN usage reports. For organizations using Teams Phone with real phone numbers (the Public Switched Telephone Network, or PSTN), Microsoft keeps detailed usage records, including billed minutes and connection details, that admins can review and export.

The right layer depends on your goal. Troubleshooting one person’s dropped calls? The client and CQD. Reviewing a month of company-wide phone activity for a report? The admin center and PSTN usage records.

How to Pull Call Logs as a User

If you only need your own recent calls, the fastest route is inside the app:

1. Open Microsoft Teams and go to Calls in the left sidebar.
2. Select History to see your recent inbound, outbound, and missed calls.
3. Hover over any entry to see duration and details, or start a callback, add a contact, or view voicemail.

This is handy for a quick check, but it has real limits. The history is personal, it does not stretch back indefinitely, and there is no built-in “export to CSV” button in the client for the average user. If you need durable records or organization-wide data, you have to move up to the admin tools.

How to Export Teams Call Logs as an Admin

Administrators have more power and more export options. There are two common paths.

Through the Teams admin center

1. Sign in to the Microsoft Teams admin center with an account that has the right permissions.
2. Navigate to Users and select the person whose call history you want, or use Analytics & reports for aggregate usage.
3. Open the Call history or PSTN and SMS usage report view.
4. Use the Export to CSV option to download the records.

The PSTN usage report is the closest thing Teams offers to a full call log spreadsheet: caller and callee numbers, call type, start time, duration, and charges for calls that touch the phone network.

Through PowerShell or the Microsoft Graph API

For repeatable or large-scale exports, admins often skip the clicking and pull data programmatically. Microsoft Graph exposes call records that you can query and dump into your own reporting system, and PowerShell cmdlets can retrieve PSTN call details in bulk. This route requires developer or IT resources, but it is the only practical way to keep a rolling archive rather than manual monthly downloads.

What’s Actually in a Teams Call Log?

Whichever method you use, the fields you get back are fairly consistent:

• Caller and callee: the numbers or user identities on each end.
• Direction: inbound, outbound, or missed.
• Timestamp: when the call started.
• Duration: how long the conversation lasted.
• Call type: internal Teams call, PSTN inbound, PSTN outbound, etc.
• Charges: for billable PSTN calls, the cost and minutes.

That is genuinely useful for billing, capacity planning, and confirming activity. But notice what is not there: there is no field telling you the caller found you through a Google ad, an organic search result, or a billboard. A Teams log knows a call happened. It does not know why.

Why a Call Log Isn’t the Same as Call Analytics

This is the gap that trips up marketers. A raw call log is a list of events. Call analytics is the interpretation of those events: patterns, sources, outcomes, and revenue. You can have every Teams call in a spreadsheet and still be unable to answer the question that pays your salary: which of our campaigns is generating phone calls?

The distinction matters because phone calls are often a business’s highest-intent leads, and they are invisible to standard web analytics. Someone clicks an ad, browses your site, then picks up the phone, and the digital trail goes cold the moment they dial. A call analytics platform exists to close that gap by tying each call back to its marketing source and turning routing data into decisions. If you want the full picture of what that layer does beyond a bare log, our guide to inbound call analytics breaks down the metrics worth tracking.

Can Teams tell you which marketing drove a call?

No, and this is the honest limitation. Microsoft Teams is a communication and collaboration platform. Its call logs record the mechanics of a call, but they contain no attribution data because Teams was never built to connect phone activity to advertising campaigns, keywords, or landing pages. If a customer calls the single number listed across your website, your Google ads, and your print flyer, the Teams log shows one number for all of them. You cannot separate the ad-driven calls from the organic ones.

To answer “which channel produced this call,” you need phone call attribution, a layer that assigns a tracked number to each marketing source (or dynamically swaps the number a web visitor sees) so every call carries its origin story with it. That is a different job from anything Teams performs.

How to Get Both: Teams Logs and Real Attribution

You do not have to abandon Teams to get marketing data. The common approach is to put a tracking number in front of your published lines. A caller dials the tracked number, the call tracking platform records the marketing source, and the call is then routed through to your Teams line or team just as before. The caller experience is identical; the difference is that now every call arrives with attribution attached.

That setup gives you three things a Teams log cannot:

• Source-level reporting. See which campaigns, keywords, and pages generate calls, not just that calls happened.
• Conversion tracking. Feed qualified calls back into Google Ads or your CRM so your reporting reflects phone leads alongside form fills.
• Outcome data. Layer on recording, transcription, and disposition so you know not just that a call connected but whether it turned into a customer.

Teams stays your phone system. The call tracking layer becomes your measurement system. Together they cover the operational log and the marketing analytics.

Frequently Asked Questions

Can you pull call logs from Microsoft Teams?

Yes. Users can view their personal call history in the Teams client under Calls → History, and administrators can export organization-wide records, including PSTN usage with numbers, timestamps, duration, and charges, from the Teams admin center as CSV, or programmatically through PowerShell and the Microsoft Graph API.

How far back do Teams call logs go?

The personal call history in the client covers a rolling recent window rather than an unlimited archive. Admin-level PSTN usage and Graph API call records reach back further, but retention depends on your Microsoft 365 plan and configuration. For a permanent archive, exporting to your own system on a schedule is the safest approach.

Can I export Teams call logs to Excel or CSV?

Yes. The admin center’s PSTN and SMS usage report includes an Export to CSV option, and the Microsoft Graph API returns call records you can save in any format. The individual user history in the Teams client, however, has no simple one-click export.

Does Teams show which marketing campaign drove a call?

No. Teams call logs record the mechanics of a call but contain no marketing attribution. To connect calls to ads, keywords, or landing pages, you need a call tracking platform that assigns tracked numbers to each source and routes the call through to your Teams line.

Can I use call tracking with Microsoft Teams?

Yes. You place a tracked number in front of your published lines, and calls route through to your Teams system after the source is recorded. The caller experience stays the same, but every call now carries the marketing data Teams alone cannot capture.

The Bottom Line

You can absolutely pull call logs from Microsoft Teams, through the client, the admin center, or the API, and for billing and activity checks, those logs do the job. What they will never do is tell you which marketing created the call. If that is the question you are trying to answer, a raw log is only half the picture. See how call tracking software sits in front of your existing phone setup to capture the source of every call while your Teams system keeps doing what it already does well.