We tried the new Office 365 groups connector. They are really great, but we found one minor issue:
From the "Get members" action you can get the members' emailaddresses. However the "Remove members" action doesn't seem to accept the emailaddres if it isn't identical to the upn.
It would be nice if we could get the upn's as well from the "Get members" action or allow the Remove members to accept any emailaddress.
Could you please show a screeshot of your flow's configuration?
I have made a test on my side and don't have the issue that you mentioned. My flow's configuration as below:
The flow works successfully as below:
In default, the UPN of a user should match the primary Office 365 email address of the user. In other words, the UPN of a user is same as the email address of the user in default. The User's Email field of "Remove member from group" action is required to fill a user's fully qualified email address (ex. firstname.lastname@example.org) rather than the UPN of a user and it only accept office 365 email address.
In addition, you could get the UPN of a member from the "List group members" action, because the output the "List group members" action returned contains UPN (User Principle Name) property. The output the "List group members" action returned as below:
More details about the Office 365 Groups connector, please check the following article:
When using the connctor to get member from a group, it returns a long emailaddress (email@example.com).
When feeding this email into remove members from a group, we receive the following error:
"message": "Uri is invalid for a DELETE operation. The URI must refer to an entity.",
When need to feed the long emailaddres to "Get user profile (v2)", from where we can get the upn. The upn is a short email address (firstname.lastname@example.org)
Join digitally, March 2–4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!
Many congratulations to the Season 1 2021 Flownaut Crew!
Check out our new profile badges recognizing authored solutions!
Check out the community blog page where you can find valuable learning material from community and product team members!