From 0900f3ee350b4e460fbbd34de81fcd9f145981b7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Lu=C3=ADs=20Teles?=
 <167199412+l-teles@users.noreply.github.com>
Date: Fri, 6 Mar 2026 18:53:50 +0000
Subject: [PATCH] Enhance Okta verification with issued certificates check
 (#40805)

Minor update on the [Enable Okta Verify on
Windows](https://fleetdm.com/guides/enable-okta-verify-on-windows-using-a-scep-configuration-profile)
article that documents the option of checking if the certificates are
being successfully issued by Okta or not
---
 ...ta-verify-on-windows-using-a-scep-configuration-profile.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/articles/enable-okta-verify-on-windows-using-a-scep-configuration-profile.md b/articles/enable-okta-verify-on-windows-using-a-scep-configuration-profile.md
index 8c5d11ed7f..fdeb4a9d45 100644
--- a/articles/enable-okta-verify-on-windows-using-a-scep-configuration-profile.md
+++ b/articles/enable-okta-verify-on-windows-using-a-scep-configuration-profile.md
@@ -107,8 +107,8 @@ Get-WinEvent -LogName Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-
 
 1. Log in to Okta Admin Console
 2. Navigate to **Reports** > **System Log**
-3. Filter for device attestation events
-4. Confirm the device appears as managed
+3. Filter for certificate issued events (`eventType eq "pki.cert.issue"`)
+4. Confirm the certificates were issued successfully (The certificate `CN` should match the hosts serial number)
 
 ## Troubleshooting