Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Licences and subscriptions that must move when you leave a host

Technical article
Hosting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

Direct answer: When you leave a hosting provider, some licences move with your organisation, some stay with the host’s agreement, and some cannot run outside their current environment without a new purchase. A licence inventory with owners—built before exit pressure—reduces last-minute discoveries that Windows, SQL, ISV cores or SaaS subscriptions cannot lawfully power the cutover stack.

This article is education only, not licensing or legal advice. Eligibility depends on programme, acquisition channel, product edition and dates—confirm with current Microsoft Product Terms and a qualified licence adviser before cutover.

This is exit licence handoff for Windows and LOB hosting customers, not a three-party ISV commercial design article. Deeper Microsoft hosting scenarios appear in Whose licences run in ISV-hosted deployments, Windows Server licensing for hosted virtual machines, and SQL Server licensing in virtual machines.

Why it matters

Commercial managers often treat hosting as “renting a server” while licences remain scattered across hoster SPLA statements, ISV portals, Microsoft admin centres and forgotten credit cards. Migration stalls when the new environment lacks activation evidence, programme rights, or vendor consent to relocate a metered subscription.

Australian organisations still face the same structural question: who is licensee of record, and does relocation require notice?

How it works

Categories to inventory before transition (illustrative examples—not exhaustive):

Category Typical licensee Moves how Common snag
Windows Server; Remote Desktop access rights Customer entitlement or host SPLA Contract- and programme-specific Inventory customer-owned RDS Client Access Licences (CALs) separately from provider SPLA Subscriber Access Licences (SALs) where a SAL applies (Microsoft describes SALs for products licensed under the Per Subscriber model; its overview also lists Per Processor and Per Core models. Confirm which programme and product-specific terms apply to your RDS offer.)
SQL Server Customer or host Per programme and edition Core minimums on new hardware
LOB application Customer direct with ISV ISV activation/support call Tied to old environment fingerprint
Microsoft 365 / Entra Customer tenant Tenant follows customer Tenant and billing move with you; re-test sign-in and Conditional Access policies in the new hosting context
Third-party backup/monitoring Either party Subscription account owner Agent tied to old VMs
SSL public certs Customer Re-issue Re-issue with a new private key does not require exporting the old key—generate or load a new key on the target. Key transfer from the old environment is a separate, policy-controlled step when you intentionally reuse an existing key
Fonts / codecs / PDF libs (examples) Often overlooked Per-seat Compliance on new farm

Provider subscription licensing (Microsoft SPLA): Microsoft describes the Services Provider License Agreement (SPLA) as a way for service providers to license eligible products on a monthly basis during an agreement term to host software services and applications for customers. If Windows or SQL is billed monthly through your hoster, editorial inference (not a Microsoft statement): ending the service may end those SPLA subscription rights unless you already hold other entitlements—read your contract schedules and Product Terms.

License Mobility (selected server applications): Microsoft’s License Mobility through Software Assurance programme requires active Software Assurance on eligible licences and describes deploying certain server application licences from a Volume Licensing agreement on an authorised mobility partner’s data centre. It is not a blanket permission for every product (for example, Windows Server has separate licensing rules). Microsoft’s page also notes a Flexible Virtualization Benefit for Software Assurance and subscription holders: under that benefit, certain outsourcers other than Listed Providers may host eligible products subject to Product Terms. That page gives Amazon, Google, Microsoft and Alibaba as examples of Listed Providers (“such as”)—not legal advice and not treated here as a closed list; read the current Microsoft page and Product Terms for your products rather than assuming mobility from this summary alone.

ISV licences: many LOB vendors issue keys bound to environment fingerprints. Plan parallel activation on the target before decommissioning the source. Some require written migration approval.

Subscriptions vs perpetual: SaaS components (tax APIs, maps, credit checks—examples only) follow the billing account. Transfer or recreate before cutover so batch jobs do not fail on auth.

What to choose and why

Build a single register: product, licence type, quantity, licensee name, renewal date, proof location, dependency server, exit owner. Review when adding workloads.

During migration, run licence parity as a gate alongside technical UAT—application open is insufficient if SQL is unlicensed on the new tier.

Negotiate hoster cooperation for licence evidence exports (activation screenshots, SPLA reports they hold on your behalf) in the service agreement early.

Risks and limits

Microsoft and ISV rules change; no statement here substitutes for Product Terms, your contract or professional advice.

No verification against a specific customer’s entitlement IDs (untested).

Does not cover ISV three-party licence split design.

Sources

Learning notes

  1. Licence inventory is a migration gate, not paperwork afterthought.
  2. SPLA through a hoster may end when the contract ends (confirm against your contract; not Microsoft advice).
  3. LOB vendors often require migration notice and new keys.
  4. SaaS subscriptions follow the billing account owner.
  5. Confirm Microsoft rights in current Product Terms and with advisers.