Clarify GA status and technical preview in warning (#3842)

Updated warning message to clarify GA status and technical preview for
Active Directory interfacing.

---------

Co-authored-by: Karen Metts <[email protected]>
Co-authored-by: Visha Angelova <[email protected]>
Co-authored-by: Visha Angelova <[email protected]>

Author: 3 people

reference/fleet/elastic-agent-unprivileged.md

@@ -234,12 +234,12 @@ For example:
 
 ## Using `unprivileged` mode with a pre-existing user and group [unprivileged-preexisting-user]
 
-::::{warning}
-This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
-::::
-
+In certain cases you may want to install {{agent}} in `unprivileged` mode, with the agent running as a pre-existing user or as part of a pre-existing group. For example, on a Windows system you may have a service account in Active Directory and you'd like {{agent}} to run under that account.
 
-In certain cases you may want to install {{agent}} in `unprivileged` mode, with the agent running as a pre-existing user or as part of a pre-existing group. For example, on a Windows system you may have a service account in Active Directory and you’d like {{agent}} to run under that account.
+:::{admonition} Active Directory to determine user group
+:applies_to: stack: preview
+The ability to interface with Active Directory to determine the user group is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
+:::
 
 ::::{note}
 On Windows, the `--password` parameter is required when specifying a custom user account.