Prerequisites
Note
We recommend customers upgrade to the latest version of FSLogix as quickly as their deployment process can allow. FSLogix will provide hotfix releases which address current and potential bugs that impact customer deployments. Additionally, it is the first requirement when opening any support request.
FSLogix may be used in any public / private data center or cloud, as long as the user is properly licensed. FSLogix operates on all Microsoft supported operating systems that include, but isn't limited to:
- Windows 10 and Windows 11
- Windows Server 2012 R2, 2016, 2019, 2022, 2025
Eligibility
You're eligible to use FSLogix if you have one of the following licenses:
- Microsoft 365 E3/E5
- Microsoft 365 A3/A5/ Student Use Benefits
- Microsoft 365 F1/F3
- Microsoft 365 Business
- Windows 10 Enterprise E3/E5
- Windows 10 Education A3/A5
- Windows 10 VDA per user
- Remote Desktop Services (RDS) Client Access License (CAL)
- Remote Desktop Services (RDS) Subscriber Access License (SAL)
- Azure Virtual Desktop per-user access license
Identity and Authentication considerations
Understanding your organization identity and authentication framework is a critical component in a successful FSLogix solution. FSLogix and your users are dependent on the underlying identity configuration to ensure they're able to access the storage provider, applications and process rule sets.
Identity next steps
Storage considerations
Before implementing FSLogix, it's important to properly design and configure your storage infrastructure based on your workload, user, and business requirements. FSLogix doesn't provide storage architecture or design guidance. The following next steps are provided as guides in your solution design process.
Storage next steps
Network considerations
Network configuration also plays an important aspect when designing your profile management solution using FSLogix. FSLogix is unique in that the standard configuration relies on mounting a container from a remote storage provider. Regardless of the configuration, network latency, bandwidth and proximity to the storage provider is pivotal to the user's experience.
Configure Antivirus file and folder exclusions
Antivirus products are known to conflict with FSLogix containers and requires that specific files and folders are excluded from any type of scanning or heuristics.
File / folder exclusions
%TEMP%\*\*.VHD%TEMP%\*\*.VHDX%Windir%\TEMP\*\*.VHD%Windir%\TEMP\*\*.VHDX\\server-name\share-name\*\*.VHD\\server-name\share-name\*\*.VHD.lock\\server-name\share-name\*\*.VHD.meta\\server-name\share-name\*\*.VHD.metadata\\server-name\share-name\*\*.VHDX\\server-name\share-name\*\*.VHDX.lock\\server-name\share-name\*\*.VHDX.meta\\server-name\share-name\*\*.VHDX.metadataCloud Cache specific exclusions
%ProgramData%\FSLogix\Cache\*(folder and files)%ProgramData%\FSLogix\Proxy\*(folder and files)
Note
If you change the default location of the cache or proxy folder, adjust the exclusions accordingly.