RSS

Tag Archives: Office 365

Top 5 Licensing questions…Answered

  1. If a customer has 4 x SQL Server Standard (8 cores), does that mean I will also need to have 4 x SQL-SAL?

There’s no server + CAL model in SPLA.  You license either per core or per user depending on the product.  Remember, SAL is not licensed per server, but for each user that has access to that server.  Your question indicates you might believe a SAL is licensed per server which is not true.

2.  Is MSDN available through SPLA?  Is it through Azure?

MSDN is not available in SPLA, but you can license the individual components through SPLA.   If an end-user would like to bring their MSDN license over to your datacenter, you must dedicate the solution for your customer.  Yes, Amazon must play by the same rules.  Oddly enough, Azure (which is shared) does allow MSDN to be transferred over to their datacenter.

3. I received an audit notification.  Should I respond?

Yes. But don’t work on their time, work on yours.

4.  If I signed the SCA addendum, do I need to sign the new QMTH addendum?

Unless you are planning on hosting Windows 10 you do not need to sign the new addendum.

5.  If I buy from a CSP indirect partner, do I qualify for QMTH?

No.  Your company must be CSP 1 tier authorized in order to qualify.

Thanks  for reading,

SPLA Man

Advertisements
 
Leave a comment

Posted by on September 11, 2017 in Top 5 Licensing Questions

 

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

Top 5 CSP Questions…Answered

Here are a few hot topics this week around CSP.  Enjoy!

What would happen if I sell myself Office Pro Plus through my own CSP authorization?  Can I do that?

No.  You cannot sell yourself Office 365 Pro Plus licenses.  You can purchase it through any volume licensing program or through another CSP provider.  Might be a good way to check out the competition support processes though!

If you are CSP authorized in Australia, but have customers in UK, can you resell Office 365 through CSP?

No. You can only resell in the region in which you are authorized. 

If my end customer purchased Office 365 Pro Plus through Volume Licensing, can I host it from my datacenter if I am QMTH authorized?

Yes. The end customer can purchase from any licensing program as long as it is Office 365 Pro Plus version.  As the service provider, you must be QMTH authorized.

 

If I purchase CSP licenses indirectly from my distributor, do I qualify for QMTH?

No.  You must CSP Direct authorized in order to that.  You cannot purchase from a distributor and offer VDI or Office Pro Plus.

If I sell Azure through CSP, how do I know which region my data is located?

With Azure, you get to pick the region.

If I sell Office 365 through CSP, which region is my service hosted from?

The address on the invoice determines the location of the services. 

***Watch out for the new Microsoft Cloud Agreement (MCA) coming in September.  You can download the old version here

Thanks for reading,

SPLA Man

 
1 Comment

Posted by on August 24, 2017 in Cloud Solution Provider Program

 

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

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

 
Leave a comment

Posted by on August 11, 2017 in Office 365

 

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

How the Microsoft CSP Program Indirect Program Works…Directly

The CSP Indirect program is a quick and relatively painless way to get started with Office 365 and other cloud solutions.  In this article, we will review how it works, how it doesn’t work, and things to consider before signing up.

The point of this blog is to make things simple; let’s stay with that concept for a moment.  In the simplest terms, CSP Indirect means you are “indirectly” selling solutions to your end customers.  Why indirect?  In this model, you do not hold (perhaps you do but don’t want to mess with it) the qualifications/authorizations to sell Microsoft cloud solutions directly to your end customers from Microsoft, you must purchase through a distributor and then sell to your customers.  This could mean higher pricing, working with third-party systems instead of your own, and procurement.  One of the biggest disadvantage (sometimes an advantage) is there’s no direct support line to Microsoft.  If something goes wrong, you contact your distributor, who works directly with Microsoft.

As a cloud provider, you are also limited in some of the solutions you can sell to your customer from your datacenter environment.  Take as an example, the Qualified Multitenant Hosting Addendum (QMH).   If you are currently purchasing licenses through an indirect partner, you cannot host Windows 10 E3/E5 from your shared cloud environment. Only authorized CSP Direct partners have that luxury.  The same is true for Office Pro Plus and other desktop applications.

The advantage of CSP Indirect is you do not have to spend resources (including investing in additional staff and funding a platform) That’s all on the distributor.  You can think of CSP Indirect as white labeling Office 365.  It’s not technically white labeled (your end customer knows they are getting Office 365) but the billing comes from you.  CSP Indirect means you are leveraging someone else’s resources to deliver a solution to your end customers.  You still bill your customer and can provide basic support, which has its benefits.

Is CSP Indirect right for your business?  If you are just getting started in selling Office 365 or are currently purchasing Office 365 licenses on behalf of your customers from the Microsoft portal, CSP Indirect is the way to go.  If you are a large provider who has the resources, personnel, and funds to support CSP Direct solution, I would recommend going CSP Direct over Indirect.

In either program, you do not get off without knowing the licensing.  That’s for another article.

Thanks for reading,

SPLA Man

 

 

 
 

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: , , , , , , , , , , , , ,

Yikes…how to move from one cloud to the next.

The latest buzz word in this crazy IT world in which we live is not “Cloud” it’s “Hybrid Cloud”.   Even the definition of hybrid cloud has evolved throughout its short existence. Having a mix of on premise workloads and cloud workloads has transformed into having workloads spread throughout different cloud vendors as well.  “Cloud Sprawl” is born and guessing is here to stay.

In this article, we will review how the licensing works to move a customer’s workload from one cloud to another; customer’s owned licenses back to on premise; and customers on premise licenses back to your cloud.  As the title of this article states..Yikes!

Moving away from your cloud to another cloud

So, your sales rep “accidentally” promised the world to your customer that he/she could not deliver.  Unfortunately, they now want to move to another provider.  First thing to do is fire the sales rep.  Second thing to do is read your SPLA agreement.

When you sign a SPLA agreement (or any Microsoft agreement) your license keys are your license keys.   The data is not yours, but the keys are (at least while you have an active agreement – remember, SPLA is non-perpetual license). License keys are not to be transferred, resold, etc. over to another datacenter provider.   Where does it say that?

In section 6C, page 5, of the 2017 SPLA Indirect Agreement “Copying and distribution of Products and Software documentation” states: “customer may distribute original media or software contains products only to outsourcing company and affiliates.”  Another cloud provider is not your affiliate or outsourcing company, they are your competitor.  The section continues: “Customer may distribute original media or software containing client software and/or redistribution software to its end users.”

What that statement is saying is the service provider can provide the image to their client but not to another service provider.  If they do this, Microsoft requires the license keys to be removed first.  Remember, your keys are your keys, not theirs. As mentioned, the data is not yours either.  An end customer has the right to transfer their data from your datacenter to another provider.  You can also transfer the media to your customer, but not to another service provider as the statement suggests.

Over the years, the transfer of data, transferring images, and using outsourcing companies has made it difficult to track which media/keys belong to which company.  My recommendation is to have language in your agreement that is like the one in your SPLA to protect you.  Is this a gray area?  Absolutely.  My other recommendation is that no matter which keys belong to which organization – be sure to license the environment correctly; in the end, that’s the most important part.

Customer’s owned licenses back to on premise 

The same sales rep screwed up again.  They promised the customer that by moving to your cloud environment they would never be audited again.  Guess what?   They got audited.  Now they are upset and want to move back to on premise.  How does the licensing work?

In this situation, let’s assume the customer is moving workloads that have software assurance (SA) and are using license mobility. (even if they didn’t, same rules would apply.  I just like using license mobility because it’s more common).   Whenever an end customer transfers their own licenses (not SPLA) it’s important to read the Product Terms, not just the SPUR.  The Product Terms is for volume licensing, which applies to customer owned licenses.  The SPUR, as we all know is for SPLA.  Two different programs, two different use rights.

Page 84 (good Lord this is a massive document) of the 2017 Product Terms states “Customer (your end customer) may move its licensed software from shared servers (license mobility) back to its Licensed Servers or to another party’s shared servers, but not on a short-term basis (not within 90 days of the last assignment).

When you buy a license through volume licensing (VL), you assign that license to a server.  That’s one of the reasons you cannot mix SPLA and VL on the same server (different use rights).  When you assign that server to a different server farm (another datacenter provider) that server license cannot move within 90 days of assignment.  If your end customer gets upset and demands you transfer their licenses back to their premise, you can pull out this little blurb in the Product Terms.  I would recommend having language in your agreement that states the same.

You might be wondering – “isn’t the benefit of Software Assurance the ability to move workloads freely without worrying about the 90-day rule?”  That’s true and I’m glad you brought that up.  If it’s within the same server farm, workloads can move freely.  Pay attention to page 84 of the Product Terms as well as the definition of a server farm.

One of the best lines in the Product Terms happens to be on the same page (84).  “Customer (again, customer in this example is your end customer) agrees that it will be responsible for third-parties’ actions about software deployed and managed on its behalf” I would definitely include that statement with your customers.

Moving back to your cloud

You gave your sales rep an ultimatum, win the customer back or lose your job!  Your sales rep won the customer back.  Now your customer can move back to your cloud, but make sure you follow the license mobility use rights as mentioned above.  Remember the 90 day rule.  Once a customer assigns a license back to their premise, they have to wait 90 days to move it back.  Secondly, if they do not have SA, you must dedicate the entire infrastructure for your customer.  Dedicated means the hardware used to support the solution.

The moral of this story?  Make sure you have a good sales rep!  Secondly, read the SPUR, Product Terms, SPLALicensing.com, and have language written in your agreement to protect yourself.  Lots of talk about moving to the cloud, moving away from it is just as important.

Thanks for reading,

SPLA Man

 

 

 

 

 
Leave a comment

Posted by on August 3, 2017 in Compliance

 

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

 
%d bloggers like this: