RSS

Tag Archives: Microsoft Cloud

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 info@splalciensing.com if you have additional questions.

Thanks for reading,

SPLA Man

 

Advertisement
 
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.  info@splalicensing.com

Thanks for reading,

SPLA Man

 
Leave a comment

Posted by on July 5, 2017 in Compliance

 

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

More Dynamics 365 Fun

Quick update for those interested in Dynamics 365 for SPLA and what you should remember when selling to your customers.

  1. No Enterprise Plans in SPLA
  2. No PowerApps in SPLA
  3. Transitions SKU’s are available in SPLA
  4. More differences found here

Not all bad news but not all good either.  You can read more about my opinion here

Thanks for reading,

SPLA Man

 
Leave a comment

Posted by on June 1, 2017 in Dynamics 365

 

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

The Cloud Insider Times – Hosted Email Edition

We read article after article, use rights after use rights, to provide you the best and accurate information.  The Cloud Insider News takes articles written by you and others to tell your story and help educate the community.  In this edition, we take a look at Hosted Email.  Have a hot topic? Email info@splalicensing.com

Intermedia.Net New Intermedia Email Protection platform delivers multi-layer security

Vaultastic– I am already using Office 365 on the cloud, do I still need a separate email archiving solution?

Wired – Google Just Made Email a Heckuva Lot Easier to Deal With

CRN.Com – RapidScale Acquires Vonage’s Hosted Infra Business For Expanded Desktop-As-A-Service Portfolio

1 &1  – Phishing & Spam – how to identify fake customer communication via e-mail

military-technologies.net – ISPs or MSPs providing email services based on MailEnable, Zimbra and cPanel can now also sell Email Archiving services based on Vaultastic

MSPMentor.Net/SherwebWhy Time is Running Out on Hosted Exchange

Zimbra.Org-  Pluggins that extend the collaboration suite

Microsoft – How the City of Golden simplifies email management with the cloud

gcn.com – Is on-premises being killed by the cloud? Not necessarily.

Forbes The 10 Email Commandments You’re Breaking Every Day

Abovethelaw.com Do This Before You Send An Angry, Emotional Email That You’ll Regret

Thanks for reading,

SPLA Man

 
 

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

Transition SKU’s for CRM Hoster’s Available Thru October, 2019

For Dynamics hosters worried about all the changes with CRM have until October 31, 2019 to license the transition SKU’s in SPLA.

Although good news and provides some flexibility, the transition pricing is still higher than current CRM licenses.  As an example, Basic CRM SKU transition pricing for Customer Service is almost double!

Transition pricing is available to ease transition to the new Dynamics 365 pricing model.  It is also designed for current CRM customers, not new customers.  To learn more about Dynamics 365, please check out Dynamics 365 Licensing for SPLA

Thanks for reading,

SPLA Man

PS- Dont forget to license SQL and Windows with CRM!

 

 
Leave a comment

Posted by on May 15, 2017 in CRM, Dynamics 365

 

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

Microsoft Online Services Terms – What you need to pay attention to before signing your Azure agreement

Article update (April, 2018 ) We created a new website called MSCloudlicensing to help SPLA and CSP partners understand the different program options and use rights available to them. The new website is www.mscloudlicensing.com it’s designed to be a collaborative platform that includes a forum to ask and answer licensing questions, document library, and licensing articles.  Check it out, it’s free. 

There’s a lot of benefits to moving to Azure, I’ll let your Microsoft account team review them with you.  On this website, we are not that concerned about the benefits, all we care about is the licensing.  In this article, we will review the Microsoft Online Services Terms.

What is the Microsoft Online Services Terms?  First starters, it used to be called Microsoft Online Services Use Rights or MOLSUR for short (or long).   It is now called OST pronounced OAST when speaking to Microsoft.  Basically the OST defines how you may consume online services through Microsoft.  You can download a copy here.  Although your legal team should review the document in its entirety, below are some of the highlights I think you will find relevant and are often overlooked.

License Reassignment 

“Most, but not all, SLs may be reassigned. Except as permitted in this paragraph or in the Online Service-specific Terms, Customer may not reassign an SL on a short-term basis (i.e., within 90 days of the last assignment). Customer may reassign an SL on a short-term basis to cover a user’s absence or the unavailability of a device that is out of service. Reassignment of an SL for any other purpose must be permanent. When Customer reassigns an SL from one device or user to another, Customer must block access and remove any related software from the former device or from the former user’s device.” (April, 2017 OST)

What does this mean?

Most Microsoft products cannot be reassigned on a short-term basis, that’s why Microsoft has the use right called license mobility.  In short, pay attention to which users are assigned a license and if/when they no longer need the service.

Hosting Exception “Customer may create and maintain a Customer Solution and, despite anything to the contrary in Customer’s volume licensing agreement, combine Microsoft Azure Services with Customer Data owned or licensed by Customer or a third party, to create a Customer Solution using the Microsoft Azure Service and the Customer Data together. Customer may permit third parties to access and use the Microsoft Azure Services in connection with the use of that Customer Solution. Customer is responsible for that use and for ensuring that these terms and the terms and conditions of Customer’s volume licensing agreement are met by that use.” (April, 2017)

What does this mean?

It allows you (a service provider) the right to use Azure as a datacenter provider.  The last sentence is very important in the above definition “Customer is responsible for that use and for ensuring that these terms and the terms and conditions of Customer’s volume licensing agreement are met by that use.”  In the above definition,  “customer” is you.  If you use Azure as a datacenter provider, purchase Azure via your own volume licensing agreement, and use SPLA for user based products (e.g. RDS) you must follow the OST, Product Terms, and the SPUR!

Azure Services Limitations

Customer may not “Allow multiple users to directly or indirectly access any Microsoft Azure Service feature that is made available on a per user basis (e.g., Active Directory Premium). Specific reassignment terms applicable to a Microsoft Azure Service feature may be provided in supplemental documentation for that feature.” (April, 2017 OST)

What does this mean?

Sounds similar to a SAL license right? “Directly or Indirectly access any Microsoft Azure Service.”  Although if you are using Azure as your datacenter provider, the likelihood of you consuming user based licensing through Azure is not very high.

Security

I encourage you to read the security measures and policy’s set forth by Microsoft for their online services.  You can read it here.  I included a breakdown of the difference compliance and security certifications below:

Microsoft Online Information Security Policy (as of April, 2017)

Online Service ISO 27001 ISO 27002

Code of Practice

ISO 27018

Code of Practice

SSAE 16 SOC 1 Type II SSAE 16 SOC 2 Type II
Office 365 Services Yes Yes Yes Yes Yes
Microsoft Dynamics 365 Core Services Yes Yes Yes Yes* Yes*
Microsoft Azure Core Services Yes Yes Yes Varies** Varies**
Microsoft Cloud App Security Yes Yes Yes No No
Microsoft Intune Online Services Yes Yes Yes Yes Yes
Microsoft Power BI Services Yes Yes Yes No No

 

Last and certainly not least, I get asked A LOT about language that you should include as a service provider.  I would encourage you to create your own online services terms for your hosted offerings.  Too many providers do not have basic language around compliance, licensing, and overall use rights.  At a minimum, you should include a copy of the End User License Terms for SPLA.  If you do not have a copy, please contact your reseller.  If you forget to include licensing terms and conditions, you could be on the hook during an audit.  Don’t be on the hook.

Thanks for reading,

SPLA Man

 
Leave a comment

Posted by on April 24, 2017 in Uncategorized

 

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

Top 5 Questions…Answered

Where can I get my license keys for CRM?  My Microsoft contact can’t seem to find the answer and my reseller doesn’t know either.  Any ideas?

For CRM and D365 you can download them directly from the VLSC website.  All other Dynamics products need to go through the License Key Creator Tool.

If I am a CSP Tier 1/direct provider, can I sell CSP to another CSP Tier 1 provider? 

Yes. There are no limitations as to who you can sell to.  Good luck!

Is CSP replacing SPLA?

Not entirely.  I am not Microsoft but I can see the similarities.  In the end, they are both Microsoft programs, how they consume it doesn’t really matter.  The only drawback to SPLA (In Microsoft’s eyes) is the service provider has the option of offering other software outside of Microsoft.  Exchange as an example, could technically be replaced with Zimbra.  If they use Office 365, the customer is using Office 365.

I offer desktop as a service.  When can we expect VDI to be available in SPLA?

Never.

Will I get audited?

Yes.  Make sure to read the MBSA agreement that you signed.

Thanks for reading,

SPLA Man

 
Leave a comment

Posted by on April 24, 2017 in Top 5 Licensing Questions

 

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

The Cloud Insider Times

In this edition of The Cloud Insider Times, you will find articles on the likes of Google, Amazon, IBM, Veeam, and the infamous Shared Computer Activation (among others) If your company would like to be included in future articles, please email info@splalicensing.com
Computer Business Review – Three Private Cloud Myths Busted!
 
Leave a comment

Posted by on April 20, 2017 in The Cloud Insider Times

 

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

Epic Community Connect and SPLA

The healthcare community has increased concerns with the way they have deployed (and licensed) their electronic medical record (EMR) software such as Epic Community Connect and others.  As a reader of this blog, you know that when you deploy software for the benefit of a third party (non employee) SPLA must be part of the conversation.  The only exception to this rule is if you actually own the code to the software you are hosting.  In other words, if you developed the software, you can use your own volume licenses to host your software.  If you host a third party software (such as Epic) you must license this in SPLA.   In most cases, many healthcare companies do not own the application, but lease it from the EMR vendor.

Rewind a few years and let’s pretend you are a large hospital who partnered with Epic to provide best in class patient record management for your clients, doctors, and other clinics. Your Epic deployment resides on a Windows Server, SQL Server, and RDS.  As the IT director, you purchased several server licenses and hundreds of Client Access Licenses (CAL) to cover all the external users.  You think you are covered; no one mentions you need to license this via SPLA.  Your reseller didn’t tell you, Microsoft didn’t tell you, and for that matter the vendor didn’t tell you.  You think all is well based off the information you received.  Fast forward 3 years and your volume licensing agreement is up for renewal.  Someone on the licensing side informs you that you shouldn’t true-up licenses or renew your agreement under volume licensing, you need to license SPLA.  You think that’s fine, if you must license under a different program who are you to argue. But what about all those license you already purchased and own?  Unfortunately, you cannot return them, you must allocate those internally.  You think to yourself that’s fine, except for one minor detail…. you purchased hundreds of CALs and you do not have hundreds of employees; those license you own are essentially worthless.  On top of everything else, you just received an audit notification.

Why would they receive an audit notification?  Once a vendor recognizes you have been under-licensed, the vendor might want to dig in deeper to see how long you have been out of compliant and if you purchased enough licenses to cover all the users.  In 90% of all audits, the customer is under-licensed.  Now you own licenses you don’t need, but should’ve purchased more because you don’t own enough licenses to cover all external users initially.  The vendor will want you to pay the delta of what you should’ve paid under SPLA and what you purchased under volume licensing (plus an audit fee).

If you are a healthcare provider and have been notified by Microsoft or any other vendor, please contact us.  We have found that in many cases the licenses report is not always 100% accurate.

Thanks for reading,

SPLA Man

 
Leave a comment

Posted by on October 12, 2016 in Compliance, EMR Software, Self Hosted

 

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

Why Windows 10 in CSP stinks now but could be GREAT later

Microsoft made a pretty big announcement around Windows 10 and CSP.  Here’s a breakdown for those that are interested:

  1. Software Assurance is not included
  2. Windows 10 is available E3 and in CSP only
  3. Customers need a qualified OS license.  In other words, this is an upgrade license only.
  4. Not available under SPLA
  5. Not available in the shared computer activation model.
  6. Per user licensing with the ability to license on up to 5 devices per license.
  7. No minimum and surprise…no maximum either.
  8. Subscription is 1 year
  9. Pricing varies
  10. New use rights highlighted in the Product Terms

So why does this stink now but could be great later?  Pay attention to number 1, 4, and 5 in the list above.  That’s what stinks.   Think this will allow VDI?  Think again.

So why not?  Why the mystery around VDI and SPLA?  If I was Microsoft, I would go ahead and allow it but for only a select few SPLA providers.  Those providers are:

  1. Report on time.  Not one late payment/report during their agreement no matter what the excuse – “My reseller sucks” is not an excuse.  It’s a good reason to work with me though 🙂
  2. Deployed Hyper V (they must have some incentive to do this)
  3. Joined CSP program.

There you have it.  Microsoft wins big time – all that missed revenue from non reporters will get reported. Now you, the compliant service provider, will be allowed VDI in SPLA.

The likelihood of this happening is slim to none.  I do think Microsoft is missing out with the Windows 10/VDI restriction.  Ever since I started in SPLA, I’ve been asked about VDI (or the lack thereof).  That was 11 years ago.

Thanks for reading,

SPLA Man

 

 

 

 
Leave a comment

Posted by on September 29, 2016 in VDI

 

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

 
%d bloggers like this: