a shared Windows User, we have no way of knowing (or proving) how many different people used that account over a period of time. This would give us a trackable and auditable SAL count per month (it could never be more than X per month, as there are only X unique Windows User Accounts with access to the system). Windows SA used to be exclusively available for licensing on a per-device basis. An alternative would be if your customers users are licensed to use Windows 10 Enterprise multi-session with Windows Virtual Desktop (WVD). You will not require any additional VDA licensing if you remotely connect from a Windows device to your primary desktop/laptop that is connected to the company network. Microsoft has introduced Windows Virtual Desktop on Azure, which is in public beta since March 2019. You will also require VDA licensing if you remotely connect to a Windows desktop that is not your primary device (let’s say, not your main desktop that is connected at work). Next to the above license models, special pricing exists for organizations that are non-profit, educational, etc. I have a client who is looking at moving to Azure. document so they understand that each unique person requires a SAL, no sharing, no re-assignment of SALs within same month except for case where employee is terminated/absent or similar. “Previously, your customers needed to bring their own RDS CAL with SA to support your RDS deployment in the customers’ environment. I had also considered using a "shared" Windows User/Login for all the end users of a particular shared computer, but I fear that it won't be easy to determine how many user to report per month (not to mention if/when an audit occurs). The activity by the customer admin in the web interface directly feeds into billing so that the customer is billed for the number of RDS SALs that they have assigned during the month. You cannot use a shared user account since that would be against the terms. Read more in our blog post about the topic! I also read about SALs (Remote Desktop Services Subscriber Access Licences) but if I'm correct that applies only on a service provider's RDS. A typical ‘extra user’ is a contractor or a colleague. A typical scenario is that the desktop is left powered on in the office at night. Given Windows E3 and E5 basically include the Software Assurance, you have the right to upgrade (or downgrade in theory) at any time. One follow on question:  Let's say we do move forward with the SPLA program for the RDS User CALs (well, SALs in this case). If this was for your employees, you would use RDS User CAL with Software Assurance (SA) for each unique person that will connect to your RDS environment in Azure/AWS. *User* CALs, but do not see anything about RDS