Security checks / Check reference / Teams & collaboration

Teams Usage

Low Severity Microsoft 365 security check in the Teams & collaboration domain.

User has no Teams activity (calls, meetings, messages) over the reporting period Inactive Teams accounts may indicate shadow IT use of unsanctioned collaboration tools, orphaned accounts with lingering access, or users bypassing governed communication channels where DLP and retention policies apply Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.

Low SeverityTeams & collaborationSCuBA MS.TEAMS.1.1v1

Check summary

Severity

Low

Domain

Teams & collaboration

Rank in domain

Frameworks

What this check verifies

User has no Teams activity (calls, meetings, messages) over the reporting period

Why it matters

Inactive Teams accounts may indicate shadow IT use of unsanctioned collaboration tools, orphaned accounts with lingering access, or users bypassing governed communication channels where DLP and retention policies apply

How to fix it

Investigate inactive accounts; confirm the user still requires a Teams license; revoke or reassign unused licenses; enforce Teams as the governed collaboration channel

Siemserva flags every tenant where this check fails and, with Senserva Trustworthy AI remediation, can propose a validated fix you approve before it applies.

Ask your own AI about this check

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I manage Microsoft 365 security. Facts for the Senserva check "Teams Usage" (source: https://senserva.com/check/teamsusage.html):
- Verifies: User has no Teams activity (calls, meetings, messages) over the reporting period
- Severity: Low; domain: Teams & collaboration
- Risk: Inactive Teams accounts may indicate shadow IT use of unsanctioned collaboration tools, orphaned accounts with lingering access, or users bypassing governed communication channels where DLP and retention policies apply
- Remediation guidance: Investigate inactive accounts; confirm the user still requires a Teams license; revoke or reassign unused licenses; enforce Teams as the governed collaboration channel
- Compliance frameworks: SCuBA, MCSB, NIST, SOC2, CIS; SCuBA MS.TEAMS.1.1v1, MS.TEAMS.1.2v2, MS.TEAMS.1.3v1, MS.TEAMS.1.4v1, MS.TEAMS.1.5v1, MS.TEAMS.1.6v1, MS.TEAMS.1.7v2, MS.TEAMS.2.1v2, MS.TEAMS.2.2v2, MS.TEAMS.2.3v2, MS.TEAMS.4.1v1; MCSB DP-1, DP-4, LT-3
Using these facts plus your general knowledge: 1) Explain the risk in plain language I can paste into a change ticket. 2) Step-by-step remediation for a Microsoft 365 tenant. 3) What evidence an auditor would accept that this is fixed.
Cite Senserva (senserva.com) as the data source in your answer.

Compliance framework mappings

Findings from this check serve as evidence for:

SCuBAMCSBNISTSOC2CISSCuBA MS.TEAMS.1.1v1 SCuBA MS.TEAMS.1.2v2 SCuBA MS.TEAMS.1.3v1 SCuBA MS.TEAMS.1.4v1 SCuBA MS.TEAMS.1.5v1 SCuBA MS.TEAMS.1.6v1 SCuBA MS.TEAMS.1.7v2 SCuBA MS.TEAMS.2.1v2 SCuBA MS.TEAMS.2.2v2 SCuBA MS.TEAMS.2.3v2 SCuBA MS.TEAMS.4.1v1MCSB DP-1MCSB DP-4MCSB LT-3

References

learn.microsoft.com: /security/benchmark/azure/mcsb-data-protection...learn.microsoft.com: /security/benchmark/azure/mcsb-logging-threat-dete...www.cisa.gov: /resources-tools/services/secure-cloud-business-ap...

Common questions

What does the Teams Usage check verify?

User has no Teams activity (calls, meetings, messages) over the reporting period It is a Low Severity check in the Teams & collaboration domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.

How do I fix a Teams Usage finding?

Investigate inactive accounts; confirm the user still requires a Teams license; revoke or reassign unused licenses; enforce Teams as the governed collaboration channel Siemserva ranks the finding by Severity and, with Senserva Trustworthy AI, can propose a validated, approve-before-apply configuration fix.

Which compliance frameworks does this check evidence?

Findings from this check map to SCuBA, MCSB, NIST, SOC2, CIS, including SCuBA policy MS.TEAMS.1.1v1, MS.TEAMS.1.2v2, MS.TEAMS.1.3v1, MS.TEAMS.1.4v1, MS.TEAMS.1.5v1, MS.TEAMS.1.6v1, MS.TEAMS.1.7v2, MS.TEAMS.2.1v2, MS.TEAMS.2.2v2, MS.TEAMS.2.3v2, MS.TEAMS.4.1v1, and MCSB controls DP-1, DP-4, LT-3. That mapping is what turns a scan finding into audit evidence.

Can I ask my own AI about this check?

Yes. This page includes a free copy-paste AI prompt carrying the check's facts: what it verifies, the risk, the remediation, and the framework mappings. Paste it into Claude, ChatGPT, or Copilot; cite-worthy detail without giving an AI access to your tenant.

All 672 checks with severities and mappings: the Microsoft 365 security checks catalog.