Added clarification about exportable private key
Added clarification about requirement of certificates to have exportable private key. This is discussed here: https://github.com/MicrosoftDocs/azure-docs/issues/33157 but seems it was not added to the documentation.
@lonevvolf : Thanks for your contribution! The author(s) have been notified to review your proposed change.
Learn Build status updates of commit 7e3dc05:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/application-gateway/key-vault-certs.md | :white_check_mark:Succeeded |
For more details, please refer to the build report.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
@greg-lindsay
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team
@greg-lindsay Is there any update on this merge? Much appreciated to add clarity for users!
Learn Build status updates of commit d513463:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/application-gateway/key-vault-certs.md | :white_check_mark:Succeeded |
For more details, please refer to the build report.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
@greg-lindsay
Can you review this old PR and determine whether it needs to be closed or merged?
#sign-off