Fix Microsoft 365 Activation and Device Registration Errors on Windows Server 2019
Question details
Resolve Microsoft 365 Apps activation failures caused by a device-registration error on a Windows Server 2019 Remote Desktop Services host.

- Product
- Microsoft 365 Apps
- Device & OS
- Windows Server 2019
- Scenario
- Users are signing in to Microsoft 365 Apps on an RDS host in an Azure environment that also uses local Active Directory.
- Observed behavior
- Sign-in fails with a device-registration error, preventing Microsoft 365 Apps from activating.
Record the exact error message and confirm with your administrator that the users have eligible Microsoft 365 licenses and that shared computer activation is configured for the RDS host. Check Microsoft's current support requirements for Windows Server 2019; historical support does not establish current support status.
Use app-only sign-in instead of enrolling the RDS host
Try this first when the error appears during the prompt to let your organization manage the device.
Signing in to an Office application and registering or enrolling the Windows device are separate actions. App-only sign-in can avoid the device-management step, but it does not override a tenant policy that requires a managed or compliant device.
Open Word or Excel in the affected user's RDS session. Select Sign in, or go to File > Account > Sign in, and enter the user's organizational account credentials.
After entering the password, look for the option labeled Allow my organization to manage my device. Clear that checkbox if it appears.
Select This app only or No, sign in to this app only, depending on the wording shown. Finish sign-in without choosing an option that registers or enrolls the entire server.
Return to File > Account and review Product Information. If activation still fails, record the new error and ask your administrator whether Conditional Access requires device registration or compliance.

Check whether a proxy or firewall blocks activation traffic
Use this when app-only sign-in still fails or the sign-in dialog cannot reach Microsoft services.
Test activation with a fresh Windows user profile
Use this to determine whether the failure is tied to the original profile or a built-in local administrator session.
Keep working on Office documents with WPS Office
WPS Office is a free, lightweight alternative for everyday document, spreadsheet, and presentation work. Its familiar interface and Microsoft Office format compatibility make migration straightforward. It does not repair Microsoft 365 activation or device registration; confirm deployment support and licensing suitability before using it on a shared Windows Server RDS host.

Frequently Asked Questions
Where do I choose This app only during Microsoft 365 sign-in?
Open Word or Excel and select File > Account > Sign in. After entering your credentials, look for the device-management prompt. Clear Allow my organization to manage my device and select This app only or No, sign in to this app only, if that option is available.
Will app-only sign-in satisfy a managed-device requirement?
No. App-only sign-in avoids enrolling the device during that sign-in flow, but it does not satisfy a Conditional Access policy requiring device compliance or a particular join state. Your administrator must review the policy and the intended RDS configuration.
Do RDS users need shared computer activation?
For Microsoft 365 Apps on a shared RDS host, the administrator should configure shared computer activation and verify that each user has an eligible license. App-only sign-in does not replace these licensing and deployment requirements.
Why test a new user profile instead of using the local Administrator account?
A fresh standard-user profile helps distinguish a profile-specific issue from a host-wide activation problem. Sign in to a separate authorized RDS account and test activation through File > Account; do not delete the original profile just to run this check.
Is Microsoft 365 Apps still supported on Windows Server 2019?
Microsoft 365 Apps was historically supported on Windows Server 2019, but that support ended on October 14, 2025. Continued security updates do not mean the configuration remains fully supported. Check Microsoft's current lifecycle guidance and plan migration to a supported platform.




