Default all users to local Windows profiles

README.md

@@ -61,7 +61,7 @@ Operational documentation:
 - [Self-hosted RustDesk server and managed Windows remote access](docs/rustdesk-operations.md)
 - [Domain monitoring, usage reports, and six-month retention](docs/monitoring.md)
 - [Laboratorio desktop wallpaper protection](docs/laboratorio-wallpaper-policy.md)
-- [Azure user roaming by role with Azure Files and FSLogix](docs/user-roaming.md)
+- [Optional Azure user roaming by role with Azure Files and FSLogix](docs/user-roaming.md)
 - [Decision: do not persist password verifiers in Redis](docs/decisions/0001-no-password-cache.md)
 
 | Prefix | Role | Default OU | Security group in the same OU |
@@ -109,11 +109,12 @@ Follow [docs/lab-runbook.md](docs/lab-runbook.md). Review
 For a public Azure VM, use
 [docs/azure-vpn-deployment.md](docs/azure-vpn-deployment.md). It supports an
 optional Azure P2S gateway or direct enrollment restricted to explicit public
-source CIDRs. P2S deployments also provision private Azure Files storage for
-role-based roaming: `AL` redirects only Documents/Desktop, while `AD` and `DO`
-use an FSLogix VHDX profile after the post-domain setup step. Existing public
-Azure Files deployments automatically use FSLogix Cloud Cache locally instead
-of performing all profile I/O across WAN SMB.
+source CIDRs. Every SGU role uses an ordinary local Windows profile by default:
+Desktop and Documents stay under `C:\Users` and no profile share is mapped.
+Azure Files/FSLogix roaming remains available only as an experimental,
+explicit opt-in that requires acknowledgement of its login, sign-out, storage,
+cache and recovery risks. See [docs/user-roaming.md](docs/user-roaming.md) for
+the opt-in and rollback procedures.
 
 Never disable the built-in Microsoft password Credential Provider. It is the
 supported recovery path if a third-party provider fails to load.