TL;DR: Is there a limit to how many managed application definitions can be created in the tenant's azure service catalog?
We are currently working on two services that we bundle via azure managed applications.
One service is published as a managed application definition internally in our tenant's azure service catalog.
The other service is published as a marketplace application and also as a managed application definition available internally in our tenant's azure service catalog.
We had a hard time understanding how versioning with managed applications could work, since we want to align the managed applications internal service infrastructure with the code that is also included in the managed application.
One of the managed application definitions has the following content:
Azure Function App
The version of the code running has version 1.2.3 for example
When we update the managed application definition, the correlation between the code version 1.2.3 and the "version" of the managed application definition's internal service infrastructure is lost, since we just overwrite the existing managed application definition.
Therefore we now want to publish a new managed application for every new version of our code, so that we ensure that every managed application's infrastructure works with the correct code.
This means that we would create:
and so on
If there is a limit to how many managed application definitions we can create in our tenant, then this approach obviously won't make sense.
The only information I've found regarding this issue is here: https://docs.microsoft.com/en-us/azure/marketplace/plan-azure-app-managed-app#choose-who-can-see-your-plan
with quote: "You can configure each plan to be visible to everyone (public) or to only a specific audience (private). You can create up to 100 plans and up to 45 of them can be private"
Does this mean we can only upload 45 managed application definitions in our service catalog?