Company migrates SQL Server workload from on-premise to AWS. “We already have licenses, we’ll just move them.” A month later, the invoice from AWS: full SQL Server licensing costs in EC2 - plus the on-premise license costs they’re still paying (maintenance). Double payment. Or: they could have used BYOL and paid only for infrastructure.
Cloud migration changes software licensing economics. On-premise: you buy a license once (perpetual) or pay subscription, host on your own hardware. Cloud: often licensing is built into service cost (license-included) - but this can be more expensive than BYOL (Bring Your Own License).
Without licensing planning, migration can cost significantly more than expected. With good planning - it can be an opportunity for optimization and savings.
What are the basic software licensing models in cloud?
“Effective IT asset management requires a lifecycle approach — from request and acquisition through deployment, maintenance, and retirement.”
— ISO/IEC, ISO/IEC 19770-1:2017 — IT Asset Management | Source
License-Included (LI): Cloud provider delivers software with license included. You pay per hour/month of usage. Simple model, no own licenses to manage. But: often more expensive long-term.
Bring Your Own License (BYOL): You have your own licenses (perpetual or subscription), use them in cloud instead of paying cloud provider for license. Lower cloud cost (infrastructure only), but you must have licenses with appropriate rights.
Subscription from cloud provider: You buy subscription directly from vendor, but delivery is through cloud. E.g., Microsoft 365 (subscription from Microsoft, used with Azure/anywhere).
Cloud-native pricing: Software has dedicated pricing for cloud, different from on-premise. E.g., Oracle Database in Oracle Cloud vs. on-premise licensing are different models.
When does BYOL make sense vs. License-Included?
BYOL makes sense when:
- You have existing licenses with Software Assurance / active maintenance
- Long-term usage (3+ years)
- High utilization (24/7 workloads)
- You have mobility rights (check license terms)
License-Included makes sense when:
- Short-term / variable workloads
- You don’t have existing licenses
- Testing / dev environments
- You want simplicity (all-in-one billing)
Break-even analysis: Compare: (License-Included hourly rate × estimated hours) vs. (BYOL infrastructure rate × hours + license cost amortized)
Example:
- SQL Server License-Included on AWS EC2: $1.50/h
- BYOL infrastructure: $0.50/h + SQL Server license ($10,000/year amortized)
- At 8760h/year: LI = $13,140, BYOL = $4,380 + $10,000 = $14,380 → LI slightly better
- But: with Software Assurance which you already paid → BYOL is $4,380 total → much better
How does Microsoft licensing work in Azure vs. AWS vs. GCP?
Azure Hybrid Benefit (AHB): Have Windows Server or SQL Server with Software Assurance? You can use licenses in Azure without additional license cost - you pay only for compute.
Savings: up to 85% for SQL Server, up to 40% for Windows Server.
AWS: BYOL possible for Windows/SQL Server, but requires dedicated hosts or dedicated instances. Not as simple as Azure Hybrid Benefit. License Mobility for some Microsoft products.
GCP: Similar - BYOL requires sole-tenant nodes. Google also offers Cloud SQL with license-included.
Microsoft’s “Azure preferred”: Microsoft gives better terms for Azure than competing clouds. Azure Hybrid Benefit is generous, BYOL to other clouds has more restrictions.
How does Oracle licensing work in cloud - and why is it a trap?
Oracle licensing in cloud is notoriously complicated and often more expensive than on-premise.
Oracle Cloud Infrastructure (OCI): Licensing per OCPU (Oracle Compute Unit). BYOL possible. Oracle offers “discounts” to attract to OCI.
Oracle on AWS/Azure/GCP: Oracle requires licensing per vCPU with specified multiplier (2 vCPU = 1 Oracle processor). But beware: some instance types require more licenses than you’d expect.
AWS Dedicated Hosts: BYOL for Oracle requires Dedicated Hosts (more expensive than shared). Licensing audits may question BYOL if not on dedicated.
Oracle authorized cloud environments: Oracle has a list of “authorized clouds” where BYOL is simpler. AWS, Azure, GCP are authorized, but rules are detailed.
Risk: Without careful analysis, Oracle on AWS can cost 2-3x more than on-premise due to licensing complications.
What are mobility rights and how to verify them?
License Mobility through Software Assurance (Microsoft): You have Microsoft licenses with active SA → you can move to “shared servers” in authorized cloud. But: requires a form to fill out, cloud provider must be on the list.
Oracle mobility: Limited. BYOL mainly to OCI. To other clouds - specific conditions, often requires dedicated hosts.
SAP licensing in cloud: SAP allows BYOL to certified cloud providers. Requires: declaration, appropriate license type, usage monitoring.
VMware in cloud: VMware Cloud on AWS, Azure VMware Solution - use your licenses or buy through cloud. Specific mobility programs.
How to verify:
- Check License Agreement - does it have mobility rights
- Check Software Assurance status (Microsoft)
- Check cloud provider on authorized list
- Document deployment - audits may require evidence
How to plan license migration step by step?
Step 1: Inventory List of all software that will be migrated. What licenses you have, what entitlements, what SA/maintenance status.
Step 2: Target architecture How will software be deployed in cloud? Instance sizes, regions, availability zones. This affects licensing.
Step 3: Licensing options analysis For each software: BYOL possible? License-Included available? Terms, restrictions, costs.
Step 4: Cost comparison Compare: current on-prem licensing cost + new cloud infrastructure cost + any additional cloud licensing cost. Vs. license-included total cost. Vs. renegotiated cloud-native licensing.
Step 5: Rights verification Check that you have rights to BYOL. Fill required forms. Notify vendors.
Step 6: Vendor negotiation Migration is an opportunity for renegotiation. “We’re migrating to Azure, we want better Azure terms.” Vendors want cloud business.
Step 7: Implementation with license tracking Deploy with appropriate tagging for license tracking. Monitor usage vs. entitlements.
Step 8: Post-migration audit Check that actual deployment = planned. Are licenses being used correctly?
What are common mistakes and how to avoid them?
Assuming BYOL is automatic. It’s not. Requires: appropriate rights, appropriate deployment (dedicated hosts for some), documentation.
Ignoring cloud provider licensing. AWS Marketplace, Azure Marketplace have software with their own licensing. Make sure you understand the model before purchase.
Forgetting maintenance/support. BYOL is the license, but support may be separate. On-prem support agreement may not cover cloud deployment. Check!
Not considering cloud-native alternatives. Instead of SQL Server in EC2 - maybe Aurora (AWS cloud-native)? Instead of Oracle - maybe PostgreSQL? Migration is an opportunity for change.
Underestimating Oracle complexity. Oracle in non-Oracle cloud is a licensing minefield. Expert advice recommended.
No tagging for license tracking. Cloud resources without tags = hard to match with licenses. Tag everything: product, version, license type.
How to negotiate with vendors during migration?
Leverage migration moment: “We’re migrating a large portion of workloads to cloud. We want to talk about cloud-friendly licensing.” Vendor knows they might lose business to cloud-native alternatives.
Consolidate and negotiate: Have licenses with Microsoft, Oracle, SAP? While migrating, talk to everyone. Maybe one will give a better offer for a larger share.
Ask for migration incentives: Microsoft, Oracle, SAP have programs encouraging migration to their clouds. Azure migrate credits, Oracle cloud migration support.
Consider term alignment: Licenses renewing at different times? Migration is an opportunity for aligned terms (one vendor negotiation per year, not four).
Get benchmark data: What are others paying for similar migration? Use consultants, Gartner, peer networks.
Table: Licensing Considerations by Major Vendor in Cloud
| Vendor | BYOL Options | Best Cloud for BYOL | Key Considerations | Pitfalls |
|---|---|---|---|---|
| Microsoft (Windows Server) | Yes with SA | Azure (Hybrid Benefit) | 40% savings possible, easy process | AWS/GCP require dedicated hosts |
| Microsoft (SQL Server) | Yes with SA | Azure (Hybrid Benefit) | Up to 85% savings | Core counting, edition matching |
| Oracle Database | Limited | OCI preferred | Processor counting rules complex | Non-OCI clouds very expensive |
| SAP | Yes with conditions | All major clouds certified | Requires declaration, proper license type | Named User vs. Engine licensing |
| VMware | Via VMware Cloud programs | AWS, Azure VMware Solution | Subscription or BYOL | vCPU counting for licensing |
| Red Hat | Yes | All clouds | Simple BYOL, also cloud marketplace | Ensure support continuity |
Cloud migration without licensing planning is a recipe for cost overruns. With good planning, BYOL and vendor negotiations - it’s an optimization opportunity. The difference can be 30-50% of total cost.
Key takeaways:
- BYOL can significantly reduce cloud costs - but requires appropriate rights
- Azure Hybrid Benefit is generous for Microsoft workloads
- Oracle in non-Oracle cloud is an expensive proposition - plan carefully
- License mobility requires verification and documentation
- Migration is a negotiation opportunity - vendors want cloud business
- Track licenses in cloud through tagging - audits are still real
- Consider cloud-native alternatives - not everything has to be lift-and-shift
Engage licensing expertise early in migration planning. It’s an investment that pays back multiple times.
ARDURA Consulting offers comprehensive Software Asset Management support for cloud migrations. We help plan licensing, negotiate with vendors, and optimize software costs in cloud. Contact us before starting your migration.