canonical: https://jentic.com/apis/azure.com/intuneresourcemanagementclient

# Microsoft Azure IntuneResourceManagementClient

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.

## For AI agents

Define iOS and Android MAM policies, target them at AAD groups and applications, and review flagged users that breach Intune protection rules.

## Scope

Does not handle device enrollment, conditional access, or Microsoft Graph deviceManagement - use for the legacy Microsoft.Intune ARM MAM policy surface only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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 your Jentic One instance injects a scoped bearer token for management.azure.com so the agent never sees the AAD client secret.

Example prompt: 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

| 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 |

## Key resources

- **Locations** — Per-tenant Intune service locations identified by hostName
- **AndroidPolicies** — Android app protection policies, their associated apps, and AAD group targets
- **iOSPolicies** — iOS app protection policies, their associated apps, and AAD group targets
- **Apps** — Managed mobile apps eligible for attachment to MAM policies
- **FlaggedUsers** — Users whose devices have triggered Intune policy violations

## Why Jentic

- **Setup:** Wiring the legacy Microsoft.Intune ARM MAM surface by hand means registering an Azure AD app, negotiating OAuth 2.0 tokens for management.azure.com, and routing every policy call through the correct Intune location host. Through Jentic you install once, import IntuneResourceManagementClient from the API Directory, store the Azure AD credential once, and your agent calls it.
- **Permission scoping:** This API puts the location host and policy in the URL path (/locations/{hostName}/iosPolicies/{policyName}), so a rule can pin your agent to one location's iOS or Android policies: it can list and read those policies. You choose the operations it may call, so writing a policy or editing its group assignments is not included unless you add it.
- **Credential handling:** Your Azure AD credential for the Intune ARM surface is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list Intune iOS MAM policies' or 'read flagged Intune users', and Jentic returns the matching Intune operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Azure Key Vault** — Key Vault stores the certificates and secrets that managed mobile apps and Intune connectors consume.
- **Azure IoT Hub** — IoT Hub manages connected devices rather than mobile end-user apps and policies.
- **Azure Stack InfrastructureInsights** — InfrastructureInsights covers Azure Stack platform alerts rather than mobile app policy.

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

### 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 your Jentic One instance 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.

### Can I limit what my agent is allowed to do with the Microsoft Azure Intune API?

Yes. Because Jentic One is self-hosted, your own rules decide which Intune operations and credentials the agent may use, and this API puts the location host and policy in the URL path (/locations/{hostName}/iosPolicies/{policyName}), so you can pin the agent to a single location's iOS or Android policies. You choose the exact operations it can call, so you can grant read-only access such as listing iOS or Android MAM policies and reading flagged users while withholding writes. Creating or updating a policy and editing its group assignments stay off limits unless you explicitly add those operations. The stored Azure AD credential is injected only at execution time, so the agent never sees the raw secret.