RSS

Tag Archives: Hosting

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

The Cloud Insider News – Dynamics CRM

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

The Register Microsoft plans summer CRM war opener against Salesforce

XRMCRM Online FAQ

Omnivue.net (white paper) – Is Your Business Ready for ERP?

SaaSPlaza – What’s all the hype about Microsoft Dynamics 365?

Wealthmanagement.com/Tamarac – Five Ways a Client Portal Can Transform Your Practice

WatServ – Dynamics 365 Pricing Plans and Migration Discount Announced at Dynamics 365 Tech Conference.

Channele2eMicrosoft Preps Partners for Dynamics 365, LinkedIN Integration

Cisco – Cisco Unified CallConnector for Microsoft Dynamics CRM

Caltech Dynamics 365 Enterprise Edition Customer Service

Tribridge Is it Time to Check the Vital Signs of Your Microsoft Dynamics CRM System?

Computer WorldAdobe continues to march to the cloud

IpipelineCustomer Centricity – Do you “CRM?”

Thanks for reading,

SPLA Man

 
 

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

Dynamics 365 Licensing for SPLA

Over the past several weeks, I’ve received several inquiries around Dynamics 365 what it means for CRM SPLA partners.  In this article, we will review the changes and when the changes will take effect.

Dynamics 365 for SPLA

In today’s SPLA licensing model, there are three products available –  CRM Essential, CRM Basic, and CRM Professional.  All come with different functionality and all come with different price points.  Those products will remain up until your agreement expires.  As with other products, once your agreement expires, you should report or license the new products.  In some cases, you are allowed to downgrade and run previous versions, but you must report the latest and greatest.  As an example, SQL 2016 is the latest edition of SQL, but that doesn’t mean you have to deploy SQL 2016; you can run 2012 or 2014 or God forbid 2008.  However, once you sign a new SPLA, you must follow the terms in the SPUR at the time of signing.  In this example, even though you deployed 2008, doesn’t mean you can license SQL 2008 by processor, you must still report it by core.  Dynamics CRM works the same way.   With Dynamics, the new products are Dynamics 365 Sales, Customer Service, and Team Members.  All come with bells and whistles and all come with higher pricing.  If you have an active SPLA prior to the announcement (November, 2016) you can continue to report the old products up until your agreement expires.  Once you sign a new agreement, you must report the higher priced products.

What are the options?

I’ve worked with a couple of Dynamics CRM hosters who had their agreement expire two months after Microsoft made this announcement.  In other words, Microsoft announced these changes in September (give or take – most widely known to resellers and partners in November) but their agreement expired in October.  The poor CRM providers are really in a pickle.  Microsoft dropped the bomb on them and two months later their pricing almost doubled!  What are they supposed to do?  Blame their reseller? Sure.  Everyone does.  Blame Microsoft?  Yes.  But that only gets you so far.  Cry?  Always.

Microsoft made some adjustments and offered “transition pricing”.  Transition pricing allows SPLA partners who have an active SPLA prior to November, 2016, the ability to report lower transition pricing up until their agreement expires.  The transition pricing is lower than new pricing but still doesn’t offer much of a discount.  When your agreement does expire, Microsoft will force you to license the under the new licensing and pricing model.

My Opinion

In my opinion, CRM provider are the old Exchange provider.   When Office 365/BPOS came about, small Exchange providers found it very difficult to compete.  It wasn’t just from a licensing perspective but also managing and deploying Exchange became too costly.  What happened?  Smaller Exchange providers are now CSP or out of business.  Dynamics CRM is now the old Exchange.  Microsoft is not going to lower SPLA pricing for Dynamics CRM.  It is not in their best interest to do so.  Harsh reality?  Yes.

Allow me to put on my Microsoft hat. What do you do?  There’s a couple of ways to think about it.  On one hand, Dynamics 365 isn’t all that bad.  I do think Microsoft rushed to market with the product.  I also think there are ways to up sell customers into the latest product.  There are opportunities to offer Dynamics CRM and deploy CRM and manage CRM.  For many organizations, CRM is the lifeblood of their sales.  CRM goes down, it’s bad for their business.  In speaking to a colleague, the LinkedIN acquisition makes Dynamics 365 an interesting proposition.  If you are able to seamlessly host Dynamics 365 on your platform and integrate their LinkedIN contacts as well, there could be a compelling reason to transition to the latest and greatest.

Ok, now my Microsoft hat is off.  I think Microsoft should be more patient and lengthen the transition pricing to make it more compelling for CRM hosters and to their customers.  I think service providers are the bread and butter to Microsoft hosted offerings.  SPLA is the one program that differentiates Microsoft v. Amazon v. Google.  Thirty thousand service providers worldwide who are willing to host Microsoft technology.  You don’t want to abruptly interrupt their business.  After all, no matter if they get Dynamics from a Microsoft datacenter or from a partner, Microsoft wins.  Amazon can’t say the same thing.

Would love to hear comments.  You can email me at info@splalicensing.com or leave a comment below.

Thanks for reading,

SPLA Man

 

 

 
Leave a comment

Posted by on May 9, 2017 in Dynamics 365

 

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

Steps to take to limit SPLA audit exposure

It’s the fourth quarter at Microsoft, this means audits are in full swing.  One of the easiest ways to collect large upfront payments are through SPLA audits.  Knowing this, what steps can you take to limit your audit exposure?

  1. Inventory – Although you submit a SPLA usage report each month, licenses are missed inadvertently.  When collecting inventory of what you should and should not report, be sure to include customer owned licenses.  If ANY customers are bringing licenses into your datacenter, they must have software assurance if it’s a shared environment.  Secondly, make sure to take a hard look at SQL.  To no one’s surprise, SQL is very expensive.  If you miss license SQL, it can add up really quickly.
  2. Agreements – Which MBSA agreement did you sign?  Don’t know what a MBSA agreement is?  Please ask your reseller for a copy.  Every SPLA customer has a signed Master Agreement.  This is the umbrella that ties all your Microsoft agreements together including SPLA.  There’s specific language in the agreement that goes over audits and the timeframe in which they are able to audit historically. Look closely at your agreements with your customer.  Did you mention they are responsible for licenses they bring into your datacenter?  Did you send them a license verification form for license mobility?  Do you have language that states they are responsible for anything under their Microsoft agreement but you are only responsible for yours?  Do you make the end user license terms (part of your signed SPLA) available to all customers?  Don’t know what an end user license terms agreement is?  Ask your reseller.
  3. Check AD closely.  Do you have administrative accounts that you are reporting?  What about test accounts?  Read your Microsoft SPLA agreement around testing, developing, and administrative access.
  4. Label server names appropriately – Label if a server is “passive” and label a server if it’s “development”.  This can save you time with the auditors.
  5. Check server install dates – If a server was active June, 2013 but nothing was reported on that server until June, 2015; Microsoft is going to ask A) what that server is doing and B) Why haven’t you reported it.  If it’s doing nothing, than shut it down before the audit.
  6. Check SAL licenses –  Do all users who potentially HAVE access are being reported?
  7. Check Office licenses – Do all users need access to Office Pro Plus?  Can they get away with Standard?  Did your engineers inadvertently publish Visio to every user when it only needs to go to a handful of end users?
  8. Double check server versions – Did your engineers accidentally install SQL Enterprise when it should be Standard?
  9. Are you taking advantage of all the use rights available?  As a SPLA, are you aware you can provide demonstrations to your customers at no charge?  Are you aware of the admin rights?  Are you aware you can run 50% of what you are hosting externally – internally?  (must actually report it all under SPLA – they are not free).
  10. Virtualization rights – Are you reporting SQL Enterprise to run unlimited VM’s? Are you running Windows Datacenter?  Remember, you do not license the individual VMs for Windows Server.  (You count physical cores which allows 1 VM for Standard or unlimited for Datacenter).
  11. MSDN, VDI, and other restrictions – No, you cannot host VDI and MSDN in a shared environment.  If you are, dedicate the servers immediately.  If you are hosting from the same hardware you are running internally, this also must be separated.
  12. Hiring Experts – Are they really experts or just advertise as such?

Hope this helps.  Any questions email info@splalicensing.com

Thanks for reading,

SPLA Man

 

 
Leave a comment

Posted by on April 25, 2017 in Compliance

 

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

SPLA Discontinued??

Read the rest of this entry »

 
Leave a comment

Posted by on March 20, 2017 in In My Opinion

 

Tags: , , , , , ,

If you could change ONE thing in SPLA…What would it be?

If you were THE Microsoft SPLA MGR in charge of the entire program, what would you change to help grow the SPLA business? (more importantly, YOUR SPLA business)  If you have multiple that’s ok.

Here’s a list from a colleague to get you started:

  • Allow Windows Desktop OS to be included in the unlimited virtualization rights of Windows Server DC
  • Allow MSDN to have License Mobility Rights.
  • Remove the SharePoint Enterprise SALs additive requirement.  Just make Enterprise more expensive.
  • Create cores for Excel and Access for ISV’s.
  • Expand the Productivity Suite and have O365 equivalents to align with O365 pricing.
  • Bring back SQL Enterprise SALs.
  • Add Power BI as a product
  • Reduce Office SPLA pricing!
  • Have the resellers require an End Customer Enrollment for deploying customer owned hardware, and open it up to include Windows PC’s.
  • Bring better clarity to RDS licensing.
  • Create a better way for Microsoft field reps to get credit for SPLA consumption.

You can tweet me at @SPLA_man or send me an email info@splalicensing.com

Thanks for reading,

SPLA Man

 
Leave a comment

Posted by on March 2, 2017 in SPLA General

 

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

 
%d bloggers like this: