Microsoft 365 Maturity Model


Over the past 9 months I have been working with a fantastic community team to build the Microsoft 365 Maturity Model.

The team comprises of

  • Emily Mancini – MVP
  • Marc Anderson – MVP
  • Sadie Van Buren – The creator of the original SharePoint Maturity Model
  • Simon Hudson – Leeds Power Platform User Group Leader

The purpose of the Maturity Model is to enable interested parties whether that is business owners, CTOs, CIOs, consultants understand the impacts and benefits to a business by implementing Microsoft 365.

The Maturity Model tries to keep away from the technology which is tricky sometimes but by doing that it can focus on the business outcomes and keep true to its function which is a tool to help businesses drive value from Microsoft 365.

The Maturity Model divides up Microsoft 365 in to a set of business focused competencies. This allows a business to focus and read up on the areas of the Maturity Model that it is most interested in.

The Maturity Model splits up the competencies into five levels which start from the initial 100 level and build up to level 500 which is the top maturity level.

For each Maturity level the Maturity Model describes the characteristics that an organisation would generally see if it was at that level.

Examples of the competencies include:

  • Communication
  • Collaboration
  • Management of content
  • Search
  • Customisation and development
  • Staff and Training
  • People and Communities

Whilst there is bound to be overlap between the compentencies this helps a business see where those connections are so that they can see how they relate and one drives benefit in other areas.

For example if you wanting to have a good search experience where people can find the content that they need or for the content to find them, then you need to have good management of content to ensure old content is tidied up and removed appropriately.


These characteristics allow an organisation to measure itself and understand where it is in the maturity model.

Additionally, by looking at the next level it can understand the type of characteristics and impacts/benefits it would achieve if it became more mature.


A business by understanding the benefits and impact can then make the concious decision as to which competencies it should prioritise and focus on first to get the required outcomes. This allows a business to achieve results more quickly as they understand and can see the goals that they need to achieve by understanding that the characteristics are to achieve those goals.

There are supporting “How to Elevate” documents which try and explain the steps that should be put in place to move from one level to another. These documents are very much work in progress and we have only implemented some of the how to documents. We move that others in the community will contribute to help make them great instructions to get a business to the next level.

Getting Started

To get started, please visit the Microsoft 365 Maturity model introduction article on the Microsoft 365 Community Docs site.

Start by reading the overview, watch the videos and read a couple of the competencies so you can start understanding the value.

Get Involved

If you have thoughts, comments, suggestions then please reach out to us on GitHub and start a discussion topic.

Finally, we are staring a Microsoft 365 Practionisers group which is part of Microsoft’s PnP Sharing is Caring and will be having a monthly community call. To find out when the next one is visit the PnP | Sharing Is Caring site.

Look forward to hearing from you and please be kind Smile

SharePoint Online and the curse of the .stp file extension


This blog post is for anyone who hits a similar issue that we had with a customer a few weeks ago. We have built a solution for a innovative renewable electrics research organization to help them manage their manufacturing release process.

The solution is built on SharePoint Online with workflow features provided by Logic Apps, Power Apps and Angular to provide a customized user interface.

Recently, we had a support call where they were having problems with an engineering file which had a file extension of .stp

My mind went racing back to old SharePoint file formats and I remember exporting list templates with an .stp file format.

Immediately I wondered if this must be the issue the fact that SharePoint is processing these files as SharePoint templates.


Manage list templates – SharePoint (

So the behaviour we experienced was this, part of the solution copies content from one library to another. The content has metadata associated but that metadata was not being copied over.

To rule out native SharePoint function, I decided to try copying over the file using the out of the box Move function when in a SharePoint Document Library. Funnily enough the same behaviour occurred, and the file was moved but without any metadata. I was a little bit relieved as at least it wasn’t just our code!

I raised a call with Microsoft, and we went through the process of showing the Microsoft support team what was happening, and the same thing happened for them. They asked us to try do the same thing but this time via the classic experience. When the file was moved using classic experience it worked correctly.

We left Microsoft to do some more investigation.


Whilst that was in place I did some more digging into the .stp file format for the engineering software. These .stp files are STEP files and they can be .stp or .step file. We spoke with the customer and suggested that they try using .step as the file extension as a workaround. This resolved the problem for the solution and SharePoint behaved as it should.

So for the time being the workaround is to use .step rather than .stp file extensions whilst we try out some alternative approaches with document library custom templates.