Slow Onedrive sign-in in AVD with FSLogix

Rick Braakman 15

We a running a few Azure virtual desktop pools with multi-session Windows 10/11 hosts. These are non-persistant environments with FSLOGIX profile roaming (profile containters only). FSLOGIX Version: 2.9.8612.60056 The VHDs are stored on a premium file share. The environment is running smoothly for our users except for the sign-in time for the onedrive applications. When a users signs in on a multisession host and enters the desktop it can takes 4-5 minutes before the ondrive syncapp is finally logged in. We created a test environment and also tested the onedrive performance with a office container but nevertheless the performance is the same. We also tried different (older) onedrive builds, same result. All our hosts are up-2-date Does anyone have idea's what we can do?

KarishmaTiwari-MSFT 18,522 Reputation points Microsoft Employee

2024-02-13T23:13:56.0233333+00:00

@Rick Braakman We would need more information to understand the issue better.

-Are the VMs hybrid joined?
-Did you configure seamless SSOin your infrastructure?
-Do you see any errors in the event log before the OneDrive sign in succeeds?
Rick Braakman 15 Reputation points

2024-02-19T11:09:42.1366667+00:00

Thanks for responding. The VMs are joined to a Microsoft Entra domain Service. Seamless SSO in not supported for VM's that a joined to that kind of domain.

Onedrive doesnt display any errors in the event log. Just to be clear; The whole environment is working perfectly, even Onedrive once onedrive is logged in and synced properly. But we just cant figger out why this takes 4-5 mins. During this period we see that the onedrive process consumes alot of CPU. It almost looks like its checking if all files are there before is continues.
KarishmaTiwari-MSFT 18,522 Reputation points Microsoft Employee

2024-02-21T00:49:50.86+00:00

@Rick Braakman I checked with the internal team. They shared that it will be difficult to achieve with Entra ID domain services. They recommended either switch to native EntraID join or to hybrid join.
Rick Braakman 15 Reputation points

2024-02-22T08:34:23.65+00:00

That will be an impossible mission, there are legacy application which are hosted within the same VNET and and require local domain authentication.
KarishmaTiwari-MSFT 18,522 Reputation points Microsoft Employee

2024-02-27T06:53:03.2766667+00:00

@Rick Braakman You would need to connect your on-premises AD to your Azure VNET using Express route or Site to Site VPN.

1 answer

KarishmaTiwari-MSFT 18,522 Reputation points Microsoft Employee

2024-03-04T22:24:36.3+00:00

On discussion with the internal team, they confirmed that this will be difficult to achieve with Entra ID domain services. The recommendation is to either switch to native EntraID join or to hybrid join.

If you have applications which are hosted within the same VNET and require local domain authentication, you will need to connect your on-premises AD to your Azure VNET using Express route or Site to Site VPN.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment