Open Connection requirements

Go to Intune deployments and select Connection requirements. The Microsoft Intune connection dialog describes four prerequisites: Verified company directory, Administrator consent, Certificate authentication and Signed Windows agent package.

This is an informational checklist. It does not open Microsoft's consent screen, register an Entra application, collect a certificate or activate a connector. The public preview has no live Microsoft sign-in flow.

Read the initial permission plan

The dialog lists GroupMember.Read.All and DeviceManagementApps.Read.All as the initial read permissions for group membership and Intune app configuration. It separately lists DeviceManagementApps.ReadWrite.All as a permission that future publishing would require after review.

The current connection screen states that no file, mailbox, group-write or device-wipe access is requested. Treat that as the scope of this development slice. Planned SharePoint, OneDrive or sensitivity-label features are separate designs and must not be assumed active because their checkboxes appear in a local draft.

Save only a directory plan

Edit directory plan opens Microsoft 365 configuration. Microsoft Entra tenant ID is optional and expects a directory ID in the displayed UUID format. It is not a field for a secret, access token or certificate.

SharePoint & OneDrive context and Sensitivity-label context record intended context preferences. Select Save integration draft to store those choices in the current browser workspace. Saving a valid-looking ID does not prove tenant control or grant permissions.

Prepare for a future pilot

An authorized company administrator will need to review the actual application, requested permissions and deployment scope when live onboarding is available. Do not send private keys, passwords or tokens through the contact form or app fields. For current planning questions, use https://aitooltracking.com/contact/ and describe the intended integration without secrets.