Install Jentic One Beta

Connect the DataShareManagementClient to your agent

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

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%2Fdatasharemanagementclient" | sh

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%2Fdatasharemanagementclient" | 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 DataShareManagementClient API.

Provision Data Share accounts and inspect provider operations

Create shares, add datasets to a share, and configure share-level synchronisation settings

Send invitations to consumers and accept or reject inbound consumer invitations

GET STARTED

Start building with DataShareManagementClient API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use DataShareManagementClient API for, with concrete tasks.

★ Cross-tenant dataset publishing

A data provider exposes curated datasets - typically blobs in storage accounts or tables in a Data Lake - to external partners as Data Shares. The API lets the provider create a share, add datasets, configure synchronisation, and dispatch an invitation to each partner tenant without granting direct access to the underlying storage account.

On the Data Share account 'partner-share' create a share named 'q2-customer-feed', add the storage blob container 'customer-feed' as a dataset, and send an invitation to a partner email

Consumer-side scheduled sync

A consumer receives an invitation to a Data Share and accepts it programmatically, then configures a recurring synchronisation so partner data lands in their own storage on a schedule. The share subscription, dataset mapping, and trigger endpoints together let an automation flow keep the consumer-side copy current.

Accept the inbound Data Share invitation with the supplied invitationId, create a daily synchronisation trigger at 02:00 UTC on the resulting share subscription, and confirm the first run completes

Share inventory audit

A data governance team needs an inventory of every active share, every consumer invited, and every dataset exposed. The list endpoints under accounts, shares, share subscriptions, and invitations let an audit tool walk the entire surface and reconcile against an approved sharing register.

List all shares on the 'partner-share' Data Share account and for each share return the dataset names, invited consumer emails, and current invitation status

Agent-mediated dataset distribution

An AI agent acting as a data steward responds to a partner request by searching Jentic for the create-share workflow, provisioning the share with the requested datasets, and dispatching an invitation. The agent never sees the partner's storage credentials - Data Share handles delivery - and Jentic isolates the steward's Azure credentials from the agent context.

Create a share named 'agent-curated-2026-q2' on the configured account, add three named storage blob containers as datasets, and email an invitation to the requesting partner

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/providers/Microsoft.DataShare/accounts

List Data Share accounts in a subscription

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataShare/accounts/{accountName}

Create or update a Data Share account

GET

/providers/Microsoft.DataShare/ListInvitations

List inbound consumer invitations across the subscription

POST

/providers/Microsoft.DataShare/locations/{location}/RejectInvitation

Reject an inbound Data Share invitation

GET

/providers/Microsoft.DataShare/locations/{location}/consumerInvitations/{invitationId}

Get a specific consumer invitation

GET

/providers/Microsoft.DataShare/operations

List Microsoft.DataShare provider operations

GET

/subscriptions/{subscriptionId}/providers/Microsoft.DataShare/accounts

List Data Share accounts in a subscription

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataShare/accounts/{accountName}

Create or update a Data Share account

GET

/providers/Microsoft.DataShare/ListInvitations

List inbound consumer invitations across the subscription

POST

/providers/Microsoft.DataShare/locations/{location}/RejectInvitation

Reject an inbound Data Share invitation

GET

/providers/Microsoft.DataShare/locations/{location}/consumerInvitations/{invitationId}

Get a specific consumer invitation

Why Jentic?

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

Setup

Wiring Azure Data Share by hand means registering an Azure AD app, handling OAuth 2.0 bearer tokens against management.azure.com, and polling long-running ARM operations for share creation and synchronisation runs yourself. Through Jentic you install once, import Data Share Management from the API Directory, store the Azure service principal credential once, and your agent calls it.

Permission scoping

Data Share puts the account and share names in the URL path (/subscriptions/{id}/resourceGroups/{rg}/providers/Microsoft.DataShare/accounts/{accountName}/shares/{shareName}/...), so a rule can pin your agent to one Data Share account. You choose the operations it may call, so destructive ones like Shares_Delete or invitation revocation are not included unless you add them alongside operations such as Invitations_Create or DataSets_Create.

Credential isolation

Your Azure service principal credential is stored once, encrypted, by your own Jentic One instance and injected as a scoped ARM bearer token at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'send an Azure Data Share invitation' or 'trigger a share synchronisation', and Jentic returns the matching operation with its input schema so the agent wires up the cross-tenant flow without learning the 50 paths under Microsoft.DataShare.

FAQs

Specific to using DataShareManagementClient API through Jentic.

Why is there no official OpenAPI spec for DataShareManagementClient?

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

The API runs through Azure Resource Manager and uses OAuth 2.0 bearer tokens issued by Azure Active Directory. Through Jentic, the AAD client secret or managed identity refresh token is held in the encrypted vault and a short-lived access token is supplied at execute time so the bearer token never appears in the agent's context.

Can I send a Data Share invitation to a partner with this API?

Yes. The provider-side invitation endpoints under Microsoft.DataShare/accounts/{accountName}/shares/{shareName}/invitations let you create an invitation by email; the consumer can then accept it via the consumerInvitations endpoints under /providers/Microsoft.DataShare/locations/{location}/consumerInvitations.

What are the rate limits for the Data Share API?

Azure Resource Manager applies subscription-level read and write throttles (around 12,000 reads per hour and 1,200 writes per hour per region per subscription) and returns 429 with a Retry-After header when exceeded. Data Share long-running operations (sync runs, share creation) should be polled with backoff rather than tight loops.

How do I trigger a synchronisation on a share subscription through Jentic?

Search Jentic for 'trigger data share synchronisation', load the schema for the share subscription synchronize operation under Microsoft.DataShare/accounts/{accountName}/shareSubscriptions/{shareSubscriptionName}/synchronize, then execute with the synchronizationMode. The pip install jentic Python SDK uses the async search, load, execute pattern.

Is the Data Share API free?

There is no per-call charge for the management API itself; Azure Data Share bills on the data sharing transactions (number of snapshots, data movement) and underlying storage. Reads and writes against the management plane are not separately metered.

Can I limit what my agent is allowed to do with the Azure Data Share API?

Yes. Because your Jentic One instance is self-hosted, your own rules decide which Data Share operations the agent may call and which credentials it uses. Since the account and share names sit in the URL path, you can pin the agent to a single Data Share account and grant only the operations you want, such as Invitations_Create or DataSets_Create. Destructive calls like Shares_Delete or invitation revocation stay out unless you explicitly add them.

Microsoft Azure DataShareManagementClient

Name: DataShareManagementClient API
Brand: DataShareManagementClient
Availability: InStock

Browse all Azure APIs

Agent-ready OpenAPI document · curated by JenticStorageObject Storageoauth250 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Publish, subscribe to, and synchronise datasets across Azure tenants - manage Data Share accounts, invitations, datasets, and synchronisation triggers.

Use for: Create a new Data Share account in a resource group, Publish a dataset by adding it to an existing share, Send a Data Share invitation to a partner tenant, Accept an inbound Data Share invitation programmatically

Not supported: Does not move bulk data outside Data Share's own synchronisation, manage source storage accounts, or handle billing - use for Data Share account, share, invitation, and synchronisation control only.

Jentic publishes the only available OpenAPI specification for DataShareManagementClient, keeping it validated and agent-ready. The API drives Azure Data Share - Microsoft's service for sharing datasets between Azure subscriptions and tenants - covering accounts, shares, datasets, share subscriptions, invitations, synchronisation settings, and triggers. It is the control plane both data providers (publishing shares) and consumers (subscribing to invitations) use to wire up cross-tenant data flows under Microsoft.DataShare.

Jentic One on Github View OpenAPI Document