would pass an audit. This offering is designed to help you quickly create a RDS on IaaS deployment for testing and proof-of-concept purposes. With Windows 10 Enterprise E3 and E5 user licensing, you have the rights for remote access for up to 5 different devices (linked to the same user). The administrative overhead, however, 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. With this model, one can enjoy a faster licensing cycle due to CSP integration with other Microsoft licenses including Windows Server, SQL Server, and Office to make it easy for partners to simplify the buying process.” Read more! With [email protected]. From a Microsoft license perspective, no costs apply. For example, if they have Windows 10 Enterprise E3/E5 for their users you could have them use WVD with your Read more in our blog post about the topic! Please see the FAQ section on page below for a list of Windows and M365 licenses that allow access to [Windows 10 multi-session] WVD: https://azure.microsoft.com/en-us/pricing/details/virtual-desktop/. by In digging through the Microsoft Product Use Terms and Licensing information, I see that if we purchase RDS CALs with Software Assurance, we gain the License Mobility benefit, which allows us to deploy the licenses on a server from an Authorized Mobility Partner (i.e., Azure 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. However, license costs might apply for other (non-Microsoft) RDP suites. An alternative would be if your customers users are licensed to use Windows 10 Enterprise multi-session with Windows Virtual Desktop (WVD). I see, however, that this documentation seems to only call out RDS The RD License server. on Based on your description it is likely you need to be licensed under For billing/reporting purposes the license is still billed even if it isn't reassigned to a new user. Related resources . You will require such a VDA license every time you connect to a Windows client that is centrally hosted (i.e. 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). Please see the Services Provider Use Rights (SPUR) document for specific terms and conditions. Windows SA used to be exclusively available for licensing on a per-device basis. Customers looking for a hosted desktop solution must purchase the complete hosted solution (Azure and RDS… The web app makes them choose reason if they try to re-assign SAL Simple and transparent. Think you've mastered IT? A typical ‘extra user’ is a contractor or a colleague. What I've done in the past is to have the customer create the user accounts via web interface, then assign the RDS SAL to each user. Each month you would report the number of authorized users for the previous month and pay based on that. an iPad). Read how Microsoft is responding to the COVID-19 outbreak, and get resources to help Pricing and licensing for Windows Server 2019 Choose from three primary editions of Windows Server based on the size of your organization, as well as virtualization and datacenter requirements. In the VDI scenario, you remotely connect to a Windows Client (i.e. An audit trail of assignments/reassignments Here, we can be short. Dec 27, 2018 at 15:42 UTC. Windows “Virtual Desktop Access” (VDA) is included in Windows 10 Enterprise E3 and E5 licenses. Do you have any insight into why RDS Device CALs can't be used in this way? The reason for the questions that we are planning to license the users by per user RDS CALs (through a licensing server in Azure) however i read few articles and forums where it has been mentioned that SA (Software Assurance) additionally needs to be purchased on the top of the CALs. On the Obtain Client License Key Pack page, use the displayed telephone number to call the Microsoft Clearinghouse. In addition, each customer needs to agree to a terms and conditions Azure Remote Desktop Services – RDS Licensing – Royal Discount Remote Desktop Services The opportunities which now exist with cloud-based IT infrastructure offer a myriad of business opportunities where companies can leverage their budgets and gain much higher productivity like never before. In that case, it’s not the primary user accessing his principal device, and thus additional VDA licensing will apply to add this additional user. RDS CAL LICENSING OPTIONS With the basics out the door, let’s go one level deeper into RDS CAL licensing. In fact, I had reached out to a couple Remote Desktop Services (RDS) is the platform of choice to cost-effectively host Windows desktops and applications. You cannot use a shared user account since that would be against the terms. It is very clear that there is a nice cost saving with that model. Try the Challenge », Help in understanding the Azure portal components. Behind the scenes the AD account is created and granted access to the system. Microsoft Products and Services Agreement (MPSA) customers should use the Business Center. RDS and VDI licensing options at a glance. No matter what features you use, how often you use them, from what device you use, or how many applications/desktops you use. We are looking at setting up a Windows Remote Desktop Services system on Azure (or AWS, we haven't 100% decided yet) that will be accessed by some of our customers. reports to demonstrate compliance from customer onboard forward. Which only makes sense, give you don’t use Windows client (no VDA needed), no Windows Server (no Windows Server CAL needed) and no RDS (no RDS CAL needed). If SAL is unassigned from a person the AD user account is disabled and removed from the security group. However, you do need to make sure that your Windows (client) licensing is properly set up: in comes “Windows Virtual Desktop Access, or VDA”. I Recommend you to contact someone from Microsoft as far i know you only need the CAL from Software Assurance. Track users' IT needs, easily, and with only the features you need. You would need to have an RDS User Subscriber Access License (SAL) for each unique person that is authorized to connect, whether or not 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). You will need to purchase both a VDA license (which might be covered by Windows 10 Enterprise E3 or E5) as well as an RDS CAL. SPLA (Server Provider License Agreement): “With the SPLA, service providers and ISVs can license eligible Microsoft products on a monthly basis, during a three-year agreement term, to host software services and applications for their customers. On the same Obtain Client License Key Pack page, enter the license key pack ID, and then click Next to migrate the RDS CALs to your license server.. Click Finish to complete the RDS CAL migration process.. The software we will be providing to our customers (which happens to be our own internally developed software) is used in an environment where the computers (and software) are used by multiple people throughout the day. I work for a software and services company. In such a case, you access the Windows client by using the Remote Desktop Services setup. 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. Awingu doesn’t enable you to cut in RDS or VDI related licenses as such. is pretty high for customers who have high employee turnover. I understand how the reporting works for the SPLA (monthly, must report total number of users with access to the system), To continue this discussion, please *User* CALs, but do not see anything about RDS For small deployments, it can be deployed on the RD Session Host. spicehead-l9025 This topic has been locked by an administrator and is no longer open for commenting. Windows User Accounts). Windows SA also came with VDA built-in. is kept for monitoring and compliance purposes. My questions is what license we need to purchase to stay compliant from RDS session perspective? a shared Windows User, we have no way of knowing (or proving) how many different people used that account over a period of time. Have you seen (or heard of) any best practices on how to handle a scenario like this with the SPLA RDS SALs and a high customer employee turnover rate?