Skip to content

Commit 94d0f98

Browse files
msmbaldwinCopilot
andcommitted
Fix h1-not-first warning: move INCLUDE after H1 heading
Co-authored-by: Copilot <[email protected]>
1 parent 84aa493 commit 94d0f98

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

articles/key-vault/keys/hsm-protected-keys-byok.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,10 +12,10 @@ ms.date: 04/09/2026
1212
ms.author: mbaldwin
1313
---
1414

15-
[!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
16-
1715
# Import HSM-protected keys to Key Vault (BYOK)
1816

17+
[!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
18+
1919
For added assurance when you use Azure Key Vault, you can import or generate a key in a hardware security module (HSM); the key never leaves the HSM boundary. This scenario is often referred to as *bring your own key (BYOK)*. Key Vault uses [FIPS 140 validated HSMs](/azure/key-vault/keys/about-keys#compliance) to protect your keys.
2020

2121
> [!IMPORTANT]

0 commit comments

Comments
 (0)