Secure your Microsoft Teams surface
External access policy, guest sprawl, and files shared from Teams-backed SharePoint sites. We don’t connect to Microsoft Teams to collect evidence for its own sake — we connect to secure it, and the compliance artefacts follow from that work.
Book a Demo[01] What This Surface Exposes
Where Microsoft Teams goes wrong
Teams goes wrong one layer down: file exposure happens in the SharePoint site behind the team, where nobody thinks to look.
- External access permitted to any domain rather than an allow list
- Guests retained in teams long after their project ended
- Files shared via anyone-links from the underlying SharePoint site
- Apps installed with broad Graph permissions across the tenant
- Meeting recordings retained without a policy, holding sensitive discussion
[02] What We Secure
What we watch, catch and fix on Microsoft Teams
On Teams we audit the underlying SharePoint sharing alongside Teams settings, since that is where the real exposure sits.
- External access domain policy reviewed against your actual partner list
- Guest lifecycle reconciled and expired
- Underlying SharePoint sharing audited, since Teams file exposure happens at the SharePoint layer where people do not look
- App permission review across the tenant
- Recording retention treated as a data risk with a classification
[03] Where It Lands
Where Microsoft Teams lands in your registers
Workspaces and document stores enter the asset register with a data classification that reflects what is genuinely inside them rather than what policy says should be. Access reviews cover external members, guests, and link-based sharing alongside internal permissions. The risk register carries data exposure risk with the specific sharing configuration that creates it.
[04] How We Engage
On Microsoft Teams specifically
On Microsoft Teams, we remove expired guests, revoke anyone-links, and tighten app permissions. External access policy and recording retention we plan with you given the business impact.
Platform licence
Everything you need to find and fix it yourself, with no ceiling on the depth of the answer.
- Every connected tool monitored for misconfiguration and drift, with findings mapped to the assets and risks they affect
- Remediation guidance that tells you what is wrong and exactly how to fix it — however deep or awkward the issue is. We are engineers running a security company, so the answer is the real one, not a link to vendor documentation
- Assets, access reviews, and risk register populated from the tools themselves rather than from spreadsheets
- Unlimited integrations and unlimited users, with anything missing built within two weeks
Managed service
Every tool you connect through Konfirmity comes under our care, with our team doing the work.
- Continuous misconfiguration and drift monitoring across every connected tool, watched by our analysts rather than by a dashboard waiting for you
- Incident response led by us, with containment coordinated with your team
- Remediation performed directly wherever you have granted us the authority to act — and where we cannot act, we project-manage the fix to completion rather than handing you a ticket
- Decision support on the tools themselves: where something is failing you on capability or costing more than it returns, we will tell you, and help you replace it
[05] Microsoft Teams FAQs
What Teams permissions does Konfirmity need?
Konfirmity needs graph API permissions covering Team.ReadBasic.All, Channel.ReadBasic.All, Sites.Read.All and Policy.Read.All. Sites access matters because Teams file sharing is SharePoint sharing, and assessing one without the other misses most of the risk.
Do you review meeting recordings?
We review their retention and access rather than their content. Recordings capture sensitive discussion and accumulate indefinitely by default, which makes them a data risk with a classification and a retention position, not just storage consumption.
Slack
Zoom
Notion
Confluence
Google Drive