Complexity of licensing is costing Microsoft

14 Mar 2016 | SAM/SLO

Is Microsoft licensing complex? Is this complexity costing Microsoft?

A recent study by the Campaign for Clear Licensing on Microsoft licensing concluded that Microsoft is stunting its own growth by making it complex.

Complexity of Microsoft Licenses

Surveying over 100 Microsoft customers worldwide, the study highlighted 4 areas that were key issues for Microsoft customers:

  1. Tracking the use of Microsoft software is difficult (30%)
  2. Licensing is at times unnecessarily complex (27%)
  3. The bundling of products benefits sales objectives over customer requirements (20%)
  4. Not enough information is provided to support transitioning to new license programs and economic models (13%)

Compared to similar research into Oracle, SAP and IBM – Microsoft is the most progressive software publisher as it promotes SAM within their partner ecosystem and has lent support to the ISO SAM standard. Feedback from Microsoft customers also suggests less hostile working relationships.

Sadly, this good work seems to be undone as the overwhelming feedback from the research suggests that Microsoft licensing complexity, designed to give customers choice, is actually stunting their own growth and getting in the way of customer innovation.

Access the full report here: Microsoft Stunts its Own Growth Through Licensing Complexity

Managing Microsoft Assets and Licenses

With the possibility of an increase in license complexity, there is the potential that non-compliance could also grow. However, you do not need to fear this. Working with a supplier who understands Microsoft licensing and implementing a SAM solution to help manage software assets and licenses, is a key tactic to not only avoid non-compliance but help drive savings and reduce over-deployment and under-licensing.

Get in touch with Certero today to discuss how you can manage your Microsoft assets and licenses.

Sign Up for our Newsletter

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *