Automatically add new SharePoint site members to a group

[Nick_Bloomfield]

I've been able to solve most things when it comes to SharePoint and Power Automate, however this one has me stumped. What I'm trying to achieve seems like it should be simple enough using a send HTTP request however how to set the trigger has me at a loss. What I'm trying to do is:

When someone is added as a member to a SharePoint site (private group team site) then trigger a flow to automatically add that member to a specific group on a different SharePoint site. 

I can do this easy enough by creating a list and adding members there and have them automatically added to a group somewhere, however rather than require the list, I'm trying to achieve the same thing by simply having the flow look at a site's members list.

Anyone got thoughts on how this could be achieved? There's a Teams trigger 'when a new team member is added', I basically need this trigger but for SharePoint. 

[Expiscornovus]

Hi @Nick_Bloomfield,

When both source and target sites are group connected sites you could use the Office 365 Group connector actions.

Below is an example approach.

Additionally you could use a trigger condition and check if the @removed property is empty. If this is the case we are talking about the adding of a member. 

@empty(triggerOutputs()?['body/@removed'])

[Nick_Bloomfield]

Thanks for the reply, much appreciated. It's going to take me a moment to absorb the info you've provided and put it into practice. Keep you posted on how I go.

[Expiscornovus]

Hi @Nick_Bloomfield,

Yes, of course. Take your time to digest and test the setup/information I shared. If you have any additional question or if something is unclear let me/us know. Happy to help out.

[Nick_Bloomfield]

Tested this method and I feel like it's definitely on the right track. Applying this technique certainly takes a member added on one site and automatically adds them as a member to another SharePoint site, however not quite what I'm after. The trigger of 'When a group member is added or removed' feels right, however I then need it to add that member to a local group on another SharePoint site rather than the members group of the other SharePoint site (if that makes sense). My gut feeling is it probably needs some sort of 'Send HTTP request' action whereby you can specify the site URL and the GroupID of the specific group on the destination site.

[Expiscornovus]

Hi @Nick_Bloomfield,

Yes, I would also use a Send an HTTP request to SharePoint action for this. You could POST against the sitegroups(id)/users. In the body you can reuse the LoginName of the user.

Below is an example of that approach.

Change the ID (12) to the ID of your specific group

Uri

_api/web/sitegroups(12)/users

Body

{
"LoginName": "i:0#.f|membership|@{outputs('Get_user')?['body/userPrincipalName']}"
}

[Nick_Bloomfield]

I'm unable to test this at the moment as I need to request Azure access from the administrator to add the connector to 'Get User'. That being said I've got a feeling you've nailed it and this will do exactly what I'm looking for.

Thank you again for your expertise, it's much appreciated.

[Nick_Bloomfield]

I'm assuming the send HTTP request will only add the member to the group. My guess is it'll require a different string in the body to remove the member? If so is there a way to insert a control condition to distinguish between whether the member was added or removed and then depending on that outcome depends on which HTTP request gets sent, either the one to add the member or the one to remove the member?

[Expiscornovus]

Hi @Nick_Bloomfield,

Apologies, I made it a bit more complicated. Instead of the Azure AD Connector you could also use the Office 365 Users connector, specifically the Get user profile (v2). Are you allowed to use that one?

Btw, you can remove the trigger condition expression from the trigger action and add it to a condition action. This way you can check within the flow itself if somebody is added or removed (and execute different steps in the removed scenario in the If No section).

The expression is:

empty(triggerOutputs()?['body/@removed'])

is equal to true

[Nick_Bloomfield]

Awesome. Tested using the O365 Users connector and adding a member to a site now automatically adds them to the desired local group on another site. Love ya work. The condition action is working correctly, ie it follows a different path depending on added or removed, however I'm having issues with the correct string to remove the member from the group. 

The following Uri string I've used to remove a member from a group in other automations isn't working;

_api/web/sitegroups(37)/Users/removeByLoginName

and when using this string I've traditionally used {'loginName’:’Member Name Claims’} in the Body however substituting Member Name Claims for Mail in this instance.

[Expiscornovus]

Hi @Nick_Bloomfield,

Can you try adding the i:0#.f|membership| part to your value? Try something like below in the body:

{
"LoginName": "i:0#.f|membership|@{outputs('Get_user_profile_(V2)')?['body/mail']}"
}

[Nick_Bloomfield]

Note, I did initially try using the same string in Body as you demonstrated in your example above, however kept getting a failure error, hence why I've attempted to use the string above. Your example works perfectly for adding the member. Seems to have an issue with the term loginName and/or removeByLoginName.

[Expiscornovus · Accepted solution]

Hi @Nick_Bloomfield,

The loginName property is case sensitive, that was my typo (LoginName instead of loginName) in the last example, my bad 😁.

Btw, I was using double quote characters around the property and the value in the body value.

Just tested the below in my own development setup. That should work.

{
"loginName": "i:0#.f|membership|@{outputs('Get_user_profile_(V2)')?['body/mail']}"
}

[Nick_Bloomfield · Accepted solution]

You're a genius. Thank you sooo much for helping me out with this. Made the adjustments and it's now working 100%.