canonical: https://jentic.com/apis/azure.com/azure-enterprise-knowledge-graph-service

# Microsoft Azure Azure Enterprise Knowledge Graph Service

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.

## For AI 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.

## Scope

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

## Capabilities

- 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
- Patch tags or basic properties on an existing graph service
- Delete a knowledge graph service that is no longer required
- Discover Microsoft.EnterpriseKnowledgeGraph resource provider operations

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **services** — CRUD on Microsoft.EnterpriseKnowledgeGraph service resources
- **subscription scope** — Subscription-wide listing of enterprise knowledge graph services
- **resource group scope** — Listing within a specific resource group
- **operations** — Discovery of Microsoft.EnterpriseKnowledgeGraph resource provider operations

## Why Jentic

- **Setup:** Wiring the Microsoft.EnterpriseKnowledgeGraph resource provider by hand means registering an Azure AD app, minting bearer tokens for management.azure.com, and polling the long-running provisioning state that service PUTs return. Through Jentic you install once, import Azure Enterprise Knowledge Graph Service from the API Directory, store the Azure AD service principal credentials once, and your agent calls it.
- **Permission scoping:** This provider puts the subscription, resource group, and service name in the URL path (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EnterpriseKnowledgeGraph/services/{resourceName}), so a rule can pin your agent to graph services in one resource group. You choose the operations it may call, so destructive ones like deleting a service or patching its SKU are not included unless you add them.
- **Credential handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Cognitive Services Management** — Manages AI accounts (e.g. Language, Vision) that often supply entities loaded into a knowledge graph.
- **Azure Cognitive Search Management** — Provisions Azure AI Search services often used as the search layer over a knowledge graph.
- **Azure Resource Graph** — Queries Azure resources at scale; not a general-purpose knowledge graph but a related graph-style API.

## FAQ

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