Troubleshoot Intermittent Microsoft 365 Connectivity in Azure Virtual Desktop
Question details
Users are experiencing intermittent connection failures with Microsoft 365 applications, including OneDrive, Teams, and Outlook, when operating within Azure Virtual Desktop environments.
- Product
- Microsoft 365 / Azure Virtual Desktop
- Device & OS
- Windows 10 / Windows 11
- Scenario
- Using Microsoft 365 productivity apps in an Azure Virtual Desktop (AVD) host pool environment.
- Observed behavior
- Intermittent connectivity drops occur, such as Outlook staying on 'Trying to connect' without prompting for a password, and other apps failing to authenticate. Some users also report errors like 1001 and 48v35, or AppX crashes after recent patches.
Ensure you have administrator access to the Azure Virtual Desktop environment and are prepared to capture system and network logs immediately when the intermittent issue occurs.
Collect System Logs and Engage Microsoft Support
The most effective way to resolve intermittent AVD connectivity issues is to capture detailed logs while the problem is actively occurring and escalate them to Microsoft Support.
Because the issue is intermittent and sometimes disappears during live support sessions, capturing logs at the exact moment of failure is critical. This includes AVD, Windows, Office, FSLogix, authentication, and network logs.
Set up network tracing tools and enable FSLogix logging in your Azure Virtual Desktop environment before the issue occurs.
As soon as a user reports that Outlook is stuck on 'Trying to connect' or Teams fails, immediately save the Windows Event logs, Office telemetry, and network traces.
Record the specific tenant details, whether the affected host pool is running Windows 10 or Windows 11, and check for any recent system patches.
Open a support ticket in the Microsoft 365 admin center and provide the collected logs, asking them to compare affected tenants and profile settings.
Migrate Affected Users to a Windows 11 Server
If the issue persists on Windows 10 host pools, moving users to a freshly deployed Windows 11 server can bypass underlying OS or profile corruption issues.
Try WPS Office for a Reliable Offline and Cloud Experience
If intermittent connectivity in Azure Virtual Desktop is disrupting your access to Microsoft 365 apps, consider WPS Office as a lightweight, highly compatible alternative. It offers robust offline capabilities and seamless format compatibility without relying heavily on constant cloud authentication.
- 1. Download WPS Office: Visit the official WPS website to download the free installation package.
- 2. Install on Your Virtual Desktop: Run the installer within your Azure Virtual Desktop environment or local machine.
- 3. Open and Edit Office Files: Easily open your existing Word, Excel, and PowerPoint files without worrying about intermittent connection errors.

Frequently Asked Questions
Why does Outlook stay on 'Trying to connect' without asking for a password in AVD?
This typically occurs due to intermittent authentication or network failures between the Azure Virtual Desktop host and Microsoft 365 servers. The authentication prompt (Modern Auth) fails to trigger properly, leaving the connection in a suspended state.
What logs are needed to troubleshoot Microsoft 365 issues in Azure Virtual Desktop?
You should collect Windows Event logs, Azure Virtual Desktop diagnostics, FSLogix profile logs, Office telemetry, network traces, and authentication logs while the issue is actively occurring to provide Microsoft Support with sufficient data.
Can upgrading to Windows 11 fix Microsoft 365 connection issues in AVD?
In some cases, deploying a new Windows 11 host pool and migrating users has resolved persistent connectivity issues and AppX crashes. However, it is more of a workaround for environment-specific bugs rather than a guaranteed fix.
What are error codes 1001 and 48v35 in Microsoft 365?
These errors are generally related to Microsoft 365 activation, authentication, or profile folder issues. They can occur after applying certain system patches in a virtualized environment, disrupting the connection to Microsoft services.




