I had one question regarding this flow. Why is the SharePoint List access not at the beginning? With that change you can optimize and only change the groups on the Sharepoint List without accessing the flow to change the declared variable.

Thank you

It was a very useful guide. Thank you so much for dedicating time for doing this.

I wanted to add an additional step that is required just before making the first call to the “HTTP Get Android Devices” and is that if your tenant has more than a 1000 devices the first Get will only get the first 1000.

To solve this I have made a Do-While, declaring a variable before with URI + filters for the first 1000 devices, and then in the get URI putting the variable on it. The same query replies with an attribute called “@odata.nextLink” with the new URI for the next 1000 devices.

Thanks so much for this guide! It’s helped me solve another problem we were having around device grouping based on user dept. I’ve got it working now, the only remaining struggle I have is the logic app status reports as failed. It will show failed if the device is already in the group or if the primary user no longer exists(this is a process thing for my team).
I was looking at adding a condition to filter out the failed tasks so it would show success if devices were already a member of the group but if I put a condition after checkmembergroups http call it will fail.

If you have any insight into where I could look or what I might be able to implement to help mitigate these false positives that would be amazing!

Thanks again and great post!!