-->
![Licensing Licensing](/uploads/1/2/5/8/125848239/201549238.png)
-->
Applies to: Windows Server (Semi-Annual Channel), Windows Server 2019, Windows Server 2016
SharePoint Online is licensed on a per-user basis. You can purchase SharePoint Online as a standalone plan or included as part of Office 365 plans. Learn more.Licensing details are available here.; For On-Premises, intranet sites are licensed using a Server/CAL (Client Access License) model.SharePoint Server 2019 is required for each running instance of the software, and CALs are required for.
Each user and device that connects to a Remote Desktop Session host needs a client access licenses (CAL). You use RD Licensing to install, issue, and track RDS CALs.
When a user or a device connects to an RD Session Host server, the RD Session Host server determines if an RDS CAL is needed. The RD Session Host server then requests an RDS CAL from the Remote Desktop license server. If an appropriate RDS CAL is available from a license server, the RDS CAL is issued to the client, and the client is able to connect to the RD Session Host server and from there to the desktop or apps they're trying to use.
Although there is a licensing grace period during which no license server is required, after the grace period ends, clients must have a valid RDS CAL issued by a license server before they can log on to an RD Session Host server.
Use the following information to learn about how client access licensing works in Remote Desktop Services and to deploy and manage your licenses:
- License your RDS deployment with client access licenses (CALs)
Understanding the CALs model
There are two types of CALs:
- RDS Per Device CALs
- RDS Per User CALs
The following table outlines the differences between the two types of CALs:
Per Device | Per User |
---|---|
CALs are physically assigned to each device. | CALs are assigned to a user in Active Directory. |
CALs are tracked by the license server. | CALs are tracked by the license server. |
CALs can be tracked regardless of Active Directory membership. | CALs cannot be tracked within a workgroup. |
You can revoke up to 20% of CALs. | You cannot revoke any CALs. |
Temporary CALs are valid for 52–89 days. | Temporary CALs are not available. |
CALs cannot be overallocated. | CALs can be overallocated (in breach of the Remote Desktop licensing agreement). |
![Licensing Licensing](/uploads/1/2/5/8/125848239/201549238.png)
When you use the Per Device model, a temporary license is issued the first time a device connects to the RD Session Host. The second time that device connects, as long as the license server is activated and there are available CALs, the license server issues a permanent RDS Per Device CAL.
When you use the Per User model, licensing is not enforced and each user is granted a license to connect to an RD Session Host from any number of devices. The license server issues licenses from the available CAL pool or the Over-Used CAL pool. It's your responsibility to ensure that all of your users have a valid license and zero Over-Used CALs—otherwise, you're in violation of the Remote Desktop Services license terms.
To ensure you are in compliance with the Remote Destkop Services license terms, track the number of RDS Per User CALs used in your organization and be sure to have a enough Per User CALs installed on the license server for all of your users.
You can use the Remote Desktop Licensing Manager to track and generate reports on RDS Per User CALs.
Note about CAL versions
The CAL used by users or devices must correspond to the version of Windows Server that the user or device is connecting to. You can't use older CALs to access newer Windows Server versions, but you can use newer CALs to access earlier versions of Windows Server.
The following table shows the CALs that are compatible on RD Session Hosts and RD Virtualization Hosts.
2008 R2 and earlier CAL | 2012 CAL | 2016 CAL | 2019 CAL | |
---|---|---|---|---|
2008, 2008 R2 license server | Yes | No | No | No |
2012 license server | Yes | Yes | No | No |
2012 R2 license server | Yes | Yes | No | No |
2016 license server | Yes | Yes | Yes | No |
2019 license server | Yes | Yes | Yes | Yes |
Any RDS license server can host licenses from all previous versions of Remote Desktop Services and the current version of Remote Desktop Services. For example, a Windows Server 2016 RDS license server can host licenses from all previous versions of RDS, while a Windows Server 2012 R2 RDS license server can only host licenses up to Windows Server 2012 R2.
![Server Server](/uploads/1/2/5/8/125848239/540555922.jpg)
Important
The Microsoft Teams admin center is gradually replacing the Skype for Business admin center, and we're migrating Teams settings to it from the Microsoft 365 admin center. If a setting has been migrated, you'll see a notification and then be directed to the setting's location in the Teams admin center. For more information, see Manage Teams during the transition to the Teams admin center.
The following Office 365 subscriptions enable users for Teams.
Small Business Plans | Enterprise Plans | Education Plans | Developer Plans |
---|---|---|---|
Office 365 Business Essentials | Office 365 Enterprise E1 | Office 365 Education | Office 365 Developer |
Office 365 Business Premium | Office 365 Enterprise E3 | Office 365 Education Plus | |
Microsoft 365 for business | Office 365 Enterprise E4 (retired) | Office 365 Education E3 (retired) | |
Office 365 Enterprise E5 | Office 365 Education E5 | ||
Office 365 Enterprise F1 |
For more information about getting Teams, check out How do I get access to Microsoft Teams?
Note
Teams is also available for non-profit organizations. Teams will begin rolling out for the US Government Cloud Community (GCC) on July 17 and be available for all eligible customers by the end of August 2018. We are working to bring Microsoft Teams to the other US government clouds (GCC High and DoD) coming soon. Read more in the Microsoft Teams blog here.
Note
Starting August 2019, all new Office 365 customers will be onboarded to Teams and will not have access to Skype for Business Online. Tenants that are already using Skype for Business Online will be able to continue doing so (including provisioning new users) until they complete their transition to Teams. To learn more, see Microsoft Teams now the primary client for meetings and calling in Office 365.
Note
If Skype for Business Online is listed in apps for the selected license, do not remove it. If it's listed and is removed, Teams user setup will not complete successfully.
In terms of Teams core functionalities, there are no differences between the Office 365 subscriptions. The availability of the compliance capabilities does rely on the correct subscription level. To learn more, read Overview of security and compliance in Teams. For a detailed list of features available in each subscription, see the Office 365 Platform Service Description.
Cloud voice features: For Audio Conferencing, your organization will need to buy and assign an Audio Conferencing license to each user who will be setting up dial-in meetings. For Calling Plans, each user will need a Phone System plus a Domestic or Domestic and International Calling Plan. To learn more, see Microsoft Teams add-on licensing.
All supported subscription plans are eligible for access to the Teams web client, desktop clients, and mobile apps.
Teams isn't available as a standalone service.
Tip
To manage user-level licensing, see Manage user access to Microsoft Teams.