Microsoft Azure Azure Location Based Services Resource Provider

Name: Azure Location Based Services Resource Provider API
Brand: Azure Location Based Services Resource Provider
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMaps GeolocationMappingoauth210 EndpointsREST

For Agents

Install Jentic One Beta

Connect the Azure Location Based Services Resource Provider to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Azure Location Based Services 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.

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 Location Based Services Resource Provider API.

Provision a Microsoft.LocationBasedServices 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

GET STARTED

Start building with Azure Location Based Services Resource Provider API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Azure Location Based Services Resource Provider, keeping it validated and agent-ready. The Azure Location Based Services Resource Provider API manages account-level resources for the Microsoft.LocationBasedServices namespace, letting operators provision Maps accounts inside an Azure subscription, list and rotate the primary and secondary subscription keys, and move accounts between resource groups. It is a control-plane API rather than a maps query API, so all calls go through Azure Resource Manager at management.azure.com and use Azure AD OAuth 2.0. Use it to automate the lifecycle of a Maps account before pointing applications at the Azure Maps data plane for geocoding or routing.

Use Cases

Patterns agents use Azure Location Based Services Resource Provider API for, with concrete tasks.

★ Automated Maps Account Provisioning

Provision a Microsoft.LocationBasedServices account programmatically as part of an Azure landing zone or environment bootstrap. The PUT call on the accounts resource accepts a SKU, location, and tags, and returns the account record once Azure Resource Manager completes the create-or-update. Combined with listKeys, this lets a deployment pipeline create a Maps account and capture its subscription key in one run.

Create an S0 Microsoft.LocationBasedServices account named 'maps-prod-eu' in resource group 'rg-platform' in West Europe, then call listKeys and return the primary key.

Subscription Key Rotation

Rotate Azure Maps subscription keys on a schedule to satisfy compliance policies. The regenerateKey endpoint accepts either 'primary' or 'secondary' as the key type and issues a fresh value while leaving the other key intact, which lets clients cut over without downtime. Pair it with listKeys to retrieve the new value and push it to a secret store.

Regenerate the secondary key for Maps account 'maps-prod-eu' in resource group 'rg-platform', then read the new value via listKeys and store it in Key Vault under 'maps-secondary-key'.

Cross-Resource-Group Account Migration

Reorganise Azure Maps accounts when a subscription is split or resource groups are consolidated. The moveResources POST under a source resource group accepts a list of account resource IDs and a target resource group, and the Resource Provider validates the move before committing. This avoids deleting and recreating the account, which would invalidate existing subscription keys.

Move the Maps account 'maps-prod-eu' from resource group 'rg-old' to 'rg-platform' using moveResources and confirm the new resource ID.

Agent Inventory and Drift Detection

An AI agent through Jentic can enumerate every Microsoft.LocationBasedServices account across subscriptions, compare SKU and tag values against a desired-state config, and trigger updates or key rotations when drift is detected. Jentic returns the matching control-plane operation for each step, so the agent never has to browse Resource Provider docs.

List all Location Based Services accounts in subscription '00000000-0000-0000-0000-000000000000', flag any account whose SKU is not 'S1', and rotate the primary key on those accounts.

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for azure location based services resource provider, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.LocationBasedServices/accounts/{accountName}

Create or update a Maps account

GET

/subscriptions/{subscriptionId}/providers/Microsoft.LocationBasedServices/accounts

List Maps accounts in a subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.LocationBasedServices/accounts

List Maps accounts in a resource group

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.LocationBasedServices/accounts/{accountName}/listKeys

Retrieve subscription keys for a Maps account

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.LocationBasedServices/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.LocationBasedServices/accounts/{accountName}

Create or update a Maps account

GET

/subscriptions/{subscriptionId}/providers/Microsoft.LocationBasedServices/accounts

List Maps accounts in a subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.LocationBasedServices/accounts

List Maps accounts in a resource group

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.LocationBasedServices/accounts/{accountName}/listKeys

Retrieve subscription keys for a Maps account

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.LocationBasedServices/accounts/{accountName}/regenerateKey

Why Jentic?

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

Credential isolation

Azure AD service principal credentials and tenant IDs are stored encrypted in the Jentic vault. Agents receive short-lived Bearer tokens scoped to https://management.azure.com/ — client secrets and refresh tokens never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'provision an Azure Maps account' or 'rotate a Maps key') and Jentic returns the matching Microsoft.LocationBasedServices ARM operation with its full parameter schema, so the agent can call the right endpoint without parsing Resource Provider docs.

Time to first call

Direct integration: 1-2 days for Azure AD app registration, token caching, and ARM polling. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Azure Location Based Services Resource Provider API through Jentic.

Why is there no official OpenAPI spec for Azure Location Based Services Resource Provider?

Microsoft Azure does not publish a single consolidated OpenAPI specification for this Resource Provider. Jentic generates and maintains this spec so that AI agents and developers can call Azure Location Based Services 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 Location Based Services Resource Provider use?

The API uses Azure Active Directory OAuth 2.0 with the implicit flow declared in the spec; in practice, 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, so raw client secrets never enter the agent context.

Can I retrieve Azure Maps subscription keys with this API?

Yes. The POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.LocationBasedServices/accounts/{accountName}/listKeys endpoint returns the primary and secondary keys for the account, and the regenerateKey endpoint rotates whichever key you specify.

Does this API let me query maps, geocode addresses, or calculate routes?

No. This is the control-plane Resource Provider API that manages the lifecycle of Azure Maps accounts. For geocoding, search, and routing you use the Azure Maps data-plane services at atlas.microsoft.com after provisioning an account here.

How do I provision an Azure Maps account through Jentic?

Search Jentic for 'provision an Azure Maps account', load the resulting PUT operation on /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.LocationBasedServices/accounts/{accountName}, then execute it with the SKU, location, and account name. Install with pip install jentic and run the async search-load-execute flow.

What are the rate limits for this API?

Azure Resource Manager applies subscription-level throttling rather than per-endpoint limits; reads are typically capped at 12,000 per hour and writes at 1,200 per hour per subscription. The spec does not declare narrower limits, so the ARM defaults apply.

Microsoft Azure Azure Location Based Services Resource Provider

Connect the Azure Location Based Services Resource Provider to your agent

Capabilities

Start building with Azure Location Based Services Resource Provider API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs