I have an Azure Web App that has 15 domain names associated with (i.e. all domain names map to the same application).
I need to provide SSL for all 15 domains, pointing to the same Web App.
My observations so far:
Conventional SSL binding requires one IP address per domain, so I would need 15 IP addresses for this one Web App.
Azure Web App only supplies a single IP per web app unless I purchase additional IPs at $39/each. I want to avoid buying 15 additional IPs.
I could create 15 Web applications under the same App Service Plan, but it looks like they all use the same external IP address as long as they are in the same app service plan, correct?
The newer SNI binding scheme can be used with a singular IP address across multiple domains, but is not supported in older browsers, such as IE on WinXP (more or less the only limitation of SNI, that I found)
I would like to avoid SNI SSL bindings since we have a decent amount of revenue coming from Windows XP/IE users that can't support SNI.
Given my requirements:
- Support SSL for 15 domain names on single App Service Plan (single or multiple web app instances)
- Avoid purchasing additional IPs if possible
- Avoid SNI if possible
... seems to me like the only reasonable option left is a UCC/SAN SSL certificate, correct?
If so, when I tried to purchase an "App Service Certificate" via Azure, I get the following info box which implies that UCC certs are not an option (at least for purchase):
My question is:
a.) Given my requirements, is my plan for using a SAN cert the appropriate course?
b.) Does Azure even support UCC/SAN certs for a scenario like this? I don't want to buy the cert only to find out I can't use it the way I intend.
Thanks in advance!