Useful PowerShell cmdlets to administer Office 365 Groups:

11

Howdy Folks! As promised in previous blog  post related to Office groups , I’m back now with some cool PowerShell cmdlets which should ease your work in managing Office 365 groups in your organization . If you’re new to Office 365 groups, I humbly request you to read in detail about Office 365 groups by accessing this link. I’ve tried my best to explain Office 365 groups there. You can read this post on HubFly blog site as well. Alright, let’s get started ….

Note : Before you can run all these PowerShell cmdlets below , you need to load the Exchange Online management shell by following this link .I’ve given a screenshot below for your reference .

1

Listed below are the operations that you can perform by following the PowerShell commands mentioned below

  • Get the list of all the Office 365 groups in your tenant
  • Remove an existing Office 365 group from the tenant
  • To make changes to an existing Office 365 group
  • Get the membership and ownership information of an Office 365 group /all the Office 365 groups in your tenant
  • Get the list of all the Office 365 groups in descending order
  • Get the list of all Private Office 365 groups in your tenant
  • Get the list of deleted Office 365 groups in descending order
  • Get the list of orphaned Office 365 groups in your tenant
  • Retrieve the list of recently created Office 365 groups
  • Update the quota of a new group if a team site exists
  • Create new Directory Settings for Groups template
  • Update the classifications for all the Office 365 groups
  • Update the privacy of an Office 365 group based on its classification
  • Determine where a group was provisioned (Planner, Yammer, Teams etc.)
  • Get the list of Obsolete Office 365 groups in your tenant

So, let’s look into all these operations in detail below….

  1. To get the list of all the Office 365 groups in your tenant:

Get-UnifiedGroup

2

  1. To remove an existing Office 365 group:

This will remove a specific Office 365 group from your tenant.

Remove-UnifiedGroup -Identity “Test Group”

  1. To make changes to an existing Office 365 group in your tenant:

Set-UnifiedGroup

Ex 1: Set-UnifiedGroup -Identity “HR Team” -AccessType Private

This example changes the Office 365 Group named HR Team from a public group to a private group.

Ex 2: Set-UnifiedGroup -Identity “HR Team” -PrimarySmtpAddress hrteam@o365techy.onmicrosoft.com -RequireSenderAuthenticationEnabled $false

This example makes the following changes to the Office 365 Group named HR Team:

i)The primary email address is changed to hrteam@o365techy.onmicrosoft.com.

ii)The Office 365 Group is allowed to receive mail from unauthenticated (external) senders.

  1. To get the membership and ownership information of an Office 365 group/all the Office 365 groups in your tenant:

Get-UnifiedGroupLinks

Ex: Get-UnifiedGroupLinks -Identity “Transport Department” -LinkType Members

This example shows the members of the Office 365 Group named Transport Department

Similarly, you can use the script below to get the list of all the members from all the Office 365 groups in you tenant.

Get Office 365 group members

This will run and display the results as shown in the screenshot below.

3

  1. To get the list of all the Office 365 groups in descending order:

Get-UnifiedGroup | Select Id, DisplayName, ManagedBy, Alias, AccessType, WhenCreated, @{Expression={([array](Get-UnifiedGroupLinks -Identity $_.Id -LinkType Members)).Count }; Label=’Members’} | Sort-Object whencreated | Format-Table displayname, alias, managedby, Members, accesstype, whencreated

4.png

  1. To get the list of all private Office 365 groups in your tenant:

Get-UnifiedGroup | Where-Object {$_.AccessType -eq ‘Private’} | Sort-Object whencreated | Format-Table displayname, alias, managedby, accesstype, whencreated

5.png

  1. To get list of deleted Office 365 groups in descending order:

Get-AzureADMSDeletedGroup | Sort-Object DeletedDateTime -Descending | Format-Table Id, DisplayName, Description, Visibility, DeletedDateTime

Note: To run this command, you need to do the below mentioned steps, else you would end up getting an error as shown in the image below. If you pay close attention to the cmdlet you would notice that this is related to Azure AD and hence you need to load the Azure AD PowerShell module for this.

I’d suggest performing these tasks in a different PowerShell window for ease of use.

  1. Uninstall the production module of Azure AD by running, (Uninstall-Module AzureAD) as this cmdlet works with the preview module of Azure AD.
  2. You cannot have the production module and the preview module running on the same machine as per Microsoft’s documentation mentioned in this link https://docs.microsoft.com/en-us/powershell/azure/active-directory/install-adv2?view=azureadps-2.0
  3. Once done, please go ahead and install the Preview module by running (Install-module AzureADPreview)
  4. After that, please connect to Azure AD by running Connect-AzureAD as shown in the image below

12

5. Once you’re done connecting to Azure AD, please go ahead and run the above-mentioned cmdlet to get the list of deleted Office 365 groups in descending order and you will get the results as shown in the image below. In my case I don’t have any deleted Office 365 group and hence it didn’t return anything.

13

8.To get the list of orphaned Office 365 groups in your tenant:

$Groups = Get-UnifiedGroup | Where-Object {([array](Get-UnifiedGroupLinks -Identity $_.Id -LinkType Owners)).Count -eq 0} `

| Select Id, DisplayName, ManagedBy, WhenCreated

ForEach ($G in $Groups) {

Write-Host “Warning! The following group has no owner:” $G.DisplayName

}

14

9.To retrieve the list of recently created Office 365 groups:

# Variables:

#   Cutoff date in days

#   Storage quota in MB

#   Storage quota warning level in MB

#………………………………………………………………………………………………………………………………………

$cutoffdate = ((Get-Date).AddDays(-20))

$quota = 500

$warning = 400

$Groups = Get-UnifiedGroup | Where-Object {$_.WhenCreated -ge $cutoffdate} | Sort-Object whencreated | Select DisplayName, WhenCreated, SharePointSiteUrl

15.png

  1. To update the quota of a new group accordingly if a team site exists:

ForEach ($G in $Groups) {

try

{

Set-SPOSite –Identity ($G.SharePointSiteUrl) -StorageQuota $quota -StorageQuotaWarningLevel $warning

Write-Host “The following site quota was updated:” $G.SharePointSiteUrl

}

catch

{

Write-Host “The following Groups does have a site:” $G.DisplayName

}

}

 

This will run and update the quota of the site as shown in the screenshot below.

16

11.To create new Directory Settings for Groups template:

There are multiple templates that are part of your Azure AD tenant.  This template can contain a settings object which has a collection of values.  By using these values, we can set the parameters below.  This needs to be done before you can set any values

Setting Description
·         EnableGroupCreation

·         Type: Boolean

·         Default: True

The flag indicating whether Office 365 group creation is allowed in the directory by non-admin users. This setting does not require an Azure Active Directory Premium P1 license.
·         GroupCreationAllowedGroupId

·         Type: String

·         Default: “”

GUID of the security group for which the members are allowed to create Office 365 groups even when EnableGroupCreation == false.
·         UsageGuidelinesUrl

·         Type: String

·         Default: “”

A link to the Group Usage Guidelines.
·         ClassificationDescriptions

·         Type: String

·         Default: “”

A comma-delimited list of classification descriptions.
·         DefaultClassification

·         Type: String

·         Default: “”

The classification that is to be used as the default classification for a group if none was specified.
·         PrefixSuffixNamingRequirement

·         Type: String

·         Default: “”

String of a maximum length of 64 characters that defines the naming convention configured for Office 365 groups. For more information, see Enforce a naming policy for Office 365 groups (preview).
·         CustomBlockedWordsList

·         Type: String

·         Default: “”

Comma-separated string of phrases that users will not be permitted to use in group names or aliases. For more information, see Enforce a naming policy for Office 365 groups (preview).
·         EnableMSStandardBlockedWords

·         Type: Boolean

·         Default: “False”

Do not use
·         AllowGuestsToBeGroupOwner

·         Type: Boolean

·         Default: False

Boolean indicating whether or not a guest user can be an owner of groups.
·         AllowGuestsToAccessGroups

·         Type: Boolean

·         Default: True

Boolean indicating whether or not a guest user can have access to Office 365 groups content. This setting does not require an Azure Active Directory Premium P1 license.
·         GuestUsageGuidelinesUrl

·         Type: String

·         Default: “”

The URL of a link to the guest usage guidelines.
·         AllowToAddGuests

·         Type: Boolean

·         Default: True

A Boolean indicating whether or not is allowed to add guests to this directory.
·         ClassificationList

·         Type: String

·         Default: “”

A comma-delimited list of valid classification values that can be applied

Let me walk you through the complete process of creating directory settings here.

  1. Install the Azure AD PowerShell Module V2 from this link
  2. Run “Install-Module -Name AzureADPreview” in the PowerShell window
  3. Once done Connect to Azure AD via PowerShell by running “Connect-AzureAD”
  4. Once done to review if you have any settings already configured in your tenant, please run the below cmdlet.

 Get-AzureADDirectorySetting | ForEach Values

17

Note: If you check the screenshot above you will notice that I have configured few directory settings such as “Usage Guidelines URL “and “Classification List “and I’ll be showing you how to configure that using PowerShell in the examples below.

5. If you do not have any settings configured the value returned will be blank as show in the screenshot below.

18

6. Alright, now let’s see some examples to set group settings.

7. All examples below will use the Get-AzureADDirectorySetting cmdlet and store that in a variable and then use the Set-AzureADDirectorySetting cmdlet with the updated settings. The full command to run a setting update is as follows. Also, I’d suggest to use PowerShell ISE for running these cmdlets for ease of usage.

$settings = Get-AzureADDirectorySetting | where-object {$_.displayname -eq “Group.Unified”}

$settings[“SETTING NAME”] = “”

Set-AzureADDirectorySetting -Id $settings.Id -DirectorySetting $settings

19.pngOk, now let’s look into some scenarios here …

Scenario 1:  Restricting Office 365 groups creation for all the users in your organization except for few users who belong to a specific Security group

$group = Get-AzureADGroup -All $True | Where-Object {$_.DisplayName -eq “Office 365 groups creation allowed”}

$settings = Get-AzureADDirectorySetting | where-object {$_.displayname -eq “Group.Unified”}

$settings[“EnableGroupCreation”] = “false”

$settings[“GroupCreationAllowedGroupId”] = $group.ObjectId

Set-AzureADDirectorySetting -Id $settings.Id -DirectorySetting $settings

20In this scenario here, I created a security group named “Office 365 groups creation allowed” and I’ve added few members to it. So, by doing this I can grant access only to those members to create Office 365 groups and not to all the users in my organization. Also, an important point to bear in mind here is, if I’m restricting the creation of Office 365 groups then these users won’t be able to create a Team, a Planner, a Yammer group etc. So, the users will be restricted by creating anything which creates an Office 365 group in the backend. So, from an end user perspective, the “create” button which you see in the screenshot below for creating Office 365 groups won’t be visible to them. The same applies for other services also, users won’t get the “Create Planner “or “Create Team” button once this option is enabled. This is one way to have control on Office 365 groups creation in your organization

6.png

In Teams, the “Create a Team “button won’t be visible for the users who are not part of that Security group which allows the creation of Office 365 groups.

7.png

In Planner, the “Create a Plan “button won’t be visible for the users who are not part of that Security group which allows the creation of Office 365 groups.

8

Similarly , as already explained above other services which creates an Office 365 group on the backend won’t be available for end users . By doing this you can have control over who gets to create an Office 365 groups and other services such as Teams and Planner in your organization .

Scenario 2: Setting Office 365 groups classification

$settings = Get-AzureADDirectorySetting | where-object {$_.displayname -eq “Group.Unified”}

$settings[“ClassificationList”] = “Internal,External,Confidential”

Set-AzureADDirectorySetting -Id $settings.Id -DirectorySetting $settings

In this scenario, we’re enabling the classification option so that you can classify your groups accordingly. Once this is done whenever you try to create an Office 365 group from the outlook webmail (provided that you have access to create Office 365 groups) you will get an option to choose the classification for that group also as shown in the image below. This could be useful from a compliance and governance perspective.

9.png

Once that’s done you can set the classification for an existing Office 365 by running the below PowerShell command.

Set-UnifiedGroup <TestGroup@o365techy.onmicrosoft.com> -Classification <Internal>

Also, if you want to create a new group with a classification then run the below PowerShell command for that.

New-UnifiedGroup <TestGroup@o365techy.onmicrosoft.com> -Classification <External> -AccessType <Public>

Scenario 3:  Setting Usage Guidelines URL

$settings = Get-AzureADDirectorySetting | where-object {$_.displayname -eq “Group.Unified”}

$setting[“UsageGuidelinesUrl”] = “<https://o365techy.sharepoint.com/sites/office365groupsgovernance/usageguidelines/SitePages/Home.aspx>&#8221;

Set-AzureADDirectorySetting -Id $settings.Id -DirectorySetting $settings

21

In this scenario, I’ve created a SharePoint subsite named “Usage Guidelines” which speaks about all the guidelines a user must follow while using Office 365 groups in my organization and the user can refer that while creating / using Office 365 groups. Once this has been enabled this what the end user view would be like. Please check the screenshot below.

10

Scenario 4: Restrict all access for guest users to Groups including the ones that were already granted access

$settings = Get-AzureADDirectorySetting | where-object {$_.displayname -eq “Group.Unified”}

$settings[“AllowGuestsToAccessGroups”] = “False”

Set-AzureADDirectorySetting -Id $settings.Id -DirectorySetting $settings

22Scenario 5: Restrict the ability to add any new guest users but do not restrict existing guest users

$settings = Get-AzureADDirectorySetting | where-object {$_.displayname -eq “Group.Unified”}

$settings[“AllowToAddGuests”] = “False”

$settings[“AllowGuestsToAccessGroups”] = “True”

Set-AzureADDirectorySetting -Id $settings.Id -DirectorySetting $settings

23Finally, if you want to review all the updated settings then please run the below mentioned PowerShell cmdlet as already described above and it will return the updated settings.

Get-AzureADDirectorySetting | ForEach Values

24

 If you want to remove the group settings that we configured in all the scenarios above then please run the below PowerShell command.

$settings = Get-AzureADDirectorySetting | where-object {$_.displayname -eq “Group.Unified”}

Remove-AzureADDirectorySetting -Id$settings.Id

25.png12.To update the classifications for all the Office 365 groups:

## Set classifications for all groups

$Groups = Get-UnifiedGroup | Where-Object {$_.Classification -Eq $Null}  | Select DisplayName, Classification

ForEach ($G in $Groups) {

If ($G.Classification -Eq $Null)

{

Write-Host $G.DisplayName

Set-UnifiedGroup -Identity $G.DisplayName -Classification “Internal”

}

}

 

#……………………………..

# Variables:

#   Cut off date in days

#   Classification

#……………………………..

$cutoffdate = ((Get-Date).AddDays(-10))

$classification = “High”

# Retrieve recently created groups with accesstype set to PUBLIC

$Groups = Get-UnifiedGroup | Where-Object {

$_.WhenCreated -ge $cutoffdate -and $_.AccessType -eq ‘Public’ -and $_.Classification -eq $classification } `

| Sort-Object whencreated | Select DisplayName, WhenCreated, AccessType, Classification, ManagedBy

# For each new group update set accesstype to PRIVATE

ForEach ($G in $Groups) {

Set-UnifiedGroup -Identity $G.DisplayName -AccessType ‘Private’

Write-Host “The following Group privacy setting was updated:” $G.DisplayName

}

26This will run and update the classification for all the Office 365 groups as shown in the image below

27

  1. To update the privacy of an Office 365 group based on its classification:

#……………………………..

# Variables:

#   Cutoff date in days

#   Classification

#……………………………..

$cutoffdate = ((Get-Date).AddDays(-10))

$classification = “High”

# Retrieve recently created groups with accesstype set to PUBLIC

$Groups = Get-UnifiedGroup | Where-Object {

$_.WhenCreated -ge $cutoffdate -and $_.AccessType -eq ‘Public’ -and $_.Classification -eq $classification } `

| Sort-Object whencreated | Select DisplayName, WhenCreated, AccessType, Classification, ManagedBy

# For each new group update set accesstype to PRIVATE

ForEach ($G in $Groups) {

Set-UnifiedGroup -Identity $G.DisplayName -AccessType ‘Private’

Write-Host “The following Group privacy setting was updated:” $G.DisplayName

}

30.png

31.png

14.To determine where a group was provisioned (Planner, Yammer, Teams etc.)

To get the list of Yammer integrated Office 365 group list:

Get-UnifiedGroup |Where-Object {$_.ProvisioningOption -eq ‘YammerProvisioning’} |select DisplayName,Alias,ProvisioningOption,GroupSKU,SharePointSiteUrl,SharePointDocumentsUrl,AccessType

To get the list of Teams integrated Office 365 group list:

Get-UnifiedGroup |Where-Object {$_.ProvisioningOption -eq ‘ExchangeProvisioningFlags:481’}|select DisplayName,Alias,ProvisioningOption,GroupSKU,SharePointSiteUrl,SharePointDocumentsUrl,AccessType

Similarly, we expect MSFT to work on for Planner and other services which create an Office 365 on the backend.

15.To get the list of Obsolete Office 365 groups in your tenant:

This is a PowerShell script from Office 365 fame Tony Redmond and the explanation for the script can be found below.

Note : You need to be connected to Exchange Online PowerShell module as well as the SharePoint Online PowerShell module to run this script

Like any object, an Office 365 Group might become unused over time. No current method exists to detect what groups are underused, so here’s a script that does the job for you by checking audit records to establish whether any SharePoint file activity has occurred in the group document library in the last 90 days and whether any conversations have happened in the group mailbox in the last year. Seeing that it’s all done in simple PowerShell, you can tailor the code to your heart’s content. A HTML report file is generated at the end, which contains some statistics like:

32.jpg

Number of groups scanned: 155

Number of potentially obsolete groups (based on document library activity): 132

Number of potentially obsolete groups (based on conversation activity): 60

Number of Teams-enabled groups: 41

Percentage of Teams-enabled groups: 26.45%

Script:

Check for obsolete Office 365 groups

Thanks for reading this post …. Good luck with Office 365 groups!!!!

Advertisements

Webinar on the new features of SharePoint Online and OneDrive for Business :

Hi All,

Please join us for a webinar on May 19th ,2018 at 6:00 pm IST on ”Deep Dive into the new features of SharePoint Online and OneDrive for Business-Part 2″

32590558_1905532662854198_2732364645032525824_n

Agenda:
This is continuity of our previous session on the same topic .If you haven’t attended Part 1 of this session you can view the recording from the link below . We will be discussing in detail about all the new features that has been rolled out by Microsoft for SharePoint Online and OneDrive for Business

Part 1 recording : _ https://youtu.be/LPohYbozOSM

Link to enroll for Part 2 :_ https://www.c-sharpcorner.com/events/deep-dive-into-the-new-features-of-sharepoint-online-and-onedrive-for-business-part-2

Thanks for enrolling yourself for this session !!!

Office 365 groups -What you need to know?

Office 365 groups lets you choose a set of people that you wish to collaborate with and easily set up a collection of resources for those people to share. Resources such as a shared Outlook inbox, shared calendar, shared document library, Planner and a site for collaborating on files are a part of an Office 365 group.

The best part of Office 365 groups is such that you don’t have to worry about manually assigning permissions to all those resources because adding members to the group automatically gives them the permissions they need to the tools your group provides. Additionally, groups are the new and improved experience for what we used to use distribution lists or shared mailboxes to do.

1

Although, Office 365 groups helps in addressing many gaps from a collaboration stand point it has become a huge challenge for IT/Office 365 administrators to manage them. So, in this article I’ll be explaining in detail about what Office 365 groups is all about, how you can create it and what are the different sources from which we can create an Office group. So, let’s get into the details …

  1. What are Office 365 groups?

2

Well, to put it in very simple words, Office 365 groups is nothing but a cross-application membership service in Office 365. It’s an object created in Azure Active Directory with a list of members in it and also has some inbuilt workloads associated with it such as a SharePoint Team site, Yammer Group, Shared Exchange mailbox, Planner, Power BI and OneNote. You can add or remove people to the Group just as you would add any other group-based security object in Active Directory.

So, what does this mean to me? Well, it simply means that you don’t need to go to different places in your Office 365 eco-system to collaborate with your team members or to find a document that’s stored in a SharePoint document library in a SharePoint site. You have a single console now called as Office 365 groups which can help in bringing all the required workloads into one single hub so that it’s easy for you to collaborate within your team members while you’re working on a project.

Alright, I think I’m just talking all technical stuff till now, but I haven’t really talked or even showed you folks about how this can add value as an end user or as a project manager/ team lead. So, let’s get into the fun stuff now ….

Every time I create an Office 365 group this is what it looks like …

3

 

I would get a welcome email in my mailbox stating that the group is ready and the members whom I’ve added to the group would receive a similar email notification stating that they’re a part of that group now. If you’re using Outlook 2016 or Office 365 Pro Plus, then the group would automatically get mapped as a folder in your outlook client as shown in the image below.

4

In addition to that, once you have created a group you would get the below mentioned workloads by default along with the Office 365 group.

a) Conversations -This helps you to have email conversations within the group by sending an email to the group’s email address as shown in the image below. Any conversation which happens within the group can be viewed by all the members of the group.

5

b) Files -You can upload all the files related to your project /team in this Tab and once it’s uploaded here it will be available to all the team members as shown in the image below.

6

c) Calendar (you can schedule or view the meeting on the group if you’re a member of the group). In addition to this you can view your own calendar as well in the same Tab.

7

d) Notebook (Notebook which is used to share updates with the entire team in the group or you can create new section which is password protected). This can be used for capturing meeting points or something of that sort.

8

In addition to all these tabs, you would notice an ellipsis button towards your right side next to the “Notebook” Tab as shown in the image below. Clicking on that ellipsis would give you two options as shown in the image below. 1.  Planner & 2. Site

9

Now, let’s look into these two options.

e) Planner (You can create tasks and plan them using planner). Any tasks that you need to plan as a part of your project can be added to the Planner with appropriate deadlines. You would also get email reminders for tasks that are nearing the deadlines.

10

f) Site (SharePoint group site, which can upload documents or create new pages, web part, InfoPath form, etc.). So, when you click on site it would take you to a SharePoint Site which has the Modern experience and you use this for document collaboration and other SharePoint related stuff.

11.png

Note: The “Files” tab which I was talking about earlier is nothing but a document library which is a part of this SharePoint site. So please don’t get confused that it’s a different document library altogether. I see many people getting confused about these two workloads in an Office 365 group where they think that these are two different pieces altogether. So please bear in mind that these are both the same. The reason why Microsoft has given this as two pieces is, using the “Files “tab you can directly upload the files/documents to the document library instead of navigating to the “Site” tab and uploading it to the document library from there.

Listed below are the features that you get in the Modern SharePoint site …

  1. Responsive Pages to provide Team News
  2. Group Classification and Privacy always on display, an indicator for external users will also show up here
  3. Jump to the Outlook Conversations or manage Group members right here
  4. Create something new: Document Libraries, Lists, Pages, etc.

Now, that I have given an overview of Office 365 groups and the workloads in it and its functionality let’s try to understand how to create an Office 365 group. Well, when I think about it, it really excites me and scares me at the same time and I’ll explain the reason for that below.

The below mentioned image depicts the different ways of creating an Office 365 group in Office 365 (meaning, the different places from which an end user can create an Office 365 group)

12.png

Note: As shown in the image above, an Office 365 group can be created from all these different sources and this may or may not change in the mere future (meaning, Microsoft can add few more sources from which you can create an Office 365 group, or they might even remove the creation of an Office 365 group from a specific source).

As of today, any end user who has access/license assigned to all these applications can create an Office 365 group. Of course, this is really exciting to me from an end user perspective as I don’t need to go to a specific location in Office 365 to create an Office 365 group and it can be created from within SharePoint, Outlook, Planner, Power BI, Teams, Yammer, Microsoft Dynamics 365 & StaffHub.

But when I think about this from an IT admin/ Office 365 admin perspective it really scares me because this would just open the door for all the users to create an Office 365 group either knowingly and unknowingly (meaning, may be the users intent was just to create a Yammer group or a Planner but, in the backend, it creates an Office 365 group and the user wouldn’t know about this).

However, there’s a catch here. If you pay attention to the image above you would notice that the behavior or the features of the Office 365 group is not the same when its created from a different source (meaning, when a group is created by the creation of a Team in Microsoft Teams you would only get outlook, Teams, SharePoint & Planner and not Yammer. On the other hand, when an Office 365 group is created as a result of the creation of a Yammer group you would only get Yammer, SharePoint & Planner). So, the point here, there’s going to be difference in the features/workloads you get in an Office 365 group based on what’s the source. The reason behind this is, Office 365 acts as a building block for all these groups created in Yammer, Teams and so on.

Now, if you’re interested in knowing more about the functionalities of all these groups and how they differ based from which source they get created then please go through the links below.

  1. Creating a Planner in Office 365 (this would create an Office 365 group in the backend) :_ https://support.office.com/en-us/article/create-a-plan-in-microsoft-planner-93e65b03-6fac-4661-a502-e3161475ab93
  2. Creating a group in Outlook :_ https://support.office.com/en-us/article/create-a-group-in-outlook-04d0c9cf-6864-423c-a380-4fa858f27102
  3. Creating a group in Yammer :_ https://support.office.com/en-us/article/create-a-group-in-yammer-b407af4f-9a58-4b12-b43e-afbb1b07c889
  4. Creating a group in StaffHub :_ https://support.office.com/en-us/article/add-employees-or-groups-in-microsoft-staffhub-f56ba0bb-8ca2-4583-8c0e-e10be3fc8985
  5. Creating a group in Power BI: _ https://docs.microsoft.com/en-us/power-bi/guided-learning/publishingandsharing#step-6
  6. Creating group in Microsoft Dynamics 365: _ https://docs.microsoft.com/en-us/dynamics365/customer-engagement/admin/deploy-office-365-groups
  7. Creating a team in Microsoft Teams( this would create an Office 365 group in the backend) :_ https://support.office.com/en-us/article/create-a-team-for-staff-in-microsoft-teams-314ac9d5-36a9-408e-8ae4-7ef20e9f1ddf
  8. Creating a modern team site in SharePoint Online (this would create an Office 365 group in the backend):_ https://support.office.com/en-us/article/create-a-team-site-in-sharepoint-online-ef10c1e7-15f3-42a3-98aa-b5972711777d

So, I believe by now you would have understood the beauty of an Office 365 group and how to create it and what are the different sources from which you can create an Office 365 group.

Now, let me get into the flip side of this….I believe by now you folks would have understood  that Office 365 groups is the basic building block for all the groups that gets created from different sources and let me also tell you that it’s also possible to create a group in Yammer or create a Team in Microsoft Teams from an existing Office 365 group ( meaning , when you create a new group in Yammer or while creating a Team in Microsoft Teams it creates an Office 365 group and that’s something which I already explained before .In addition to this I can create a Yammer group or a Team in Microsoft Teams from an existing Office 365 group ) as shown in the image below .

13

Note: In the image above, you can see that I’m trying to create a Team in Microsoft Teams and it gives me an option to choose an existing Office 365 group that already exists in Azure AD.

Behavior of an Office 365 group when it’s connected to Microsoft Teams:

  1. When a Group is created through Teams, the privacy of the Office 365 Group is automatically set to private and cannot be changed.
  2. You can add a Teams chat to an existing Office 365 Group if it’s set to private and has fewer than 600 members in the group. Note that this may change in the future.
  3. Teams cannot be added if the Office 365 Group uses Yammer for conversations instead of Outlook, as mentioned above

 

Behavior of an Office 365 group when it’s connected to a Yammer group:

Outlook Conversations are for emails; Microsoft Teams are to live chat and Yammer is for forum-like threaded conversations. Yammer conversations are a little different, as they are not always available with Office 365 Groups. To get an Office 365 Group with Yammer Conversations, you must create it from within Yammer and Yammer only.

If you decide to create a Yammer connected group, it’s exclusive. You will not be able to use the Outlook Conversations, Microsoft Teams, or the Calendar.

14

The behavior of an Office 365 groups varies based on which service it’s connected to and you can test if for yourself by creating it from different sources.

Alright. That’s all I have for this blog post and I’ll come back to you folks soon on different topics in Office 365 groups such as 1. How to restrict the creation of Office 365 groups to all the users? 2. Best practices for Office 365 groups administration 3. PowerShell for Office 365 groups etc.

Please stay tuned until then and good luck with Office 365 groups!!!