Forum Discussion
Copilot for Microsoft 365 is not working on Terminalserver RDS
https://learn.microsoft.com/en-us/copilot/microsoft-365/microsoft-365-copilot-requirements
You can also just search for the phrase
Those words are not in the link you sent. When was the last time you read that?
- Andrey_ShermanMar 13, 2025Copper Contributor
It is still there:
- Copilot isn't available when using device-based licensing for Microsoft 365 Apps for enterprise.
- tylderlurdenMar 13, 2025Brass Contributor
Device-based licensing for Microsoft 365 Apps is not Shared activation. These are two different models.
Device based.
https://learn.microsoft.com/en-us/microsoft-365-apps/licensing-activation/device-based-licensing
Shared Activation.
https://learn.microsoft.com/en-us/microsoft-365-apps/licensing-activation/overview-shared-computer-activation
There is no wording that says shared activation is not supported. In fact Microsoft support (be it level 1) has stated that shared activation is supported with coPilot.
Edit1: This is there response
"Copilot for Microsoft 365 is a user-based license and requires that Microsoft 365 Apps on Windows desktop are deployed using a user-based license . Shared Computer Activation](https://learn.microsoft.com/deployoffice/overview-shared-computer-activation ) is supported. May I know if every user signing to the shared computer has prerequisites license and copilot license? "
Edit 2:
I have confirmed that "Microsoft 365 apps with shared computer activation is user-based licensing"
- JCMCN2025Mar 13, 2025Copper Contributor
Thats device-based licensing, not necessarily all forms of "shared computer licensing" -- in my case, we are using user-based shared licensing.
- tylderlurdenMar 13, 2025Brass Contributor
You are correct. office 365 shared activation in terminal servers\Citrix\RDS ect is user-based license. It does not fall under Andreys and others quote about device license. People are confused about 0365 device based and shared activation.
Additionally, I just have confirmed with another company who uses server 2022 shared desktops with Office in shared activation mode deployed with the ODT and it works. Maybee this is a 2019 thing (doubtful)? I don't have a 2022 server to stand up and test. I have read another post where someone was having the same issue with existing profiles. Newly created profiles on the same server would show copilot. Have you tried 2022 server or fresh profiles in 2019?