Skip to content

ECH Azure MP: document BYOK configuration after deployment creation - #7599

Open
eedugon wants to merge 3 commits into
mainfrom
byok_azure_mp
Open

ECH Azure MP: document BYOK configuration after deployment creation#7599
eedugon wants to merge 3 commits into
mainfrom
byok_azure_mp

Conversation

@eedugon

@eedugon eedugon commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Added an admonition to the Azure Native Service page explaining that some advanced settings (deployment size, customer-managed encryption keys) are not available when creating a deployment from the Azure portal, and how to access them from the Elastic Cloud console after creation.
  • Added a new sub-page (azure-native-isv-service-byok.md) documenting the BYOK workflow specifically for Azure Native Service users, including context on default encryption and a link to the main BYOK doc.
  • Registered the new page in toc.yml under the Azure Native Service section.

Test plan

  • Check admonition renders correctly in the Azure Native Service page
  • Check new BYOK sub-page renders and appears in the TOC under Azure Native Service
  • Verify links to the main BYOK doc resolve correctly

🤖 Generated with Claude Code

- Add admonition to azure-native-isv-service.md explaining that advanced
  settings (deployment size, BYOK) are not available at creation time in
  the Azure portal but can be configured from the Elastic Cloud console
- Add new sub-page azure-native-isv-service-byok.md documenting how Azure
  Native Service users can add a customer-managed encryption key to an
  existing deployment via the Elastic Cloud console
- Register new page in toc.yml under the Azure Native Service section

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@eedugon
eedugon requested a review from a team as a code owner July 28, 2026 10:02
@github-actions

Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

  • Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

@github-actions

github-actions Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
navigation_title: Customer-managed encryption keys
---

# Customer-managed encryption keys for Azure Native Service [azure-native-isv-service-byok]

@shainaraskas shainaraskas Jul 28, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

imo this page is not adding a lot of value, so I'd just leave the note on the other page but have it link to the BYOK config page instead (deep link to reincryption)

@shainaraskas shainaraskas left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one note about the PR structure. imo this is a lot of words for "you can encrypt after you create the deployment. go look here" :)

nothing wrong with the content as it stands so ✅ if you really prefer this strategy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants