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 / Cloud Infrastructure / Azure / ManagementLinkClient
ManagementLinkClient logo

Microsoft Azure ManagementLinkClient

Browse all Azure APIs
41
AI ReadinessFoundational (D-)41/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticCloud InfrastructureComputeoauth26 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Declare and inspect logical links between Azure resources so dependency graphs survive across resource groups. Useful for tagging owners, tracking dependencies, and enforcing cleanup workflows.

Use for: I need to record that a virtual machine depends on a storage account in another resource group, List every resource link declared in this subscription, Get a resource link by ID to inspect its notes, Delete a stale resource link after one side was decommissioned

Not supported: Does not enforce dependencies, prevent deletion, or evaluate policy - use for declaring and auditing logical links between Azure resources only.

Jentic publishes the only available OpenAPI specification for ManagementLinkClient, keeping it validated and agent-ready. The Azure Resource Links API records logical relationships between Azure resources, even across different resource groups within the same subscription. Use it to create a directional link from a source resource to a target, list every link declared at a subscription or scope, and clean up dangling links when one side is deleted. Each resource can hold up to 50 outbound links and the API is authenticated via Azure Active Directory OAuth 2.0 on Azure Resource Manager.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the ManagementLinkClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ManagementLinkClient, 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-managementlinkclient" | 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-managementlinkclient" | 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 ManagementLinkClient API.

Create or update a directional link between two Azure resources, with optional notes describing the relationship

List every resource link declared in a subscription to build a dependency map

List resource links scoped to a specific source resource to inspect its outbound dependencies

Retrieve a single link by ID to inspect the source, target, and notes

Delete an obsolete link without affecting either of the linked resources

Enumerate Microsoft.Resources operations exposed for resource link management

Use Cases

Patterns agents use ManagementLinkClient API for, with concrete tasks.

★ Document cross-resource-group dependencies

Platform teams use the Resource Links API to make implicit dependencies explicit, especially when a workload spans multiple resource groups. Linking an app service to its key vault, storage account, or database produces a queryable graph that audit and incident-response tooling can rely on instead of inferring from naming conventions.

PUT /{linkId} with sourceId set to the consuming resource and properties.targetId set to the dependency, including a notes field that explains the relationship.

Cleanup stale links during decommissioning

When a workload is retired, agents iterate through the links attached to its resources and delete each one before the underlying resource is removed. The list-by-scope endpoint returns every link rooted at a given resource so the cleanup step is deterministic, and link delete is a single DELETE call per ID.

Call GET /{scope}/providers/Microsoft.Resources/links to enumerate links, then DELETE /{linkId} for each link belonging to a resource scheduled for retirement.

Build a subscription-wide dependency map

Architects feed the subscription-scoped list endpoint into a graph database to visualise how resources reference one another, often layered on top of resource groups and tags. Because links are directional, the resulting graph distinguishes between dependents and dependencies and surfaces orphaned resources that hold no inbound references.

Call GET /subscriptions/{subscriptionId}/providers/Microsoft.Resources/links and emit one edge per link with sourceId, targetId, and notes for ingestion into a graph store.

Agent-driven dependency declarations

Through Jentic, an AI agent can read a deployment plan, infer which resources reference which others, and declare links between them automatically. The agent searches Jentic for 'link azure resources', loads the input schema, and chains the create-or-update call once per relationship. Jentic injects the Azure AD bearer token at execution time.

Use Jentic search 'create azure resource link', load the operation, supply target resource ID and notes, and execute against the source link ID path.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

PUT

/{linkId}

Create or update a resource link

GET

/{linkId}

Get a resource link by ID

DELETE

/{linkId}

Delete a resource link

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Resources/links

List all links in a subscription

GET

/{scope}/providers/Microsoft.Resources/links

List links rooted at a source scope

PUT

/{linkId}

Create or update a resource link

GET

/{linkId}

Get a resource link by ID

DELETE

/{linkId}

Delete a resource link

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Resources/links

List all links in a subscription

GET

/{scope}/providers/Microsoft.Resources/links

List links rooted at a source scope

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

ManagementLinkClient

- Foundational (D-)
41/100
68
Foundational Compliance
56
Developer Experience & Jentic Compatibility
20
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
68

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B+Signals: 4
97%

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

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

56

Developer Experience & Jentic Compatibility

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

Grade: CSignals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

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.

20

AI-Readiness & Agent Experience

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

Grade: FSignals: 4
79%

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 Resource Links API by hand means setting up MSAL and an Azure AD service principal, minting bearer tokens against management.azure.com, and handling the unusual nested {linkId} routing plus nextLink pagination yourself. Through Jentic you install once, import ManagementLinkClient from the API Directory, store the service principal credentials once, and your agent calls it.

Permission scoping

The link id travels in the URL path (/{linkId}), so a rule can pin your agent to creating and reading links under a named source scope. You choose the operations it may call, so deleting a resource link is not included unless you add it.

Credential isolation

Your Azure AD client credentials are stored once, encrypted, by your own Jentic One instance and exchanged for a short-lived ARM-scoped bearer token at execution time. The raw secret never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'link two azure resources together' or 'list all resource links in a subscription', and Jentic returns the matching ResourceLinks operation with its input schema so the agent declares links without reading the ARM documentation.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Resource Management Client

→

Manage the resources and resource groups that links reference.

Use Resource Management to look up source and target resource IDs before declaring links.

Complementary

Management Lock Client

→

Apply read-only and delete locks to the resources tracked by links.

Pair with links when the goal is both to document and to protect a dependency chain.

Alternative

Azure Resource Graph

→

Query Azure resources at scale with KQL rather than maintaining explicit links.

Pick Resource Graph for ad-hoc queries; pick Resource Links to record explicit, owner-curated dependencies.

Complementary

Policy Client

→

Enforce that certain resources must always declare links before deployment.

Combine with links to require dependency documentation as a deployment gate.

FAQs

Specific to using ManagementLinkClient API through Jentic.

Why is there no official OpenAPI spec for ManagementLinkClient?

Microsoft Azure does not publish a standalone OpenAPI specification for the resource links API. Jentic generates and maintains this spec so that AI agents and developers can call ManagementLinkClient 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 Resource Links API use?

The API uses Azure Active Directory OAuth 2.0 via the azure_auth scheme on https://management.azure.com/. Jentic stores your Azure AD client secret encrypted in its vault and exchanges it for a short-lived bearer token at execution time, so the raw secret never enters the agent context.

Can I link resources that live in different resource groups?

Yes. Resource links are subscription-scoped and the source and target can sit in different resource groups within the same subscription. PUT /{linkId} accepts the full ARM resource ID for both the source path and the targetId in the body.

How many links can a single resource hold?

Each resource can be the source of up to 50 outbound links. Inbound links from other resources do not count against this limit, so widely depended-on resources such as shared key vaults can still appear as the target of many links.

What are the rate limits for the Resource Links API?

The endpoints inherit the standard Azure Resource Manager throttle quotas surfaced through x-ms-ratelimit-remaining-* headers. List operations are paginated with nextLink and agents should follow the link rather than parallelising large scans.

How do I declare a link through Jentic?

Search Jentic for 'create azure resource link', load ResourceLinks_CreateOrUpdate, supply the link path under the source resource and a body with properties.targetId plus optional notes, then execute. The link becomes visible immediately in subscription-wide list calls.

Does deleting a linked resource remove its links?

No. Resource links are stored independently of the resources they reference, so when a linked resource is deleted the link becomes a dangling reference. Cleanup workflows should call DELETE /{linkId} for each affected link as part of resource decommissioning.

Can I limit what my agent is allowed to do with the Azure Resource Links API?

Yes. Because you run Jentic One yourself, your own rules decide which Resource Links operations the agent may call and which Azure AD credentials it may use. Since the link id travels in the URL path (/{linkId}), you can pin the agent to a named source scope and grant only the calls you want, such as creating and reading links while withholding DELETE /{linkId} so it cannot remove links. The agent can reach nothing you have not explicitly allowed.

GET STARTED

Start building with ManagementLinkClient API

Explore with Jentic One
View OpenAPI Document