Microsoft lets BYOL bring SQL Server to Amazon RDS, bypassing double licensing

Microsoft has quietly flipped a major switch for people running SQL Server outside Azure: it now allows customers to apply their existing SQL Server licenses toward SQL Server usage on Amazon’s managed database service, Amazon RDS. In plain English, if you already own SQL Server licenses, you can use them for SQL Server as a service on AWS, not just for self-managed deployments on EC2. That matters because it removes the need to pay licensing again under the previous “License Included” setup when customers wanted fully managed RDS.

This is the crux of Amazon’s own explanation, delivered via a blog post and discussed with The Register: customers paying with Microsoft’s Software Assurance licensing program could previously bring SQL Server licenses to AWS only on self-managed Amazon EC2 through Microsoft’s License Mobility program. But if the goal was a fully managed database like Amazon RDS, customers still had to pay a second time, because the RDS experience was not covered the same way. Amazon’s RDS database engineer Srikanth Katakam summarized the pain point directly: “If you wanted a fully managed database like Amazon Relational Database Service (Amazon RDS), and you already had SQL Server licenses, you had to pay for licensing a second time through the License Included model.”

So what changed? Amazon is now offering Bring Your Own Media (BYOM) for RDS for SQL Server. The program lets customers use existing SQL Server Enterprise or Standard Edition licenses to cover both installation media and licensing on the managed service, with no additional fees. It is also not a vague “call us and we’ll figure it out” story. Amazon laid out a three-step process that effectively operationalizes the license and the bits, so the move is doable for real teams, not just procurement.

Step one: customers submit a License Mobility Verification Form to Microsoft to confirm eligibility. Step two: customers upload their SQL Server Release to Manufacturing media to Amazon S3. Step three: in the Amazon RDS Console, users select the SQL Server major version, point RDS to the media file in S3, select their minor version, and then create the database. Amazon also notes that customers can track their Microsoft SQL Server license usage with AWS License Manager. Net effect: instead of forcing a “managed means pay again” tradeoff, the workflow now connects Microsoft’s eligibility checks to AWS’s console creation flow.

If you are thinking, “Sure, but why would Microsoft do this when it is competing with AWS?” the source gives clues, even though Microsoft declined to comment on why it got involved. On Amazon’s side, the self-interest is unusually explicit. AWS says that once operational data is in the cloud, it sits alongside AWS AI and analytics services, enabling teams to build agentic AI applications that “reason directly over their business data without complex data pipelines or infrastructure constraints,” per the AWS statement provided to The Register. In other words, AWS wants SQL Server workloads to live near the AI stack that can turn operational databases into fuel for analytics and agents.

Microsoft, meanwhile, has its own equivalent technology in Fabric, its data lake and analytics environment, with a control console to manage databases. So Microsoft may not be “offloading SQL Server into AWS forever.” But the practical implication for the market is sharper: SQL Server on AWS becomes easier to adopt, faster to expand, and cheaper to scale, because the licensing friction is reduced. That shifts leverage in migration negotiations. Teams can choose AWS RDS for management and operational simplicity without the same budget hit that previously came with fully managed deployments.

The Register also frames what this could signal strategically for Microsoft. In the absence of any firm statement from Redmond, it seems reasonable, the source argues, to interpret that SQL Server is no longer the strategic priority it once was. Microsoft has been inviting users to migrate to its database services, including Azure SQL and SQL Database in Fabric. And it offers alternatives, including database services running MySQL and PostgreSQL. The competitive context is also sobering for SQL Server loyalists: SQL Server remains third in the DB-Engines ranking, though its popularity has been sliding for more than five years, and it looks like PostgreSQL will overtake it in the near future.

For decision-makers, the real story is not just “Microsoft supports BYOL on AWS.” It is the economics and sequencing of migration choices for a large installed base. If you were holding back because the licensing model forced double payment when moving from EC2 to managed RDS, this update attacks that blocker. And if you are on the other side of the negotiating table, it changes how you should think about platform risk, cloud cost models, and vendor lock-in. Even analysts seem to be watching SQL Server through a broader lens: Adam Ronthal, vice president analyst at Gartner, pointed out that “Of the leading vendors in 2011 (Oracle, IBM, Microsoft, and SAP), only Microsoft has grown their market share in the last 15 years.”

Translation: Microsoft may be pruning its strategic focus, but it is still disciplined about the business outcomes. For peers and competitors, this move is a reminder that database platforms are not only technical ecosystems, they are licensing ecosystems. And when licensing friction falls away, migrations accelerate, data gravity shifts, and AI stacks gain more convenient access to the same core operational sources.