Tag Archives: SPLA Compliance

SPLA Audit Support

We are quickly approaching Microsoft’s fiscal year-end which tells us two things:  1) Microsoft will announce new program and cloud strategies and 2) Microsoft will more than likely increase audit notifications.

I work for an organization that helps specifically around audit support, compliance, and SPLA reporting.  One of the biggest cost for any hosting or manage service organization is licensing.  Let’s eliminate risk before it becomes a risk.  Our technique:

Data Collection – Create a baseline of what you are reporting, how you are reporting, and why.

Review of the Data: Ensure we mutually have a clear understanding of your risks as well as what you should be licensing, contracts you need to have in place, and how you should report.

Forward Strategy:  How to optimize or reduce your costs moving forward, tools and practices you need to implement, and what you should consider before outsourcing your datacenter environment.

If you would like to learn more, please email

Thank you,


Leave a comment

Posted by on March 8, 2018 in Compliance, Uncategorized


Tags: , , , ,

Why you need a plan B, C, D, and E.

The title seems obvious, if you are an entrepreneur, you should always be thinking about what’s next.  I read/follow Richard Branson, who wrote an article recently on focusing on the future, check it out here.  It’s all about looking forward to what’s next and dreaming big.  Very few organizations are as diversified as Virgin.  In a way, it might be too diversified, but the point is he does not settle for the status quo, if he doesn’t like it, he changes it.  Think of all the different industries under his portfolio: Entertainment, health, financial, technology, travel, and many more.  The company started out in the music industry!

What does this have to do with SPLA licensing?  Over the past week alone, how many different programs and licensing nuances did I write about? (too many to count). Those changes only had to do with Microsoft!  Think of all the other changes going on in the industry including security, data and backup, and development.   If you do not have a plan in place or to adapt change, you might be left in the dust.

In SPLA, way too many organizations report the exact same thing each month.  They even report the same quantities!  They have a few loyal customers in which their hosting business depends on.  My question to them –  What happens if the loyal customer is not so loyal?   If you are hosting, you have everyone and their brother trying to convince your customer to move to their cloud.  If you are a managed service provider, forget about it.  Not only are hosters your competition, everyone in the industry is your competition.  What are you going to do to stand out?

This blog is about licensing, and I like to think there are ways to be creative with your SPLA usage to diversify your business.  Don’t just report the same thing each month and not give it a second thought.  There are always ways to reduce or optimize what you license.  In a way, licensing can help expand your offering.  SAL for SA, as an example, can help build your DR business and lower your SPLA costs.  Check out my article here  Windows Datacenter, allows unlimited VM’s which can help build your IaaS platform.  Azure Stack, can help bring an Azure type offering from your own datacenter.   Qualified Hosting Addendum, will allow you to offer VDI from a shared environment.  My point being, don’t just settle for the same old usage report each month.  Licensing is a big headache even for a guy who spends his free time writing about it, but that doesn’t mean you cannot learn to leverage licensing to your own advantage.  If you understand the licensing, you can start to look at ways to really get creative and expand your offering.   I’ll go back to SAL for SA.  If you did not know about SAL for SA, you would be telling your customers that they cannot leverage their investment in software assurance from both your datacenter and theirs.  You would probably tell them about license mobility which transfers a license over to your datacenter.  That’s a big miss in my opinion.

Learn the licensing, diversify your business, and I promise your loyal customer will remain loyal.

Thanks for reading,



Leave a comment

Posted by on July 23, 2017 in In My Opinion


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

What is a Service Provider?

The year 2017 has brought on A LOT of change for the hosting community.  A hosting company used to be an organization that hosted Exchange – fast forward to today and a service provider takes on a whole new meaning.  In this article, we will take a look at defining a service provider and how it applies to licensing.   Let’s play a little game called “Do they qualify”  Have a question?  Email

An organization that provides or extends  litigation software (that they leased from the publisher) to law firms and other legal entities who are not wholly owned by the organization providing the solution. Does this organization qualify for SPLA?

Yes.  If you are an avid reader of, you probably read my article on EMR Software The same holds true for any software (not just EMR) that runs on Microsoft technology that you do not own, but lease from a third-party.   Remember “AS”  If you are providing software AS a service that’s hosted from your datacenter environment,  SPLA must be part of the equation.  Why does this solution qualify for SPLA?

#1 they don’t own the software they are hosting

#2 they do not own the organization(s) who are consuming (using) the software for their benefit.

An organization who sells a product on a website to external users –   do they qualify for SPLA?

No.  Although they are selling something to consumers via the internet, the software used to deploy the solution benefits the e-commerce company, not the end-user.   Where SPLA does fit is if the web company decides to host a website on behalf of another organization.  The web company would fall under the SPLA rules.  Who benefits from the access is a key question to ask yourself.  Second question – is the access used to run their business or my own?

An organization who provides SharePoint to end users to share information.  Do they qualify?

No.  Simply sharing information does not qualify.  If the organization was hosting SharePoint on behalf of another organization, that’s SPLA.

A company hosts Exchange on behalf of another organization but does not charge for this access.  Does this qualify for SPLA?

Yes.  Microsoft doesn’t care how much money you make from the solution.  The question remains – are you providing this “as a service” for a third-party?

A company decides to use AWS as their datacenter provider to host an application they use internally.  Do they need SPLA?

No.  In this example, you are the end-user.  AWS has a SPLA to cover all infrastructure products they host on your behalf.  If you were to use AWS as a datacenter provider to host SharePoint to your end customers employees; you would pay AWS for Windows and SQL and report on your SPLA SharePoint SAL licenses.


I have 25 Linux machines that I host for my customers.   Do I need SPLA? 

No.  You have 25 Linux machines.  If you had 24 Linux machines and 1 Windows VM, you would have to license the host machine to cover that Windows VM through SPLA.

My reseller told me I didn’t need SPLA because the access qualifies for Self-Hosted.  The auditors told me it does not qualify.  Why?

All software used to deploy the solution has to be self-hosted eligible.  I bet you are running an application that does not qualify as part of your solution.  This would be SPLA.  Secondly, if you did not buy the software with software assurance, that is out of compliant.

Thanks for reading,


Leave a comment

Posted by on July 18, 2017 in Compliance, Uncategorized


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

Epic Community Connect for Healthcare Organizations

In this article we will review how Epic Community Connect effects your Microsoft licensing position.  This is a follow up to my earlier post which can be found here

What’s the concern?

If you host/extend Epic (or any EMR software that you do not own) to outside clinics or other healthcare facilities SPLA must be licensed.

What’s an outside organization?

If your organization (who hosts Epic/EMR) does not have at least 51% ownership of the other entity, that would be considered an outside organization as it pertains to this solution.

I’m confused…big time.  Why would I license SPLA when I was told to license through my Enterprise Agreement?

The EA is for your own internal employees.  The Service Provider Licensing Agreement (SPLA) is for companies who host Microsoft software to third parties.

Wait.  I just went to your website and I am not an employee.  Are you saying you have a SPLA agreement?

No.  I don’t host an application or any server whatsoever.  I do pay a web company to host my website.  The web company is under a SPLA agreement if they use Windows Server.

What are my options now?  I already deployed Epic and I don’t have a SPLA.  

I would work with a SPLA Reseller who can walk you through the steps and how to be compliant.  You can email me at if you have additional questions.

Thanks for reading,



Leave a comment

Posted by on July 11, 2017 in EMR Software, Uncategorized


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

Top 5 Compliance Trends for MSP’s and SPLA

There are so many license changes and gotchas with SPLA, Azure, AWS, and all the others that I thought I would highlight for you some of the trends we see when it comes to compliance.

  1. Licensing Office Standard when Office Professional is installed.  In many cases, an IT administrator will inadvertently install Office Pro, report Office Standard to their procurement team who in return reports it to the reseller.  The IT admin will leave the company, and the procurement team continues to report Standard not knowing Pro is installed until audit time.  In this situation, Microsoft will check when Office was installed, and take the delta of what was reported (STD) v. what should be reported (Pro).  Don’t make this mistake.  Many partners are only charging their customers for Standard pricing!
  2. Not reporting SPLA at all.  Sounds silly, but many providers focus on developing software and not on the licensing.  We have found instances in which the procurement manager (who was in charge of reporting SPLA) left the organization and no one else took over their responsibility.   The reseller continues to email the procurement manager but obviously the email goes unnoticed.  After many months, their SPLA will be terminated and all licenses will have to be trued up.  The problem with this scenario is not just unexpected licensing expense, but when your SPLA terminates, you must sign a new one.  When you sign a new SPLA, you must adhere to the latest SPUR use rights.  As an example, if you had a SPLA prior to the Windows core licensing change, you could continue to report processors.  If your SPLA terminates, you would be forced to license by core now instead of later when your previous agreement (that is now terminated) expired.
  3. Using a VL copy of Office to deploy Shared Computer Activation (SCA).   SCA is specific to Office 365.  If you install Office Pro Plus VL, it goes against the product use rights in which Office (without SCA) cannot be installed on shared hardware.  It takes a lot of negotiation power and time to prove you are SCA eligible, the customer purchased Office 365, and you inadvertently installed the wrong product.
  4. Using License Mobility without License Mobility.  This is by far the most popular compliance trend.  Many organizations do not know what is installed in their datacenter when it comes to customer owned licenses.  Be sure to have the right documentation, addendum, and licensing to ensure compliance.
  5. Leasing an application, hosting the application, and purchasing volume licensing agreement to offer software as a service.   A healthcare company may lease an EMR application, host the application to other healthcare organizations, and license the infrastructure through volume licensing.  If your organization does not own the application you are hosting, you must license it through SPLA.  Self-Hosted for ISV is only eligible for providers who develop and own the application.  This means the code, the rights, everything must be owned by the organization.  Leasing the application and using other plugins you may have developed does not qualify.

I hope this provides you a little insight into the world of compliance.  If you find yourself out of compliant, let us know and we can connect you to the right resource.

Thanks for reading,


Leave a comment

Posted by on July 5, 2017 in Compliance


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

%d bloggers like this: