What's changed: Created MS-700 Chapter 3 (domain: Manage teams, channels, chats, and apps). Create/manage teams (Advisor for Teams; create via admin center/client/PowerShell/Graph/from existing groups or templates; template policies; owner/member; privacy/sensitivity; frontline teams), channels and chats (standard/private/shared channels, channel settings, messaging policies), and apps (org-wide app settings, app setup policies, app permission policies, consent/block, extensibility tabs/messaging extensions/workflows, Teams app store, upload).
3.1Create and manage teams
Understand rollout planning with Advisor for Teams, creating teams via multiple methods (admin center / client / PowerShell / Graph / from existing groups or templates), team templates and template policies, membership and roles, privacy/sensitivity, and frontline teams.
Create teams by the method that fits the purpose, and set membership and roles, privacy and classification appropriately.
3.1.1Ways to create a team
Create teams in the Teams admin center, the Teams client, the Teams PowerShell module, or Microsoft Graph. Creating from an existing Microsoft 365 group, SharePoint site, or team inherits members/resources. Creating from a team template quickly deploys a team with a predefined structure of channels/apps; template policies control which templates users can use. Plan large rollouts with Advisor for Teams.
3.1.2Membership, roles, and classification
Team roles are owner and member. Owners can change settings and manage members; members mainly join and post. Privacy is public (anyone can join) or private (approval), and a sensitivity label applies classification/encryption/guest control. For frontline workers, configure frontline teams for shift- and task-oriented experiences.
Cues: "deploy quickly with a predefined channel/app structure" = team template. "inherit existing members/resources" = create from an existing M365 group/SharePoint site. "change settings/manage members" = owner; "join/post" = member. "public/private" = privacy; "classify/encrypt/guest control" = sensitivity label. "plan large rollouts" = Advisor for Teams.
Watch the mix-ups: (1) Create from a template (predefined structure) vs from an existing group (inheritance). (2) Owner (admin rights) vs member (participation). (3) Privacy (public/private) vs sensitivity label (classify/protect) are separate. (4) Template policies control which templates are available—distinct from the templates themselves.
3.1.3Section summary
- Create teams via admin center/client/PowerShell/Graph/from existing groups or templates
- Roles are owner (admin) and member (participate); privacy is public/private; sensitivity labels classify/protect
- Advisor for Teams plans large rollouts; frontline teams suit frontline workers
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. You want to quickly and consistently deploy teams with a predefined channel/app structure to many departments. Best?
Q2. You want to create a team inheriting the members and resources of an existing Microsoft 365 group. Best?
Q3. Which role can change team settings and manage members?
Q4. You want to apply classification, encryption, and guest-access control to a sensitive team. Best?
Q5. You want to plan a large Teams rollout across the org and check readiness/recommendations. Best?