Skip to content

Update how-to-integrate-certificate-authority.md for CertCentral divisions missing support #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

MarcoLodini
Copy link

CertCentral divisions are not supported using the Key Vault integration, resulting consistently in an error. Docs have been updated to reflect this problem.

Copy link
Contributor

@MarcoLodini : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Copy link

Learn Build status updates of commit 25cca41:

✅ Validation status: passed

File Status Preview URL Details
articles/key-vault/certificates/how-to-integrate-certificate-authority.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@v-dirichards
Copy link
Contributor

@msmbaldwin

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

Copy link

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

@MarcoLodini
Copy link
Author

Hello, just pinging to check if there were any news on the matter. Thanks!

@github-actions github-actions bot removed the inactive label Jan 23, 2025
@v-dirichards
Copy link
Contributor

@msmbaldwin Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

Copy link

github-actions bot commented Feb 6, 2025

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

@MarcoLodini
Copy link
Author

MarcoLodini commented Feb 6, 2025 via email

@github-actions github-actions bot removed the inactive label Feb 7, 2025
Copy link

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

@v-dirichards
Copy link
Contributor

I sent email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

@v-dirichards v-dirichards requested review from msmbaldwin and removed request for msmbaldwin February 26, 2025 17:06
@github-actions github-actions bot removed the inactive label Feb 26, 2025
Copy link

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

@v-dirichards
Copy link
Contributor

@msmbaldwin Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

@github-actions github-actions bot removed the inactive label Mar 13, 2025
Copy link

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

Copy link
Contributor

@MarcoLodini : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@MarcoLodini
Copy link
Author

Hey everyone, a heads up: we have discussed the issue with DigiCert and it seems the error is thrown when API keys are not created in the parent organization (or something along the lines) resulting in insufficient permissions; hence the organization ID changes too. I'm not sure if it's better to add this information or drop the pull request altogether

@github-actions github-actions bot removed the inactive label Mar 27, 2025
@v-dirichards
Copy link
Contributor

v-dirichards commented Mar 27, 2025

@msmbaldwin Can you respond to the comment above?

@MicrosoftDocs/public-repo-pr-review-team

@PMEds28
Copy link
Contributor

PMEds28 commented Apr 10, 2025

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

Copy link

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

@v-dirichards
Copy link
Contributor

@msmbaldwin - Would you add a comment to indicate what action to take on this PR?

Thanks!

@github-actions github-actions bot removed the inactive label Apr 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants