Allow to bind an APIM instance with multiple domain names.
One might bind an APIM instance with a.com at the beginning and has it published to customers. Then decided to switch to b.com, but he don't want to add breaking changes to his existing customers and thus wants to keep both a.com and b.com binding to that APIM instance at the same time.
Patrik Norrgård commented
Wildcard support solves half of our problem, as two old endpoints share the same domain, but a third is on a completely different domain so we still need that to be possible. Thanks!
Samuel Li commented
Currently in order to support a new client, just for branding purpose, we have to lunch a new APIM instance, which is costly and a management headache.
We really need a feature to support multiple DNS names for developer portal.
For example, client a has clientA.contoso.com as entry point, and client B has clientB.contoso.com as entry point;
Can you please take a look at it?
Is there any detail on how this works. The documentation for APIM doesn't show how to achieve this. The ideas is that a wildcard cert will allow multiple sub domains for a songle APIM instance for different clients
Following this blog post but adapting to new portal
I went to "Custom domains and SSL'
Select type as 'Custom'
Set the Hostname to *.api.company.com
Uploaded the wildcard Certificate for *.api.company.com
Create a DNS A-Record mapping say a custom subdomain like mobile.api.company.com to the public VIP of the APIM?
The developer portal shows request URL as https://*.api.company.com
Of course this cannot be tested within dev portal.
Terry Zhou commented
Supporting wildcard domain names is a good progress, thanks APIM team.
Could we also support binding different domain names that do not have a common root domain name? Say binding api.a.com and api.b.com to the same APIM instances?
We recently introduced support for wildcard custom domains e.g. *.contoso.com which makes it possible to bind multiple subdomains to an APIM instance.