ManagementLinkClient

Name: ManagementLinkClient API
Brand: ManagementLinkClient
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth26 EndpointsREST

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.

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.

Install Jentic One Beta (Self-Hosted)

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

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

GET STARTED

Start building with ManagementLinkClient API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for ManagementLinkClient, keeping it validated and agent-ready.

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.

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Azure AD client credentials live encrypted in the Jentic vault. Jentic mints a scoped bearer token at execution time and injects it into the request, keeping raw secrets out of agent context.

Intent-based discovery

Agents search Jentic with intents like 'link two azure resources' and Jentic returns the matching ResourceLinks operation with its input schema, so the agent can declare links without browsing ARM documentation.

Time to first call

Direct integration: a day or two to handle MSAL, the unusual nested {linkId} routing, and pagination. Through Jentic: under an hour.

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 at https://app.jentic.com/sign-up.

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.