Before you begin
- The permission to view FSLogix storage (operations.fslogix.storage.view). Administrators, Operators, Helpdesk and Auditors have it; without it the page shows a restricted notice
- A Professional plan or above for the Capacity Monitor, profile reset and pushing configuration. On a lower plan a banner reads "FSLogix Capacity Monitor is not included in your current plan", and the other tabs stay available
- The pool-management permission (Administrator or Operator) to see the Settings tab and to start automatic detection
Detection is automatic
There is no detect button. When someone with the pool-management permission opens the page, Atlas scans every host pool for FSLogix if the last scan is missing or more than 15 minutes old. The status beside the page title shows "Detecting FSLogix from VMs…" while it runs and "Auto-detected" with the time once it finishes, and the badge reads Enabled as soon as one pool has FSLogix on. The scan also picks up pools that were configured outside Atlas. Use Refresh to reload the page's data on demand.
A quick tour of the tabs
- Overview: every host pool with its FSLogix state, file server and share. Click a file server to jump to that storage account on the Storage tab, or use a row's menu to configure FSLogix on that pool
- Profiles: every user's profile container, with its size, account status and row actions. See the next section
- Storage: your Azure Files storage accounts and shares, grouped by region. You can create a storage account or a new share here
- Host Coverage: each session host's live FSLogix state, such as Active, Partial, Registry (off) or Not found, for one pool or all of them. Refresh probes every running host in the pool
- Health: whether each FSLogix-enabled pool is fully configured. A pool is Healthy when it has a file server, a share and a profile type set
- Capacity: the Capacity Monitor and its auto-expand settings. See below
- Actions: fleet-wide operational controls (see Actions)
- Settings: where FSLogix is switched on and configured for each host pool. Only shown with the pool-management permission
Profiles: sizes, orphans and resetting a profile
The Profiles tab lists every profile container across your FSLogix-enabled pools, with totals for profiles, profiles that need attention, and storage. Search by user or pool, or pick one host pool from the list.
To measure profiles, select a single host pool and click Scan sizes & orphans. Atlas reads each container's size, flags size outliers that sit well above the fleet median, and checks each user's account: Enabled, Disabled, or No account. A container whose user is disabled or deleted is orphaned and is a candidate for clean-up. The scan works on one pool at a time because it reads every profile from storage.
Each row's menu holds the profile actions:
- Reset Profile: signs the user out of that host pool and moves their container aside, so a fresh profile is created at their next sign-in. Atlas keeps the old container on the share as a backup (renamed with _RESET_ and a timestamp) rather than deleting it. You confirm in a dialog first, and the reset can take a few minutes. It needs the pool-management and security-management permissions
- Detach Container and Mark for Rebuild: shown in the menu but not available yet
Anything the user hasn't saved in their open session is lost when you reset their profile, and their new profile starts empty. Use the backup on the file share if you need to recover files from the old one.
Actions
The Actions tab lists four fleet-wide controls: Push FSLogix Config, Validate File Share Access, Test Container Mount and Rotate Storage Credentials. They are not available yet, so each card is shown with its button disabled. Until they are, manage FSLogix one host pool at a time from its Settings and Diagnostics. When Rotate Storage Credentials arrives it will need the security-management permission, and you will type ROTATE CREDENTIALS to confirm, because it replaces the storage account keys used by every VM in the tenant.
The Capacity Monitor
A full profile share stops users signing in, so the Capacity Monitor checks every FSLogix profile share in every tenant every 15 minutes. The Capacity tab shows the result:
- Capacity Overview: how many shares are monitored, how many are near capacity, and how many auto-expansions ran in the last 30 days
- Auto-Expand Configuration: Enable Auto-Expand, Warning Threshold, Expand Trigger Threshold and Expand Amount. Click Save Settings to apply them (Administrator only)
- Run Check Now: checks every share immediately instead of waiting for the next cycle. It needs the permission to resize file shares
- Capacity Event History: recent checks, warnings and expansions, with each share's usage, quota and result. It updates live, or every 60 seconds if the live connection drops
Thresholds and auto-expand
Out of the box a share shows a warning at 85% full. Auto-expand is off until you turn it on; once it is on, a share that reaches 95% grows by 10% of its current size. The warning threshold must be lower than the expand trigger threshold.
Each expansion grows a share by at least 1 GB and never more than doubles it in one go, so a mistyped percentage can't run away with your storage bill. After an expansion the share is graded against its new size.
Settings resolve Global → Tenant → Host Pool: the values you save on the Capacity tab apply to the selected tenant, and a host pool with its own override uses that instead.
Only Azure Files shares can auto-expand. Azure NetApp Files and other SMB (UNC) shares are monitored and warn you as they fill, but Atlas never resizes them; grow those volumes yourself. For the profile errors users actually hit, see the FSLogix Troubleshooting post on the Atlas AVD blog.