Hi Kris, thanks for the reply! Specifically to answer your questions:
Could you please share a screenshot of your flow's configuration? I haven't created a final flow yet, it's going to be relatively basic pulling from the Graph and keeping a list of users in sync in a CRM system.
Do you use the HTTP action to access your Microsoft Graph API within your flow? Yes, it would be the generic HTTP action.
Do you want to handle more records than are returned in a single call from your Microsoft Graph API? Yes
Further, could you please show more details about your scenario? Yes, I was going to be using the Microsoft Graph to retrieve a fitlered list of AD Users (into the tens of thousands). The query would be all enabled users not containing "#" in their UPN. The results would then be used to ensure each user is listed as a 'contact' in a CRM system (simple contact details, name & email maybe title).
I wasn't sure if there was a known way to implement paging with the Graph or if it generally would work "plug and play" as-is with the paging settings on the HTTP Action connector. I was also hoping I could find some documentation or someone with previous experience using the graph with the HTTP Action connector and paging - if not I'll give it a shot myself and see how it goes.
Thanks for the response!
