WEBVTT

00:00:00.250 --> 00:00:06.585
Open Microsoft from the Network section. No customer tenant is connected in this fictional

00:00:06.585 --> 00:00:12.567
workspace, so the landing page shows a setup instruction rather than tenant or device

00:00:12.567 --> 00:00:18.550
data. This recording does not authorize a Microsoft tenant or exercise provider APIs.

00:00:19.784 --> 00:00:25.598
Open the written guide for setup and permission choices. Microsoft cloud records and fresh

00:00:25.598 --> 00:00:30.766
endpoint reports are different evidence. Read and write permissions are separate

00:00:30.766 --> 00:00:36.515
decisions. A described action does not prove that a tenant is licensed, consented or able

00:00:36.515 --> 00:00:37.484
to complete it.

00:00:38.683 --> 00:00:44.257
Follow the written guide to connect an authorized tenant with the intended permission

00:00:44.257 --> 00:00:49.504
scope. Confirm the specific collector result and tenant mapping, then verify any

00:00:49.504 --> 00:00:55.406
separately approved action in Microsoft and the RMM. A successful token or connected label

00:00:55.406 --> 00:00:57.833
alone is not full feature acceptance.
