Why do Teams and Outlook keep asking users to sign in on our RDS server?

November 16, 2026 5 answers
Asked by 6h+marbletoggle_291

Most users on a standalone Windows Remote Desktop Services server get recurring Microsoft 365 sign-in prompts, and a few see them almost daily. Teams and Outlook can also lose connectivity.

Rebuilding profiles, reinstalling Office, clearing Teams data and rebooting have not fixed it. Users have valid licenses and log off daily. The server has free disk space, but Windows is not activated. What should we check next?

Answers

t.934!kavlo

Check Shared Computer Activation before reinstalling Office again. On an RDS host, Microsoft 365 Apps needs shared computer activation enabled, and each user needs a license that supports it. A valid Microsoft 365 license by itself does not confirm that.

Check SharedComputerLicensing under HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration. It should be set to 1. Also check the deployment configuration used for the reinstall, so you know whether the setting was applied rather than assuming it survived.

6h+marbletoggle_291:

Office has already been reinstalled without a lasting fix, but the activation setting is worth checking separately.

Reply to this answer
r.439~fusepocket

Start with Entra sign-in logs for an affected user at the time of a prompt. Check the failure details and any Conditional Access policies applied, especially sign-in frequency. The prompt may point in that direction, but it is not enough on its own to prove a policy is responsible.

Compare a frequently affected user with one who rarely sees it. If the logs show a policy requiring reauthentication, review that policy before changing anything on the server.

Reply to this answer
z.416+plaidcompass

Take a close look at what happens to the user profile at logoff and logon. Office and Windows authentication depend on per-user cached data, so a cleanup task, policy or profile persistence problem could explain why a fresh profile works only temporarily.

Check scheduled tasks, Group Policy and any profile management or cleanup tools. Rebuilding the profile won't fix a process that removes or fails to retain the data afterward.

6h+marbletoggle_291:

There are no known cleanup scripts, but checking logoff tasks and Group Policy makes sense.

Reply to this answer
Tervilo-7q

Since this is isolated to one server, check its network path too. DNS and domain connectivity are worth testing, along with firewall, proxy or filtering rules that might block Microsoft 365 authentication or token refresh traffic.

Compare the server's connectivity with an unaffected environment and look for blocked requests around the time users are prompted.

Reply to this answer
_g32+ticketladle.6

I'd check the server's Entra join status as well as Windows activation. Get Windows properly activated, but don't assume that alone explains the sign-in loop. The sign-in logs and activation settings should give you better evidence about what's actually failing.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions