Fix it now
The Exchange Server edition caps mounted mailbox databases and nothing else: Standard mounts five, Enterprise mounts one hundred. Users are handled entirely by CALs, and a mounted passive copy in a database availability group counts against the ceiling of the server holding it, which is what decides most designs.
- Buy Standard for a single server, or any design where no member server mounts more than five databases including passive copies.
- Buy Enterprise the moment any one server’s mounted database count could exceed five after a failover, not just in normal operation.
- Count copies, not databases. A three-copy availability group with six databases puts six mounted copies on each member.
- Do not size the edition by mailbox count or headcount. Neither is limited by edition.
- Get it right first time: Standard upgrades to Enterprise with a product key, but there is no supported downgrade without reinstalling Exchange.
- Price Exchange Online first. It removes the server licence, the CALs and this decision entirely.
Exchange Server SE needs an active qualifying entitlement to install and run: Software Assurance on Exchange Server licences, or a qualifying Microsoft 365 subscription with on-premises use rights.
If your per-server copy count already exceeds five, stop here and buy Enterprise. Below is how to size the count properly, what counts as mounted, and how the edition change actually works.
Why it happens
Every other Microsoft server product scales its editions on something visible – cores, virtual machines, users. Exchange scales on an internal structural unit most organisations have never had to think about, and the number they need is usually decided by an availability design somebody else drew.
Microsoft publishes the figures plainly. Exchange Server SE Standard Edition supports five mounted databases. Enterprise Edition supports one hundred. Those limits have held across Exchange 2016, 2019 and SE. Everything else about the two builds is identical: same features, same protocols, same management surface. Mailboxes per database are not limited by edition, and neither is the number of users, which is handled by Client Access Licences bought separately.
You are counting databases when you should be counting mounted copies
You have this one if The design says six mailbox databases and three copies of each, and somebody has concluded that six is under one hundred so Enterprise is obviously unnecessary – or that six is over five so Standard obviously fails.
- Microsoft defines a mounted database as one that is in use: an active mailbox database mounted for clients, or a passive mailbox database mounted in recovery for log replication and replay.
- Both count. Six databases with three copies each is eighteen mounted copies distributed across the member servers, and the limit applies per server.
- A recovery database does not count towards the limit.
- You may create more databases than the edition allows. You may only mount up to the maximum the edition permits, which is why the failure appears as a database that will not mount rather than as a licensing warning.
The design is sized for normal operation, not for a failure
You have this one if Each member holds four copies today and the maths works, but nobody has asked what one surviving node holds when another is down.
- Work out the mounted copy count on each server after the worst single failure the design is meant to survive, and compare that with the ceiling.
- A surviving node picks up the copies of the node that failed, so a design comfortably inside five in steady state can breach it at exactly the moment you need it not to.
- Add headroom for growth on top. The point at which you notice the ceiling is when a database will not mount, in the middle of an incident.
Restore time, not mailbox count, is setting your database count
You have this one if You are being pushed toward many small databases because a single large one cannot be restored inside the recovery target.
- Decide the largest database you are willing to restore inside your recovery objective. Divide your total mailbox data by that figure to get the minimum active database count.
- Multiply by the number of copies, distribute across members, and take the highest per-server figure.
- If recovery time is what sets the count, Enterprise is usually the honest answer, because the database count is being chosen for you rather than by you.
One thing the edition never changes is access licensing. Every user or device that accesses the server software needs a CAL whichever edition you run, and the Enterprise CAL is a separate additive purchase for compliance features rather than a consequence of the server edition. Server edition and CAL edition share the words Standard and Enterprise and are otherwise unrelated decisions.
Full reference
What the edition governs, and what it does not
| Dimension | Exchange Server SE Standard | Exchange Server SE Enterprise |
|---|---|---|
| Mounted mailbox databases | 5 | 100 |
| What counts as mounted | Active databases mounted for clients, plus passive copies mounted for log replication and replay | Same rule |
| Recovery database | Does not count | Does not count |
| Databases you may create | More than the limit; you may only mount up to it | More than the limit; you may only mount up to it |
| Mailboxes per database | Not limited by edition | Not limited by edition |
| Users supported | Not limited by edition; handled by CALs | Not limited by edition; handled by CALs |
| Database availability groups | Supported | Supported |
| Feature set | Identical | Identical |
| How the edition is set | Product key entered after installation | Product key entered after installation |
| Changing edition later | Upgrade to Enterprise by product key | No supported downgrade without reinstalling Exchange |
Sizing the database count before you choose
- Decide the largest mailbox database you are willing to restore from backup inside your recovery target. Divide your total mailbox data by that figure: the result is your minimum active database count.
- Decide how many copies of each database the design needs, including any lagged copy.
- Map copies onto member servers and count how many each one mounts in normal operation.
- Repeat that count for the state after the worst failure the design must survive, when a surviving node picks up another node’s copies.
- Take the highest per-server figure from step four and compare it with five. If it is over, you need Enterprise on that server.
- Add headroom, because estates grow and the symptom of the ceiling is a database that will not mount.
Changing edition without rebuilding the server
Exchange reads its edition from the product key you enter after installation. To move a Standard server to Enterprise you enter the Enterprise key, either in the Exchange admin center under Servers, or with Set-ExchangeServer, and then restart the Information Store service on that server. Mailboxes, databases, certificates and configuration all stay where they are, and the outage is the length of a service restart rather than a migration.
Set-ExchangeServer -Identity <ServerName> -ProductKey <product key>
Restart-Service MSExchangeIS
The route runs one way only. Microsoft states you cannot downgrade from an Enterprise Edition licence to a Standard Edition licence without reinstalling Exchange. A server over-licensed by mistake has to be rebuilt to correct it, so size before you buy.
Because the promotion is this easy, there is a reasonable argument for starting on Standard when the design sits comfortably inside five mounted copies and promoting later. The counter-argument is that a growing Exchange estate usually grows its availability group at the same time, and relicensing several nodes under pressure is less pleasant than buying correctly at the start.
The subscription requirement that changed with SE
Exchange Server SE is not a perpetual purchase you can leave alone. Microsoft states that customers must maintain an active qualifying entitlement to install, run and stay current with Exchange Server SE. That entitlement comes either from active Software Assurance on Exchange Server Standard or Enterprise licences, or from a qualifying Microsoft 365 subscription acquired through an Enterprise Agreement that includes on-premises server use rights. Exchange Server SE follows the Modern Lifecycle Policy, which means staying current rather than working towards a fixed end-of-support date.
There is a useful consequence on the CAL side. Microsoft states that Exchange Online Plan 1 and Plan 2 licences provide Client Access Licence equivalency for Exchange Server SE. If part of your organisation already holds Exchange Online seats, check whether those users are already covered before buying CALs for them.
When neither edition is the right purchase
- A single site, a handful of databases, no availability group: Standard, with room to spare.
- A two-node availability group with two copies of each of two databases: still Standard on both nodes, because each mounts four.
- Any design with three or more copies of more than one database: check the per-node figure carefully, because it climbs faster than the active database count suggests.
- A large estate where restore windows force small databases: Enterprise, because your database count is being set by recovery time.
- A hybrid server kept only for recipient management after the mailboxes moved: the smaller edition, since there are few or no databases to mount.
- A small organisation with no residency or regulatory reason to keep mail on site: neither. Price Exchange Online, which removes the server, the CALs and the subscription entitlement question.
When a licence is the actual fix
If your worst-case per-server count of mounted databases and copies stays within five, Exchange Server SE Standard is the correct licence and Enterprise buys headroom you will never mount. Arco supplies Exchange Server SE in both editions along with the Standard and Enterprise CALs, and will confirm which edition your availability group design actually requires if you send us the database and copy layout, including what each node holds after a failure. Because Exchange Server SE requires an active qualifying entitlement rather than a one-off purchase, we will also set out what keeping it covered involves, check whether Exchange Online seats you already hold give CAL equivalency, and tell you plainly if the honest comparison with Exchange Online favours moving the mailboxes instead.
Questions people ask about this
Does the Standard edition limit how many mailboxes I can have?
No. The edition limits mounted mailbox databases only – five on Standard, one hundred on Enterprise. Mailboxes per database are not limited by edition, so a Standard server can hold as many mailboxes as your storage and performance design supports, spread across the databases it is allowed to mount.
Do passive database copies count against the limit?
Yes, when they are mounted. Microsoft defines a mounted database as an active mailbox database mounted for use by clients or a passive mailbox database mounted in recovery for log replication and replay. Both count against the ceiling of the server holding them. A recovery database does not count.
Can I run the Standard edition as a database availability group member?
Yes. Availability groups are supported on both editions and the underlying Windows failover clustering is available in Windows Server Standard. The constraint is arithmetic rather than capability: each member has to stay within five mounted copies, including whatever it picks up after another node fails.
Do I still need CALs if I buy the Enterprise edition?
Yes, and the server edition does not change them. Every user or device accessing the server software needs an Exchange Standard CAL, and those needing archiving, hold, multi-mailbox search or data loss prevention need an Enterprise CAL in addition. Check first whether Exchange Online Plan 1 or Plan 2 licences you already hold give those users CAL equivalency for Exchange Server SE.
Is on-premises Exchange still worth running?
For some organisations, yes: data residency requirements, regulated environments, unreliable connectivity, or an application estate tightly coupled to a local server. Exchange Server SE now requires an active qualifying entitlement rather than a one-off licence, so the ongoing cost sits closer to a subscription than it used to. Compare properly against Exchange Online before committing to another hardware refresh.
