8

The blog you linked to has the correct answer. It's not optimal, but it works. One source of confusion is that after creating a team site, there are two groups with the same name. For example, if you create a new team site named "project 1", the following groups will be created: "project 1" - This group is visible in the list of groups in the admin console....


5

You need to call EnsureUser with the login name in the format c:0o.c|federateddirectoryclaimprovider|groupId where groupId is the id of the group in Azure AD i.e. a guid. e.g. c:0o.c|federateddirectoryclaimprovider|629b9938-dd1b-4006-97a8-6bb9c4e84ac2 You can get this from the Microsoft or Azure Graph APIs.


5

The question is really a Yammer group vs an Office group. And for all intents and purposes, an Office group is superior to a Yammer group. You have more functionality (Yammer or outlook for conversations, file storage, Planner, Power BI, Teams, OneNote) versus what Yammer offers.


4

You first need to create and register an Azure AD app in the Azure portal. That app needs the delegated Group.ReadWrite.All permission from Microsoft Graph API. Then you need to get the client ID and client secret of that app. We will need to use that in our application. Once you have that, you can try and modify the below code: static async Task ...


4

For our company, the factors that we took into account to choose between Yammer and Teams, are as follow, Sharing Files. We have a hard time in sharing files in Yammer but Teams is integrated with SharePoint Libraries. Cost: Yammer is free for external users. For Teams, you need to pay for each member as of now. Planner: In Teams you could use Planner for ...


4

Both addresses are valid; every object gets a @.onmicrosoft.com address.


4

When you create a modern team site, it automatically creates an office 365 group (azure ad group) that contains all members and adds to site members sharepoint group. When you add user/invite user from modern UI you are essentially adding the user to the Azure Ad group. The services connected to the Office 365 group like shared mailbox, planner etc use the ...


4

An "Office 365 Group" is a (special) Active Directory group plus a Site Collection. This AD group can be used as an ordinary AD group when granting access to other sites. When used this way, they are just an AD group with no special "Office 365 Group" features in that site. I.e. they are managed as ordinary SharePoint users and are directly assigned ...


4

To actually disable this, go to the classic settings page: https://contoso-admin.sharepoint.com/_layouts/15/online/TenantSettings.aspx About in the middle you will find this one: Control whether site collection administrators can use the "Connect to a new Office 365 Group" command on the Settings menu to connect classic team sites to new Office 365 ...


3

What has been shared by f1365 is not true as of 2019-10-23 You run Remove-SPOSiteGroup cmdlet to remove SharePoint Online group. As of 2019-10-23 you cannot complete the following actions: Disconnect SharePoint Online from the group Change SharePoint Online connection from one group to another Connect SharePoint Online to an existing group If you remove ...


3

In case anyone is interested. Now it's possible to do this using below PowerShell CMDLET. https://docs.microsoft.com/en-us/powershell/module/sharepoint-online/remove-spositegroup?view=sharepoint-ps Remove-SPOSiteGroup -Site https://contoso.sharepoint.com/sites/marketing -Identity GroupToRemove


3

At the top of the Site Collection page in the admin center there may be a link for "Try the preview". This will also list the Groups sites. (You may not have access to it yet.) https://yourDomain-admin.sharepoint.com/_layouts/15/online/AdminHome.aspx#/siteManagement Otherwise, you can use the SharePoint Online PowerShell cmdlets. Connect-SPOService ...


3

Here is what I ended up needing to do if someone else needed something like this Import-Module ActiveDirectory #will required to be downloaded/installed $Url = 'https://SharePoint/Site/Path' $Library = 'Team Reports' $RootFolder = '/Team Reports/Engineers' Connect-PnPOnline -Url $Url # Get Folders in the Root folder $folders = Get-PnPFolderItem -...


3

There is no PnP native way to do this but you can do it by dropping down into the CSOM EnsureUser method. Try this: $web = get-pnpweb $user = $web.EnsureUser("user@company.com") $ctx = Get-PnPContext $ctx.Load($user) Execute-PnPQuery $user


3

The solution for the 403 error was to unlock the site collection. Set-SPOSite -Identity <URL> -LockState unlock After that the site collection could be removed with Remove-SPOSite


3

Just page through the results on /_layouts/15/online/SiteCollections.aspx in your admin center. If you don't see a paging link, then you have less than 30 site collections and if there are none with teams managed path, then you don't have any. Based on your update, the modern sites will not show up in the admin center. You have to query Exchange for those. ...


3

There is a hidden GroupifyMenuButton feature that is responsible for hiding and showing the "Connect to new Office 365 Group" button. This action button redirects to the following URL when we click it: /_layouts/15/creategroup.aspx?mode=connectgroup URL We can disable this feature with the following Powershell PnP code: Connect-PnPOnline -url "https://...


2

PowerShell based solution: Download SharePoint Online Management Shell https://www.microsoft.com/en-us/download/details.aspx?id=35588 Run the commands below to get a list of all site collections Connect-SPOService -Url "https://tenantname-admin.sharepoint.com" Get-SPOSite


2

First I'll answer your question, and then I'll teach you how to find these properties for your self. Just add the LastContentModifiedDate to your list of properties Get-sposite -Limit All | Where {$_.Template -like "GROUP#0"} | Select URL,Title,LastContentModifiedDate,StorageQuota,StorageUsageCurrent,Template,Status Now, to find these properties for ...


2

In the Office 365 admin center, when you delete a SharePoint Online site collection, it is moved to the SharePoint Site Collection Recycle Bin where it will remain and can be restored for the next 30 days. To permanently delete a SharePoint Online site collection and all of its subsites without the use of the Recycle Bin, you need to use PowerShell. This ...


2

First of all, the setting only hides the command and does not disable the option to create sites for users. It says so in the setting in your screenshot. And yes, whenever a group is created in Office 365 you get a SharePoint Modern Team site. And a group is created when you create a Team, Yammer Group, Staffhub group, PowerBI workspace, and maybe more. ...


2

Only top level sites can be connected to O365 groups, not subsites. You'd have to promote your subsites to separate site collections, and then run the "connect to new O365 group" command for each one. By "promote subsites to site collections", there is not an OOB tool for this, so this step is not trivial. There are 3rd party tools to help move all the ...


2

There is a way. Although it's theoretical. Modify your PowerShell script so that it also hosts a mini-web server. You can use two PowerShell modules for that: Import-Module Polaris -Verbose Import-Module PSHTML -Verbose Add-Type -AssemblyName System.Web http://chen.about-powershell.com/2018/09/exploring-pshtml-for-polaris-yet-another-way-to-build-forms-...


2

You can create a Modern team site with associated O365 group using PnP PowerShell. New-PnPSite -Type TeamSite -Title "Test Group" -Alias "TestGroup" -Description "Test group desc" -IsPublic Reference - New-PnPSite If you want create it via MS Graph, PnP PowerShell also supports that. You can provision the Group as below. You need to be Global admin to run ...


2

All the approaches you outlined are identical. If you add them to the Office 365 Group in the various ways you can do so, they will have the appropriate access to Teams, SharePoint, and any other associated applications (Planner, Yammer, Stream, etc.).


2

You can only connect an Office 365 group to an existing SharePoint site. It is a one-to-one relationship.


2

No, it isn't possible. Office 365 Groups are a take it or leave it object.


2

You could use the Get-UnifiedGroup cmdlet to view Microsoft 365 Groups. Reference: https://docs.microsoft.com/en-us/powershell/module/exchange/get-unifiedgroup?view=exchange-ps


2

You could go to the sharepoint online admin center, select the site. Click Permissions in the Info panel, if the group is disconnected from the admins role, a message box will show up with a link to reconnect it.


2

An Office 365 group is a Security Group within Azure Active Directory. Groups have their own permission model that comprises the roles Owner and Member. Owners: manage the group (e.g. changing titles, managing members and privacy settings) Members: collaborate around content (e.g. conversations in Yammer and Outlook, documents within a SharePoint team site) ...


Only top voted, non community-wiki answers of a minimum length are eligible