#RDS USER CAL SOFTWARE LICENSE#
#RDS USER CAL LICENSE#
#RDS USER CAL PLUS#
#RDS USER CAL WINDOWS#

#RDS USER CAL WINDOWS#

Luckily Group Policies are not needed anymoreДЄzure AD Join makes it easy to directly switch to MDM based management which allows better control of the device in a mobile environment, and reduces costs because you don't need Windows Server-based DC, no VPNs and you can control (MDM) policies regardless of the device location - and you can control all kinds of devices with a single MDM solution like Intune, not only Windows. So no local DC is required for login, thus no server is required - and then also no CAL. This sounds like a scenario where it would make more sense to use AzureAD join instead of traditional domain join for the on-premises clients. So For this scenario it does not really make sense to have an on-premises DC, it would not offer additional redundancy. If Internet connection fails, the user can't work anyway wince no Apps/files are available to them. So if internet connection works, no redundancy is needed. The question what kind of redundancy should be achieved here if there is no workload on the local server. If the users are only synced from this local AD to AzureAD via AAD Connect, but the users never access the server directly, no CAL is required, this is also stated explicitly in the licensing terms.

#RDS USER CAL LICENSE#

This also applies to scenarios where they authenticate with AD, even when users/devices are just receiving a IP address from DHCP service on Windows Server the license terms say that a CAL is required.

If user access a Windows Server they need to have a CAL. Make use of Azure Virtual Desktop for the M365 E3 User, and therefor not to renew the RDS CAL SA by switching from RDS Sessions to Azure Virtual Desktop.ДЄnd for the O365 E3 standalone User which are using Thin Clients to switch them from M365 E3 to O365 E3 Licensing within a separate Profile in EA, and confirm that for this users no Windows Server CAL or EMS is needed for the access to Windows Server in Azure with Azure Hybrid Use Benefit. We would like to recommend the customer now to:

#RDS USER CAL PLUS#

Some of the Users do only need O365 E3 instead of M365 E3 (accessing via RDS on Windows Server) via Thin Client.Д«efore moving to Azure they had to license the M365 E3 Bundle for all Users due to License requirements of Windows Server CAL and EMS (in EA) plus RDS Cal. It is not described in the PT or in other sources like Azure Hybrid Use Benefit FAQ.Д¬ustomer has moved all his Windows Server Workloads to Azure with Azure Hybrid Use Benefit and is using M365 E3 and RDS. Hi up on the initial question from customers need a Windows Server CAL plus SA, which making use of the Azure Hybrid Use Benefit? Pleae note: In this case the customer has moved all of his Windows Server Workload to Azure (no on Premise Windows Server). Hope this helps - unfortunately the whole aspect of licensing is a bit complicated Product Terms rarely does document things like 'you are not allowed' or 'your are not required', it normally only documents what is required.

by the lack of a documented requirement that you need a certain license. Often rulings are only described indirectly, e.g. how any cores you can use, that you are allowed to use Datacenter Edition even if you only have WS Standard license + SA is well described in the Product terms How Azure Hybrid Benefits can be applied, e.g. That said, it is true that the CAL requirements are not described very good in there - generally it is said that runnning Windows Server in Azure is governed by the use terms for Azure, and those Use terms do not describe any requirements for CALs when Server is deployed in Azure.

an Open License contract, MPSA or EA where the Product Terms are referenced).

#RDS USER CAL SOFTWARE LICENSE#

The official document the customer is looking for is the product terms at ДЇor his Windows Server software license + SA the use rights and Hybrid Use Benefits are documented there, and this document is part of his licensing contract (If he has Win server + SA he has e.g. It is true that Windows Server in Azure does not require Windows Server CALs (RDS CAL, AD RMS CALs are still required if using these workloads)

Rds user cal