What is statics.teams.cdn.office.net in my analytics?
23 September 2026 · by Nordva, who make Nordva Launch
The short answer
It means someone clicked a link to your site inside Microsoft Teams. In organisations that use Microsoft's Safe Links, Teams opens every clicked link through a check page that Microsoft serves from statics.teams.cdn.office.net, and that page then sends the person on to you. Your analytics sees the check page as the referrer, not the chat or channel the link was in.
- Referrer
- statics.teams.cdn.office.net
- What sends it
- A link clicked in Microsoft Teams, passed through its link check
- Nordva Launch counts it as
- Referral (another website or app)
- Also shows up as
- teams.microsoft.com · teams.live.com · android-app://com.microsoft.teams
Why a Microsoft host instead of Teams
Microsoft Defender for Office 365 has a feature called Safe Links. When it is on for Teams, a clicked link is checked at the moment of the click, in the Teams desktop, web and mobile apps. Microsoft’s documentation describes an intermediary page that does the check and then redirects to the page the link points to.
Microsoft doesn’t name the host in that documentation, but a “Verifying link” page sits at a Safe Links path on statics.teams.cdn.office.net, a host Microsoft uses for Teams. The browser loads the check page first, then your site. So the page that “sent” the visitor is Microsoft’s check page, and that is what your analytics records.
Safe Links is part of Microsoft Defender for Office 365, which Microsoft sells to business customers, so this referrer means the click came from inside an organisation that has it. Other clicks from Teams can show up differently:
teams.microsoft.com: Teams for work or school in a browser.teams.live.com: the free, personal Teams in a browser.android-app://com.microsoft.teams: the Teams app on Android, when it passes its name on (the Gmail app referrer page explains the form).- Nothing at all, in which case the visit counts as direct.
What it hides
The referrer only names the check page. It doesn’t say which company, which team, which channel or which message. A link your customer forwarded to their whole department and a link one person pasted into a private chat look the same.
How to see which conversation it was
When you share a link in Teams yourself, or hand one to a customer to share, tag it. The tags are part of the address, so they survive the check page:
https://example.com/?utm_source=teams&utm_medium=chat&utm_campaign=acme-pilotUse a different utm_campaign for each group you share with. Links that other people copy from your site won’t carry tags, and for those the Teams referrer is as much as you’ll get.
With Nordva Launch
Launch counts statics.teams.cdn.office.net as a referral, the channel for another website or app, and keeps the host as the referring site. The same goes for teams.microsoft.com and teams.live.com. The tagged link above also counts as a referral, with teams as its source and your campaign attached. A UTM tag that names a channel (a medium such as email or social, or a known source) wins over the referrer.
When Launch is the wrong tool
If all you need is to know that someone at a company shared your link in Teams, the referrer already tells you that. Launch is for when you want to know whether those visitors signed up and paid.
- Why is statics.teams.cdn.office.net sending me traffic?
- How do I see traffic from Microsoft Teams in analytics?
- What is teams.microsoft.com referral traffic?
- Microsoft Learn: Safe Links overview, the section on Microsoft Teams (time-of-click checks, the intermediary page that redirects to the target) (read 23 September 2026)
- Microsoft Teams: the "Verifying link" page at the Safe Links path on statics.teams.cdn.office.net (an asset, not documentation) (read 23 September 2026)
- Microsoft Support: Use Microsoft Teams on the web (teams.microsoft.com) (read 23 September 2026)
- Microsoft Support: Teams Free, whose web link (aka.ms/teamspersonal) leads to teams.live.com (read 23 September 2026)
- Google Play: Microsoft Teams (package com.microsoft.teams) (read 23 September 2026)