Skip to content

Fix role name for Key Vault Secrets Officer#144

Open
dylan8902 wants to merge 1 commit into
MicrosoftDocs:mainfrom
dylan8902:patch-1
Open

Fix role name for Key Vault Secrets Officer#144
dylan8902 wants to merge 1 commit into
MicrosoftDocs:mainfrom
dylan8902:patch-1

Conversation

@dylan8902

Copy link
Copy Markdown

This PR fixes a typo for the Key Vault Secrets Officer role

@prmerger-automator

Copy link
Copy Markdown
Contributor

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

1 similar comment
@prmerger-automator

Copy link
Copy Markdown
Contributor

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

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit e860f2d:

⚠️ Validation status: warnings

File Status Preview URL Details
articles/confidential-ledger/ledger-explorer-concepts.md ⚠️Warning Details
articles/key-vault/general/rbac-guide.md ✅Succeeded

articles/confidential-ledger/ledger-explorer-concepts.md

  • Line 7, Column 11: [Warning: ms-topic-invalid - See documentation] Invalid value for 'ms.topic': 'conceptual'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@v-regandowner

v-regandowner commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

@dylan8902 - Typo fix looks good, but validation warnings must be resolved before we can merge!

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

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.

3 participants