Fix it now
The definition decides this, not the arithmetic. Microsoft’s Product Terms define external users as people who are not your employees, not contractors or agents typically working for you more than 30 hours a week, and not contractors or agents typically on your site every working day. Everyone else needs a CAL. One External Connector then covers a whole server for any number of genuine external users.
- Buy nothing for a public website with no sign-in. The Product Terms exempt web workloads from CAL requirements.
- Buy user or device CALs for a small, known and stable group of external partners. They are cheaper than a connector at low counts and simpler to administer.
- Buy a Windows Server External Connector when the external population is large, unknown or growing – a customer portal, a public authenticated service.
- Buy one External Connector per physical server that external users access. It covers any number of operating system environments on that server, but it does not travel to another server.
- Buy ordinary CALs for on-site contractors. They fall inside the employee-equivalent definition however their contract is worded.
- Add a Remote Desktop Services External Connector on top of the Windows Server one where external users reach published desktops or applications. It is an additive licence, not a substitute.
An External Connector permits access by any number of external users only where that access is for the benefit of the licensee, not for the benefit of the external user.
If you can classify your external population against the 30-hours and on-site tests, the purchase follows and you can stop. Below is the full definition, the CAL exceptions, and how to work out the crossover on your own quote.
Why it happens
Start with the definition, because it settles most of these cases before any pricing. Microsoft’s Product Terms glossary defines external users as users that are not employees of the customer or its affiliates, not contractors or agents that typically work for the customer or its affiliates for more than 30 hours on average per week, and not contractors or agents that typically work on site for the customer or its affiliates on each working day. Anybody who fails one of those tests is an internal user for licensing purposes and needs a CAL, whatever their contract says.
The two mechanisms are priced on opposite principles. A Client Access Licence covers one named user or one named device across your licensed servers of that product, so the cost grows with every person you add. An External Connector is assigned to a server and permits access by any number of external users – Microsoft’s wording is that this holds as long as the access is for the benefit of the licensee and not the external user. So the cost is fixed per server, whatever the population. Microsoft’s Windows Server licensing guidance puts the unit precisely: an External Connector is required for each physical server, covering any number of operating system environments, that is accessed.
There are also cases where nothing is required at all, and they are worth knowing before you buy either. The Product Terms exempt several kinds of access from the CAL requirement: access through another licensed server, web workloads, high-performance computing workloads, and physical operating system environments dedicated to hosting virtual machines. Anonymous access to a public website has never needed a Windows Server CAL or an External Connector, so a brochure site with no sign-in is a purchase of nothing.
A handful of named partners or suppliers need accounts
You have this one if Six people at two suppliers, each with a login on one of your servers, and no plan to add more.
- User CALs for those individuals. At low, stable counts CALs cost less than a connector and are simpler to defend at audit.
- Apply the version rule: a user CAL allows access to the corresponding version of the server software or earlier versions, so buy CALs at the version of your newest server.
- Revisit the decision if the population grows. The crossover is a division sum you can redo on any quote.
Members of the public authenticate against your server
You have this one if A customer portal, a booking system, a members’ area – a population you cannot count in advance and would not want to track.
- Windows Server External Connector for each physical server they reach. One connector, any number of external users, no counting.
- Check the benefit test: the access must be for the benefit of your organisation rather than for the benefit of the external user. Hosting a service on someone else’s behalf is a different licensing model.
- If external users reach the service through published desktops or applications, you also need a Remote Desktop Services External Connector.
Contractors work on your site
You have this one if Agency staff, long-term contractors, or an outsourced team sitting in your building on your equipment.
- These are not external users. The Product Terms exclude contractors or agents that typically work for you more than 30 hours a week on average, and those who typically work on site each working day.
- Licence them with ordinary CALs, on the same footing as employees.
- The test is the working pattern, not the contract of employment. A self-employed contractor at a desk in your office five days a week is an internal user for licensing purposes.
The service is a public website
You have this one if A marketing site, a published price list, a downloads page – content anyone can read without signing in.
- Buy nothing. The Product Terms exempt web workloads from the CAL requirement, alongside high-performance computing workloads and access through another licensed server.
- The exemption stops where authentication and line-of-business function begin. A public site with a members’ area needs a decision about the members’ area, not about the public pages.
Full reference
The two mechanisms, compared
| Dimension | Client Access Licences | External Connector |
|---|---|---|
| Unit of licensing | One user, or one device | One physical server, covering any number of OSEs |
| Population covered | Only the users or devices you licensed | Any number of external users |
| Cost behaviour | Grows with every user added | Fixed per server, whatever the count |
| Covers internal users | Yes – that is their purpose | No |
| Needs a count in advance | Yes, and it must stay accurate | No |
| Multiple servers | One CAL covers a user across your licensed servers of that product | One connector needed per physical server accessed |
| Version rule | A user CAL allows access to the corresponding version or earlier versions | Buy the connector at the version of the server accessed |
| Remote Desktop Services | Additive RDS CAL required on top of the base CAL | Additive Remote Desktop Services External Connector required |
| Best for | A handful of known partners or contractors | Customer portals and public authenticated services |
| Administrative effort | Ongoing tracking as people join and leave | Set once per server |
Working out the crossover without a price list
The comparison is a single division. Take the External Connector price on your quote for one server and divide it by the price of one CAL of the type you would otherwise buy. Round up. That number is how many external users the connector is worth on that server. If your genuine external population is smaller and stable, buy CALs. If it is larger, unknown, or growing, buy the connector. Redo the sum per server, because the connector is a per-server licence and the CAL is not.
Two adjustments are worth making before you trust the result. First, add the cost of being wrong: an under-counted CAL population is a compliance exposure that surfaces at audit, and a connector removes that risk entirely. Second, add the cost of counting: tracking a churning external population is real administrative work that nobody budgets and everybody eventually stops doing.
Additive licences sit on top, not instead
Microsoft’s base-and-additive CAL model is where a lot of quotes go wrong. The base CAL is the minimum requirement for accessing the server product’s functionality; access to advanced functionality associated with an additive CAL requires that additive CAL in addition to the base. Remote access to Windows Server is the canonical example: a Remote Desktop Services CAL is an additive CAL for Windows Server and is required alongside the Windows Server CAL, not instead of it. Active Directory Rights Management Services works the same way.
The External Connector family follows the same pattern. Microsoft’s Product Terms list both a Windows Server External Connector and a Windows Server Remote Desktop Services External Connector, the latter being the additive licence needed when the server hosts graphical user interfaces through Remote Desktop Services. External users reaching a published desktop or application therefore need both, and neither substitutes for the other.
Versions, and the direction the rule runs
CALs are version-specific, and the rule runs in one direction only. The Product Terms describe a user CAL as allowing access to the corresponding version of the server software or earlier versions, from any device, by one user. Read that as: newer CALs reach older servers, older CALs do not reach newer servers. Remote Desktop Services documents the same rule explicitly – you cannot use earlier-version RDS CALs to access later versions of Windows Server, but later-version RDS CALs will reach earlier session hosts. Buy CALs and connectors at the version of your newest server, not your oldest.
Where neither mechanism applies
Two situations sit outside this comparison entirely. SQL Server licensed per core has no CAL concept at all, which is precisely why per-core licensing is the model used for internet-facing databases: it covers any user population without counting anyone. SQL Server’s Server plus CAL model, which remains available on Standard edition, is the one that requires CALs and is therefore the one that raises an external-user question.
The second is a Cloud Solution Provider hoster arrangement. Microsoft’s Product Terms note that the External Connector requirement is waived for customers using Cloud Solution Provider hoster services. If your servers run with such a provider, confirm what their agreement covers before buying connectors of your own.
When a licence is the actual fix
If your external population is genuinely external under Microsoft’s definition, authenticated, and larger than a handful, a Windows Server 2025 External Connector for each affected physical server is both cheaper and far easier to defend than trying to count customers. It is not always the answer: for a few named partner staff, user CALs cost less and are simpler to administer. Arco supplies External Connector licences, Windows Server CALs and Remote Desktop Services CALs and connectors, and will work through which of your users fall inside the external definition before you commit – the 30-hours-a-week and on-site-each-working-day tests reclassify more people than most organisations expect, and that classification decides the whole purchase.
Questions people ask about this
Who counts as an external user?
Microsoft’s Product Terms define external users as users that are not employees of the customer or its affiliates, not contractors or agents that typically work for the customer or its affiliates for more than 30 hours on average per week, and not contractors or agents that typically work on site for the customer or its affiliates on each working day. Failing any of those tests makes someone an internal user who needs a CAL.
Does a public website need CALs?
No. The Product Terms exempt web workloads from the CAL requirement, along with access through another licensed server, high-performance computing workloads, and physical operating system environments dedicated to hosting virtual machines. Anonymous access to public web content has never required a Windows Server CAL or an External Connector.
How many External Connectors do I need?
One for each physical server that external users access. Microsoft’s guidance states it is required for each physical server, covering any number of operating system environments on it. The connector does not follow users between servers the way a CAL does, so a service spread across three servers needs three.
Do on-site contractors need CALs?
Yes. They are excluded from the external user definition by the on-site and 30-hour tests, so they are internal users for licensing purposes and need ordinary CALs on the same footing as employees. The test is the working pattern, not the contract of employment.
Do external users on a published desktop need anything extra?
Yes. Remote Desktop Services access is licensed additively, so external users reaching published desktops or applications need a Windows Server Remote Desktop Services External Connector as well as the Windows Server External Connector. Neither substitutes for the other, exactly as an RDS CAL sits on top of a base Windows Server CAL rather than replacing it.
Is there an External Connector for SQL Server?
The question usually goes away rather than being answered. SQL Server licensed per core has no CAL concept at all, which is why per-core licensing is the model used for internet-facing databases – it covers any user population without counting. Server plus CAL, which remains available on SQL Server Standard, is the model that raises an external-user question in the first place.
