Migrating Microsoft Software Licenses to Shared Hosting Services

With increased pressure to maintain and increase top line earnings organizations are looking at all options to reduce cost.  One of those options is moving from dedicated data centers to shared hosting services.  There are no shortage of options to choose from when it comes to shared hosting services, which is great for organizations wishing to outsource their data center needs.  

What is often overlooked in the process is software licensing.  Software licensing models are often very different when it comes to shared hosting services.  Microsoft is no exception and the software licensing rules that apply to on premise software are not the same in a shared hosted environment.

Microsoft offers volume licensing customers the option to move certain on premise software licenses to a Microsoft Authorized Mobility Partner.  This option is one of the benefits of active Software Assurance (SA) and requires the customer maintain active SA to continue leveraging the benefit known as License Mobility through Microsoft Software Assurance.

It is also very important to point out that some Microsoft software licenses will have different product use rights when moved to a Microsoft Authorized Mobility Partner.  Customers with heavy investments in private SQL Server clouds may find their costs significantly increasing when they move their SQL Server to a shared hosting service at a Microsoft Authorized Mobility Partner. 

Please note there is a formal verification process Microsoft requires to leverage License Mobility through Microsoft Software Assurance.

I strongly recommend software licensing is front end center when considering migrating your organization to a shared hosting service.

 

Turbo Charge Your SAM Program with the SAM Charter Process Kit: Version 2

Do you want to take your organization's SAM program to the pinnacle of success?  If yes, then you are in luck because SAM Charter has recently released version 2 of the SAM Charter Process Kit.

Most SAM programs struggle to get off the ground, and often they confuse tools as a substitute for people and process.  I often hear I wish there was a turnkey solution to launching my SAM program.  The good news is the SAM Charter Process Kit: Version 2 is the solution you have been searching for and at a fraction of the cost of a professional services engagement.

Rory Canavan has taken his many years of SAM experience and learning's and put them into a single solution set that is easy to understand and implement. The kit is available in three forms: eBook, Process Maps, and my favorite the bundle with the eBook and Process Maps. 

If you make only one SAM related purchase, then it should be the SAM Charter Process Kit: Version 2.  And before you even think about purchasing any SAM tool, you should first invest in the SAM Charter Process Kit: Version 2.

Let the SAM Charter Process Kit: Version 2 be your personal Sherpa to SAM success!

Please click here to learn more about the SAM Charter Process Kit: Version 2

Self Hosted Applications under Product Terms

In looking through the last PUR Microsoft published I noticed an interesting section covering self hosted applications under software assurance was not carried forward to the new Microsoft Product Terms.  I am not sure why, but I thought it was interesting and decided to share it with my readers.

The below section appears on page 72 of the April 2015 PUR, but was not carried over to the new Product Terms.

Changes to Use Rights

"Despite the terms of your volume licensing agreement, we may modify or discontinue the above use rights at any time. However, if we do so, these use rights and the terms and conditions of your license agreement continue to apply to your use of the Self-Hosted Applications under licenses acquired before the effective date of that change until the end of your current term of Software Assurance coverage"

 

Critical Changes to MSDN Use Rights - Update 2

Please click here to read update 1 on this post...

Please click here to read the original post...

After much thought and deliberation on this issue, I have come to the conclusion the language in the new Product Terms is not by chance, and is well thought out and deliberate.  Based on this I would say that contractors cannot use their volume licensed based MSDN to cover them for non-production systems while working at client sites. This would also prevent MSDN users from utilizing any MSDN software on their home systems, including Visual Studio.  Despite the fact that the July 2015 Microsoft Visual Studio 2015 and MSDN Licensing white paper states they can, the Product Terms has legal precedence over the whitepaper and clearly states they cannot.

It would be very helpful if Microsoft would come forward and clarify this, but I do not expect that to happen.  I am on the lookout for an update to the Microsoft Visual Studio 2015 and MSDN Licensing white paper, and will report back if changes are made to its language.

I strongly encourage all customers this issue impacts to speak directly with Microsoft, and only accept written guidance from them.

 

System Center Client Management Suite dropped in August 2015 Product Terms

Ever since the new Enterprise Cloud Suite (ECS) was released and there was no clear bridge path for the System Center Client Management Suite I have been trying to figure out why.  Well the August 2015 Product Terms have answered the why by removing the System Center Client Management Suite from both the ECAL and ECAL Bridge.

In order to soften the blow Microsoft has added a special promotion on page 86 of the August 2015 Product Terms shown in excerpt 1 below.  This language is a bit squishy to me, so I have asked Microsoft if this language actually grants a perpetual license to the System Center Client Management Suite, or just the right to use it while under active Software Assurance (SA).  I am still waiting for an answer from Microsoft.

I would also like to note that excerpt 2 below is from page 14 of the June 2015 Product List, and I cannot find any like language in the July or August Product Terms.  I have to assume any licenses purchased under the new Product Terms will not be eligible for this extended use right.

Excerpt 1

System Center Client Management Suite Promotion

The right to use System Center Client Management Suite will be included with all Enterprise CAL Suite and Enterprise CAL Suite Bridge for Office 365 (with or without Microsoft Intune) licenses ordered through December 31, 2016.

Excerpt 2

Extended Use Rights for Enterprise Cloud Suite Customers

For qualifying customers, the Enterprise Cloud Suite or combination of Office 365 and Enterprise Mobility Suite provides access rights to the component services of Exchange Online Archiving for Exchange Server and System Center Client Management Suite. “Qualifying Customers” are Enterprise Enrollment or Enterprise Subscription Enrollment customers who have active Software Assurance coverage for the Enterprise CAL Suite as of November 30, 2014.

 

Language on Creating & Storing Instances missing in new Microsoft Product Terms

I was reviewing the new Microsoft Product Terms for the language regarding creating and storing instances, which I expected to find under the universal license terms section.  I checked both the July 2015 and August 2015 versions and found nothing.   Excerpt 1 below is from the April 2015 Microsoft Product Use Rights (PUR), which happened to be the last PUR published before the new Product Terms were introduced in July 2015.  As you can clearly see this was part of the universal licensing terms, and starting with the new Product Terms this language is suddenly missing.  When I searched through my library of Microsoft volume licensing briefs I found the November 2013 volume licensing brief titled "Licensing Windows Server 2012 R2 for use with virtualization technologies", and I found the language shown in excerpt 2 below.  

I am perplexed this key language is missing from the new Product Terms, and I do not know if it was an oversight or intentional by Microsoft.  Please make sure to address this in your upcoming agreement renewals with Microsoft.

Excerpt 1

Creating and Storing Instances

You may create and store any number of instances of the software on any of your servers or storage media solely to exercise your right to run instances of the software under your server licenses or your Windows Enterprise license terms.

Excerpt 2

Storing Instances

With a licensed copy of Windows Server 2012 R2 you can make any number of copies of the software and store them on any of your servers or storage media without requiring an additional Windows Server licenses. You can also store instances on a large storage area network (SAN) or store instances on your servers without needing additional licenses for each instance.

Critical Changes to MSDN Use Rights - Update 1

Please click here to read update 2 on this post...

This is an update to my post on July 13th regarding what appeared to be a critical change to where Visual Studio 2015 / MSDN software could be installed and run.  The concern first appeared in the new July 2015 Microsoft Product Terms, which replaced the Microsoft Product Use Rights and the Microsoft Product List. 

The July 2015 Microsoft Product Terms Developer Tools section states the following:

"One Licensed User may use any number of copies of the software and any prior version on any device dedicated to Customer’s use for each User License it acquires."

The concern was based on the addition of the language "device dedicated to Customer’s use".  This was interpreted by multiple independent Microsoft licensing experts that Microsoft was no longer allowing MSDN users the ability to use their MSDN licenses to cover non-production systems at their customer's site, or allow developers to install Visual Studio on their home device.   It is commonplace for contract developers to bring their own MSDN to a customer and have the customer only supply the needed server CALs.

I am very pleased to report the July 2015 Microsoft Visual Studio 2015 and MSDN Licensing white paper clears up any concerns on page 13.  We can all relax and enjoy the same rights we have been accustom to as to where the software can be installed and run.

As for the new language in the Microsoft Product Terms I do not have any insight as to why Microsoft added it.  This language never appeared in the Product Use Rights or Product List for Developer Tools.  If I had to guess the language was added to tighten up most use rights, but should not have been applied to the Developer Tools section.  It would be great if Microsoft were to update the Product Terms to match the white paper.

Please note the Microsoft Product Terms have a higher order of legal precedence than the July 2015 Microsoft Visual Studio 2015 and MSDN Licensing white paper.  Based on the language in the white paper Microsoft's intent is very clear me.  If you want to play it super safe then ask your Microsoft account team to provide an amendment stating there are no changes to where Visual Studio 2015 / MSDN software can be installed and run.

Click here to download the July 2015 Microsoft Visual Studio 2015 and MSDN Licensing white paper