Tag Archives: Office
There’s March madness in college basketball and March madness in licensing. College basketball is over, but licensing is just getting started. In this post, I completed a list of the top 5 questions in SPLA. Enjoy!
1. Can we offer a customer dedicated VMs where they can have Windows-admin access? We want to offer the OS-plattform and let the customer handle applications etc themselves
No. You can offer dedicated VMs, but unless a customer is transferring their licenses over to your datacenter, they should not have admin access. Amazon does a good job of explaining this. Check it out here
2. I am looking at licensing SQL in Azure. My question is can we run multiple instances on a single VM or is it 1 instance per VM? How can we reduce our consumption?
Yes. You can run multiple instances on a single VM to reduce the number of VM’s deployed. This works with Azure, AWS, or even your own datacenter.
3. If we have a hypervisor running 2012r2 datacenter edition. Can I install server 2016 on a VM or does the hyper visor also have to be 2016?
You can install the VM with 2016 but the entire host must be licensed by core if you do. (even if you are also running 2012) Remember with 2016, there is an 8- core minimum per physical processor and is sold in packs of 2 cores.
4. I have a production SQL server fully licenced. We will be introducing a second server that will only receive SQL transaction logs throughout the day. It’s not a hot standby, not even a warm standby. Does it require a license?
As long as that server is passive, log shipping is allowed.
5. We are a cloud hosting provider and find it very frustrating in regard to Office 365 and not being able to use SCA. Any help?
There are specific requirements to become CSP Tier 1. I will say Microsoft has made the requirements easier as it pertains to support. If you are having difficulty becoming CSP Tier 1, it may help to look at partnering. Let us know. firstname.lastname@example.org
Thanks for reading,
The #1 post (by volume) on this blog site is “Office 365 Under SPLA.” (It’s probably what brought you to this article in the first place). For those that read this blog regularly, can you guess #2? Ok…you give up. If you would’ve guessed “Office Needs Mobility Rights” you would have been correct. Can I conclude in my scientific analysis that Office is at the top of everyone’s mind in the hosting industry?
Who remember’s BPOS? Remember that beauty? I used to manage BPOS several years ago. BPOS consisted of Exchange Online, OCS (that’s right…OCS not Lync) and SharePoint online. It was bundled as a package and sold to smaller companies (originally). It was a big deal. For “x” amount of dollars you would get a 5GB mailbox! Google caught on, raised the bar to 10GB mailbox, than 20 and the cloud race still continues today. Mailbox size and price was what everyone talked about. I remember it well. Than Microsoft threw the cloud world a curve ball. “What would happen if we offer Office as a subscription model and call it Office 365” Things started to change pretty quickly. Office as a subscription? “But wait…let’s allow Office to be installed on not one device, but 5! Now the cloud world is really spinning.” What’s next?
Let’s don’t forget about our friend Azure. Who could forget about him? Azure is growing rapidly (talk about a generality but remember I am SPLA Man, not Gartner) and adding new features such as Linux VM’s, ability to purchase using your Enterprise Agreement, and the biggest news of all….ability to install a copy of Office from Office 365. Wait! What?!!!
Let’s take a step back and look at what Office means for the SPLA community. You want to host Office? Here’s what you need. Windows + RDS+Office. There you have it.
Here’s what you can’t do – Under no circumstance can you have your end customer purchase Office under Office 365 and install it in your shared cloud. Don’t argue with me here…you can’t do it. You are probably thinking…well, that’s ok, i will dedicate a VM. Ahhhh….there we go again. Dedicated a customer owned license on a VM. What did I just describe?
Dedicate a VM +shared hardware = License Mobility. What does not have license mobility rights? Office.
Now back to Azure. You might be thinking that Azure is a shared cloud. It is. How can they do it but I can’t? Well, they developed Office and they developed Azure. They can make up the rules to their own game. Check out the online services terms page 22
What happens if you purchase your own Azure agreement to host your SaaS offering for your clients? It doesn’t matter. A hoster leveraging Azure for their offering would not be able to accept end-user Office 365 Office licenses.
So is it all doom and gloom? Not by a long shot. When there’s confusion, when your competitors spend more time worrying about what they can’t do instead of focusing on growing their business, consider that an opportunity. I’ve written 70+ articles on SPLA. It’s not going away and neither are you. I just think you (the service provider) need to get creative. Price is always an issue. Office is an issue today, but it will be something else tomorrow. Again, don’t focus on what you can’t do, it’s time to start thinking about what you can do.
I am going to write another article in which I provide a real world example on how I was able to save a service provider money It’s not revolutionary, but it proves that if your not working with someone who looks at your usage report regularly and makes suggestions to reduce costs, you are missing out. Sounds kind of like a salesman, but I think you will find the article helpful. I can’t change the rules of SPLA, but I can make recommendations in the way you think about your business. It’s time to reconsider our licensing strategy. Stay tuned. In the meantime, here’s a cool glimpse into the future.
Thanks for reading,
Starting a new series on this blog “top licensing questions” Here’s a list of some often unanswered questions…answered! In many instances it’s tough to go into great detail or specific customer scenarios via a blog. Please email me at email@example.com for specific scenarios. Keep in mind, blogging is my hobby and I am relaying information from experience. You should refer to the SPUR for specific/audit questions. (It’s a great read). Microsoft has the final say. I am interested in feedback and/or ideas for new posts; let me have it!
1. Does a service provider need to report an extra Exchange SAL for non-authorized users, such as a conference room?
A mailbox that represents a room is defined as a resource mailbox and does not require a SAL.
2. Can I use the same server I use internally to host software via SPLA?
No. Regardless of the licensing program, the license is always assigned to the hardware/VM. If you choose to assign two licenses from two different programs to one hardware, some of the use rights will contradict each other. SPLA is designed for external consumption whereas internal licensing is designed for your own employees. Good news – SPLA allows 50% of what you are hosting externally to be used internally. Let’s say you host 50 exchange licenses, you can use up to 25 internally. These are not free, just reported under your SPLA. (Instead of reporting just 50 licenses, you would report 75). Check SPUR for more details.
3. Can I install Office on a device without reporting Windows desktop?
No. This would fall under the managed PC use case. There is an addendum that would allow you to rent out a desktop to third parties; to do this via SPLA, there is a “managed PC” addendum. This would require you to license the desktop OS via an OEM license and report Windows 7/8 via SPLA (as well as Office if Office is installed). Ugh. Only other option would be to report Exchange “plus” Skus which includes Outlook. (no other Office components) or install Office on a server and report Windows, RDS, and Office. (RDS & Office by user- Windows by processor)
4. What are the rules of licensing additional users under License Mobility for Software Assurance? Can a service provider license additional users with SALs?
No. In License Mobility for SA scenario, the end customer has to maintain CALs in their perpetual licensing program to access the application servers. It is not possible to license additional users with SALs, because that would mean mixing/matching licensing for one Product. Keep in mind that under license mobility – end customer’s are in essence transferring those licenses into your data center. They can only transfer back after 90 days. To quote the mobility brief (download a copy here ) You may move your licensed software from a third party’s shared servers back to your servers or to another third party’s shared servers, but not within 90 days of the last assignment. Check mobility addendum.
6. What happens if my customer claims to have SA on these licenses but in actuality…they don’t. Am I on the hook?
Yes. You are responsible for your own hosted offering. I would ensure you have documentation of all customer owned licenses AND make sure this is part of your agreement with your customer. You may get audited, but that does not stop you from auditing your customer.
7. Where do I report my SPLA licenses?
Contact the SoftwareONE SPLA team 1-800-444-9890 or SPLA.US@softwareone.com
Stay tuned for more questions but more importantly – answers to these questions!
Thanks for reading,
If I received a dollar for every time I’m asked this question you and I can both retire! Things are changing in the world of data center outsourcing, but for some reason this is still stuck in the mud. Why no VDI today?
1) I have no idea
2) See answer 1
I wrote about this topic earlier, but my hunch is it has something to do with the OEM manufactures. OEM is a big piece of Microsoft business, and they protect it. (Although Surface kind of muddies that theory). As an example of this, if you were to “lease” a desktop to an end customer, you would first need a OEM license pre-installed and use SPLA and/or volume licensing as an upgrade license. So even under a rented desktop model, OEM is still a requirement. If everyone used VDI and dummy terminals – OEM manufactures would be left out of the game. (at least in volume)
The only thing that would change this model is if they received a very high number of requests to offer this through Azure. Look at what happened with Remote Desktop Services (RDS). RDS was never part of license mobility. Azure comes along and before you know it- RDS has mobility rights! Check it out here
That being said, Microsoft can make the rules of their own game, and even know Microsoft can do it does not mean the service provider/partner community can do it. Office 365 is a prime example of this. Under O365, you can take Office and install it on up to 5 PCs. Try that under SPLA and you have to license every PC with a separate Office license, use Windows 7/8 upgrade license, have a OEM on the machine that you own, and sign a rental addendum. That’s why I wrote “office needs mobility rights”
One new capability in the latest SPLA agreement is you can install software on customer owned hardware. BUT guess what? That does not apply to PCs.
I’m not sure if this will ever change. Every conference that I’ve attended the past 10 years partners ask the same question – “Can I provide VDI under SPLA?” I don’t like the word “no” but unfortunately, the answer is “no.”
Would love to hear about your thoughts on the topic. Have you tried Windows server and RDS as an alternative? What about dedicated environments for VDI?
Thanks for reading,
The other day I was on a call with a customer who developed a financial application that takes a customer’s information and then reports it back from Excel. The goal would be to have it deployed via a web browser, possibly using SharePoint. Immediately I thought of Office Web App. Browser based, users could not only read it but edit it as well, sounds like a perfect fit What about the licensing? Since this is their own Intellectual Property (IP) I thought of the self hosted rights for volume licensing. SPLA might be too expensive since users could not be tracked. This is where we got stuck.
Self hosted is a software assurance benefit. It allows volume licensing customers to host their application that runs on Microsoft technology to third parties. I included the terms and conditions directly from the Product Use Rights (PUR) at the bottom of this post (in case you are really bored) but in my opinion this will allow developers to continue to build their applications and utilize volume licensing that offers the greater discount.
As a SAM manager, I was engaged by the customer to review both past and current licensing. Since this was a new offering, nothing was licensed or even deployed yet. Whew…Rule #1 – before building a datacenter make sure the solution fits the licensing. Secondly, this is being provided as a service, not simply allowing external users to access.
What did we advise? In order for a solution to qualify as “self-hosted” all applications must be self hosted eligible. Unfortunately, Office does not qualify. Ugh. There goes that option. Now we must look at SPLA for everything (one unified solution as defined in the PUR). The problem with SPLA is you must license Office STD or PRO to enable Office Web Apps. To add more complexity, Office in a server environment is licensed by user (SPLA) Since user count is expected to be very high, this does not seem to be an economical solution. What I proposed was to get rid of Office. That’s right, I recommended they remove it from the solution and use Open Office. The solution worked and met the compliance guidelines set forth by Microsoft.
In conclusion, I hated my recommendation but went with it in order to be compliant. Microsoft Office is a superior product to “Open Office” If only Microsoft would allow Office to be self hosted eligible, I think it would benefit the service provider, Microsoft, and more importantly the end customer.
Bottom line- make sure if you have your OWN application (not license someone else’s) and you decide to use volume licensing to host, make sure all software is eligible or risk BIG compliance risk.
Thanks for reading.
From the PUR
You must have the required Microsoft licenses and maintain Software Assurance coverage for:
• the Self-Hosted Applications run as part of the Unified Solution; and
• all access licenses used to make the Unified Solution available to external users (See Universal License Terms, Definitions).
All Microsoft software used to create and deliver the Unified Solution must:
• be licensed through a Volume Licensing program that is subject to these license terms (e.g., Enterprise Agreement, Select Plus Agreement, Open License Agreement) and not any other (e.g., Services Provider License Agreement, Independent Software Vendor Royalty License and Distribution Agreement); and
• be marked as ‘Yes’ for ‘Self Hosting of Applications Allowed’ in these license terms
Your software must:
• add significant and primary functionality to the Self-Hosted Applications that are part of the Unified Solution (dashboards, HTML editors, utilities, and similar technologies are not a primary service and/or application of a Unified Solution);
• be the principal service and/or application, and sole point of access, to the Unified Solution;
• be delivered over the Internet or a private network from your datacenter to end users. The Self-Hosted Applications component may not be loaded onto the end user’s device; and
• be owned, not licensed, by you, except that your software may include non-substantive third party software that is embedded in, and operates in support of, your software.
The number one post on splalicensing.com is “Office 365 under SPLA” To date over 20,000 users have read it, several have commented on it, and many more are still asking – what am I missing and why can’t I offer “SPLA Office” in the same fashion as Office 365?
Microsoft recently announced mobility rights for Remote Desktop Services (RDS). I wrote about it here I think that’s a great move by Microsoft as it provides more flexibility for both service providers and consumers. In my opinion, we need Office mobility rights, and we needed it yesterday.
Think about your environment and the licensing restrictions around Office. To legally deploy Office for a customer that has Office 365, you as a service provider would need to have your customer purchase 1 volume licensing copy of Office, install it on your server, and for each user for Office 365, they must allocate one of the five licenses (Office 365 allows 5 installations of Office on 5 devices per user) to access Office remotely. The Office bits on Office 365 has issues with installing it on server. Thus, the reason for a volume license copy of Office. (at least that’s my experience in the past, maybe that’s changed now) Doesn’t sound too bad. Five devices is a lot anyways, and now with RDS mobility rights, the service provider can use the end customers RDS licenses (if they have software assurance). YES!!!!
Ahh…but what about Office? Does Office have mobility rights? The answer is….no. Although the service provider can have customer RDS mobility rights, since Office is installed, the entire environment has to be dedicated. Yes, that includes the hardware and the VM. That’s the issue I struggle with and I am sure many of you do too. Why offer RDS mobility rights but not Office? This would solve some of the issues between Office 365 and the service provider community. Office is expensive for SPLA’s, let’s allow end customers to leverage their existing volume licensing agreements to purchase it and allow service providers to host it in a shared hardware/ dedicated VM using mobility rights? Think of how many users would purchase Office under Office 365 if they did this? Or if they didn’t purchase Office 365, they would at least need to purchase Office with Software Assurance. Think of how many service providers would push volume licensing on behalf of Microsoft and the resellers if they allowed this? Either way Microsoft, service providers, and more importantly the end customer would win.
Thanks for reading,