cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Regular Visitor

Office 365 Group - Add Member to Group returns 404 Resource Not Found

I am trying to use the 'Add member to Group' action in my flow.  I have a 'Create Office 365 Group' action working fine and I have a 20 second delay built in.  But when I pass the Group ID to the 'Add member to Group' action it returns a 404 Resource Not Found error.  Here is the error...

 

"Resource 'c843d56d-a727-4c4d-bdb1-c03e4d097d15' does not exist or one of its queried reference-property objects are not present."
9 REPLIES 9
Highlighted
Dual Super User II
Dual Super User II

Hi @fubak 

 

Is the group id correct - check id in azure portal

 

Is the user conext under which Flow is running, an Owner of the group?

 

Regards,

Reza Dorrani

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

Highlighted
Community Support
Community Support

 

Hi @fubak ,

 

I did a test on my side, even if I didn't use Delay, Flow could run successfully.

You need to ensure that the connection between Create group action and Add member to group action is created using the same email address.

Image reference:

58.PNG

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Highlighted

Hi,

 

I had this step working fine and suddenly start getting the 404.

Before that step I do have abn HTTP request to get the group, so I know is accessible.

 

Any help to solve it?

Highlighted

Hello,

The error is probably in your http action. Please use a compose action to put the ID in before using it in the add group members action.

Now run the flow and see if the group ID is that what is expected.




Did I answer your question? Mark my post as a solution!

If you like my post please hit the Thumbs Up


Proud to be a Flownaut!


Check out my blog for Power Automate tips, tricks, and guides
FlowAltDelete




Highlighted

Hello @Jcook 

Failure is using the Add User of Azure AD (not an HTTP request)

 

HTTP request is used to check if team is accessible before trying to add the user.

 

https://graph.microsoft.com/beta/groups/groupID

Highlighted
Anonymous
Not applicable

Did you ever get a resolution to this issue, same thing work through 3 weeks of Dev on the hand off to the business this is just appeared.

Highlighted

didn't found resolution. i just configured run after failure step so flow doesn't fail.

I guess no one in MS will look into this as all other bugs they have

Highlighted

Hi @Jorge_s 

 

Please consider creating a ticket with Power Automate support:

https://flow.microsoft.com/en-us/support/





Did I answer your question? Mark my post as a solution!

If you like my post please hit the Thumbs Up


Proud to be a Flownaut!


Check out my blog for Power Automate tips, tricks, and guides
FlowAltDelete




Highlighted

I would increase your delay to 1 min.  I had failures running a similar flow with 10s then 30s delay .. it was creating inconsistent success.  Finally with 1 min it seems to have resolved all 404 issues.

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

Power Platform ISV Studio

Power Platform ISV Studio

ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.

Users online (7,176)