From e2500002edd9b65cea09e77fb740a3b2b1ede663 Mon Sep 17 00:00:00 2001
From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
Date: Fri, 23 Jan 2026 03:47:36 -0500
Subject: [PATCH] macOS setup experience: Clarify behavior (#38379)

- macOS setup: "may" isn't that helpful. It doesn't make the user feel
confident on what they should document internally.
---
 articles/setup-experience.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/articles/setup-experience.md b/articles/setup-experience.md
index 9384b961f9..958c918b7e 100644
--- a/articles/setup-experience.md
+++ b/articles/setup-experience.md
@@ -18,7 +18,7 @@ You can enforce end user authentication during automatic enrollment (ADE) for Ap
    to populate and lock the macOS local account **Account Name**. For example, a
    "johndoe@example.com" email will turn into a "johndoe" account name.
 
-> **NOTE**  If the host is restarted during the mdm enrollment process, there may be an issue with populating the macOS local account creation screen. The fields are not guaranteed to be populated with the user's IDP email and username.
+> If the host is restarted during automatic enrollment (DEP), the macOS local account fields won't be populated with the user's IDP email and username.
 
 3. Make sure your end users' full names are set to one of the following attributes (depends on IdP): `name`, `displayname`, `cn`, `urn:oid:2.5.4.3`, or `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name`. Fleet will automatically populate and lock the macOS local account **Full Name** with any of these.