Support for Let's Encrypt
Allow publishers to easily use Let's Encrypt with the API management. https://letsencrypt.org/
Please tell us a bit more about scenarios you are trying to enable and how do you see this feature working.
Jeff harry commented
Hey, Excellent work. I must appreciate the way you manage your article’s content and the look & feel of your website. you are really doing a great job, carry on the hard work. https://getgeek.info/geek-squad/
sophia world commented
I can only recommend that certificates could be stored in a key vault and auto rolled on renewal. If anyone is free please also give your suggestion on- https://openfiles.org/extensions/torrent/
Elliot Huffman commented
I agree with @James, allow the selection of a lets encrypt cert (auto enrolled by the Az fabric) instead of having to upload your own.
The certificates could be stored in a key vault and auto rolled on renewal.
This would also allow for wildcard dns based certs to be shared with a single key vault.
James smith commented
There a lot you can do to improve azure and I have made a list on it that you can see at- https://gooff.info/how-to-setup-office/
Tekson Roy commented
Use acmev2 to set up autorenewal or https://getgeek.co/ contact team.
You can set up autorenewal through acmev2 as @rolfeleveld mentioned below or you can contact https://mcafee-activate-product-key.org/ team.
Seema Bhogal commented
I totally agree with you if they improve Azure API management then it will benefit us all. If anyone wants to discuss it further then you can contact me at https://i-nortonsetup.info/
Rolf Eleveld commented
Set up autorenewal through acmev2 on the system for specific names which have supporting txt record set up in DNS, or through an API like a Plugin on cerbot that can run from cloud shell.
Tom Bosworth commented
Please implement LE support for application gateway. Would like to use a tick box for LE cert.
Philip Coupar commented
Azure frontdoor supports azure managed certificates, this would be great for provisioning SSL certs against custom domains and possibly an easier alternative to let's encrypt as it is already provisioned for another service within the azure ecosystem.
Alexei Barnes commented
AWS API Gateway makes SSL with a custom domain name dead easy. Why this is so ******* Azure is a mystery to me. Shouldn't Microsoft be making every effort to enforce https with valid certificates?
Povl H. Pedersen commented
I don't care if it is lets encrypt, or like Amazon AWS that can issue/maintain certificates, or like Microsoft Azure CDN ( https://docs.microsoft.com/en-us/azure/cdn/cdn-custom-ssl?tabs=option-1-default-enable-https-with-a-cdn-managed-certificate ) - Here Microsoft calls it CDN managed certificate.
What is important is, that certificates has become free, and https required. So it shoul be a maintenance free part of the service provided. Not only to CDN customers, but to all customers.
Need to be deployed to all services.
Aaron Sadler commented
I agree, let's encrypt across the whole of Azure would be beneficial
James Schumann commented
When following the steps to "Configure a custom domain name" (https://docs.microsoft.com/en-us/azure/api-management/configure-custom-domain), I'd like a checkbox to use a Let's Encrypt cert in lieu of "In the Certificate, specify a valid .PFX file that you want to upload."
API Management would then create and apply the cert, and handle cert renewal automatically.