Instiq
Chapter 3 · Manage teams, channels, chats, and apps·v1.0.0·Updated 6/29/2026·~13 min

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.2Channels and chats

Key points

Understand standard/private/shared channels, adding/editing/removing channels, channel settings, private/shared channel membership, and messaging policies.

Channels differ by who can access them. Chat features are controlled by messaging policies.

3.2.1Channel types

A standard channel is accessible to all team members. A private channel is accessible only to a limited subset of team members and has a dedicated SharePoint site. A shared channel (Teams Connect) can be shared with other teams or external orgs, and participants access the channel without joining the team. Choose by requirement (everyone/limited/external).

3.2.2Channel settings and messaging policies

Channels can be added/edited/removed, and channel settings configure moderation, mentions, connectors, etc. Messaging policies allow/disallow chat features per user (edit/delete messages, read receipts, giphy/stickers, priority, translation). Distinguish "channel type and access" from "chat feature control (messaging policy)."

Exam point

Cues: "all team members can access" = standard channel. "limited subset only, dedicated SharePoint" = private channel. "shared with other teams/external orgs, no team join" = shared channel. "control chat features like edit/delete or giphy" = messaging policy.

Warning

Watch the mix-ups: (1) Standard (everyone) vs private (limited members) vs shared (external). (2) A private channel has its own SharePoint site. (3) Messaging policies (chat feature control) are separate from channel type. (4) External use of shared channels requires B2B direct connect + cross-tenant access (see ch2).

Diagram: a standard channel is for all team members; a private channel is for a limited subset with its own SharePoint; a shared channel is shared with other teams/external (no team join); channel settings configure moderation; messaging policies allow/disallow chat features (edit/delete/giphy).
Who can access

3.2.3Section summary

  • Standard = all members; private = limited members (own SharePoint); shared = other teams/external
  • Channel settings configure moderation; messaging policies allow/disallow chat features
  • External shared channels require B2B direct connect + cross-tenant access

Sign in to track progress — Log in.

Quick check

(just a quick review)

Q1. You need a channel accessible only to a subset of team members with its own SharePoint site. Best?

Q2. You want ongoing collaboration with another org’s team in one channel without either side joining the team. Best?

Q3. You want to control whether users can edit/delete chat messages or use giphy. Best?

Q4. Which is the most standard channel that everyone in the team can access automatically?

Q5. What correctly distinguishes a private channel from a shared channel?

Check your understandingPractice questions for Chapter 3: Manage teams, channels, chats, and apps