Microsoft Teamsset up securely.The same in every tenant.
Who may chat from outside, who gets into a meeting without the lobby and where files go: Conbool 365 Tenants defines it once, shows every deviation and rolls out the settings once you approve.
Why Teams is more open than expected
The defaults are built for collaboration, not for protection.
Chat with any organisation
Out of the box, users may chat with other organisations and personal Teams accounts. Attackers use exactly this route, for example posing as IT support.
Meetings without control
Anonymous participants, external people taking control and recordings nobody expected.
Files outside Microsoft 365
Dropbox, Google Drive and other storage can be added to Teams. What lives there is outside any sharing review.
Every tenant different
The settings live in the Teams admin center, tenant by tenant. What is set up cleanly at the first customer is missing at the tenth.
From template to configured Teams
Choose, compare, roll out after approval.
1. Choose entries
Tick the Teams entries from Conbool hardened. None is preselected because each one applies to every meeting.
2. Compare every tenant
365 Tenants reads the Teams settings and shows field by field what deviates. Stricter values remain.
3. Roll out with a dry run
The plan shows every change in advance. Writing happens only after approval, then every value is verified.
What the Teams entries define
Eight optional entries for chat, meetings and files.
Limited external access
No chat with personal Teams accounts and with trial tenants. Optionally no chat with other organisations at all.
Protected meetings
Guests wait in the lobby, the organiser presents and external people do not take control.
No anonymous participants
Optionally only signed-in people join.
Recording
Optionally no cloud recording of meetings.
Files stay in Microsoft 365
No third-party storage in Teams and no email from outside into channels.
Report suspicious messages
Users report suspicious messages in Teams to administrators.
Teams with a template and Teams by hand
The settings are the same. The difference lies in what comes after.
Conbool 365 Tenants | Teams admin center by hand | |
|---|---|---|
| Basis | Versioned template, the same for every tenant | Set up anew per tenant |
| Implementation | Dry run, approval, then every value verified | By hand in several areas |
| Deviations | Regular snapshot, deviation per field | Noticed at the next review |
| Changes | Every change between two snapshots in the history | Scattered across Microsoft's logs |
| Undo | Latest run can be rolled back, changed values restored | Reconstruct by hand |
| Many tenants | Distribute from the partner portal to many tenants | Every tenant a project of its own |
As of October 2026. The right-hand column describes the usual approach without a tool, not a specific vendor.
FAQ on secure Teams settings
Which Teams settings does 365 Tenants read and write?
Does this apply to all users?
Can we keep chatting with partners?
Which role does Conbool need in the tenant?
Can a change be undone?
Does 365 Tenants read chats or meetings?
Related solutions
365 Tenants
Define security settings as a template and roll them out to every tenant.
Microsoft 365 security baseline
One secure state for every tenant, with comparison and dry run.
Conditional Access templates
Conditional Access with report-only mode and checked break-glass accounts.
Intune security policies
Compliance, BitLocker and app protection for every tenant.
Microsoft 365 security check
Tenant settings and sharing in one report.
365 Permissions
Who can access what in SharePoint, OneDrive and Teams.
Entra ID Backup
Back up the users, groups and policies of the directory.
Set up Teams securely and the same in every tenant.
Choose settings, compare, roll out safely.