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.

Can I limit what my agent is allowed to do with the Azure Maps Resource Provider API?

Yes. Jentic One is self-hosted, so your own rules decide which operations and credentials your agent may use. Because this provider puts the subscription, resource group, and account name in the URL path, you can pin the agent to a single Maps account and grant only the operations it needs, such as listing accounts or reading keys. Sensitive operations like regenerateKey or moveResources stay unavailable unless you explicitly add them.