Cosmos Always Encrypted misleading documentation about CMK key versions

[asos-gaborbuzasi]

The CreateClientEncryptionKeyAsync method requires the full path to the CMK key in KeyVault specified - it doesn't accept a key URL without the version. Thus you can't actually provide a non-version specific URL to the DEK.

[prmerger-automator]

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

[learn-build-service-prod]

Learn Build status updates of commit 1347f87:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/cosmos-db/how-to-always-encrypted.md	✅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

[learn-build-service-prod]

Learn Build status updates of commit a607c7e:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/cosmos-db/how-to-always-encrypted.md	✅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

[Court72]

@iriaosara

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

[github-actions]

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