RSS

Tag Archives: Serviceproviderlicensingagreement

Licensing Microsoft Workloads in AWS

If you have followed me for some time, you may know that I always like to refer to the AWS model as an example for hosters in handling licensing and educating customers. AWS has a SPLA, they have end customers, they report usage, and they have to manage Microsoft licenses.   Sound familiar? 

AWS has more complexities than the average hoster because they are a Listed Provider. There’s no Flexible Virtualization or CSP-Hoster option; they are also restricted by the Hyperscaler definition in the SPLA Agreement, limiting certain use rights for specific products. So how do they win?

If you take one thing away from this article, please educate your end customers on licensing. AWS does a phenomenal job at that as compared to Microsoft. They have very informative licensing videos and a dedicated webpage specifically for Microsoft licensing inquiries. You can check it out here. I would do the same for your organization. Need help? You can email info@splalicensing.com

What are the licensing rules for running Microsoft workloads using AWS? Glad you asked. As mentioned, AWS is a Listed Provider, which means they have restrictions on workloads end customers can bring into their datacenters. For example, they cannot host a Windows 10 Operating System from their datacenter in shared environments because they are not authorized outsourcers. Let’s review some licensing challenges and options for end customers using AWS.

October 2019 Microsoft Licensing Changes

Changes were announced on October 1, 2019, that prohibited software without License Mobility to be installed in a Listed Providers datacenter regardless of whether it is dedicated (single-tenant) or shared. A good example of this is Windows Server. If you purchased Windows Server after 10/1/2019, you can no longer bring that Windows license to AWS. You can still install it on dedicated infrastructure if you purchased it before 10/1/2019 and the version was publicly available. Once you upgrade, you can no longer leverage your existing Windows licenses.   As a regular hoster (non Listed Provider), you can still run workloads in dedicated environments without issue. 

It seems unfair, especially since Azure has Hybrid-Use-Benefits.  One way AWS solves this issue for customers who want to upgrade or maybe purchase the Windows license after 10/1/2019 is to offer the “License Included” option. The end customer will lease (through SPLA) the Windows Server license. In many cases, end customers no longer want to mess with the licenses; they can purchase them from AWS and move on.

No Flexible Virtualization Benefit 

Microsoft does allow AWS customers to bring their M365 apps for Enterprise (workspace only) to their environment. They also can provide Windows desktops on dedicated infrastructure only, but with restrictions, they have to pay for the VDA license (M365 VDA E3 or E5). That is an increased cost for end users to use AWS versus an authorized outsourcer. However, they offer Windows Server + RDS to emulate a desktop and offer it as a service. This is a less expensive option, and end users would not know the difference. Using Windows Server + RDS + M365 apps for Enterprise makes a good bundled solution. As a hoster, you can offer the same thing.

End of Security Updates

I get asked a lot about this in the community.   Windows Server 2012/2012R2 support will end on October 10, 2023. That’s a big deal. What is ESU? This means Microsoft no longer offers patch security updates for products that reached their expiration (Windows 2012 – October 10 and SQL 2012 – July 12). Customers can bring their licenses (with SA) that are ESU eligible to AWS. Quick note: SPLA licenses are eligible. You purchase the ESU SKU from CSP or Microsoft directly.

What does AWS think of the new licensing rules? Flexible Virtualization/CSP Hoster/Listed Provider?

Are they happy? No. But one of AWS’s big advantages is they are not Microsoft. The cloud space is minimal right now. It seems odd to say that, but there are a lot of on-premise workloads not in the cloud. There’s an opportunity for everyone, including you (SPLA provider).   One thing that is consistent with Microsoft is change. No matter what Microsoft does, how will you help win customers and keep the ones you already have? I think AWS does a great job at both. With all the new changes, I believe, brings opportunities. Help your customers understand the licensing rules, and you will win.

Thanks for reading,

SPLA Man

 
Leave a comment

Posted by on September 29, 2023 in Outsourcing Scenarios

 

Tags: , , , , , , , , , , , , , , ,

Is Azure Arc the gateway to ending SPLA?

I had a dream the other night, SPLA was going away. I woke up in horror. My wife thought something dramatic happened, and in a way, it did. In my dream there were pricing discounts, incentives, metered pricing, and security updates for hosters, not one benefit was part of the SPLA program. When I woke up, I was thankful it was just a dream until I Binged (man I can’t say that) Googled around and found Azure Arc. Is SPLA gone? No. But maybe there’s opportunities hosters should consider. In this article, let’s dive into the licensing side of Azure Arc and how it may benefit SPLA providers.

I like to think of Azure Arc as a bridge between your infrastructure and Azure. Maybe it’s the “arc” in the title or I just plagiarized it from the Microsoft website. https://azure.microsoft.com/en-us/products/azure-arc#overview either way, there’s a connection because it manages IT resources in your cloud, Joe’s Hosting Cloud, or another third-party using the same tools you would use to manage Azure hosted resources. So let’s take a look at how a SPLA partner might use this technology ,where does the licensing come into play, and the benefits.

I think we can all agree SQL is one of the most expensive products at Microsoft and managing SQL Server can be just as expensive. Azure Arc allows a hoster to manage all SQL Servers deployed in the hosters datacenter from, you guessed it, Azure. A hoster is still “hosting” SQL Server but using Azure resources to manage it. From the Azure portal, a hoster can query deployment information, get detailed information on the number of cores, or maybe they want to know which editions are running and where.

Ok, we get the management piece of it. But managing doesn’t replace SPLA. That statement is correct. When Azure Arc is enabled, customers, hosters, whoever has the ability to purchase SQL using a pay as you go model through Microsoft directly or CSP such as the CSP Hoster program. Yes, pay as you go model is SPLA, but one benefit over SPLA is pay as you use. In other words, if you are looking to save costs on SQL Server for development projects or maybe there’s times in high demand and times of low demand, hosters might benefit. With SPLA, if you spin up a server on the 28th of the month, you have to report that license as if you deployed it on the 1st of the month. You also receive incentives, rebates, and the deployment of Azure Arc goes towards your Azure revenue credit. One other side note, is end of security updates are also included as an add on which is not available in SPLA. (Your end customers can purchase ESU and deploy it in a SPLA providers datacenter though).

Ok, but the biggest benefits of SPLA is unlimited virtualization rights. And that is a BIG benefit. You can’t license SQL Enterprise on the host level and deploy SQL Standard virtual machines using CSP licenses. I also think Windows Datacenter in SPLA is very profitable for service providers. In addition, just because the virtual machine is installed locally when using Azure Arc, data/information is relayed back to Azure. There could be compliance/security concerns. You don’t have that issue with SPLA.

SPLA has it’s place and so does CSP. Can’t we all just get along? Either way, Microsoft still gets paid.

Thanks for reading,

SPLA Man

 
Leave a comment

Posted by on September 21, 2023 in Uncategorized

 

Tags: , , , , , , , , , , , ,