How to model Microsoft 365 - my thoughts

Hi, we are working on many digital transformation projects. The customer has a legacy infrastructure VM's, FileShares, applications, Active Directory etc. This is going to land, since we are a Microsoft partner, in Microsoft 365 e.g. Azure, SharePoint Online, Teams, etc.

Since it's been a while I got certified and I'm currently reliving everything I'm a bit struggling on how to model. Currently: My modelling is a means to an end: My way of getting things clear.

The problem for me is what are the components of Microsoft 365? How to model Azure, SharePoint Online, a document solution, etc. I've been reading this forum and got some nice insights from several post (eg: https://community.opengroup.org/archimate-user-community/home/-/issues/26). Based on this I came to the following conclusions:

Office 365 tenant: Node, since a node is often a combination of a hardware device and system software, thus providing a complete execution environment

SharePoint Online: System Software because you should first do a lot of configuration to build the solutions you need A document solution build on SharePoint Online as a Software Component because this is usable by the business (or should be :-))

For that matter, I see Azure as a Node.

As said: It's been a while since I used ArchiMate and I started using it very recently and customers and co-workers highly appreciate the visuals. Please don't shoot me for getting the syntaxis wrong...