How to Stop Office 2024 LTSC from Switching to Microsoft 365 in VDI
Question details
Users need to prevent Office 2024 LTSC from changing its features or appearance based on a user's Microsoft 365 license when deployed in a Virtual Desktop Infrastructure (VDI).
- Product
- Microsoft Office 2024 LTSC
- Device & OS
- not provided
- Scenario
- Managing Office 2024 LTSC deployments in a VDI environment where end-users sign in with Microsoft 365 licenses.
- Observed behavior
- The Office 2024 LTSC installation automatically shifts its interface or feature set to match Microsoft 365 upon user sign-in.
Gather your Office deployment configuration (XML files), current update channel details, and shared computer activation settings before initiating the troubleshooting process.
Consult the Office Management Microsoft Q&A Community
Because licensing-based switching in VDI environments involves complex deployment configurations and backend validation, engaging Microsoft specialists is the recommended approach to find a supported configuration.
In a Virtual Desktop Infrastructure (VDI), Microsoft Office dynamically evaluates the signed-in user's license. If the system detects a higher-tier Microsoft 365 license, it may attempt to upgrade the Office LTSC feature set to match the subscription.
Resolving this usually requires targeted modifications to deployment XMLs or Group Policy configurations that are best audited by Microsoft engineers.
Open your web browser and visit the official Microsoft Q&A community forums.
Click 'Ask a question' and ensure you select the 'Office management' tag so it routes directly to deployment specialists.
In the body of your post, include your Office deployment configuration (ODT XML), update channel, shared computer activation settings, VDI design, user license types, and the exact affected Office build.
Publish your question so Microsoft engineers can review the licensing overlap and recommend specific registry or policy changes.
Avoid Complex Licensing Issues with WPS Office
Managing LTSC installations alongside Microsoft 365 licenses in VDI can create frustrating administrative overhead. WPS Office offers a free, lightweight, and highly compatible alternative that bypasses complex licensing conflicts while keeping your organization productive.
- 1. Download the installer: Visit the WPS Office website and download the standalone installation package.
- 2. Deploy in your environment: Run the installer on your local machine or distribute it across your VDI environment without worrying about shared computer activation constraints.
- 3. Open existing files: Launch WPS Office and immediately edit your existing Microsoft Office documents with perfect formatting.

Frequently Asked Questions
Why does Office 2024 LTSC switch to Microsoft 365 automatically?
This occurs because Office connects to licensing servers upon sign-in. If it detects that the user has an active Microsoft 365 subscription, it automatically updates the user interface and feature set to match the subscription, overriding the baseline LTSC features.
Can I block user sign-ins to prevent this license switch?
Yes, administrators can restrict sign-ins using Group Policy or by modifying the 'BlockSignIn' registry key. However, doing so will prevent users from accessing cloud-dependent features like OneDrive, SharePoint, and roaming settings.
What information do I need when reporting this issue to Microsoft?
You should prepare your Office Deployment Tool (ODT) XML configuration files, the exact Office build number, your assigned update channel, and specific details about your VDI environment and user license types.
Is Office 2024 LTSC supported in VDI environments?
Yes, Office LTSC is supported in VDI scenarios such as Remote Desktop Services (RDS). However, mixing an LTSC installation with Microsoft 365 user licenses often requires advanced Shared Computer Activation configurations to function predictably.




