Microsoft Azure Azure Maps Resource Provider
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentMaps GeolocationMappingoauth210 EndpointsREST
For Agents
Provision and manage Azure Maps accounts under the Microsoft.Maps namespace, including listing accounts, rotating subscription keys, and moving accounts between resource groups.
Use for: I need to provision an Azure Maps account under Microsoft.Maps, List all Maps accounts in my subscription, Rotate the primary subscription key on a Maps account, Retrieve the access keys for a Maps account
Not supported: Does not handle geocoding, routing, or map tile rendering — use for Microsoft.Maps account lifecycle, key management, and resource moves only.
Jentic publishes the only available OpenAPI specification for Azure Maps Resource Provider, keeping it validated and agent-ready. The Azure Maps Resource Provider manages account-level resources under the Microsoft.Maps namespace, the successor to the older Microsoft.LocationBasedServices namespace. Operators can provision Azure Maps accounts, list accounts at subscription or resource-group scope, retrieve and rotate primary and secondary subscription keys, update SKU and tags, and move accounts between resource groups. All requests authenticate with Azure AD OAuth 2.0 against Azure Resource Manager.
Install Jentic One Beta
Connect the Azure Maps Resource Provider to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Azure Maps Resource Provider, 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.
1
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 | sh2
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 instanceJentic 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 Maps Resource Provider API.
Provision a Microsoft.Maps account inside a resource group
List Maps accounts across a subscription or scoped to a resource group
Rotate primary or secondary subscription keys for a Maps account
Move a Maps account between resource groups using moveResources
Update SKU and tags on an existing Maps account
Enumerate Microsoft.Maps Resource Provider operations for RBAC tooling
Use Cases
Patterns agents use Azure Maps Resource Provider API for, with concrete tasks.
★ Account Provisioning Under Microsoft.Maps
Teams migrating off the legacy Microsoft.LocationBasedServices namespace, or starting fresh, provision Azure Maps accounts directly under Microsoft.Maps. The PUT on the accounts resource accepts a SKU and location and returns the account record with provisioningState. Pair with listKeys to capture the subscription key for the data-plane Azure Maps services at atlas.microsoft.com.
Create an S1 Microsoft.Maps account named 'maps-prod-eu' in resource group 'rg-platform' in West Europe and return the listKeys primary key.
Subscription Key Rotation
Subscription keys backing the Azure Maps data plane are rotated on a schedule for compliance. The regenerateKey POST accepts 'primary' or 'secondary', issues a fresh value, and leaves the other key intact so clients can cut over without downtime. Pair with listKeys to retrieve the new value and push it to a secret store.
Regenerate the secondary key on Maps account 'maps-prod-eu' in 'rg-platform', read the new value via listKeys, and store it in Key Vault under 'maps-secondary-key'.
Cross-Resource-Group Account Migration
Reorganising Azure subscriptions often requires moving Maps accounts between resource groups without recreating them, which would invalidate keys and break clients. The moveResources POST accepts a list of account resource IDs and a target resource group; the Resource Provider validates and commits the move while preserving keys and identity.
Move Maps account 'maps-prod-eu' from 'rg-old' to 'rg-platform' via moveResources and confirm the new resource ID.
Agent-Driven Account Inventory
An AI agent through Jentic can enumerate Microsoft.Maps accounts across subscriptions, compare SKU and tag values against a desired-state config, and rotate keys or update SKUs where drift exists. Jentic returns the operation schema for each step so the agent does not have to navigate the Microsoft.Maps Resource Provider docs.
List every Microsoft.Maps account in subscription '00000000-0000-0000-0000-000000000000', flag any whose SKU is not 'S1', and patch them to S1.
Key Endpoints
10 endpoints — jentic publishes the only available openapi specification for azure maps resource provider, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Maps/accounts/{accountName}
Create or update a Maps account
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Maps/accounts
List Maps accounts in a subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Maps/accounts
List Maps accounts in a resource group
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Maps/accounts/{accountName}/listKeys
Retrieve subscription keys
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Maps/accounts/{accountName}/regenerateKey
Regenerate primary or secondary key
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/moveResources
Move accounts between resource groups
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Maps/accounts/{accountName}
Create or update a Maps account
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Maps/accounts
List Maps accounts in a subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Maps/accounts
List Maps accounts in a resource group
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Maps/accounts/{accountName}/listKeys
Retrieve subscription keys
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Maps/accounts/{accountName}/regenerateKey
Regenerate primary or secondary key
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/moveResources
Move accounts between resource groups
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD service principal credentials and Maps subscription keys are stored encrypted in the Jentic vault. Agents receive short-lived Bearer tokens scoped to https://management.azure.com/ — client secrets and account keys never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'create an Azure Maps account' or 'rotate Maps subscription key') and Jentic returns the matching Microsoft.Maps Resource Provider operation with its parameter schema.
Time to first call
Direct integration: 1-2 days for Azure AD setup, ARM polling, and key rotation wiring. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Azure Maps Resource Provider API through Jentic.
Why is there no official OpenAPI spec for Azure Maps Resource Provider?
Microsoft Azure does not publish a single consolidated OpenAPI specification for the Microsoft.Maps Resource Provider. Jentic generates and maintains this spec so that AI agents and developers can call Azure Maps Resource Provider via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Azure Maps Resource Provider use?
The API uses Azure Active Directory OAuth 2.0; agents acquire a token for the https://management.azure.com/ resource and pass it as a Bearer token. Jentic stores the service principal credentials in its vault and injects scoped tokens at call time.
Can this API geocode addresses or render map tiles?
No. This is the control-plane Resource Provider that manages Maps account lifecycle. Geocoding, search, routing, and tile rendering are served by the Azure Maps data plane at atlas.microsoft.com once an account is provisioned and a subscription key is issued.
How do I retrieve subscription keys through Jentic?
Search Jentic for 'list Azure Maps account keys', load the resulting POST operation on /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Maps/accounts/{accountName}/listKeys, then execute it with the account name and resource group. Install with pip install jentic and run the async search-load-execute flow.
How does Microsoft.Maps differ from Microsoft.LocationBasedServices?
Microsoft.Maps is the current namespace for new Azure Maps accounts; Microsoft.LocationBasedServices is the legacy namespace from the 2017 preview. The data-plane services are unchanged, but new account provisioning, key rotation, and tooling should target Microsoft.Maps.
What are the rate limits for this API?
Azure Resource Manager applies subscription-level throttling — typically 12,000 reads and 1,200 writes per hour per subscription. The spec does not declare narrower limits, so the ARM defaults apply.
GET STARTED