Closed stephanadler1 closed 1 year ago
Thanks for the feedback! We are currently investigating and will update you shortly.
@stephanadler1 , We have assigned this issue to the respective product owner for review.
@amitsriva , for your review.
Some clarification: I've eventually found the limitation being described in FAQ item 7. However, since selecting Latest
as the way to automate updates when new certificates arrive is so prominently featured in the notes, its limitations when using BYOC should be described as prominently.
Better to remove Latest
if it just doesn't work. Remove it if fixing it is too much trouble. Its confusing and a waste of time to watch it fail.
Image: The pit of failure.
Unfortunately, we have been unable to review this issue in a timely manner. We sincerely apologize for the delayed response. We are closing this issue. If you feel that the problem persists, please respond to this issue with additional information.
Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
The suggestion to select
Latest
as the certificate/secret version is not available for BYOC in KeyVault. In my case I've imported the certificate into KeyVault and made another attempt by creating a new certificate (CSR) is created in the KeyVault with the type of CA set toCertificate issued by a non-integrated CA
.I'm using the Azure CDN
Premium_verizon
SKU.Note from section Select the certificate for Azure CDN to deploy item 4.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.