canonical: https://jentic.com/apis/azure.com/mixed-reality # Microsoft Azure Mixed Reality Jentic publishes the only available OpenAPI specification for Azure Mixed Reality, keeping it validated and agent-ready. The Mixed Reality Resource Provider provisions and manages Spatial Anchors accounts, the cloud resource that backs Azure Spatial Anchors apps for HoloLens, iOS, and Android. The control plane lets developers create accounts in a region, list them across a subscription or resource group, regenerate primary or secondary access keys, and check name availability before provisioning. Spatial Anchors accounts are the gating credential boundary for any client SDK call against the Spatial Anchors data plane. ## For AI agents Provision Azure Spatial Anchors accounts, manage their access keys, and check name availability. Covers 10 endpoints across the Microsoft.MixedReality control plane. ## Scope Does not handle anchor creation, anchor lookup, or any Spatial Anchors data plane operation - use for Mixed Reality account control plane only. ## Capabilities - Create and update Spatial Anchors accounts in a specific Azure region - List Spatial Anchors accounts across a subscription or scoped to a resource group - Retrieve the current primary and secondary keys for a Spatial Anchors account - Regenerate the primary or secondary key to rotate Spatial Anchors credentials - Check whether a Spatial Anchors account name is available in a region before provisioning - Apply tags to Spatial Anchors accounts for cost allocation and governance ## Use cases ### Provisioning Spatial Anchors backends for AR apps AR development teams building HoloLens or ARKit apps create a dedicated Spatial Anchors account per environment. The Mixed Reality API lets a CI workflow check name availability, create the account in the chosen region, retrieve the primary key, and surface that key as a secret for the mobile build pipeline. End-to-end provisioning takes under a minute for each environment. Example prompt: Check availability of name spatial-prod in eastus, create the Spatial Anchors account in resource group ar-prod, and return its primary key. ### Spatial Anchors key rotation Security teams that rotate cloud credentials on a schedule need to cycle the primary or secondary keys on every Spatial Anchors account in scope. The API exposes a regenerateKey action that swaps a single key without breaking the other, allowing zero-downtime rotation: rotate secondary, deploy app updates, rotate primary. Each rotation completes in seconds. Example prompt: Regenerate the secondary key on Spatial Anchors account spatial-prod in resource group ar-prod, then return the new key value for redeployment. ### Cost and governance reporting on AR resources Cloud governance dashboards need an inventory of Spatial Anchors accounts across the tenant. Listing accounts per subscription returns location, SKU, and tags, which can be joined against billing data to attribute Mixed Reality spend to product teams. Tag updates can be pushed via the same API to enforce cost-allocation policy. Example prompt: List all Spatial Anchors accounts in subscription abc, group them by tag costCenter, and return a JSON summary of the count per cost center. ### Agent-driven Spatial Anchors lifecycle AI agents can use Jentic to discover Mixed Reality Resource Provider operations by intent, load the structured input schema, and execute calls against management.azure.com without browsing the Azure REST docs. An onboarding agent for a new AR project can stand up the entire backend with a single intent search and return the credential to the developer to plug into their client SDK. Example prompt: Search Jentic for create azure spatial anchors account, load the input schema, and execute it for region westeurope with the SKU S0 and tag environment dev. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | PUT | /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MixedReality/spatialAnchorsAccounts/{spatialAnchorsAccountName} | Create or update a Spatial Anchors account | | GET | /subscriptions/{subscriptionId}/providers/Microsoft.MixedReality/spatialAnchorsAccounts | List Spatial Anchors accounts in a subscription | | GET | /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MixedReality/spatialAnchorsAccounts/{spatialAnchorsAccountName}/keys | Get the access keys for a Spatial Anchors account | | POST | /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MixedReality/spatialAnchorsAccounts/{spatialAnchorsAccountName}/keys | Regenerate a Spatial Anchors account key | | POST | /subscriptions/{subscriptionId}/providers/Microsoft.MixedReality/locations/{location}/checkNameAvailability | Check Spatial Anchors account name availability | ## Key resources - **Spatial Anchors Accounts** — Top-level Mixed Reality account resource that backs Spatial Anchors data plane operations and holds access keys. - **Account Keys** — Primary and secondary access keys used by Spatial Anchors client SDKs for authentication. - **Operations** — Self-describing metadata for the Microsoft.MixedReality resource provider operations. ## Why Jentic - **Setup:** Wiring Azure Mixed Reality by hand means implementing Azure AD OAuth 2.0, minting an ARM-scoped bearer token for management.azure.com, and handling the Spatial Anchors account provisioning flow and key regeneration yourself. Through Jentic you install once, import Azure Mixed Reality from the API Directory, store the Azure AD credential once, and your agent calls it. - **Permission scoping:** The API puts the subscription, resource group, and Spatial Anchors account name in the URL path, so a rule can pin your agent to one Spatial Anchors account: it can read the account and its keys and nothing else. You choose the operations it may call, so destructive ones like regenerating a key or deleting the account are not included unless you add them. - **Credential handling:** Your Azure AD credential is stored once, encrypted, by your own Jentic One instance and exchanged for a short-lived ARM-scoped bearer token at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create an Azure Spatial Anchors account' or 'rotate a Spatial Anchors key', and Jentic returns the matching Mixed Reality operation with its input schema so the agent supplies the region and account name and executes. ## Related APIs - **Azure Cognitive Services** — Provisions Cognitive Services accounts that AR apps often pair with Spatial Anchors for vision and speech. - **Azure Maps Resource Provider** — Provisions Azure Maps accounts for outdoor location services that complement indoor Spatial Anchors. - **Azure Resource Management** — Manages the resource groups and tags that contain Spatial Anchors accounts. ## FAQ ### Why is there no official OpenAPI spec for Azure Mixed Reality? Microsoft Azure does not publish an OpenAPI specification for the Microsoft.MixedReality Resource Provider. Jentic generates and maintains this spec from the Azure Resource Manager contracts so that AI agents and developers can call Azure Mixed Reality 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 Azure Mixed Reality API use? The API uses Azure Active Directory OAuth 2.0 with the user_impersonation scope against https://login.microsoftonline.com/common/oauth2/authorize. Jentic stores the AAD client secret or service principal credentials encrypted in its vault and supplies scoped bearer tokens to agents at execution time without exposing the underlying credential. ### Can I create a Spatial Anchors account through the Azure Mixed Reality API? Yes. PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MixedReality/spatialAnchorsAccounts/{spatialAnchorsAccountName} creates or updates the account. The body must include a location and may include tags and a SKU. After creation, retrieve the access keys via the keys endpoint to wire the account into a client SDK. ### What are the rate limits for the Azure Mixed Reality API? The control plane follows the standard Azure Resource Manager throttling limits, which apply per subscription and per region. Read operations are limited to 1200 requests per hour per subscription. Account creation and key regeneration are infrequent control-plane operations, so practical rate limits are not a concern for typical workflows. ### How do I rotate a Spatial Anchors account key through Jentic? Search Jentic for regenerate spatial anchors key, load the schema for POST under spatialAnchorsAccounts/{name}/keys, and execute it with the keyName field set to primary or secondary. Jentic handles the AAD token exchange and returns the new key, which the agent can hand off to a deployment workflow. ### Does the Mixed Reality API call the Spatial Anchors data plane? No. This API is the control plane: it provisions accounts and manages their keys. Actual anchor creation, lookup, and deletion is done through the Spatial Anchors client SDKs (HoloLens, iOS, Android, Unity), which authenticate using the keys retrieved from this control plane. ### Can I limit what my agent is allowed to do with the Azure Mixed Reality API? Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and the subscription, resource group, and Spatial Anchors account name all sit in the URL path, so a rule can pin the agent to a single Spatial Anchors account. You choose the operations it may call, so you can let it read an account and list its keys while leaving out destructive ones like regenerating a key or deleting the account. Those operations are excluded unless you explicitly add them, and the Azure AD credential is exchanged for a scoped token at execution time rather than handed to the agent.