cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Nick_Bloomfield
Frequent Visitor

Automatically add new SharePoint site members to a group

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. 

2 ACCEPTED SOLUTIONS

Accepted Solutions
Expiscornovus
Most Valuable Professional
Most Valuable Professional

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']}"
}

 

 

removebylogin.PNG



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


View solution in original post

Nick_Bloomfield
Frequent Visitor

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

View solution in original post

13 REPLIES 13
Expiscornovus
Most Valuable Professional
Most Valuable Professional

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.

 

sourceandtarget_group.png


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'])

 

 

 

 

empty_removed.png

 

 



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


Nick_Bloomfield
Frequent Visitor

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
Most Valuable Professional
Most Valuable Professional

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.



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


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
Most Valuable Professional
Most Valuable Professional

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']}"
}

 

addusertogroup.png



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


Nick_Bloomfield
Frequent Visitor

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
Frequent Visitor

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
Most Valuable Professional
Most Valuable Professional

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

 

getuserprofile.PNG



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


Nick_Bloomfield
Frequent Visitor

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.

Screen Shot 2022-05-02 at 11.00.59 pm.png

Expiscornovus
Most Valuable Professional
Most Valuable Professional

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']}"
}

 



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


Nick_Bloomfield
Frequent Visitor

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
Most Valuable Professional
Most Valuable Professional

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']}"
}

 

 

removebylogin.PNG



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


Nick_Bloomfield
Frequent Visitor

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

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (2,642)