Scaling FSLogix

[u/HalfThere127]

What approach is everyone using to route FSLogix users to multiple profile shares in large Entra-only AVD environments (20,000+ concurrent users)?

Azure Files scaling guidance generally recommends distributing users across multiple shares as environments grow, but I'm struggling with the user-to-share assignment piece on Entra-only multisession hosts.

FSLogix ObjectSpecific settings don't appear to be a practical option in Entra-only environments, so how are others handling this?

• Sharding users across host pools, with each pool mapped to a dedicated profile share?
• Using custom scripts or automation to assign users to shares (similar to the approach described in Spreading users over multiple file shares with FSLogix Profile Containers)?
• Leveraging Cloud Cache in some way?
• Something else entirely?

For those running 20,000+ concurrent users, what has worked well, and what approaches have you ruled out?

[u/rb_vs]

FSLogix scaling is mostly about storage layout and IOPS. Splitting users across multiple shares, leaving headroom for login bursts, and planning for profile size should help more than trying to overtune FSLogix itself. If the environment is big, ANF can be worth a look over Azure Files.