RSS

Category Archives: Office 365

Licensing Office Online for External Users

What happens if you have end customers who want to use Office Online for external users (non-employees of your organization).  Is that SPLA?  In this article, we will break down Office Online through three programs – SPLA, Volume Licensing, and CSP.

SPLA

If you are hosting Office for another organization SPLA definitely fits.  As an example, if you provide DaaS to your customers who are also licensed for Office, they can access Office Online.  In this model, you license SharePoint (requirement for Office Online) Office by user, RDS per user, and Windows + SQL Server.   Very expensive to simply offer a customer the ability to view and edit documents online.

Volume Licensing and Office 365

Office Online was added as a Software Assurance benefit for Office in 2016.  End customer’s who simply want to view documents can download it directly from the Volume Licensing Services Center (VLSC).  End customers that require document creation, edit/save functionality will be required to have an on-premises Office license with Software Assurance or an Office 365 ProPlus subscription. Any customer that purchased an Office 2016 suite through Volume Licensing before August 1, 2016 will not require SA through August 1, 2019.   After August 1, 2019 they must buy SA for any on-premise Office licenses.

According to the Product Terms (May 2016) “If Customer has a License for Office 365 Pro Plus, then Customer may use Office Online services.  Each of Customer’s Licensed Users of Office 365 Pro Plus may access Office Online services for viewing and editing documents, as long as they are also licensed for SharePoint Online or OneDrive for Business.”  It’s the last sentence that stings.  In other words, you want Office Online?  Better buy Office 365 E3.

Office Online for CSP

The same rules apply.  In this scenario, the hosting company could sell Office 365 E3 through CSP program to their end users.  In CSP, the end customer is paying month – month and paying for support.

Thanks for reading,

SPLA Man

Advertisements
 
Leave a comment

Posted by on August 11, 2017 in Office 365

 

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

Details of the Qualified Multitenant Addendum

There’s been a lot of talk as of late about the new QMTH addendum.  I’ve written a couple of articles on the topic here  In this article, we will summarize what is written in the addendum so there’s no surprises.  I listed some (not all) of terms and conditions to ensure you are up to speed on the latest developments.

  • CSP Membership – You (or affiliates) must be a Direct CSP partner.  This means you cannot leverage an Indirect CSP partner for this program.  In other words, if you receive CSP licensing from Ingram Micro or SherWeb (as an example) your partnership with those distributors/partner does not qualify for QMTH.  Your organization must be CSP Direct authorized, not your partner.
  • Must meet the system requirements – System Requirements can be found here
  • Have an active SPLA agreement.
  • Reporting Requirements – You will always need to report underlying licenses in SPLA.  Those underlying licenses could be any software to deploy a VDI solution – (Windows Server and RDS).   In addition, you must report (by the last calendar day of each month) the Windows 10/O365 licenses deployed.  This is manual, meaning you will send an email to the QMTH alias for submission.  Once automated reporting is available, you must enable Microsoft’s automated reporting tool.  Microsoft will use the tool to collect your customer’s organization ID and tenant ID as well as the total number of users accessing the software.
  • As the provider, you must report to your SPLA Reseller the program administrative fee.  If you are currently in the SCA program, you will be familiar with this SKU.
  • As the provider, you must make all education materials publicly available.  You cannot just sign up for CSP, the education material should be like what’s on the QMH website.
  • For each per user subscription to Windows 10 Enterprise, the end-user can only access up to four (4) instances of Windows 10 either on Azure or you, the QMTH hoster.  This is like the SCA program in which the end user has five (5) instances of Office Pro Plus, Windows 10 works the same way.

Listed above is a summary.  I encourage you to reach out to your Microsoft rep for additional information.  I am happy to review it further, it’s a new program with pluses and minuses.  Be sure to understand the minuses first 🙂

Thanks for reading,

SPLA Man

 

 
Leave a comment

Posted by on August 3, 2017 in Office 365

 

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

Top 5 CSP Questions….Answered!

  1. Is the SCA addendum removed now that Microsoft announced the Qualified Multitenant Hoster addendum?  Yes.  SCA has been removed and replaced with the QMH addendum.
  2. If I have a CSP Indirect/Tier 1 authorization, can I resell Azure Stack but license Windows Server through SPLA?  Yes.  You will pay the base consumption rate because you A) Purchased the hardware through an authorized dealer and 2) paid for the Windows license through SPLA.
  3. If I am not authorized for CSP, can I still sell Office 365 to my end users?  Not in the general sense.  What you can do is resell CSP through a distributor or authorized CSP Indirect/Tier 2 partner. You can also partner with a CSP Direct partner to offer the solution.  They would resell the actual license but you can provide services on top of it.
  4. I am a SPLA partner who wants to resell Office to my end users.  What are my options?  You can sell Office through SPLA and include RDS and Windows.  You can become CSP Direct authorized and use the QMH addendum mentioned above.  You can also use end customer owned Office licenses and host it in a dedicated environment.
  5. Will Microsoft offer QMH for Indirect partners as well?  Not at this time.  You must be CSP Direct to qualify, not Indirect.

Lots more on this.

Thanks for reading,

SPLA Man

 
Leave a comment

Posted by on July 17, 2017 in Office 365

 

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

VDI Under SPLA? Maybe it’s possible after all – Multitenant Hosting Rights for Windows 10

Good news for those who have customers who want you to host Windows 10 in your shared cloud environment –  they might now have that as an option.  Microsoft recently announced “Multitenant Hosting Rights for Windows 10.  You can read the announcement here

What is it?

Allows customers who purchased qualified Windows 10 licenses the ability transfer those licenses over to a Qualified Multi-Tenant Hoster shared datacenter environment.

Why is this important?

For years SPLA partners have asked for VDI in SPLA.  Although this is not technically VDI in SPLA, is does provide an avenue to implement a virtual desktop session from your shared server environment.  At the end of the day, it gives your end customers deployment options.

Can I still license Windows Desktop in SPLA?

No.  Windows desktop licenses were removed last year.  You can read/download the lease agreement that outlines the details here

What are the requirements?

To no surprise, the SPLA partner must be CSP Tier 1 authorized.  They must also sign the Qualified Multitenant Hoster addendum and have an active SPLA with Microsoft.  To get the QMH (another Microsoft acronym) you can contact info@splalicensing.com or your Microsoft Reseller.

What happens if I offer dedicated environments?  Do I still need the addendum?

No.  If it is 100% dedicated (isolated hardware) you can always transfer end customer  licenses over to your datacenter environment.  Whenever it is shared – VM or hardware, you must consider SPLA or in this case the QMH addendum)

When is it available?

Program will be available August 1, 2017 for VL and September 6, 2017 to transact in CSP.

Can I bundle my customers Office solution they purchased as well as Windows 10 to offer a complete VDI experience?

Yes.  This is a great way to bundle different desktop applications.

Conclusion 

If you provide IaaS to your customers, this is definitely something you should consider.  Any time you can offer your customers the ability to leverage existing investments the better.  Azure is not going away.  In fact, you don’t have to be QMTH authorized to leverage Azure as your datacenter provider.  Please review the announcement, there will be a lot more information on this in the coming days.  I will also write out several scenarios to make this more simple.  As always, you can email me at info@splalciensing.com

Thanks for reading,

SPLA Man

 

 

 
2 Comments

Posted by on July 12, 2017 in Office 365

 

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

CAL’s, SAL’s and Multiplexing. 101 Licensing for on premise and cloud environments

 

In this article, we will take a closer look at CAL’s and SAL’s…what they are and how to license them.  We will also look at the User Subscription License (USL) for Microsoft Online Services.

Client Access License 

A Client Access License (CAL) provides the right to access a server.  Depending on the environment and product licensed, a CAL can either be a user or a device.   Many resellers, consultants, and even Microsoft, make it a lot more complicated than it needs to be.  The biggest trick to CAL licensing is remembering it is just a “right” not a technical requirement to access the server.  In other words, you can spin up a server, users can access it (in most cases with or without a CAL) and away they go.  Sounds great, but it’s not compliant, and I would argue that is the #1 reason customer’s fall victim to compliance.

SQL is a great example of this.  When I go to my SharePoint site, I pull reports, store information, share information, and perform many other tasks.  What I don’t know is SQL is used in the background to provide access to this information.  Did I log into a SQL Server?  No.  Did I “use” SQL?  Yes.  This is where multiplexing come into play. Multiplexing uses hardware and/or software to pool connections.  The best way to know if a user needs a license (and I’ve said this before) is to ask yourself “If I remove this from my hosted solution would it still work the same as it did prior?” If you answer “no” you need a license.  If your SQL Server is licensed in the Server/CAL model, you’re required to have CALs for any User or Device that accesses that application directly or indirectly. Very few users in an organization have credentials to a SQL Server.  One way to eliminate some of the risk with SQL is to license by core.  Cores allow unlimited number of users to access the server.  If they use the server or not, they are covered.

SAL Licensing

Under SPLA there is a Subscriber Access License (SAL).  SAL’s are licensed by user only (there are very few exceptions such as desktop applications and System Center).  Like a client access license, a SAL license is not concurrent.  This is important, since other vendors are based on concurrent licensing.  SAL is like your cable bill, your provider is going to charge you regardless if you turn your TV on or not, SAL licensing works the same way.  I’ve written about this before but it’s worth repeating – SAL is for any person that HAS access not who does access.  Unlike CAL’s, there is no need to purchase a server license in SPLA.

Online Services

To add a bit more complexity, let’s review Microsoft Online Services.  If you license Exchange Online or an Office 365 Suite, you will purchase a User Subscription License (USL).  A USL provides a user access to the online solution.  Unlike a CAL and like a SAL (that’s a mouthful) you do not need a server license to access the solution if it’s online.  If you want to run anything on premise or in another third-party datacenter, you would require a server license.  In other words, if you have SharePoint Online, the USL license will provide on-premises rights (essentially CALs) in addition to their online rights. This allows for the ability to migrate over time and have hybrid environments without incurring additional cost.  Keep in mind, when you run hybrid, you do require a server license on premise.

Additionally, if you to purchase an online suite (Exchange Online, SharePoint Online, Skype) you can run pieces of the suite on premise. For example, maybe you want to keep SharePoint on-premises but move Exchange to the cloud. An Office 365 Suite includes both online and on-premises rights for each product in the suite, which means you don’t have to pay for the E Suite and then buy Exchange CALs separately.   Just remember the server license!

Summary

It is very important to understand the licensing rules before purchasing any software.  There has and always will be a difference in the way in which technology can be deployed and the way it must be licensed.  Don’t waste money, time, and effort planning a cloud solution without considering the license impact.  I was on a call recently where a customer wanted to leverage their Windows Server with Software Assurance in a shared public cloud.  Unfortunately, Windows is not license mobility eligible.  They worked with a consultant or “expert” who told them one thing, but the rules state otherwise.  Yes, maybe they can take advantage of Windows HUB, but Azure unfortunately was not the right fit.  Pay attention to the license rules, it can save you.  Question?  Email info@splalicensing.com

Thanks for reading,

SPLA Man

 

 

 
6 Comments

Posted by on June 30, 2017 in Office 365, SPLA General

 

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

Office Under Office 365 and Shared Environments…Can we do it or not?

There’s a rumor that Microsoft will allow a service provider the ability to host Office licenses under Office 365 in a shared cloud environment.  Is the rumor true?  Yes, it’s true.  But with everything in the world of licensing there’s always a catch.

For those that have read my blog for a while know that this blog is not a news source, but an education source.  I don’t care about late breaking news, I just want you to get the licensing right, the information right, and be profitable.

So what does Office under Office 365 really mean?  Some time ago, Microsoft created a use right titled “Shared Computer Activation”  For those playing at home this is code for installing end user Office license from O365 in a shared cloud infrastructure similar to license mobility.  In the past, this was only available in Azure.  (imagine that).  Fast forward to today and Microsoft is opening it up to the service provider channel as well.  Good news for you, and even better news for Microsoft.  If you would like to use this use right (SCA) you must meet the following criteria:

  1. You must be authorized for  Cloud Solution Provider Program (CSP Tier 1).  Thats why it’s good news for Microsoft.
  2. You must be managed by a Microsoft hosting team member.
  3. You must be an authorized SCA partner.  (Licensing Addendum)

If you don’t know if you are managed, let me know – I can see if you are.  Typically this is for SPLA partners that report not only high SPLA revenue (although not necessarily), but are also strategic in marketing activities with Microsoft.  If you are international, let me know and we can look into getting US authorized as well.  You can email me at info@splalicensing.com to learn more.  I also have a cool powerpoint.  (well, about as cool as powerpoint’s can go).  Although a bit out dated, here is a good overview as well on SCA: https://technet.microsoft.com/library/dn782860(v=office.15).aspx

Last, I sit on a licensing panel and would love to review the different use cases for this program.  Let me know how you may/may not benefit from Shared Computer Activation and we can voice our collective opinion to Microsoft.  info@splalicensing.com

There’s also a big change for rental PC’s.  Little teaser for an upcoming blog post.

Thanks for reading,

SPLA Man

 

 

 

 

 

 

 

 
3 Comments

Posted by on January 25, 2016 in Office 365

 

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

Is No News Bad News?

It’s the fall season here in the United States – the leaves are changing, weather is FINALLY getting cooler, and it’s time for our friends in Redmond, WA to make an update.  In this article, I will highlight some upcoming changes (or lack thereof) to SPLA.

Last week I was in San Francisco visiting with the resellers and Microsoft to discuss SPLA and other initiatives.  The good news? There are no major licensing changes.  Bad news?  There are no major licensing changes.

Why is that bad news?  Well, I was hoping Microsoft would announce Office mobility rights.  I really think this is a miss with Microsoft.  It would encourage your end customers to invest in Office with Software Assurance and offer a more complete desktop as a service solution.  Do you agree?

Here’s my take. I believe Microsoft will allow your end customers to invest in Office via Office 365.  Wow, there’s a surprise right?  But I do believe Microsoft will allow your end customer to take (1) of the (5) installs allowed under Office 365 and transfer it to your datacenter.  In doing so, you would be allowed to offer a shared infrastructure, dedicated VM (Similar to License Mobility).  This is my opinion, but something I think they would entertain.  I don’t think they will offer regular Office (outside of O365)to be transferred over in this capacity without dedicating the infrastructure.  Why?  To encourage Office 365 sales of course!  Again, just my opinion. And NO, you cannot do this today in a shared environment.

So what about Windows Desktop (Windows 10)?  Will this ever have mobility rights?  I am guessing not.  What about in Windows Azure?  Perhaps.  Going back to my point about Office, by allowing Windows 10 in Azure would encourage Azure sales.  Maybe this will happen sooner than later.  Check out this article by my friends at ZDNET  Get ready hoster’s, there might not be a licensing change, but change is definitely on the horizon.

Thanks for reading,

SPLA Man

 
2 Comments

Posted by on October 10, 2015 in Azure, License Mobility, Office 365

 
 
%d bloggers like this: