Posted on
office 365 groups

This publish belongs to our Microsoft Teams Admin Guide series. Browse the other records within the series as they’re added below: 


In Feb 2017 I authored your blog that appeared like clickbait, but was really meant to on-site visit the confusion from the yet-to-be-released Microsoft Teams. This specific publish has actually been typically the most popular publish around the AvePoint blog, continues to be known because of it journalists, and discussed/debated among IT pros in a number of forums even even today.

In fact lots of people find Office 365 Groups confusing, particularly when it requires Microsoft Teams. I still find this in conversations I see online, by using it pros, so when talking to clients who’re somewhat a new comer to Office 365.

For users and organisations who weren’t considering SharePoint but desire to use Microsoft Teams well, now they need to. Weren’t considering OneNote? Well, you have it now! And so forth, over the options that come with Office 365 Groups.

I have seen a variety of methods to provisioning and “lifecycle” management with regards to both Office 365 Groups and Microsoft Teams.

Regrettably, provisioning is either too simple (i.e. allow anybody to produce a Group/Team whenever), too restrictive (i.e. allow only others or simply IT to produce a Group/Team), or too complex (i.e. using PowerApps, SharePoint lists, Flow, Azure Functions and also the Microsoft Graph to produce a request &amp approval system).

Office 365 Groups and Microsoft Teams aren’t a “vs.” and they’re not really a “plus” they’re together. Click To Tweet

While an easy method of provisioning would be to restrict the development of teams by restricting the opportunity to several users, this cripples the users’ capability to create other things that utilizes Office 365 Groups. Including Microsoft applications for example:

  • Stream
  • Outlook
  • SharePoint
  • Power BI
  • Yammer
  • StaffHub
  • Planner

Let’s assume you’ve include a method to manage the provisioning of Groups and Teams. How’s it going handling the lifecycle? Sure, Microsoft has lately implemented the power that you should expire and archive a Team—but how about all of those other components connected to the Group? Could they be treated equally?


Web seminar: How you can Ensure a Seamless Hybrid SharePoint Atmosphere


Where do you turn with all from the content over the elements connected to the Group? Have you got a tactic to archive that? And just what if your team is disbanded and does not need their Group/Team – would you wait for a expiry tactic to start working? How would you know when the Group/Team continues to be needed?

Because the publication of my original publish, several things have altered and improved with Office 365 Groups, the attached components, and Microsoft Teams. A few examples of the are guest access, integration, expiry, archival, recovering deleted channels, etc. That being stated, several things still haven’t altered and potentially won’t.

Organisations frequently want “best practices” when searching to apply technology. In fact Microsoft Teams is barely 18 several weeks old and adding additional features quickly. Exactly the same could be stated for a few of the supporting components (though less the rate aspect). Guidelines are fluid they evolve, change and, most significantly, are subjective.

When organisations turn to implement Microsoft Teams, they are actually applying Office 365 Groups and want to look after everything it brings and it is linked to. As a result, they have to arrange for provisioning, lifecycle, directory &amp discovery, training on related applications, and so forth.

office 365 groups

As numerous organizations adopt Microsoft Teams his or her de facto method of communicating, they have to start planning for future years. Where individuals lament email due to how poorly it’s used and just how expensive is relied on, exactly the same may happen to Microsoft Teams if attention isn’t provided to naming conventions, data retention, security, exterior access, and many other factors.

Frequently the conversation around adoption, deployment and integration is concentrated around Microsoft Teams make certain that that conversation provides equal focus on Office 365 Groups and also the bits that include it.

Office 365 Groups and Microsoft Teams aren’t a “vs.” and they’re not really a “plus” they’re together.


Want more Office 365 Groups and Microsoft Teams content? Sign up for our blog!