Teams Policies
Augmentt lets you create and manage Microsoft Teams policies for your customer tenants directly from the platform, without signing into each Teams admin center.
Secure > Teams has three pages:
Policies — per-tenant policy management, for every policy type
Templates — reusable policy and settings templates
Settings — the tenant's org-wide Teams settings
On the Policies page, five tiles filter the list by type, each showing how many policies of that type the tenant has:
Tile | What the policy controls |
|---|---|
Meeting | What users can do when scheduling, joining and running Teams meetings |
Messaging | What users can do in chats and channel conversations |
Channels | Who can create private and shared channels, and how channels are discovered |
External access | Which outside organisations and account types users can communicate with |
App setup | Which apps are pre-installed and pinned for users |
For each type you can create a policy, edit it, assign it to users and groups, and delete it.
Old links still work. If you have bookmarks or documentation pointing at the previous per-type pages —
/secure/teams/meeting-policiesand its siblings — they redirect to the consolidated Policies page. You don't need to hunt down old links, but new ones should point at Policies.
Access. You need the Manage permission on Secure to create, edit, assign or delete Teams policies. With read-only access the policy list is visible but the Create button is hidden.
Scope. These policies are written to the customer's Microsoft tenant. Changes made here appear in the Teams admin center, and changes made in the Teams admin center appear in Augmentt after the next sync.
Policies are per-user; Settings are per-tenant. A policy governs the users or groups you assign it to. The Settings page governs the whole tenant — guest access, federation, team creation. If you're trying to change something for everyone, you probably want Settings, not a policy. See the Teams Org-Wide Settings and Templates guide.