In a move that reflects the increasingly pragmatic reality of enterprise cloud strategies, Microsoft has quietly given a green light for SQL Server customers to bring their existing licenses to Amazon RDS, AWS's fully managed relational database service. What once required running SQL Server on raw Amazon EC2 virtual machines can now be done on a managed DBaaS platform, a change that carries significant implications for enterprise IT teams managing hybrid or multi-cloud environments.
The mechanism enabling this is AWS's newly introduced "Bring Your Own Media" (BYOM) feature for RDS for SQL Server. The three-step workflow is straightforward: organizations first submit a License Mobility Verification Form to Microsoft, then upload SQL Server installation media to an Amazon S3 bucket, and finally configure the deployment through the RDS Console. This process covers both SQL Server Enterprise and Standard editions, and Microsoft is not levying additional fees for the license migration.
The policy shift is notably significant because Microsoft's License Mobility program previously stopped short of extending to managed cloud database services run by competitors. Customers wanting fully managed SQL Server on AWS had to either use AWS's separately licensed RDS offering, paying AWS's own SQL Server licensing fees, or self-manage the database on EC2, sacrificing the operational simplicity of a managed service. Now that the barrier is removed, organizations with existing Enterprise Agreement licenses can extend their investment to AWS without double-paying.
Why It Matters
This development signals something broader than a licensing technicality. It is a recognition by both Microsoft and AWS that enterprise customers increasingly refuse to be locked into a single cloud vendor's ecosystem, and that flexible licensing policies are a competitive differentiator in winning or retaining their business. For enterprises running workloads across Azure and AWS, a common real-world scenario, the ability to apply a single SQL Server license to managed services on either platform dramatically simplifies cost management and compliance auditing.
The timing also aligns with AWS's strategic push to get more enterprise data into its cloud to fuel agentic AI workloads. Once SQL Server databases run on RDS instead of on-premises or self-managed EC2, those data assets become easier to connect to AWS AI services. In the long run, the licensing flexibility may matter less as a cost story and more as a data mobility story.
For Microsoft, which remains third-ranked on DB-Engines with PostgreSQL closing the gap fast, the move may also be defensive. Keeping customers on SQL Server by reducing friction around where they run it is preferable to those customers migrating to open-source alternatives entirely. Gartner has noted Microsoft as the only major 2011-era database vendor to have grown market share consistently over 15 years, and pragmatic licensing policies are part of what sustains that position.
Enterprise architects evaluating multi-cloud or AWS-primary strategies should review their existing SQL Server EA terms and assess whether the BYOM migration path aligns with their current DBaaS consolidation plans.