Domain 1: Plan and design collaboration communications systems
- Meeting format follows the interaction model: a meeting for interactive participants, a webinar where registration and attendee reporting matter, a town hall for one-to-many broadcast at scale, a virtual appointment for scheduled business-to-customer engagements.
- Teams Phone supplies the PBX capability and nothing more. Reaching the public network needs a separate connectivity option: Calling Plan, Operator Connect, Direct Routing or Teams Phone Mobile. Mistaking one for the other is the commonest scoping error.
- Operator Connect keeps the customer's carrier while the operator owns the session border controllers; Direct Routing keeps the carrier and puts the infrastructure burden on the customer. That trade-off, not price, is usually what decides it.
- Shared Calling gives light PSTN users an outbound number they share, and each participating user still needs their own emergency location. That requirement is the one most often missed and its failure is invisible until it matters.
- Service numbers carry far higher concurrency than user numbers, which is why auto attendants, call queues and conferencing bridges need them. The type is chosen when the number is acquired, not at assignment.
- Network readiness is measured, not assumed: the Network Assessment Tool measures whether an existing path performs, while Network Planner estimates the bandwidth a site will need. They answer different questions.
- QoS only acts where the organisation controls the equipment, so it addresses congestion inside the network rather than conditions on the internet path. Audio takes the highest priority because it degrades most noticeably.
- Emergency calling coverage is derived from the network topology, with wireless access points and switch ports giving finer resolution than a subnet alone. Any gap falls back to a registered address silently.
Domain 2: Configure and manage Teams meetings, webinars, and town halls
- Three layers decide a user's experience: tenant-wide meeting settings establish what is possible, assigned policies determine what that user may use, and per-meeting options or a template determine how one meeting behaves.
- Policy precedence is deterministic. A direct assignment beats any group assignment; failing that, group assignments are evaluated by ranking; failing that, the global default applies. An overlooked direct assignment explains most surprises.
- A meeting template presets options and can lock them, which is how a required configuration is enforced on a class of meeting. Templates become visible to organisers only through an assigned meeting template policy.
- A sensitivity label applied to a meeting carries enforced meeting options, linking meeting protection to the classification scheme already used for documents.
- Watermarking deters and attributes casual capture rather than preventing it. Describing it as prevention sets an expectation the control cannot meet.
- Audio conferencing is licensed on the organiser, not on the people dialling in. Toll-free inbound and dial-out draw on funded consumption, so an exhausted balance stops them working.
- Registration scope and lobby admission are separate controls, which is why an event can accept public registrations while nobody can actually join.
- The Call Quality Dashboard aggregates trends across the tenant; Call Analytics examines one user's sessions. Using the wrong one is a common inefficiency.
Domain 3: Implement and configure Teams Phone
- The evaluation order is normalise, then check permission, then route. A call failing immediately is usually normalisation, one refused is permission, and one failing at connection is routing.
- Normalisation rules are evaluated in order and the first match wins, so a broad rule above a specific one prevents the specific one ever being reached.
- Unassigned number routing is configured per range, which is what handles the retired numbers customers keep dialling without an entry per number.
- Auto attendants and call queues each need their own resource account, but only those reachable from outside need a phone number. A queue behind an attendant needs none.
- Queue agents supplied by a group stay current as people join and leave; individually named agents drift, leaving a queue offering calls to departed staff.
- Overflow triggers on the number of waiting calls and timeout on the duration of one wait. Both need a destination, and both left at defaults is how callers get disconnected without explanation.
- Emergency calling fails silently: a gap in the topology produces a call carrying a plausible but wrong address rather than an error, which is why testing from each location is the only real control.
- On Direct Routing, route availability comes from the usage records in a user's voice routing policy. A policy containing only domestic usages is how a population is restricted from international destinations.
Domain 4: Configure and manage Teams Rooms and devices
- A room signs in as a resource account on an unattended device, so policies written for user workstations produce lock screens and credential prompts. Rooms need their own group and their own policy set.
- Room account exceptions to interactive requirements are bounded by compensating controls, typically restricting the account to the network locations or the device the room actually uses.
- Teams Rooms Basic is the no-cost tier up to a capped number of rooms; Pro adds the advanced audio and video capabilities and the management portal that makes an estate of any size operable.
- Calendar processing on the room mailbox decides whether the subject and organiser survive, which determines what the console and the panel outside display, and is also a privacy decision.
- Android devices frequently run without Google services and enrol through AOSP device management, which is a different path from standard Android enrolment.
- On a shared device the session timeout is the setting that matters: a session left open hands the next person the previous user's identity and calls.
- Monitoring reports what the device can observe. It cannot see a wrong display input, moved furniture or changed acoustics, so periodic physical checks catch a different class of fault.
- A bring your own device space has no console and so no one-touch join, but it can still be represented for booking and its peripherals can still be monitored.
MS-721: Collaboration Systems Engineer exam tips
- Microsoft publishes the four weights as ranges (20-25 / 15-20 / 30-35 / 20-25), so treat Teams Phone as roughly a third of the exam and weight your preparation accordingly. Its six sub-areas are the widest ground in the blueprint.
- For any calling failure, reason in the order the platform does: normalise, permit, route. Most scenario questions are solvable by identifying which of those three stages the described symptom belongs to.
- When a question asks which layer owns a behaviour, check whether it must hold for everyone (tenant-wide setting), varies by person (policy), or applies to one meeting (options or template). Applying a rule at the wrong layer is the trap.
- Emergency calling questions reward knowing that the failure is silent. Anything relying on a configuration review rather than a test from each location is the wrong answer.
- For rooms, remember the device is unattended and signs in as a resource account. Answers that assume an interactive user, or that apply workstation policy to a room, are wrong for that reason.
- Where several answers are technically possible, prefer the one that scales: group assignment over per-user, group-supplied queue agents over named individuals, configuration by room category over per-device.
Study guide FAQ
What format and passing requirements does MS-721 have?
You have 100 minutes and need a score of 700 or greater to pass. There is no stated prerequisite, the certification renews every 12 months, and the exam is offered in English, Chinese (Simplified), French, German, Japanese, Portuguese (Brazil) and Spanish. Microsoft does not publish a fixed question count for role-based exams.
How does MS-721 relate to MS-700?
MS-700 is the Teams Administrator exam and covers the platform broadly. MS-721 goes deep on the communications half: Teams Phone and PSTN connectivity, meetings and webinars and town halls, and Teams Rooms and certified devices. There is overlap in the meetings area, but the telephony and device depth here is well beyond what MS-700 asks.
Which section carries the most weight?
Implement and configure Teams Phone, at 30 to 35 per cent. It also covers the widest ground, spanning dial plans and calling policies, auto attendants and call queues, emergency calling, licensing and number assignment, calling features, and Direct Routing. If your background is meetings rather than telephony, that is where the gap usually sits.
How much networking knowledge does the exam expect?
A working understanding rather than a network engineer's depth. You should know why real-time media is sensitive to loss and jitter rather than bandwidth, what QoS can and cannot influence, why media should egress close to the user and bypass inspection, and how the network topology feeds dynamic emergency calling and location-based routing.
Do I need hands-on experience with Teams Rooms hardware?
It helps considerably, because several answers turn on the physical reality of a room: microphone coverage that does not reach the far end of a table, a content camera that cannot see the whole whiteboard, a display switched to the wrong input. Those are the faults that dominate real room estates and the exam reflects that practical emphasis.