Microsoft Azure Azure Enterprise Knowledge Graph Service

Name: Azure Enterprise Knowledge Graph Service API
Brand: Azure Enterprise Knowledge Graph Service
Availability: InStock

Browse all Azure APIs

★ Only Publicly Available OpenAPI DocumentAI/MLMl Inferenceoauth27 Endpoints

Install Jentic One Beta

Connect the Azure Enterprise Knowledge Graph Service to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Azure Enterprise Knowledge Graph Service, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: 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 Azure Enterprise Knowledge Graph Service API.

Provision a Microsoft.EnterpriseKnowledgeGraph service in a target region and resource group

List enterprise knowledge graph services across a subscription

List graph services scoped to a single resource group

GET STARTED

Start building with Azure Enterprise Knowledge Graph Service API

Explore with Jentic

View OpenAPI Document

For Agents

Provision and manage Azure Enterprise Knowledge Graph services as ARM resources, including listing, retrieving, creating, updating, and deleting graph instances. Supports seven endpoints under Microsoft.EnterpriseKnowledgeGraph.

Use for: I need to provision an enterprise knowledge graph service in eastus2, List enterprise knowledge graph services in resource group rg-graph, Retrieve the SKU and tags of an existing knowledge graph service, Patch tags on an enterprise knowledge graph service

Not supported: Does not load entities, run graph queries, or expose data-plane graph operations - use for Microsoft.EnterpriseKnowledgeGraph service resource provisioning only.

Use Cases

Patterns agents use Azure Enterprise Knowledge Graph Service API for, with concrete tasks.

★ Stand Up an Enterprise Knowledge Graph Backend

Provision an Azure Enterprise Knowledge Graph service so downstream applications can register entities and relationships into a managed graph store. The Resource Provider API takes a single PUT with location and SKU, after which the service endpoint becomes available for graph-loading workflows. Provisioning typically takes a few minutes and is callable from any IaC pipeline that targets ARM.

PUT /subscriptions/{subscriptionId}/resourceGroups/rg-graph/providers/Microsoft.EnterpriseKnowledgeGraph/services/AcmeKG with location=eastus2 and the desired SKU.

Knowledge Graph Service Inventory

Produce a portfolio inventory of every enterprise knowledge graph service in the tenant. The API's EnterpriseKnowledgeGraph_List returns each service with location, SKU, tags, and provisioning state, enough to build a governance report. The same flow applies for resource-group scoped queries and is callable from any pipeline with reader access.

List Microsoft.EnterpriseKnowledgeGraph services in subscription 1111-2222 and emit one row per service with name, location, sku, and provisioningState.

Decommission Preview Graph Services

Cleanly remove enterprise knowledge graph services that have been migrated to other graph stores or that no longer serve active workloads. The DELETE endpoint removes the resource at the resource provider level, freeing the name and stopping ongoing charges. Pair with a tag-based selector to scope cleanup safely across a portfolio.

List services in rg-legacy-graph, identify any with tag deprecated=true, and DELETE each via the services resource endpoint.

Agent-Driven Graph Service Standardisation

A Jentic agent enumerates every Microsoft.EnterpriseKnowledgeGraph service across multiple subscriptions and patches each one to align tags, region, and SKU with a governance baseline. The agent uses the same seven endpoints in this spec to list, get, and patch services, replacing manual portal review with deterministic enforcement.

List every Microsoft.EnterpriseKnowledgeGraph service in subscription 1111-2222, find any without the tag environment, and PATCH each to set environment=production.

Key Endpoints

7 endpoints — the azure enterprise knowledge graph service resource provider api manages knowledge-graph services as arm resources under microsoft.

METHOD

PATH

DESCRIPTION

GET

/providers/Microsoft.EnterpriseKnowledgeGraph/operations

List Microsoft.EnterpriseKnowledgeGraph operations

GET

/subscriptions/{subscriptionId}/providers/Microsoft.EnterpriseKnowledgeGraph/services

List services across the subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EnterpriseKnowledgeGraph/services

List services in a resource group

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EnterpriseKnowledgeGraph/services/{resourceName}

Get a single service

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EnterpriseKnowledgeGraph/services/{resourceName}

Create a knowledge graph service

PATCH

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EnterpriseKnowledgeGraph/services/{resourceName}

Update tags or properties on a service

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EnterpriseKnowledgeGraph/services/{resourceName}

Delete a knowledge graph service

GET

/providers/Microsoft.EnterpriseKnowledgeGraph/operations

List Microsoft.EnterpriseKnowledgeGraph operations

GET

/subscriptions/{subscriptionId}/providers/Microsoft.EnterpriseKnowledgeGraph/services

List services across the subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EnterpriseKnowledgeGraph/services

List services in a resource group

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EnterpriseKnowledgeGraph/services/{resourceName}

Get a single service

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EnterpriseKnowledgeGraph/services/{resourceName}

Why Jentic?

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

Credential isolation

Your Azure AD service principal credentials are stored once, encrypted, by your own Jentic One instance and injected as a bearer token scoped to management.azure.com at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'provision an Azure enterprise knowledge graph service' or 'list knowledge graph services in a subscription', and Jentic returns the matching EnterpriseKnowledgeGraph operation with its input schema, including the SKU and tags fields, so the agent does not consult the ARM docs.

Time to first call

FAQs

Specific to using Azure Enterprise Knowledge Graph Service API through Jentic.

What authentication does the Azure Enterprise Knowledge Graph API use?

Azure Active Directory OAuth 2.0 via the azure_auth scheme (user_impersonation scope) on https://management.azure.com/. With Jentic, AAD client credentials live in your Jentic One instance and the agent receives a runtime bearer token rather than the secret.

Can I provision a knowledge graph service with this API?

Yes. PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EnterpriseKnowledgeGraph/services/{resourceName} with location, SKU, and tags. Provisioning runs as a long-running operation; clients should poll the resource until provisioningState reaches Succeeded.

What are the rate limits for the Azure Enterprise Knowledge Graph API?

It shares Azure Resource Manager subscription throttling, typically 12,000 reads and 1,200 writes per hour per subscription. Honour 429 responses and the Retry-After header; the spec does not declare per-endpoint quotas.

How do I list every knowledge graph service through Jentic?

Search Jentic for "list azure enterprise knowledge graph services", load the schema for EnterpriseKnowledgeGraph_List, then execute with subscriptionId. Run it through Jentic One, the self-hosted execution layer to get an API key.

Does this API let me load entities or relationships into the graph?

No. This is a control-plane API that provisions and configures the graph service resource. Loading and querying entities and relationships happens against the data-plane endpoint exposed by the provisioned service, which is outside this OpenAPI spec.

Should I use this for new projects?

Microsoft has retired this preview-era service and recommends modern graph stores such as Azure Cosmos DB Gremlin API or Microsoft Fabric for new builds. Use this API when managing existing Microsoft.EnterpriseKnowledgeGraph resources or migrating off them.

Can I limit what my agent is allowed to do with the Azure Enterprise Knowledge Graph Service API?

Yes. Jentic One is self-hosted, so your own rules decide which of the seven Microsoft.EnterpriseKnowledgeGraph operations the agent may call, meaning you can grant read-only actions like listing and getting services while withholding the PUT, PATCH, and DELETE that create, reconfigure, or remove a service. Because the subscription, resource group, and service name all sit in the URL path, a rule can pin the agent to graph services in a single resource group. The Azure Active Directory service principal credentials are held encrypted by your instance and injected as a bearer token at execution time, never reaching the agent's prompt or logs.

Microsoft Azure Azure Enterprise Knowledge Graph Service

Connect the Azure Enterprise Knowledge Graph Service to your agent

Capabilities

Start building with Azure Enterprise Knowledge Graph Service API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs