From bb7f8cbc2b3eb7779125b942e6b415bebfe35221 Mon Sep 17 00:00:00 2001
From: Steven Palmesano <3100993+spalmesano0@users.noreply.github.com>
Date: Mon, 6 Jul 2026 10:04:39 -0500
Subject: [PATCH] Update Okta PSSO guide (#48681)

See [Slack
thread](https://fleetdm.slack.com/archives/C07MYE3KKPX/p1783033256079649?thread_ts=1783032590.786169&cid=C07MYE3KKPX)
for context.
---
 articles/deploying-okta-platform-sso-with-fleet.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/articles/deploying-okta-platform-sso-with-fleet.md b/articles/deploying-okta-platform-sso-with-fleet.md
index f54230702f..bf822ed562 100644
--- a/articles/deploying-okta-platform-sso-with-fleet.md
+++ b/articles/deploying-okta-platform-sso-with-fleet.md
@@ -52,7 +52,7 @@ The recommended approach is to use Fleet as a SCEP proxy with Okta's dynamic cha
 
 1. In the Okta Admin Console, go to **Security** → **Device integrations**
 2. Click the **Device Access** tab (not Endpoint management)
-3. Click **Add platform**
+3. Click **Add SCEP configuration**
 4. Select **Desktop (Windows and macOS only)**, then click **Next**
 5. On the Add device management platform page, select:
    - **Certificate authority:** Use Okta as certificate authority
@@ -151,7 +151,7 @@ If you prefer to use a static challenge without Fleet acting as a SCEP proxy, fo
 
 1. In the Okta Admin Console, go to **Security** → **Device integrations**
 2. Click the **Device Access** tab (not Endpoint management)
-3. Click **Add platform**
+3. Click **Add SCEP configuration**
 4. Select **Desktop (Windows and macOS only)**, then click **Next**
 5. On the Add device management platform page, select:
    - **Certificate authority:** Use Okta as certificate authority