Multiple APIM developer instances in one resource group

Question

Multiple APIM developer instances in one resource group

Laurens van de Venn 200

Good afternoon,

Is it wise to host multiple APIM developer instances in one resource group taking into account that we need to use private endpoints?

What would be disadvantages of having multiple APIM developer instances in one resource group?

Regards,

Laurens van de Venn

Khadeer Ali 4,615 Reputation points Microsoft External Staff

2025-04-09T11:24:13.28+00:00

@Laurens van de Venn Just checking in to see if the answer provided by Michael Taylor helped resolve your query. If it answers your question, please consider clicking Accept Answer and selecting Yes for "Was this answer helpful?" This helps others in the community as well! Let us know if you have any further questions

Accepted answer

1 additional answer

Your answer

Khadeer Ali 4,615 Reputation points Microsoft External Staff

2025-04-09T11:24:13.28+00:00

@Laurens van de Venn Just checking in to see if the answer provided by Michael Taylor helped resolve your query. If it answers your question, please consider clicking Accept Answer and selecting Yes for "Was this answer helpful?" This helps others in the community as well! Let us know if you have any further questions

Answer 1

Is there a specific issue with hosting multiple APIM in a single RG? Not really. If you have the need for multiple APIMs (that is a separate conversation) then whether they are in the same RG or not is mostly a mute point. An RG is nothing more than a grouping of related resources. If your APIMs are related then putting them into the same RG might make sense. It depends on how you are using your RGs.

In general an RG is recommended to be per-environment and contain all the resources needed for deploying and using it. So many companies have an RG for each of their environments (e.g. Dev, Staging, Prod). If you need multiple APIMs for an environment then having them in the same RG makes sense.

In other cases you may create a separate RG for each related set of products for each environment. In this case if you have multiple APIMs to support a product then that would seem odd to me, since each would have its own API and users. In this case I'd assume you'd have a single APIM with multiple APIs for the product(s) hosted in the RG. But if you really need multiple APIMs then it is fine.

Note that each APIM is priced separately so the more APIMs you configure the more you pay. But whether that is in a single RG or separate ones doesn't impact the price, that I'm aware of.

Answer 2

Laurens van de Venn 200

Hi Michael,

We have several devops teams which will use their own APIM instance in development and test subscription. In Acceptance and production we will have one premium tier APIM instance for all devops teams (hopefully with workspaces).

So it should not be an issue to host several APIM instances in development and test subscription.

Only design question we would have, is it ok to host all APIM instances for development in one resource group (same for test) or across several resource groups?

Regards,

Laurens van de Venn

Michael Taylor 58,451 Reputation points

2025-04-08T15:29:21.8466667+00:00

You can host them all in a single RG if you want. I don't think there is a right or wrong answer for this. Ideally though your non-prod configuration should match as closely as possible to your prod configuration. This avoids the nasty "deployment shock" issues that occur because assumptions made in non-prod don't apply to prod.

Share via

Multiple APIM developer instances in one resource group

1 additional answer

Your answer