How many Azure Maps accounts can be created per subscription?

Question

I intend to use Azure Maps Creator for indoor maps. Each creator resource and therefore maps account should only show a single customer's buildings indoor map(s) (possibly multiple datasets, one per building). This allows me to isolate both a single customer's campus (set of buildings) rendering and the cost associated to a single customer.

I could have many customers and therefore many maps accounts. Some questions:

1. Is there an upper limit on the number of maps accounts per subscription?
2. Would this isolation be the recommended approach or should I create a separate subscription per customer with one maps account for that customer? These subs would either have to use the same AAD as the core application resources' subscription, or a trusted AAD at least, in order for my backend app's client id to be authorized to obtain tokens to supply to the client app for accessing maps, but that's a side issue.

Answer 1

@Mark Phillips Please find the below answers to your queries.

1. Is there an upper limit on the number of maps accounts per subscription?

AFAIK, There is no specific upper limit on the number of Azure Maps accounts that can be created per subscription. You can create as many Azure Maps accounts as you need within the limits of your Azure subscription.

However, it is important to note that each Azure Maps account has its own set of limits and quotas, which are designed to ensure the availability and performance of the service. These limits include limits on the number of transactions (e.g. map tiles, geocoding requests, etc.), the amount of data that can be stored in the account, and the number of users that can access the account.

If you need to create a large number of Azure Maps accounts, or if you expect to exceed the limits of a single Azure Maps account, you may want to consider using Azure Maps Account Scaling, which allows you to scale your Azure Maps account up or down as needed to meet your needs.

I suggest you, please refer to Azure Maps limits, Azure Maps pricing and Choose the right pricing tier in Azure Maps for more details.

2. Would this isolation be the recommended approach or should I create a separate subscription per customer with one maps account for that customer? These subs would either have to use the same AAD as the core application resources' subscription, or a trusted AAD at least, in order for my backend app's client id to be authorized to obtain tokens to supply to the client app for accessing maps, but that's a side issue.

It is generally recommended to use a single Azure subscription and multiple Azure Maps accounts to isolate resources and data for different customers, rather than creating separate subscriptions for each customer.

Using multiple Azure Maps accounts within a single subscription allows you to take advantage of the shared infrastructure and resources of the subscription, while still providing isolation between different customers' data and resources. You can also use Azure role-based access control (RBAC) to manage access to the different Azure Maps accounts and resources within the subscription.

If you need to create a large number of Azure Maps accounts, or if you expect to exceed the limits of a single Azure Maps account, you may want to consider using Azure Maps Account Scaling, which allows you to scale your Azure Maps account up or down as needed to meet your needs.

As for your question about using the same Azure Active Directory (AAD) or a trusted AAD for the different subscriptions, this is something you will need to consider based on your specific requirements and security needs. If you need to share resources or data between the different subscriptions, using the same AAD or a trusted AAD may be necessary.

For more details, see Manage authentication in Azure Maps and Authentication with Azure Maps

Hope this helps! Do let us know if you have any other questions.

If the response is helpful, please click "Accept Answer" and upvote it.