Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Identity Auth / Azure / ManagedServiceIdentityClient
ManagedServiceIdentityClient logo

Microsoft Azure ManagedServiceIdentityClient

Browse all Azure APIs
44
AI ReadinessFoundational (D)44/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticIdentity AuthDirectory Servicesoauth27 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Provision and manage Azure user-assigned managed identities through Azure Resource Manager. Use for identity resource lifecycle, not for assigning RBAC roles or granting access to specific resources.

Use for: Create a user-assigned managed identity 'app-identity' in resource group 'prod-app', List all user-assigned managed identities in my subscription, Find managed identities assigned to a specific resource group, Update tags on the 'pipeline-identity' managed identity

Not supported: Does not assign RBAC roles, manage system-assigned identities, or issue tokens directly - use only for Microsoft.ManagedIdentity user-assigned identity resource lifecycle.

Jentic publishes the only available OpenAPI specification for ManagedServiceIdentityClient, keeping it validated and agent-ready. ManagedServiceIdentityClient is the Azure Resource Manager surface for the Microsoft.ManagedIdentity provider - user-assigned managed identities. It provisions identity resources that other Azure resources (VMs, App Services, Functions) reference to obtain AAD tokens without storing client secrets, and exposes the operations catalog for the provider.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the ManagedServiceIdentityClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ManagedServiceIdentityClient, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-managedserviceidentityclient" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-managedserviceidentityclient" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 ManagedServiceIdentityClient API.

Provision user-assigned managed identities in a resource group

List user-assigned managed identities across a subscription or resource group

Update tags or properties on an existing managed identity via PATCH

Delete user-assigned managed identities that are no longer in use

Inspect the operations catalog exposed by the Microsoft.ManagedIdentity resource provider

Use Cases

Patterns agents use ManagedServiceIdentityClient API for, with concrete tasks.

★ Provision Identities for Workload Authentication

Platform teams give applications a stable identity by provisioning user-assigned managed identities once and attaching them to compute resources (VMs, App Services, AKS clusters). The PUT on /userAssignedIdentities/{resourceName} returns the principalId and clientId - the values downstream resources use to obtain AAD tokens. Identities can be reused across resources, simplifying secret-free authentication patterns.

PUT a user-assigned managed identity 'app-prod-identity' in resource group 'app-prod' at westeurope, then return the principalId and clientId from the response so downstream RBAC role assignments can reference it.

Identity Inventory and Cleanup

Security teams audit which user-assigned managed identities exist, when they were created, and whether they are still attached to any resource. UserAssignedIdentities_ListBySubscription returns the full set; combined with Resource Graph queries for identity assignment, this surfaces orphan identities safe to delete. Removing unused identities reduces the AAD service principal sprawl.

List UserAssignedIdentities in the subscription, return name, principalId, and resource group for each, and flag identities not referenced by any resource for follow-up deletion.

Managed Identity Tag Governance

Compliance teams enforce tagging on managed identities to attribute usage and cost allocation. UserAssignedIdentities_Update (PATCH on the identity) lets an automation set or update tags such as costCenter, owner, or environment without altering the identity's principal or client IDs. Updates are atomic and do not require token refresh on dependent resources.

PATCH each user-assigned managed identity in resource group 'prod-app' to set tags costCenter=CC-1234 and owner=platform-team.

AI Agent Identity Provisioning

Platform agents that automate landing zone setup use Jentic to discover the managed identity creation operation. Searching for 'create azure user assigned managed identity' returns the schema; the agent loads it and executes against management.azure.com using a token retrieved from your Jentic One instance, so identity provisioning runs as part of larger landing zone automations without bundling the ManagedServiceIdentity SDK.

Use Jentic to search 'create azure user assigned managed identity', load the UserAssignedIdentities_CreateOrUpdate schema, and PUT the identity in the requested resource group, returning principalId for use in subsequent RBAC role assignment.

Key Endpoints

7 endpoints — jentic publishes the only available openapi specification for managedserviceidentityclient, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ManagedIdentity/userAssignedIdentities/{resourceName}

Create or update a user-assigned managed identity

GET

/subscriptions/{subscriptionId}/providers/Microsoft.ManagedIdentity/userAssignedIdentities

List user-assigned identities in a subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ManagedIdentity/userAssignedIdentities

List user-assigned identities in a resource group

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ManagedIdentity/userAssignedIdentities/{resourceName}

Delete a user-assigned managed identity

PATCH

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ManagedIdentity/userAssignedIdentities/{resourceName}

Update an identity's tags or properties

GET

/providers/Microsoft.ManagedIdentity/operations

List Microsoft.ManagedIdentity provider operations

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ManagedIdentity/userAssignedIdentities/{resourceName}

Create or update a user-assigned managed identity

GET

/subscriptions/{subscriptionId}/providers/Microsoft.ManagedIdentity/userAssignedIdentities

List user-assigned identities in a subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ManagedIdentity/userAssignedIdentities

List user-assigned identities in a resource group

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ManagedIdentity/userAssignedIdentities/{resourceName}

Delete a user-assigned managed identity

PATCH

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ManagedIdentity/userAssignedIdentities/{resourceName}

Update an identity's tags or properties

GET

/providers/Microsoft.ManagedIdentity/operations

List Microsoft.ManagedIdentity provider operations

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

M

ManagedServiceIdentityClient

- Foundational (D)
44/100
73
Foundational Compliance
63
Developer Experience & Jentic Compatibility
21
AI-Readiness & Agent Experience
94
Agent Usability
35
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
73

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
93%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

21

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
86%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

0%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

35

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
35%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Microsoft.ManagedIdentity API by hand means registering an Azure AD app, negotiating OAuth 2.0 tokens for management.azure.com, and threading subscription and resource-group scope through every user-assigned-identity call. Through Jentic you install once, import ManagedServiceIdentityClient from the API Directory, store the Azure AD credential once, and your agent calls it.

Permission scoping

This API puts the user-assigned identity in the URL path (/userAssignedIdentities/{resourceName}), so a rule can pin your agent to reading identities: it can list user-assigned identities across a subscription or resource group. You choose the operations it may call, so creating, updating, or deleting an identity is not included unless you add it.

Credential isolation

Your Azure AD credential for the ManagedIdentity control plane 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.

Intent-based discovery

Agents search Jentic by intent such as 'list user-assigned managed identities' or 'read a managed identity', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

KeyVaultClient

→

Grant a managed identity access to keys, secrets, and certificates in a Key Vault.

Use after creating an identity to give it data-plane access to a Key Vault.

Complementary

PolicyClient

→

Enforce that resources must use a user-assigned managed identity rather than embedded credentials.

Use when wrapping managed identity adoption into Azure Policy compliance.

Complementary

ManagedLabsClient

→

Grant managed identities access to Lab Services automation runbooks.

Use when classroom automation needs an identity to manage labs without static credentials.

FAQs

Specific to using ManagedServiceIdentityClient API through Jentic.

Why is there no official OpenAPI spec for ManagedServiceIdentityClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ManagedServiceIdentityClient 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 ManagedServiceIdentityClient use?

AAD OAuth 2.0 bearer tokens scoped to https://management.azure.com/. With Jentic, AAD client credentials live in the encrypted vault and a short-lived bearer token is injected into the Authorization header at call time.

Does this API assign RBAC roles to the managed identity?

No. RBAC role assignments are made through the Microsoft.Authorization provider (roleAssignments). This client only creates, updates, and deletes the identity resource itself; once you have its principalId, you assign roles separately.

What are the rate limits for the ManagedServiceIdentityClient?

Standard Azure Resource Manager throttling - typically 12,000 reads and 1,200 writes per hour per subscription per region. Identity create operations on /userAssignedIdentities/{resourceName} are normally synchronous and return the principalId and clientId in the response body.

How do I create a managed identity through Jentic?

Run pip install jentic, then search Jentic for 'create azure user assigned managed identity'. Jentic returns the UserAssignedIdentities_CreateOrUpdate schema; load it, supply the resource group, identity name, and location, and PUT to /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ManagedIdentity/userAssignedIdentities/{resourceName}.

Can I create system-assigned identities with this API?

No. System-assigned identities are toggled on the parent resource (for example, on a VM via Microsoft.Compute) and cannot exist independently. This client is only for user-assigned identities, which are independent ARM resources.

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

Yes. Because you self-host Jentic One, your own rules decide which operations and credentials the agent may use, and the identity name sits in the URL path, so you can pin the agent to read-only work such as listing user-assigned managed identities across a subscription or resource group. You choose the operations it may call, so creating, updating, or deleting an identity is excluded unless you explicitly add it. The Azure AD credential is stored by your own instance and injected only for the calls you permit.

GET STARTED

Start building with ManagedServiceIdentityClient API

Explore with Jentic One
View OpenAPI Document