You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation provides explicit formatting requirements for organization names only in the Windows registry key method, but not in other methods where the same requirements likely apply.
In the Windows registry key section:
Use lowercase letters only
Add each organization on a separate line
Do not use spaces or commas as separators
However, the Mac configuration profiles, plist, and cross-platform registry.json methods show organization names in examples but don't explicitly state the lowercase requirement or other formatting rules.
Why this matters
Administrators following the Mac or Linux setup methods might enter organization names with uppercase letters or other formatting that could cause enforcement to fail. They would need to troubleshoot and discover the formatting requirements indirectly, rather than being told upfront.
Suggested fix
Add a consistent note about organization name formatting requirements at the beginning of the "Choose your method" section or in each method's instructions. For example:
Note
Organization names must use lowercase letters only. Do not include spaces or special characters.
Alternatively, add this guidance to each method's setup instructions where organization names are first mentioned.
File:
content/manuals/enterprise/security/enforce-sign-in/methods.mdIssue
The documentation provides explicit formatting requirements for organization names only in the Windows registry key method, but not in other methods where the same requirements likely apply.
In the Windows registry key section:
However, the Mac configuration profiles, plist, and cross-platform registry.json methods show organization names in examples but don't explicitly state the lowercase requirement or other formatting rules.
Why this matters
Administrators following the Mac or Linux setup methods might enter organization names with uppercase letters or other formatting that could cause enforcement to fail. They would need to troubleshoot and discover the formatting requirements indirectly, rather than being told upfront.
Suggested fix
Add a consistent note about organization name formatting requirements at the beginning of the "Choose your method" section or in each method's instructions. For example:
Note
Organization names must use lowercase letters only. Do not include spaces or special characters.
Alternatively, add this guidance to each method's setup instructions where organization names are first mentioned.
Found by nightly documentation quality scanner