Microsoft Azure IntuneResourceManagementClient
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentSecurityComplianceoauth233 EndpointsREST
For Agents
Define iOS and Android MAM policies, target them at AAD groups and applications, and review flagged users that breach Intune protection rules.
Use for: I want to create a new iOS app protection policy in Intune, List all Android MAM policies for the tenant location, Attach a managed app to an existing iOS policy, Target an Android policy at a specific AAD group
Not supported: Does not handle device enrollment, conditional access, or Microsoft Graph deviceManagement — use for the legacy Microsoft.Intune ARM MAM policy surface only.
Jentic publishes the only available OpenAPI specification for IntuneResourceManagementClient, keeping it validated and agent-ready. The Microsoft.Intune resource provider API manages mobile application management (MAM) policies for iOS and Android applications under an Azure tenant. It exposes 33 ARM endpoints to define platform-specific app protection policies, attach them to managed apps and AAD groups, and surface flagged users whose devices have triggered policy violations.
Install Jentic One Beta
Connect the IntuneResourceManagementClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the IntuneResourceManagementClient, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with IntuneResourceManagementClient API.
Define iOS and Android app protection policies under Microsoft.Intune
Attach managed applications to a named MAM policy
Target a policy at one or more Azure Active Directory groups
List Intune service locations available for a tenant by hostName
Surface flagged users and their flagged enrolled apps for compliance review
Use Cases
Patterns agents use IntuneResourceManagementClient API for, with concrete tasks.
★ Onboarding a New Mobile App to MAM
When a company rolls out a new internal iOS or Android app, the security team uses the Intune RP to attach the app to existing app protection policies and target the same AAD groups that already receive other managed apps. The API exposes per-platform policy and apps endpoints, so a single script handles both iOS and Android variants. Onboarding becomes a few-minutes operation rather than a click path through the portal.
PUT the app 'com.acme.fieldworker' onto iOS policy 'fieldworker-policy' under hostName 'fef.msua06' and confirm the response.
Compliance Audit of Flagged Users
Compliance teams pull the list of flaggedUsers under their Intune location and, for each one, walk the flaggedEnrolledApps to understand which apps triggered the violation. The output drives outreach or device wipe workflows. Because the endpoints are scoped under /locations/{hostName}/flaggedUsers, the audit naturally partitions per Intune location.
List all flaggedUsers under hostName 'fef.msua06' and emit a CSV with userName plus the count of flaggedEnrolledApps.
Group-Targeted Policy Rollout
Roll a new MAM policy out by stages: create the policy, attach the relevant apps, and target the groups in waves by adding them to the policy's groups collection. The API supports per-group attachments under both androidPolicies and iosPolicies, so a single rollout script can mirror the same wave plan across both platforms. Setup of a phased rollout is roughly half a day.
Add AAD groupId 'pilot-users' to androidPolicy 'pilot-mam' under hostName 'fef.msua06'.
Agent-Driven Intune Operations via Jentic
An AI agent can automate Intune MAM tasks through Jentic without holding raw Azure AD credentials. The agent searches Jentic for 'create an Intune iOS app protection policy', loads the operation schema, and executes against Microsoft.Intune. Jentic's MAXsystem injects a scoped bearer token for management.azure.com so the agent never sees the AAD client secret.
Use the Jentic MCP tool azure_intune_create_ios_policy to create policy 'mfa-required' under hostName 'fef.msua06' with default settings and return the resource id.
Key Endpoints
33 endpoints — jentic publishes the only available openapi specification for intuneresourcemanagementclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/providers/Microsoft.Intune/locations
List Intune service locations available to the tenant
GET
/providers/Microsoft.Intune/locations/{hostName}/iosPolicies
List iOS app protection policies
PUT
/providers/Microsoft.Intune/locations/{hostName}/iosPolicies/{policyName}
Create or update an iOS policy
GET
/providers/Microsoft.Intune/locations/{hostName}/androidPolicies
List Android app protection policies
PUT
/providers/Microsoft.Intune/locations/{hostName}/androidPolicies/{policyName}/groups/{groupId}
Target an Android policy at an AAD group
GET
/providers/Microsoft.Intune/locations/{hostName}/flaggedUsers
List flagged users at the location
GET
/providers/Microsoft.Intune/locations/{hostName}/flaggedUsers/{userName}/flaggedEnrolledApps
List a flagged user's flagged enrolled apps
GET
/providers/Microsoft.Intune/locations
List Intune service locations available to the tenant
GET
/providers/Microsoft.Intune/locations/{hostName}/iosPolicies
List iOS app protection policies
PUT
/providers/Microsoft.Intune/locations/{hostName}/iosPolicies/{policyName}
Create or update an iOS policy
GET
/providers/Microsoft.Intune/locations/{hostName}/androidPolicies
List Android app protection policies
PUT
/providers/Microsoft.Intune/locations/{hostName}/androidPolicies/{policyName}/groups/{groupId}
Target an Android policy at an AAD group
GET
/providers/Microsoft.Intune/locations/{hostName}/flaggedUsers
List flagged users at the location
GET
/providers/Microsoft.Intune/locations/{hostName}/flaggedUsers/{userName}/flaggedEnrolledApps
List a flagged user's flagged enrolled apps
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD OAuth 2.0 client secrets for management.azure.com are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped bearer tokens — raw client secrets never enter the agent's context.
Intent-based discovery
Agents search Jentic by intent (e.g. 'create an Intune iOS policy') and Jentic returns the matching Microsoft.Intune operation with its parameter schema, so the agent can call the right endpoint without parsing the legacy Intune RP docs.
Time to first call
Direct Intune RP integration: 2-4 days to wire AAD against the management audience, walk the platform-specific policy paths, and handle long-running ARM responses. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using IntuneResourceManagementClient API through Jentic.
Why is there no official OpenAPI spec for IntuneResourceManagementClient?
Microsoft does not publish a maintained OpenAPI 3 specification for the Microsoft.Intune resource provider. Jentic generates and maintains this spec so that AI agents and developers can call IntuneResourceManagementClient via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the IntuneResourceManagementClient use?
It targets management.azure.com and requires Azure Active Directory OAuth 2.0 bearer tokens like every other Azure Resource Manager call. Through Jentic the AAD client secret is held in the Jentic vault (MAXsystem) and a scoped token is injected per call so the agent never sees raw secrets.
Can I attach a managed app to an existing MAM policy?
Yes. PUT to /providers/Microsoft.Intune/locations/{hostName}/iosPolicies/{policyName}/apps/{appName} for iOS, or the equivalent androidPolicies path for Android. The path-bound app and policy names identify the link uniquely.
What are the rate limits for IntuneResourceManagementClient?
It runs on the Azure Resource Manager plane, which throttles at roughly 12,000 reads and 1,200 writes per hour per subscription, surfaced via x-ms-ratelimit-remaining-subscription-* headers. The Intune RP does not document tighter per-resource limits.
How do I list flagged users through Jentic?
Run pip install jentic, then search Jentic with 'list intune flagged users', load the flaggedUsers list operation, and execute with the hostName parameter. Jentic returns the JSON array of flagged users for the location.
Does this API replace the Microsoft Graph Intune endpoints?
No — it covers the legacy Microsoft.Intune ARM resource provider focused on MAM policies. For modern Intune device and policy management, Microsoft Graph (deviceManagement) is the supported surface. Use this API only when you need the ARM-style MAM resources it exposes.
GET STARTED