Added line breaks for profile values (#26029)

# Checklist for submitter

If some of the following don't apply, delete the relevant line.

<!-- Note that API documentation changes are now addressed by the
product design team. -->

- [ ] Changes file added for user-visible changes in `changes/`,
`orbit/changes/` or `ee/fleetd-chrome/changes`.
See [Changes
files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Committing-Changes.md#changes-files)
for more information.
- [ ] Input data is properly validated, `SELECT *` is avoided, SQL
injection is prevented (using placeholders for values in statements)
- [ ] Added support on fleet's osquery simulator `cmd/osquery-perf` for
new osquery data ingestion features.
- [ ] If paths of existing endpoints are modified without backwards
compatibility, checked the frontend/CLI for any necessary changes
- [ ] If database migrations are included, checked table schema to
confirm autoupdate
- For database migrations:
- [ ] Checked schema for all modified table for columns that will
auto-update timestamps during migration.
- [ ] Confirmed that updating the timestamps is acceptable, and will not
cause unwanted side effects.
- [ ] Ensured the correct collation is explicitly set for character
columns (`COLLATE utf8mb4_unicode_ci`).
- [ ] Added/updated automated tests
- [ ] A detailed QA plan exists on the associated ticket (if it isn't
there, work with the product group's QA engineer to add it)
- [ ] Manual QA for all new/changed functionality
- For Orbit and Fleet Desktop changes:
- [ ] Orbit runs on macOS, Linux and Windows. Check if the orbit
feature/bugfix should only apply to one platform (`runtime.GOOS`).
- [ ] Manual QA must be performed in the three main OSs, macOS, Windows
and Linux.
- [ ] Auto-update manual QA, from released version of component to new
version (see [tools/tuf/test](../tools/tuf/test/README.md)).

articles/deploying-entra-platform-sso-with-fleet.md

@@ -39,18 +39,18 @@ Before we start to add values to the payload, double-check to make sure that onl
 
 >Note: This profile uses the `SecureEnclaveKey` authentication method, which uses a Secure Enclave-backed key to authenticate with the IdP instead of the user’s local account password. If you wish, you can instead use Password, which prompts the user for their local account password to authenticate with the IdP and keeps it in sync with the IdP.
 
-Enter the following values for the specified keys:
-**Extension Identifier:** com.microsoft.CompanyPortalMac.ssoextension
-**Type:** Redirect
-**Team Identifier:** UBF8T346G9
-**URLs:** https://login.microsoftonline.com
-https://login.microsoft.com
-https://sts.windows.net
-**Screen Locked Behavior:** Do Not Handle
-**Authentication Method:** User Secure Enclave Key
-**Platform SSO Authentication Method:** UserSecureEnclaveKey
-**Use Shared Device Keys:** Checked
-**Account Name:** preferred_username
+Enter the following values for the specified keys:\
+**Extension Identifier:** com.microsoft.CompanyPortalMac.ssoextension \
+**Type:** Redirect \
+**Team Identifier:** UBF8T346G9 \
+**URLs:** https://login.microsoftonline.com\
+https://login.microsoft.com \
+https://sts.windows.net \
+**Screen Locked Behavior:** Do Not Handle \
+**Authentication Method:** User Secure Enclave Key \
+**Platform SSO Authentication Method:** UserSecureEnclaveKey \
+**Use Shared Device Keys:** Checked \
+**Account Name:** preferred_username \
 **Full Name:** name
 
 The finalized profile should look like this: