Add support for free tls/ssl certificates
I want to create a tls/ssl binding to a custom host-name with a free certificate
Thank you for your feedback. We understand that lack of support for naked domains is limitation. We are working with our partner teams to bring support for naked domains to this feature. You can vote and keep track of the progress here: https://feedback.azure.com/forums/169385-web-apps/suggestions/38981932-add-naked-domain-support-to-app-service-managed-ce.
Also, we are working to bring App Service Managed Certificates to Free and Share tiers. You can vote and keep track of this here: https://feedback.azure.com/forums/169385-web-apps/suggestions/39223321-support-app-service-managed-certificates-on-free-a
Rodd Harris commented
Does the currently "completed" functionality include wildcards?
Ty Cahill commented
This should NOT be marked "completed" with a link for people to vote on yet another feature request for the same feature--FULL support for free TLS/SSL certificates.
I've been waiting YEARS as a paying Azure customer for this basic support that every $5/month web host provides built-in and free.
How can I generate the certificate using the CLI (az webapp config ssl ...) ?
The documentation only refers to using the portal.
My CLI version is 2.0.77
Not completed. Add this to the free tier (or at least the shared tier).
Andrew Funk commented
I agree with sentiment here that without naked domain support this service is severely lacking, so here's a suggestion to support it...
No naked domains, this is not a solution
1) This is fantastic news. We have been trying to use Let's Encrypt and to apply those certs to a WAF, and it's been painful. Is it possible to apply the more expensive option, "App Service Certificates," to a WAF?
2) Quickly read the documentation, and it really needs a quick comparison table. I created one for myself, so see attached Excel file. (Not a Microsoft employee, just a cloud engineer trying to understand the trade-offs.)
This is limited to "www. ..." No naked domains or wildcards?? So this solution is not a solution.
Who on earth still types (or sees) www in websites anymore? That died about a decade ago!
Can someone create a new request to include "naked domains" and "wildcards" like can be easily done by sslforfree.com? It will get 9000 votes again in no time.
While we super-appreciate the attempt, Microsoft should be in the business of enticing developers to come to Azure, and ssl certificates should not be a 'money maker' since Azure is making billions. A "real" free SSL solution would be so very appreciated. You will get far more money from Devs coming to and using, and paying for Azure if there was a "true" free SSL option.
This is great. This is flat out great. I've been playing with it today and it works well. Very nicely done and congrats to Microsoft for doing something that may seem counter intuitive to their bottom line but is so much value added that it's a no-brainer to use Azure. Please keep making these great decisions. Thank you.
Lorand David commented
Is there a way to generate a wildcard certificate? which can be used for *.mydomain.com
Zdenek Havlin commented
@Chris West, @Kevin Walter, is there feature request/suggestion to support naked domains? I would happily +1 it!
Chris West commented
Agree.. needs naked domain support at least to be usable. Will continue with my Let's Encrypt process for now.
Stuart Bale commented
Kevin Walter commented
You cannot seriously consider this a completed task. Without naked domain support, these certs are virtually worthless.
Scott Devine commented
free? Nope - not on all plans you have to upgrade to get the free tls/ssl certificates....
Martin Meixger commented
César Augusto Swarowsky commented
Any progress on release TLS/SSL bindings?
I will migrate my small web app to other cloud hosting platform because of this... Azure force me to increase my application final cost from 43 BRL to 248 BRL just because i want to insert a TLS/SSL binding.
I don't see the logic of this. Why there is not others plans? why it has to be that large variance? I think Microsoft loses some money because of this feature (as if Microsoft cares about it haha) but makes small business get away from its cloud platform.
Sandro Galfo commented
It looks like things are finally moving. A new "Create App Service Managed Certificates" option recently appeared in SSL/TLS settings.
What a depressing thread, showing that Microsoft is just not willing to make developers' lives easier. Oh, they can add a 1-click option to charge people hundreds of dollars. But they can't figure out how to make the industry standard work easily.
So, any news on this?