From 19459e417da4ca89567d0883c5d318870fbca90b Mon Sep 17 00:00:00 2001
From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com>
Date: Mon, 24 Jun 2024 12:28:25 -0400
Subject: [PATCH] updates
---
windows/security/docfx.json | 5 -----
.../deploy/on-premises-cert-trust-enroll.md | 2 ++
2 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/windows/security/docfx.json b/windows/security/docfx.json
index af2b39bffc..2e3135282a 100644
--- a/windows/security/docfx.json
+++ b/windows/security/docfx.json
@@ -167,11 +167,6 @@
"✅ Windows Server 2019",
"✅ Windows Server 2016"
],
- "identity-protection/hello-for-business/**/*.md": [
- "✅ Windows 11",
- "✅ Windows 10",
- "✅ Windows Server 2025 (preview)"
- ],
"identity-protection/smart-cards/**/*.md": [
"✅ Windows 11",
"✅ Windows 10",
diff --git a/windows/security/identity-protection/hello-for-business/deploy/on-premises-cert-trust-enroll.md b/windows/security/identity-protection/hello-for-business/deploy/on-premises-cert-trust-enroll.md
index 2c9e551150..63391d32fc 100644
--- a/windows/security/identity-protection/hello-for-business/deploy/on-premises-cert-trust-enroll.md
+++ b/windows/security/identity-protection/hello-for-business/deploy/on-premises-cert-trust-enroll.md
@@ -75,6 +75,8 @@ The AD FS registration authority verifies the key used in the certificate reques
The CA validates that the certificate is signed by the registration authority. On successful validation, it issues a certificate based on the request and returns the certificate to the AD FS registration authority. The registration authority returns the certificate to Windows where it then installs the certificate in the current user's certificate store. Once this process completes, the Windows Hello for Business provisioning workflow informs the user that they can use their PIN to sign-in through the Action Center.
+> [!VIDEO 387edee6-45a2-421d-9ea7-0f5aa0f02289]
+
### Sequence diagram
To better understand the provisioning flows, review the following sequence diagram: