@Tennant, Andrew welcome to the Microsoft Q&A community.
Below are a few key areas to investigate.
- DNS Configuration
Even if you don’t manage Azure DNS directly, misconfigured or unreachable DNS endpoints can cause session drops. Consider:
Verifying that your session hosts can resolve internal and external names consistently.
Using Azure-provided DNS or explicitly setting custom DNS servers in your virtual network settings.
- FSLogix Profile Container Issues
FSLogix can be sensitive to:
Storage latency or permissions misconfigurations on the profile share.
Antivirus interference—make sure FSLogix paths and VHD locations are excluded.
Cloud Cache misbehavior—if enabled, it can cause profile mounting delays or failures.
- Session Host Health
Check:
VM performance metrics (CPU, disk I/O, network throughput).
Event Viewer logs under Applications and Services Logs > FSLogix
for profile load errors.
The frxtray
tool on session hosts—it gives a quick status of FSLogix profile health.
- Network Stability
Since the issue occurs both at home and in the office, it might be:
A backend Azure networking issue (e.g., virtual network peering, NSG rules).
- Or Windows App client instability—try updating or switching to the web client temporarily to compare behavior.
N/B: I have generated the above answer using co-pilot as an AI tool. Also I have validated and updated the AI output.
I hope these helps. Let me know if you have any further questions or need additional assistance.
Also if these answers your query, do click the "Upvote" and click "Accept the answer" of which might be beneficial to other community members reading this thread.