I do not think so.
Site collection admin should be Azure AD identity (group or user). It exists at tenant level.
SharePoint group exists within SharePoint site.
Instead you should be able to create an AAD Security Group (login to https://portal.azure.com/, then Azure Active Directory, Groups, + New Group), wait ~10 minute, then you can
manage group ...
To correct this same issues we had to find the group within SharePoint and open it to see the members. On this screen you need to go to "Settings - Group Settings", then changed the option "Who can view the membership of the group?" from "Group Members" to "Everyone".
I guess you want the group members be able to edit permission of other group? If so, for default permission levels, you will need to grant full control.
When you edit permission level, you can find the site permission with named "Manager Permissions". It is the permission needed to assign permissions to users and groups.
For more information, ...
Currently adding user/group as Site Collection Administrators is not possible using Site design JSON.
addPrincipalToSPGroup action currently only supports the Visitors (permission level: read), Members (permission level: contribute or edit, depending on the site template), and Owners (permission level: full control) groups.
Source: Add users (principals) ...
After creating a SharePoint group, you need to assign the permissions to it at site (web) level.
Add a new action 'Send HTTP request to SharePoint' and configure the action to use endpoint as below:
roledefid is for Permission Levels which are as follows:
Did you delete a security group in the M365 admin center or simply remove the permission of a SharePoint group?
For M365 admin center, I am not sure if there is a way to restore it. You can open a service request for more help.
If you just remove the permission of the group in Site permissions page, you can just re-assign proper permissions there. It still ...
Here are the steps you can try:
Declare an array and initialize it with group ids like [2, 3, 4, 5]
Declare a string variable to store all the emails (email1;email2;)
Declare another string variable to store current email from JSON parse action
Add "Apply to each" action to process group id array
Within "Apply to each", add "Send an ...
It seems to have something to do with Access Control for Unmanaged Devices, which is configured to restrict end users’ actions (Download, Print, and Sync commands) in Office apps.
Do you have sensitivity labels set in your tenant, or see Confidential labels in this site? I haven’t been able to enable this permission level in my tenant, possibly due to ...
Quoting the official document:
Membership to the site collection owner and member groups are kept in
sync with the membership of the private channel within Teams.
Any changes to the membership of Owner or Member groups in SharePoint
Online will be reverted to private channel membership within four
So technically, you can sync a ...
There is no way to make a SharePoint Group as site collection administrator. As a workaround, you could make an offcie 365 group as site collection administrator.
Create a Office 365 group and add users to it. Then go to SharePoint admini center, choose the site and click permissions. Add the Office group as admin.
Unfortunately for Sharepoint groups no, and this has been a long standing caveat with Site Collection Administrators - they can only be defined users.
You can use Azure AD / Office 365 Security Groups though.
This link to previous question explains this well this very well.
Try using your flow like below. This works for me:
OR simply like:
I have used endpoint like: /_api/web/sitegroups/removebyid('<group-id>'). Group ID is enclosed by single quote (').
In my case I am the owner for both group and flow.
You can ignore the flow output in this case, all you have to do is to remove the Headers part from your Flow action, everything else looks OK. All you need is the POST method to the _api/web/sitegroups/removebyid([id])
Note the headers accepts JSON string, but you're providing it as a JS object. Removing it altogether will make it work.
As long as you're ...
Run the PowerShell with SharePoint Online Management Shell.
Get started with SharePoint Online Management Shell for your reference:
Similar issue post for your reference:
Update your management shell to a current version; I would strongly suggest using the PowerShell Gallery version for easy updating in the future, if you're currently using the MSI.
You will want to uninstall the MSI version prior to installing the PoSh gallery version.
If the REST API is acceptable, you can get the groups for a user by using their user name using the following query:
https://server/sites/site/_api/web/siteusers?$filter=Title eq 'The User Name'&$select=Title,Id,Groups/Title,Groups/Id&$expand=Groups
Obviously you can choose to return more information about the user or the groups by including more ...
Your request should be using GetByName instead of GetByTitle
So your request should be: