Resources · Make integration

Microsoft Intune Make integrationAutomate Microsoft Intune with Make.

Need your managed devices somewhere other than the Intune console? The Microsoft Intune Make integration gives you 2 modules: one search that lists devices and one open API call. This guide is for IT admins who want a working scenario, connection included.

Try the Microsoft Intune integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Microsoft Intune Make integration actually do?

It lets Make read your Intune tenant and act on it without code. You build a scenario, the automation Make runs for you, out of modules, each one a single brick such as a search or an action. Intune brings two of those bricks, and neither one starts a scenario by itself.

A device inventory that refreshes itself. Put List Devices first and let Make run it on the scenario's schedule. Every device comes back as its own bundle, meaning one item passed to the next module, so you can push each one into a sheet or a ticketing tool.

A request from another tool that checks Intune. A form or helpdesk app can open the scenario, then List Devices looks up what Intune knows before anyone answers the request.

Anything the list does not cover. Make an API Call reaches any endpoint of the Intune API with the connection you already set up. It is the way out when you need more than a list.

Two limits are worth knowing up front. There is no trigger in this app, so Intune never pings Make when something changes; the scenario starts on a schedule or from another app. And Make labels its own Intune documentation as AI-generated, so check important details against Microsoft. If you want a feel for the editor first, the Make review walks through it, and n8n vs Make helps if you are still choosing a tool.

Connect

How do you connect Microsoft Intune to Make?

  1. 01

    Register an app in Microsoft Entra

    Intune connects through an app registration, so an admin account on your Entra tenant is required. In the Entra admin center, open App registrations, click New registration, name it and paste https://www.integromat.com/oauth/cb/intunes as the callback URI if asked.

  2. 02

    Copy the ID and create a secret

    On the overview page, copy the Client ID. Then go to Certificates & secrets, click New client secret, pick an expiration period and click Add. Copy the secret shown on screen and keep it next to the Client ID.

  3. 03

    Create the connection in Make

    Add a Microsoft Intune module to your scenario and click Create a connection. A connection is your Intune account linked to Make once and reused by both modules. Give it a name if you like, paste the two credentials and confirm.

First scenario

Your first scenario with Microsoft Intune

GoalWhen the schedule fires, Make lists your Intune devices and calls the Intune API once for each device.

  1. 01

    Start a blank scenario

    From the Scenarios page, create a new scenario and click the big +. Search for Microsoft Intune and pick List Devices as your first module.

  2. 02

    Link your tenant

    Click Create a connection and use the Client ID and secret from the Entra registration. Once saved, the module can read your tenant and you fill in its fields.

  3. 03

    Add the API call

    Click the + to the right of List Devices and add Make an API Call. Map data from the device bundle into the request, so the call targets the device that just came through.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time, and you can open each module to read the bundles it received. Each module run on one bundle is an operation, the unit Make counts on your plan.

  5. 05

    Set the clock and switch it on

    Open the clock on List Devices. A new scenario runs every 15 minutes by default; the Free plan keeps you at 15 minutes minimum, paid plans go down to 1. Then switch the scenario on.

Modules

What the Microsoft Intune modules do

Microsoft Intune gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Microsoft Intune1

List Devices

SearchIn the docs only

This search gives you your managed devices as separate bundles, so every module after it handles one device at a time. It is the starting point for inventories, reports and per device checks.

When to use it
you need the fleet in a spreadsheet or a ticketing tool, or you want to loop over each device.
Watch out
a search can return zero, one or many bundles, and each bundle downstream costs operations.
Microsoft Intune2

Make an API Call

ActionIn the docs only

With this module you reach any endpoint of the Intune API while reusing the connection you already made. You pick the request yourself, which covers everything List Devices does not.

When to use it
after List Devices, when each device needs a follow up request the app has no ready module for.
Watch out
you write the request yourself, so read Microsoft's documentation for the endpoint and check the permissions on your app registration.
Need help

Need help automating Microsoft Intune with Make?

A person reads every message.

FAQ

Microsoft Intune and Make: common questions

01Is the Microsoft Intune Make integration free?
Yes, on the Make side. Microsoft Intune is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, a 15 minute minimum between scheduled runs, 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Your Intune subscription is a separate matter handled by Microsoft.
02What do you need to connect Microsoft Intune to Make?
An active Microsoft Entra tenant with administrator credentials, plus an app registration carrying the right Microsoft Graph API permissions. From that registration you copy a Client ID and a client secret, then paste both into Make after clicking Create a connection. The registration also asks for a callback URI, which Make's documentation provides. Without admin rights on the tenant, you will need someone who has them to create the registration.
03Can a Microsoft Intune scenario in Make run in real time?
No. The app has no trigger, so Intune cannot notify Make when a device changes. You start the scenario in one of two ways. Either put List Devices first and set a schedule on it, every 15 minutes by default and down to 1 minute on paid plans. Or let another app open the scenario, a form or a helpdesk tool for example, and add the Intune modules after it.
04What if the Intune module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Intune API with the same connection, so you are not limited to listing devices. You write the request yourself, which means checking Microsoft's documentation for the endpoint and the permissions it requires. Also keep in mind that Make openly marks its Intune page as AI-generated content, so confirm any detail that matters directly with Microsoft before building on it.
05Should you use Make or n8n for Microsoft Intune?
It depends on the tool your team already runs. Make offers two Intune modules, List Devices and Make an API Call, which covers inventory and any extra request through the API. n8n often has a node for the same app too, so the right choice comes down to which editor you prefer and where your other automations live. A side by side comparison of the two tools helps if you are still undecided.
Same platform

Other docs you might need on this stack.

Browse all integrations