Adding a user to a Microsoft Team or Office365 group

[Michaelvds]

Hello,

I'm having difficulties with adding users to an Office365 group.

These are my flows:

Flow 1: Takes the input from a Microsoft Form to a Sharepoint List.

Flow 2: Triggers whenever a new item is added to the Sharepoint list. Starts an approval. After the approval the user is created in Azure AD.

After the user is created in Azure AD I add the user to an office365 group using the Office365 groups -> Add member to group action.

I select the group from the drop down and I user the UPN based collected from the previous Azure AD -> create user action.

For some reason I keep getting this error: Action add user to group failed: Invalid target for navigation property update. URI must target an entity.

I already tried using the GUID but this gives me an error: Resource '......0-8beb-4300-ae3e-1ef9f543a14e' does not exist or one of its queried reference-property objects are not present. I used the Powershell Get-UnifiedGroup command to get this GUID.

Hopefully someone can help me solve this issue 🙂

Thanks a lot!

[abm]

Hi @Michaelvds 

This post might help.

https://powerusers.microsoft.com/t5/Building-Flows/Use-a-flow-to-add-member-to-Office-365-group/td-p...

[Michaelvds]

Hello,

Thanks for your answer! I found that post when doing some research to solve my issue. However the topic ends with a question.

What source should I use to extract the UPN from?

[abm]

Hi @Michaelvds 

Thanks for your reply.

Use Search for users.

[Jcook]

Hi,

Have you tried to use the Office 365 Groups action instead?

—Josh
If you like my post please hit the "Thumbs Up" -- If my post solved your issue please "Mark as a Solution" to help others

[Michaelvds]

Hello,

So I just tried using the Search for users -> upn. This gives me the same error:

{

"error": {

    "code": "Request_BadRequest",

    "message": "Invalid target for navigation property update. URI must target an entity.",

    "innerError": {

      "request-id": "440538f1-b6ab-415c-a27b-1110d4f181d4",

      "date": "2020-03-05T14:11:29"

    }

  }

Here's an overview of my flow:

}

[Jcook]

Hi,
The error is inside the apply to each loop. Can you open that in the run and post picture

—Josh
If you like my post please hit the "Thumbs Up" -- If my post solved your issue please "Mark as a Solution" to help others

[Michaelvds]

Hi,

Thanks for your assistance!

[Jcook]

@Michaelvds 

That is weird..

Are you selecting the group from the dropdown list in the action?

 —Josh
If you like my post please hit the "Thumbs Up" -- If my post solved your issue please "Mark as a Solution" to help others

[Michaelvds]

Yes, I do.

[abm]

Hi @Michaelvds 

Are you searching one user or multiple (Search for users v2)?

Thanks

[Michaelvds]

Hi,

I'm using Search for users v2 (limited to 1 entry)

[Michaelvds · Accepted solution]

Ok so I found a solution to my problem which, to be fair, was mentioned in the link provided by abm: 

https://powerusers.microsoft.com/t5/Building-Flows/Use-a-flow-to-add-member-to-Office-365-group/td-p...

[PCS_Titan12]

*Please Read This - Not the Top Solution but this is the solution/explanation*

Premise: I ran into this issue as well as I was trying to automate the Microsoft onboarding process for our clients. I reviewed the solution above provided by @Michaelvds, however it does not accomplish what we need. I use a Microsoft Form that triggers the automation when a new response is submitted. The form details information needed to create a user account that fits the emailing convention for the client company. I tested several ways by retrieving the UPN from connectors to hard-coding this field, all initially failing.

Issue: When I attempted to create a new user and add them to a given group as @Michaelvds  does above, error message above is returned when using the connector above to add a given user to an O365 Group

{

"error": {

    "code": "Request_BadRequest",

    "message": "Invalid target for navigation property update. URI must target an entity.",

    "innerError": {

  ...

  ...

  ...

}

Cause: Microsoft Servers has not had time to process and create the user entity or object in Office 365

Power Automate connectors communicate with O365 servers but ultimately Automate is Asynchronous or runs independently from the requests/actions you send to O365.

The above flow creates the user account but instantly jumps to the next action without giving O365 servers enough time to process or create the object in their systems.

Thus, when you try to add a user to a group, the task will fail because it tries to add a user that does not exist (yet) to a group.

Note: This does not apply to users that already exist in O365

Solution: You need to add a Delay action after creating the user in Azure.

I chose 30 seconds as this was the safest time it took for O365 to process our "create user" task

Note: In my example below, the User Principal Name is the email address, which I hardcoded using the emailing format, FirstName.LastName@someemail.com

This does not matter. You can use Azure AD "User Principal Name" function or O365 "Email" function like above which I tested and confirmed works in those ways.

Moving forward, it's good to keep in mind that automate runs asynchronously from the systems it tries to update. 

Have a great day everybody.

[Anonymous]

This may not be the selected answer but should be. Thank you!!