MS-700 cheat sheet

Coexistence modes are Islands, Skype for Business Only, Teams Only, and SIP/Hybrid; the mode is set tenant-wide and can be overridden for individual users.

Teams Only routes all chat, meetings, and calling to Teams and disables the Skype for Business client for those workloads for the assigned user.

Guest access creates an Azure AD B2B account for an outside person; external access (federation) lets users chat and call with other domains without a guest account.

An org-wide team automatically includes every user in the tenant, stays current as users join or leave, and supports a maximum of 10,000 members.

Policy precedence on conflict: a policy assigned directly to a user overrides a group assignment, and a group assignment overrides the tenant-wide default policy.

When a user belongs to multiple groups that each have a policy assignment, the assignment with the lowest ranking number takes precedence.

Sensitivity labels for teams are created in Microsoft Purview, not the Teams admin center; a label can enforce privacy (public or private) and control guest access.

Bulk changes use Teams PowerShell: connect with Connect-MicrosoftTeams, then run cmdlets such as Grant-CsTeamsMeetingPolicy or Set-CsTeamsMessagingPolicy with -Identity or -Global.

Tenant-wide settings such as guest access, external access, and the Teams upgrade are configured in the Teams admin center under Org-wide settings.

Channel types: standard channels are open to all team members, private channels are limited to an invited subset, and shared channels connect users across teams or organizations.

A team can contain up to 30 private channels and up to 30 shared channels; each private channel is backed by its own SharePoint site.

A team can have up to 25,000 members, while an org-wide team is capped at 10,000 members.

Messaging policies control whether users can create group chats, edit or delete messages, use Giphy, memes, and stickers, and translate messages.

App permission policies allow or block apps by publisher (Microsoft, third-party, custom); app setup policies pin apps to the app bar and preinstall apps for users.

Channel moderation lets team owners designate moderators who control who can start new posts and who can reply in that channel.

Shared channels require cross-tenant B2B direct connect configuration; participants sign in with their home tenant identity and do not become guests in the host tenant.

Archiving a team makes its content read-only but keeps it searchable; deleting a team moves it to the recycle bin, where it can be restored for 30 days.

Files posted in standard channels are stored in the team's SharePoint site, while files in a private channel are stored in that channel's separate SharePoint site.

Meeting policies define who can start meetings, who bypasses the lobby, who can present, and whether recording, transcription, and screen sharing are allowed.

Lobby options include only organizers, people in my organization and trusted organizations, invited users, and everyone; presenter options include everyone, org-only, or specific people.

Teams Phone connectivity options are Microsoft Calling Plans, Direct Routing through a certified SBC, and Operator Connect; each requires a phone number and the matching license.

A dial plan applies normalization rules that convert dialed strings to E.164, and a voice routing policy maps PSTN usages to voice routes that point at SBCs or gateways.

Call queues require a resource account with a phone number and license; routing methods are attendee, serial, round robin, and longest idle.

Auto attendants answer calls and present menu options that route callers to people, call queues, or operators, and they also run on resource accounts.

Emergency calling combines emergency calling policies with emergency locations; dynamic emergency calling uses the network topology to determine the caller's address.

Live events assign organizer, producer, presenter, and attendee roles, and production can be delivered from Teams or from an external app or encoder.

Audio conferencing supplies dial-in numbers and PINs; organizers need an Audio Conferencing license, and toll-free bridge numbers require additional licensing.

Teams admin center reports cover active users, teams and channels, messages, app usage, PSTN usage, and call quality, and can be filtered by date range and exported.

Call Analytics shows per-user call history with detailed media, network, and device metrics, and is used to troubleshoot an individual user's poor call.

Call Quality Dashboard aggregates quality data tenant-wide by network, device, and location, and supports subnet-level or building-level analysis.

Teams audit events are searched in the Microsoft Purview compliance portal under Audit; Teams content is discoverable through eDiscovery and content search.

Microsoft 365 service health in the admin center lists active incidents and advisories, while Message center announces upcoming service changes.

Teams desktop client logs are written to %appdata%\Microsoft\Teams\logs.txt on Windows, and web client diagnostics are captured through browser developer tools.

The Microsoft 365 network connectivity test validates required endpoints, ports, and latency for Teams; QoS depends on DSCP tagging and UDP ports 3478-3481.

Tool choice: Call Analytics for one user's call problem, Call Quality Dashboard for tenant-wide quality trends, and usage reports for adoption and activity.

Channel messages are stored in the Microsoft 365 group mailbox and channel files in SharePoint, while chat messages are stored in the participants' mailboxes.