Blog
Exchange Server 2019 Licensing and CAL Planning
Exchange Server 2019 licensing has two separate parts: the Exchange Server licence and the Client Access Licences (CALs) for people or devices that access the server. Treating these as one product is a common cause of incomplete purchasing decisions.
This Exchange Server licensing guide focuses on Exchange access rights. It does not replace the separate licensing work needed for Windows Server, Remote Desktop Services (RDS), SQL Server, SharePoint, backup software, or endpoint products. Those products may have their own server licences, CALs, subscriptions, or usage rules.
Start with the Exchange Server licence
An on-premises Exchange deployment needs a licence for the Exchange Server software as well as the required CALs. The server licence covers the Exchange software running in the organisation’s environment. It does not automatically give every employee, consultant, application, or device the right to access mailboxes and other Exchange services.
Exchange Server Standard 2019 is intended for organisations that want to operate their messaging environment on infrastructure they control. It provides the platform for business email, calendars, contacts, tasks, meeting scheduling, shared calendars, room mailboxes, distribution groups, and shared mailboxes.
When planning the server side, record the following information for every deployment:
- How many Exchange Server instances will run in production?
- Will there be separate test, development, disaster recovery, or migration environments?
- Which servers will host mailbox databases and which will provide other Exchange roles?
- Will the deployment be physical, virtual, or a combination?
- Is the organisation keeping Exchange on premises or using it temporarily during a migration?
- Does the planned design require functionality or capacity associated with another Exchange edition or licence type?
Do not assume that one server key covers every copy of the software in a multi-server or multi-environment design. Review the Microsoft licence terms and your agreement before counting test, standby, or recovery installations.
Exchange Server edition and access licensing
The server edition and the CAL edition work together. Exchange Server Standard 2019 is normally paired with Exchange Server 2019 Standard CALs. A Standard CAL gives the licensed user or device access rights for the standard Exchange functionality covered by that CAL.
Some Exchange deployments may require additional functionality or a different CAL level. If administrators need advanced compliance, archiving, unified messaging, or other specialised capabilities, they should verify the applicable Microsoft licensing terms rather than assume that a Standard CAL includes everything available in the product family.
| Item | What it covers | Cosa non sostituisce |
|---|---|---|
| Exchange Server Standard 2019 | The Exchange Server software licence for the licensed deployment | It does not replace Exchange CALs for accessing users or devices |
| Exchange Server 2019 Standard CAL | Access rights for one licensed user or one licensed device | It is not a Windows Server CAL, RDS CAL, SQL Server licence, or SharePoint licence |
| Windows Server licensing | The operating system and its own access requirements | It does not provide Exchange access rights |
| RDS licensing | Remote Desktop Services access where RDS is used | It does not provide Exchange mailbox access |
This distinction matters in a virtualised environment. A Windows Server licence and Windows Server CALs may be needed for the host or guest operating system, while Exchange Server licensing and Exchange CALs cover the messaging software. One set of CALs does not substitute for the other.
Choosing an Exchange Server 2019 CAL
The main choice for a Standard CAL is whether to license users or devices. The two models solve different access patterns.
| CAL model | Come funziona | Usually suitable for |
|---|---|---|
| User CAL | One named person may access Exchange from multiple devices | Employees using a desktop, laptop, smartphone, tablet, and remote workstation |
| Device CAL | One device may be used by multiple people | Shared workstations, shift environments, reception desks, or common terminals |
A User CAL is normally easier to manage when staff have several devices. For example, an engineer who uses Outlook on a laptop, a mobile phone, and a home computer is generally counted as one user for the User CAL decision, subject to the applicable licence terms.
A Device CAL can be more practical where many people use the same controlled workstation and do not need individual access across multiple devices. A production floor terminal, warehouse workstation, or shared reception computer may fit this pattern.
Do not choose the model based only on the number of mailboxes. Count the actual access pattern. A small company with ten employees and four devices per person may find User CALs simpler. A call centre with many operators using a limited pool of workstations may need to examine Device CALs instead.
Planning users, shared mailboxes, and service access
The most useful planning document is an access inventory, not just a list of email addresses. Create a row for every person, shared access pattern, device group, and application that connects to Exchange.
For each entry, record:
- The person or device that accesses Exchange.
- Whether the access is through Outlook, a mobile device, a browser, an application, or an administrative tool.
- Whether the person uses several devices or several people share one device.
- Whether the account is a normal user mailbox, a shared mailbox, a room mailbox, or an application identity.
- Whether the access is permanent, temporary, or limited to migration and testing.
- Which CAL type is being assigned and who is responsible for maintaining the record.
Shared mailboxes need particular care. A shared mailbox is a functional address such as sales@example or support@example; it is not automatically a substitute for licensing the people who access it. If five employees open and use a shared mailbox, analyse the access rights for those five employees or their devices. Do not simply count the shared mailbox name as one employee.
Room mailboxes and equipment mailboxes also need to be considered in the design, but their existence alone should not be used as the only basis for counting CALs. The correct result depends on how the environment is configured and who or what accesses Exchange. For unusual cases, confirm the interpretation with Microsoft licensing specialists or your licensing agreement.
Applications and service accounts can create another gap. A ticketing system, multifunction printer, monitoring platform, archive product, or line-of-business application may connect to Exchange using a service identity. Document this access and check the licence terms instead of assuming that a non-human account is free of licensing requirements.
Standard licensing for small and medium deployments
For a small or medium organisation, the basic purchasing pattern is straightforward:
- Select the Exchange Server Standard 2019 server licence for the planned deployment.
- Choose User CALs or Device CALs based on how people access the system.
- Count the required CALs using the selected model.
- Add separate licensing for Windows Server and any other Microsoft products in the solution.
- Keep an assignment record so that staff changes, device replacements, and contractors can be reviewed.
Some buyers prefer a combined Exchange Server Standard 2019 package with 10 Exchange Server 2019 Standard CALs. This can simplify an initial purchase when the organisation needs the server licence and a small number of CALs together. The CAL type still matters: the package can be planned with User or Device CALs, so the buyer should decide which model matches the real access pattern.
If the organisation already owns the Exchange Server licence, purchasing additional Standard CALs separately may be more appropriate. Conversely, buying only CALs does not provide the Exchange Server software licence. Before ordering, compare the existing licence inventory with the intended number of server instances and accesses.
Buying individual CALs or CAL bundles
Individual CALs are useful when an existing deployment is growing gradually or when a managed service provider is onboarding one customer at a time. They also make it easier to maintain separate User and Device counts when the environment has mixed access patterns.
A server-and-CAL bundle is convenient for a new, small deployment because the core Exchange licence and an initial group of CALs are purchased together. It is still important to check the quantity, CAL type, language, licence version, and delivery method shown on the product page.
| Situazione | Practical choice | Planning check |
|---|---|---|
| New small organisation | Exchange Server Standard 2019 with an initial CAL bundle | Confirm whether User or Device CALs match the workplace |
| Existing server, more employees added | Additional Exchange Server 2019 Standard CALs | Update the user or device count before ordering |
| Shared workstations | Consider Device CALs | Count the devices and check whether access is truly shared |
| Mobile and multi-device workforce | Consider User CALs | Count people rather than every phone, laptop, or tablet |
| Mixed environment | Use a documented User and Device strategy where permitted | Keep separate assignment records and confirm the licence terms |
Migration and support planning questions
Exchange Server 2019 reached the end of its Microsoft support lifecycle on October 14, 2025. In 2026, that date should be part of every buying decision. A licence purchase does not restore vendor support or turn an end-of-support deployment into a supported platform.
Before starting a new Exchange Server 2019 project, ask:
- Is this a short-term migration or recovery stage, or a new long-term deployment?
- What is the target messaging platform after the transition?
- How will mailboxes, calendars, contacts, permissions, mobile access, and shared mailboxes be moved?
- Which identities and applications connect to Exchange today?
- Will the organisation need a different Microsoft product or service for the future state?
- How will administrators preserve records of licences and access during the migration?
For an existing installation, review the support position, security plan, backup and recovery process, and migration timetable with the organisation’s Microsoft adviser. Do not buy extra CALs solely to postpone an architectural decision if the business is already planning to move away from Exchange Server 2019.
Exchange Server licensing checklist
- List each Exchange Server instance and environment.
- Confirm that Exchange Server Standard 2019 is suitable for the planned functionality.
- Separate Exchange licensing from Windows Server, RDS, SQL Server, and SharePoint licensing.
- Choose User CALs for people with multiple devices or Device CALs for shared devices, based on the real usage pattern.
- Count employees, contractors, devices, shared mailbox users, and application access carefully.
- Record temporary migration, testing, and recovery access separately.
- Check the Microsoft licence terms for unusual service-account, application, or shared-access scenarios.
- Include the Exchange Server 2019 end-of-support date in the migration and budget plan.
- Keep purchase records and CAL assignments available for internal reviews.
Genuine Exchange Server Standard 2019 licences and Exchange Server 2019 Standard CALs are available from KEYFORREST with instant electronic delivery. Review the current product page to confirm the edition, CAL type, quantity, and licence details before purchase.
Domande frequenti
Do Exchange Server 2019 CALs include Windows Server CALs?
No. An Exchange CAL covers access to Exchange according to its licence terms. Windows Server, RDS, SQL Server, and SharePoint have separate licensing requirements where applicable.
Should I buy a User CAL or a Device CAL?
Choose a User CAL when one person uses several devices. Choose a Device CAL when many people share a limited number of devices. Review the actual access pattern rather than only the mailbox count.
Does every shared mailbox need its own Exchange CAL?
Do not treat the shared mailbox name as a person automatically. Review the people, devices, and applications accessing it, then confirm unusual cases against the applicable Microsoft licensing terms.
Can I buy Exchange CALs without the server licence?
CALs provide access rights but do not provide the Exchange Server software licence. A complete on-premises deployment needs the appropriate server licence as well as the required CALs.
Is Exchange Server 2019 still supported?
Microsoft support for Exchange Server 2019 ended on October 14, 2025. Organisations buying or extending a deployment should include migration and support planning in the decision.