FSlogic issue with Entra Id

Welcome to the Microsoft Q&A Platform and thank you for your question!

Based on your description, I would like to share some guidance that may help you resolve the issue you are encountering.

In environments that are fully based on Microsoft Entra ID, FSLogix may not function as expected because it relies on traditional Active Directory (AD) authentication to access profile containers.

To address this:

1. Ensure you are using the latest version of FSLogix, as recent updates may include enhancements for compatibility with cloud-native environments.
2. Review the policies applied during FSLogix configuration, particularly for cloud-only deployments. Since your setup is Entra ID-only, it’s recommended to configure FSLogix to use Cloud Cache (CCD) locations instead of traditional SMB shares. This helps mitigate authentication challenges caused by the absence of Kerberos in Entra ID-only environments.
3. Verify group policy settings for Cloud Cache and confirm that the necessary permissions are properly set on your CCD storage locations—such as Azure Files or Azure Blob Storage—using either Active Directory Domain Services (AD DS) integration or Shared Access Signatures (SAS).

Implementing these configurations can significantly improve profile reliability and availability in a fully cloud-native deployment.

For more details, please refer to the official documentation:

• Tutorial: Configure Profile Containers with Cloud Cache - FSLogix | Microsoft Learn
• Configuration Settings - FSLogix | Microsoft Learn

I hope this information can help you to finish it successfully. Wish you a pleasant day!