Skip to content

Adds a section on unsupported keys to troubleshoot-tde.md #10106

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: live
Choose a base branch
from

Conversation

iamjustsam
Copy link

Adds a section on unsupported keys. Using an unsupported key will throw an InternalServerError without further information.

Adds a section on unsupported keys. Using an unsupported key will throw an InternalServerError without further information.
@iamjustsam
Copy link
Author

@microsoft-github-policy-service agree

Copy link
Contributor

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

Copy link
Contributor

Learn Build status updates of commit 8eeb8f5:

✅ Validation status: passed

File Status Preview URL Details
docs/relational-databases/security/encryption/troubleshoot-tde.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@v-regandowner
Copy link
Contributor

@rwestMSFT - 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

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label May 30, 2025
@VanMSFT
Copy link
Member

VanMSFT commented May 30, 2025

Hi @Pietervanhove - Can you please review to see if this is an appropriate addition the doc? Thanks!

#assign:Pietervanhove

@Pietervanhove
Copy link
Contributor

It might be a good idea to add this, but I'm not sure if the error message "500 InternalServerError - An unexpected error occured while processing the request." is only related to a wrong key format. I'll need to double check with engineering.

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.

5 participants