Image of car shells on the production line

We have migrated email to Microsoft 365, but what do we do next? – Add your content

So, you have setup Microsoft 365. Your teams and organisation are using it for email. What next?

In our previous post we discussed what should you do first when you have first migrated to Microsoft 365? To be honest, it was a bit of a cop out! Our answer, well it’s up to you and then linked to some other resources.

So, let us put our opinion out there. The situation is that you have moved your e-mail into Microsoft 365, but what do you do next?

At iThink 365 we think there are two things that are next:

  • Move your content into Microsoft 365.
  • Move your collaboration into Microsoft 365.

However, for this blog post we are going to talk about moving your content into Microsoft 365. This really is the best next step as until your content is in Microsoft 365 then your organisation and teams are not able to work effectively and will be straddling across two systems. At iThink 365 we want our client’s teams to be able to work anytime and anywhere. That way they are able to work in the way that works for them to get the job done.

Of course, the Microsoft 365 Maturity Model provide some great thought on this top with the Management of Content Competency article. This will provide some great food for thought on the topic.

So, what would you use in Microsoft 365 to hold your content?

Let talk next about when you would use these services.

Where to put your content and the benefits

Microsoft One Drive

Microsoft One Drive is your team’s personal area which by default is secured so that only the user has access to the content.

The Microsoft One Drive Logo

The advantage of having the content in Microsoft One Drive means:

  • It is available when you are in and out of the office.
  • You can find the content using the search feature.
  • Soliciting feedback from others is easier and less work by sharing one document and getting feedback added to that one document.
  • The user’s content is backed up and protected by recycle bin.
  • User’s content is protected from ransomware with automated detection of large-scale deletions which is how ransomware behaves.

Microsoft Teams

Microsoft Teams provides a way for groups of people to be able to collaborate, communicate and work on content. Behind the scenes, Microsoft Teams uses SharePoint to hold the files content.

We see Microsoft Teams as being a way for teams, whether they are department, project, product, and/or social teams to work, communicate and build content together.

The advantage of having the content in Microsoft Teams is like that of SharePoint (it’s the same backend) however its lifecycle is shorter. Some of the advantages include:

  • Content can be discovered.
  • Content can be secured.
  • Users find accessing content, easier as its through a desktop application on their machine.
  • Content can be encrypted and protected if stolen from the organisation.
  • Communication of new content and discussions around the content are more natural.

Currently, we see Microsoft Teams as being an internal group resource. What we mean by this is that the content is not being shared outside of the team. We recommend that SharePoint sites are created for a department, or resources to share information with public or across the rest of the organisation. These sites can be used to share news and communicate within an Intranet but also allow users to self-serve and get the resources that they need from the department.

Microsoft SharePoint

Microsoft SharePoint provides a way to pull together content into one place. A SharePoint site should contain related information and content around a subject, for example a product, project, or department.