No. Standard Windows Server 2022 CALs do not normally give a user or device the right to access Windows Server 2025.
Microsoft’s version-rights model works in the other direction. A Windows Server CAL can access the corresponding version of Windows Server and earlier versions. Therefore, a Windows Server 2025 CAL can cover access to Windows Server 2025, 2022 and supported earlier releases, while a Windows Server 2022 CAL cannot be used as the access license for Windows Server 2025.
This becomes an important upgrade-budget issue. An organization may have perfectly valid Windows Server 2022 server licenses and hundreds of 2022 User or Device CALs today. Upgrading the servers to Windows Server 2025 can create a separate CAL upgrade requirement even if the number of employees, devices and servers has not changed.
There are exceptions to the need to purchase completely new CALs, particularly where existing licenses have qualifying Software Assurance, subscription rights or CAL Suite coverage. Those entitlements should be checked before ordering additional licenses.
The basic Windows Server CAL rule is straightforward:
| Windows Server being accessed | Windows Server 2022 CAL | Windows Server 2025 CAL |
|---|---|---|
| Windows Server 2019 | Yes | Yes |
| Windows Server 2022 | Yes | Yes |
| Windows Server 2025 | No | Yes |
Microsoft’s current Windows Server 2025 licensing guidance explicitly shows that 2025 CALs can access 2025, 2022 and 2019 servers, while 2022 CALs can access 2022 and 2019 but not Windows Server 2025.
A useful rule to remember is:
New CAL → same or older server version
Old CAL → not a newer server version
That rule answers most straightforward Windows Server 2022-to-2025 migration questions.
A Windows Server license and a Windows Server CAL perform different jobs.
The server license gives the organization rights to run Windows Server according to the applicable edition, core and virtualization rules.
The CAL gives an assigned user or device access rights to Windows Server.
Purchasing or upgrading the server software therefore does not automatically convert every existing Windows Server 2022 CAL into a Windows Server 2025 CAL.
For example, suppose a business owns:
Windows Server 2022 Standard licensing for its servers.
75 Windows Server 2022 User CALs.
It upgrades its infrastructure to Windows Server 2025.
The server upgrade and the CAL question must be evaluated separately. If those 75 employees will access Windows Server 2025 and the organization has no qualifying new-version entitlement, the old 2022 CALs are not enough for access to the new 2025 server software. Microsoft requires the appropriate corresponding-version CAL for users or devices accessing the server directly or indirectly.
Yes.
This backward compatibility is particularly useful in environments that cannot upgrade every server at the same time.
Imagine an organization operating:
Two Windows Server 2025 domain controllers.
One Windows Server 2025 file server.
Two Windows Server 2022 application servers.
If an employee has the appropriate Windows Server 2025 User CAL, that CAL can cover the user’s Windows Server access across both the 2025 and 2022 systems.
The organization does not need a separate 2022 CAL for that same user simply because an older application server still exists.
The newer CAL already provides access rights to the earlier server version.
This is one reason upgrading CALs can simplify a mixed-version estate rather than creating separate CAL inventories for every Windows Server generation.
Not necessarily.
The deciding factor is which users or devices access Windows Server 2025.
Suppose a company has 100 employees with Windows Server 2022 User CALs.
The company upgrades one department’s application server to Windows Server 2025, but only 30 employees access that server. The remaining 70 users continue accessing only Windows Server 2022 systems.
At a basic version-rights level, the 70 users who remain entirely on the 2022 environment can continue to rely on valid Windows Server 2022 CAL coverage.
The 30 people accessing Windows Server 2025 need appropriate Windows Server 2025 access rights, whether through 2025 CALs, qualifying upgraded CAL entitlement or another valid CAL-equivalent right.
If those 30 later need access to a 2022 server as well, their Windows Server 2025 CALs can cover both versions.
This makes migration planning more precise than assuming every CAL in the company must be replaced on the first day one Windows Server 2025 machine is installed.
Consider a company with:
Four Windows Server 2022 servers.
60 employees.
60 Windows Server 2022 User CALs.
The company upgrades all four servers to Windows Server 2025, and all 60 employees continue accessing those servers.
If the existing 2022 CALs do not carry qualifying new-version rights, the organization now needs Windows Server 2025 access rights for those 60 users.
The old 2022 CALs have not become invalid. They can still provide access to Windows Server 2022 and earlier according to their terms.
The problem is that the target server version has changed.
Because every employee now accesses Windows Server 2025, every relevant employee needs CAL coverage that permits Windows Server 2025 access.
Now assume the same business takes a phased approach.
It has:
Two Windows Server 2025 servers.
Two Windows Server 2022 servers.
Twenty users access the new 2025 application.
Forty other employees continue using only the old 2022 environment.
In this situation, the CAL upgrade can potentially follow the migration population rather than the physical server count.
The 20 users who access Windows Server 2025 need 2025-compatible access rights.
The remaining 40 users can continue using their valid 2022 CALs while they remain restricted to the 2022 environment.
When another department migrates to Windows Server 2025, its CAL requirements should be reviewed at the same point.
This staged method can make CAL spending follow the actual migration rather than forcing an unnecessarily broad purchase before every user needs 2025 access.
Suppose one employee needs access to:
A Windows Server 2025 domain environment.
A Windows Server 2025 file server.
A legacy Windows Server 2022 application server.
You do not need a 2025 CAL plus another 2022 CAL for that employee simply because two Windows Server versions are present.
An appropriate Windows Server 2025 User CAL provides access to the corresponding 2025 version and permitted earlier versions.
The highest Windows Server version the user accesses is therefore a useful starting point when reviewing CAL version requirements.
For this user, that version is Windows Server 2025.
This scenario requires separating the server license entitlement from the software actually being accessed.
Microsoft’s Windows Server 2025 licensing guidance states that if an organization uses an earlier server version under applicable downgrade rights, CALs corresponding to that earlier server version can also be used for access to that earlier version.
For example, suppose an organization acquires Windows Server 2025 server licensing but, for application-compatibility reasons, deploys Windows Server 2022 under valid downgrade rights.
Users accessing that running Windows Server 2022 instance may be covered with the appropriate Windows Server 2022 CALs.
Owning a 2025 server license does not by itself mean every user must immediately use a 2025 CAL when the actual server software they access remains Windows Server 2022.
But that changes when the running server is upgraded to Windows Server 2025.
At that point, the CAL version requirement changes with it.
This distinction is worth emphasizing because it causes purchasing mistakes.
Suppose your organization owns Windows Server 2025 licensing.
You initially deploy Windows Server 2022 because an application vendor has not yet certified its product on 2025.
Existing Windows Server 2022 CALs can potentially remain appropriate while users access the 2022 server.
Six months later, the application vendor certifies Windows Server 2025, and you upgrade the operating system.
The fact that the server originally ran under downgrade rights does not make the 2022 CALs valid for accessing the new 2025 installation.
Once users are accessing Windows Server 2025, the access licensing needs to support 2025.
The server-version decision and CAL-version decision therefore need to be revisited together during the final upgrade.
This is one of the most important checks to perform before purchasing replacement CALs.
Microsoft Software Assurance includes New Version Rights. A license covered by active Software Assurance can generally be upgraded to a newer version released while that Software Assurance coverage is active. Microsoft specifically identifies new-version rights as a Software Assurance benefit for products in the server pool.
Therefore, an organization that originally acquired Windows Server 2022 CALs with qualifying Software Assurance may already have rights to the Windows Server 2025 CAL version if its coverage remained active through the relevant release entitlement period.
That is different from an ordinary perpetual 2022 CAL with no current upgrade entitlement.
Before buying new CALs, verify:
Do not assume Software Assurance exists because the organization has used volume licensing in the past.
No, not when the RDS Session Host itself is Windows Server 2025.
Remote Desktop Services CALs have their own version compatibility rules.
Microsoft’s current compatibility matrix is explicit.
The Remote Desktop Session Host role is the part of an RDS deployment that hosts Windows-based applications or complete session desktops for users.
Multiple users can establish separate sessions against the same Session Host infrastructure.
This is very different from an administrator occasionally connecting to a server to configure it.
If the business objective is to provide employees with ongoing remote application or desktop sessions, RDS CAL planning should happen before the environment enters production.
Microsoft’s licensing system uses an RD Licensing server to install, issue and track the appropriate RDS CALs used by Session Hosts.
| RD Session Host version | 2022 RDS CAL | 2025 RDS CAL |
|---|---|---|
| Windows Server 2022 | Yes | Yes |
| Windows Server 2025 | No | Yes |
A Windows Server 2022 RDS CAL therefore cannot license access to an RD Session Host running Windows Server 2025.
A Windows Server 2025 RDS CAL can be used with Windows Server 2025 and compatible earlier Session Host versions.
This follows the same basic direction as ordinary Windows Server CAL version rights: newer CALs can work backward, while older CALs cannot be used to access newer server versions.
An RDS migration can require checking two different CAL layers.
For a normal internal-user Remote Desktop Services deployment, the organization generally needs:
Windows Server base CAL coverage
plus:
Windows Server RDS CAL coverage
Suppose a company upgrades its RD Session Host from Windows Server 2022 to Windows Server 2025.
It has:
50 Windows Server 2022 User CALs.
50 Windows Server 2022 RDS User CALs.
Without another qualifying entitlement, both layers need attention.
The base 2022 Windows Server CALs do not normally cover access to Windows Server 2025.
The 2022 RDS CALs also cannot be used for a Windows Server 2025 RD Session Host.
Upgrading only the RDS CALs while ignoring the base access requirement does not complete the licensing review.
There is an additional operational consideration for RDS.
A Windows Server 2025 RDS CAL must be installed on an RD Licensing server running a compatible Windows Server version.
Microsoft’s current matrix shows that a Windows Server 2025 RD Licensing server can host 2025 and earlier RDS CAL versions. A Windows Server 2022 RD Licensing server cannot host Windows Server 2025 RDS CALs.
That means an RDS migration can involve three separate version checks:
The RD Session Host version.
The RDS CAL version.
The RD Licensing server version.
A company that upgrades its Session Hosts to Windows Server 2025 but leaves its licensing server and RDS CAL inventory at 2022 has not completed the RDS licensing migration.
Yes.
A Windows Server 2025 RDS CAL can provide access to a Windows Server 2022 Session Host because Microsoft permits newer RDS CALs to access earlier supported Session Host versions.
There is an important operational detail, however.
If the RDS CAL itself is version 2025, the RD Licensing server needs to be able to host that 2025 CAL. A Windows Server 2022 licensing server cannot install 2025 RDS CALs, even though a Windows Server 2022 Session Host can accept users covered by 2025 RDS CAL rights when those CALs are served from a compatible licensing server.
This difference between the Session Host version and license server version is easy to miss.
No.
The Windows Server CAL version requirement should not be confused with the Standard-versus-Datacenter edition choice.
Both Windows Server 2025 Standard and Windows Server 2025 Datacenter use Windows Server access licensing under Microsoft’s applicable Per Core/CAL model.
Moving from Windows Server 2022 Standard to Windows Server 2025 Datacenter does not make the old 2022 CAL version valid for access to Windows Server 2025.
Likewise, choosing Datacenter because you need unlimited virtualization rights does not eliminate the ordinary CAL requirement.
Edition rights, server core licensing and CAL version rights are separate parts of the licensing model.
Yes.
Whether you license access by User CAL or Device CAL, the version rule remains the same.
A Windows Server 2025 User CAL allows the assigned user to access the corresponding Windows Server version and permitted earlier versions.
A Windows Server 2025 Device CAL provides the corresponding rights to the licensed device.
A Windows Server 2022 User or Device CAL does not become a Windows Server 2025 CAL merely because the organization upgrades the server. Microsoft’s Product Terms explicitly apply the corresponding-version-or-earlier principle to both User and Device CALs.
The User-versus-Device question determines what you license.
The 2022-versus-2025 question determines which server version that CAL can access.
Consider an organization with 80 employees.
The infrastructure contains:
Two Windows Server 2022 application servers.
One Windows Server 2025 domain controller.
One Windows Server 2025 file server.
Thirty employees access only the old application servers.
Fifty employees access both the 2025 servers and the old 2022 applications.
A sensible version analysis is:
The 30 users restricted to Windows Server 2022 can continue using valid Windows Server 2022 CALs.
The 50 users accessing Windows Server 2025 need Windows Server 2025-compatible access rights.
Those same 2025 CALs can also cover those 50 users when they access the older 2022 application servers.
The organization therefore does not necessarily need to upgrade all 80 CALs on day one unless all 80 users will access Windows Server 2025.
But administrators need technical controls and accurate records to ensure users licensed only for 2022 are not also accessing 2025 server resources.
Organizations sometimes focus only on the application server being upgraded.
That can miss other Windows Server access.
Suppose you leave your business application on Windows Server 2022 but upgrade your Active Directory domain controllers and other Windows Server infrastructure to 2025.
The fact that the application itself remains on 2022 does not automatically mean every employee can remain on 2022 CALs.
You need to evaluate which users or devices directly or indirectly access the new Windows Server 2025 infrastructure and apply the corresponding CAL rules.
This is why a migration inventory should identify all Windows Server 2025 instances being accessed, not merely the server hosting the most visible business application.
One frequent mistake is assuming that CALs are permanently version-neutral. They are not. Microsoft gives CALs rights to the corresponding server version and earlier versions, not future versions.
Another is budgeting only for the Windows Server 2025 core licenses. An infrastructure proposal can correctly calculate every physical CPU core while still overlook the required access-license upgrade.
A third mistake is replacing every CAL automatically without checking active Software Assurance, CAL Suites, subscription rights or other valid entitlement that may already provide access to the new version.
RDS creates another common problem. Organizations upgrade the Session Host to 2025 but retain 2022 RDS CALs. The older RDS CALs cannot cover a Windows Server 2025 Session Host.
Finally, some organizations replace 2022 CALs for users who will continue accessing only Windows Server 2022. In a phased migration, the CAL upgrade can often be planned around actual 2025 access rather than simply the company’s total employee count.
Before moving production workloads to Windows Server 2025, check:
That review should happen before the production upgrade, not after users begin connecting to the new servers.
For ordinary Windows Server access, Windows Server 2022 CALs do not provide access rights to Windows Server 2025.
You generally need Windows Server 2025 CALs, qualifying CAL-equivalent rights, or a valid upgrade entitlement such as applicable new-version rights from Software Assurance or subscription licensing.
The compatibility direction is:
Windows Server 2025 CAL → Windows Server 2025, 2022 and permitted earlier versions
Windows Server 2022 CAL → Windows Server 2022 and permitted earlier versions, but not Windows Server 2025.
RDS follows the same version direction. Windows Server 2022 RDS CALs cannot cover a Windows Server 2025 Session Host, while 2025 RDS CALs can cover compatible 2025 and earlier Session Hosts.
If you are planning a Windows Server 2022-to-2025 migration, do not treat CALs as an afterthought. Inventory who and what will access the new servers, check existing Software Assurance or subscription entitlements, review RDS separately, and then upgrade only the access licenses that the new environment actually requires.
Learn when Windows Server 2025 RDS CALs are required, User vs Device licensing, base CAL requirements, admin exceptions, and version compatibility.
Learn how Windows Server 2025 CAL licensing works, when to choose User or Device CALs, version compatibility, external access, and RDS requirements.
Calculate Windows Server 2025 core licensing for 16-, 24- and 32-core hosts, Standard VM stacking, Datacenter, and real server scenarios.