The Microsoft Intune module addresses no addresses in your network but your
Microsoft tenant. Like Microsoft 365 it requires exactly one entry for that:
the Entra ID app registration through which access happens.
The wizard shows four steps for this module:
Basics › Entra ID App › Schedule › Summary
That is the same sequence of steps as with Microsoft 365, and it is the same
step: both modules choose their app from the same list.
Prerequisites
The scan captures the devices managed in Intune with user and device data and
the apps in use.
Ports and protocols
Permissions
Creating the app requires a Global Administrator—only for that. The app itself
only reads. Here too, one Entra ID app can be used for several Docusnap365
subscriptions.
Network requirements
- The gateway reaches the internet, at least
https://login.microsoftonline.com/
and https://graph.microsoft.com/.
- If a proxy sits in between, it may need exceptions.
The app registration
It is prepared under Scan › Credentials as an entry of the type
Entra ID App. How you create an entry, test access through Verify and renew
certificate and client secret is on
Microsoft 365—the path
is the same for both modules.
In the Entra ID App step you choose the prepared entry in a searchable picker;
the second line per entry names the tenant. Without a selection the step stops.
A cloud scan runs over a gateway as well: the Basics step requires a gateway
and a job name for every module.
One job per module
Microsoft 365 and Microsoft Intune are two scan modules. The same entry can
supply both, but each module needs its own job—and therefore its own schedule.
If the client secret or the certificate expires, that affects both jobs at once,
because they hang on the same app. How you keep the date in view is on
Microsoft 365. 
