MS-700 common mistakes
MS-700 · Understand the traps and how to avoid them.
Answering questions about talking to people in other organizations by editing Guest access settings, and answering questions about inviting outsiders into a team by editing External access settings.
The two settings sit next to each other in the Teams admin center and both involve 'people outside the org', so candidates pattern-match on the word 'external' instead of on what the outsider needs to do (chat/call only vs. be a team member with access to files and channels).
What to do instead
Anchor on the object being shared: no team membership, no access to files, just chat/calls = External access (federation) with allow/block domain lists. Team membership, channels, SharePoint files = Guest access, which also depends on the tenant-level guest settings in Entra ID and on the team owner inviting the guest. Rehearse one scenario of each and state out loud which object is being shared.
Telling a candidate that a setting 'didn't apply' because the global policy was edited, when the user actually receives a group-assigned policy or a direct assignment.
Candidates learn the global (Org-wide default) policy first and treat it as a single switch for the tenant. Teams policies follow assignment precedence (direct assignment beats group assignment beats global), and the admin center's 'Manage users' page will show the effective policy only if you look for it.
What to do instead
In every policy scenario, ask 'who is the user and what policy are they actually assigned?'. Check the user's effective policy in the Teams admin center, then trace: direct assignment > group assignment > global. When a change must apply to one pilot group first, use a group assignment policy; when it must apply immediately to a single user, assign directly.
Assuming that granting Enterprise Voice in a calling policy, or turning on 'Teams Phone', is enough to let a user make PSTN calls.
Calling policy, dial plan, voice routing, number assignment and licensing are separate objects, and the exam wording often names only one of them. Candidates pick 'edit the calling policy' as a universal answer.
What to do instead
Build a mental checklist for any PSTN scenario: Teams Phone licence, phone number (or Direct Routing number) assigned to the user, a dial plan that normalises the number the user dials, a voice route that sends the call to a PSTN gateway/SBC, and a calling policy that permits the feature. Missing any one of them breaks the call.
Trying to stop self-service team creation from the Teams admin center's Teams settings page, or assuming a messaging policy can block it.
Team creation is tied to Microsoft 365 group creation, which is a directory/tenant-level control, not a Teams client policy. Because the option appears inside admin experiences candidates have used before, they pick the familiar Teams blade.
What to do instead
Turn off self-service creation with the Microsoft 365 Groups creation setting (Entra ID group settings / Microsoft 365 admin center org settings), then, if a subset must keep creating teams, allow the Teams 'Create teams' app only to a security group through an app permission policy. State both layers when the scenario asks for 'only the pilot team can create teams'.
Using an app permission policy when the requirement is to pin an app to the app bar, or using an app setup policy when the requirement is to make an app unavailable to a group of users.
Both are policies applied to users and both list apps, so the names blur. Candidates remember 'there is a policy for apps' but not which one controls availability versus presentation.
What to do instead
Separate the verbs: permission policies control whether a user is allowed to use an app at all (allow/block); setup policies control what is installed and pinned for the user and the order on the app bar. If the question says 'cannot use', it is permission; if it says 'visible/pinned/preinstalled', it is setup.
Assuming that adding a user to a private channel happens automatically because they are already a member of the team, or that private channel files are stored in the team's SharePoint site.
Standard channels are open to all team members, and the team site holds their files, so candidates generalise that model to every channel type.
What to do instead
Memorise the private channel contract: membership is a separate, explicit list even for team owners; only owners can add members; the channel gets its own SharePoint site collection, not a folder in the team site; and files, OneNote and the channel must be managed with that separate site in mind.
Advising that meetings must be cancelled and recreated after a meeting policy change, or looking for a per-meeting setting to change lobby behaviour.
Candidates treat meeting policies like SharePoint permissions that are baked in at creation. In fact most meeting policy values are evaluated when a participant joins, using the organizer's assigned policy.
What to do instead
State that the change takes effect for existing meetings after the policy propagates (allow for replication time); then note that some values the organizer can override per meeting in the meeting options, and that the organizer's policy - not the attendee's - governs lobby bypass, who can present and recording.
Answering a call-handling scenario with only an auto attendant or only a call queue, and forgetting the resource account and its licence/number.
Both features appear under Voice in the Teams admin center and both 'answer calls', so candidates collapse them into one answer and skip the account that the phone number must actually be assigned to.
What to do instead
Model the flow end to end: resource account (with Teams Phone and, for calling, a virtual user licence as required) carries the number, then either an auto attendant for menus and routing or a call queue for distributing to agents with a routing method and timeout/overflow, or an auto attendant that hands off to a call queue. Name every component in the answer.
Using Call Quality Dashboard (CQD) to investigate one named user's poor call, or using Call Analytics to answer a tenant-wide network trend question.
Both are 'call quality' tools in the Teams admin center and candidates conflate 'quality' with 'reporting'. The scope difference - one call/one user versus aggregated tenant data - is the whole point of the question.
What to do instead
Decide by scope and time: Call Analytics is per-user, per-call, short retention, for 'why did this person's call fail'. CQD is aggregated, near-real-time, filterable by subnet/building/network, for 'where is quality bad across the estate'. If the question names a user, choose Call Analytics; if it names a location or a trend, choose CQD.
Searching the Teams admin center for audit records or sign-in failures when the evidence lives in another portal.
Candidates expect a single 'Teams admin center' answer for every troubleshooting question, so they never reach for Microsoft Purview or Entra ID.
What to do instead
Map evidence to portal: who changed a Teams setting or who was added to a team = Purview audit log search; why a user cannot sign in or why a conditional access block fired = Entra ID sign-in logs; Teams usage and activity = Teams usage reports; device/client health = Teams-specific monitoring. Practise naming the portal before naming the tool.