MS-700 — Frequently Asked Questions

No, the Teams Administrator role does not include permissions to manage physical Teams devices. You must assign the Teams Device Administrator role.

You need either the Teams Service Administrator or Teams Device Administrator role to view device health and peripheral status.

An access review only recertifies group membership or role assignments on a schedule; it never presents a terms-of-use document at sign-in, so fabrikam.com guests would still reach Teams first.

No. PIM controls just-in-time activation of privileged administrative roles, not guest access to a standard Teams channel or acceptance of a terms-of-use policy.

E2EE is a client/licensing capability, not a VDI platform limitation, and the E5 subscription's Teams Premium licensing covers it. The VDI client only drops locally rendered background effects.

Yes. Live captions are generated by the cloud transcription service and multi-window is supported in the new Teams VDI client, so neither is one of the unavailable features.

Tenant and site sharing settings only control how content can be shared externally; they do not override the site-collection lock that removes a chat recipient's limited-access permission.

On the OneDrive site that stores the file: open Site settings, then Site collection features, and select Deactivate next to Limited-access user permission lockdown mode.

Outbound settings control your users accessing shared channels hosted by other tenants. Here the marketing department hosts the channel and invites external users, so inbound access is required.

The requirement is for the marketing department only, and the least-privilege principle means you should scope the Teams policy to that department rather than enabling it for all users.

In the Teams admin center under Teams devices > Panels > Configuration profiles, toggle Maximum room occupancy notification for the panel.

No. Meeting policies control meeting features, while panel display settings like occupancy notifications are managed through device configuration profiles.

It only verifies network connectivity to Microsoft 365 endpoints; guest invitation failures are caused by configuration or policy, not network paths.

They run automated checks against your Teams guest access configuration and policies, pinpointing what blocks User1 from inviting guests.

Teams real-time media uses UDP 3478–3481; TCP 3478–3481 carries no media, so the warning persists. Clients would fall back to TCP 443 with degraded quality.

No. The connectivity test simulates client-to-cloud calls, so only outbound UDP 3478–3481 is required from the test location's network.

Teams Rooms Pro is for dedicated Microsoft Teams Rooms systems, not for standalone Teams conference phones, which require a Microsoft Teams Shared Device license.

No, Microsoft 365 E5 is a user license and cannot be assigned to a shared device; use a Microsoft Teams Shared Device license instead.

Retention policies in Microsoft Purview don't depend on the unified audit log; auditing powers audit search, activity reports and some eDiscovery features. Option D does not fix the F1 licensing blocker for Teams chats and channel files.

Teams retention guidance requires an appropriate license such as Office 365 E3 or A3, so F1 users must be upgraded (option A) before a one-year retention policy can apply to their chats and channel files.

Because it also manages calling and meeting features, which exceeds the read-only requirement, whereas Support Engineer only adds report access.

No, that role is limited to the Call Quality Dashboard and cannot access activity reports in the Microsoft 365 admin center.