Azure Enterprise Knowledge Graph Service

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

★ Only Publicly Available OpenAPI DocumentAI/MLMl Inferenceoauth27 EndpointsREST

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.

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.

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

Retrieve a specific knowledge graph service to inspect SKU, tags, and provisioning state

GET STARTED

Start building with Azure Enterprise Knowledge Graph Service API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Azure Enterprise Knowledge Graph Service, keeping it validated and agent-ready.

The Azure Enterprise Knowledge Graph Service Resource Provider API manages knowledge-graph services as ARM resources under Microsoft.EnterpriseKnowledgeGraph. It exposes seven endpoints to list services across a subscription or resource group, retrieve a service, and create, update, or delete graph instances. The service itself was a preview offering for building enterprise knowledge graphs at scale; the API surface here is the control plane that provisions the graph backend.

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 though Jentic?

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

Credential isolation

Azure AD service principal credentials stay in the Jentic MAXsystem vault. The agent calls Microsoft.EnterpriseKnowledgeGraph endpoints with a runtime-issued bearer token scoped to https://management.azure.com/, so secrets never enter prompts or logs.

Intent-based discovery

Agents search Jentic by intent (e.g. "provision azure enterprise knowledge graph") and Jentic returns the matching EnterpriseKnowledgeGraph operation with its full request schema, including SKU and tags fields, so the agent does not need to consult ARM docs.

Time to first call

Direct integration: about half a day for AAD setup, ARM long-running operation polling, and SKU validation. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Cognitive Services Management

Manages AI accounts (e.g. Language, Vision) that often supply entities loaded into a knowledge graph.

Use alongside this API when the agent also needs to provision the AI services that extract graph entities.

Alternative

Azure Cognitive Search Management

Provisions Azure AI Search services often used as the search layer over a knowledge graph.

Choose Azure AI Search when full-text and vector search over content is the goal rather than entity-relationship storage.

Alternative

Azure Resource Graph

Queries Azure resources at scale; not a general-purpose knowledge graph but a related graph-style API.

Choose Azure Resource Graph when the graph in question is the inventory of Azure resources, not enterprise domain entities.

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