EDIT - I do have a work around for this SPECIFIC issue, @marciokataoka ... I'll post it separately, because this is a bit of a side note.
Using the Graph Send an HTTP request action should have all the permissions of the user using them, though, right, @Expiscornovus?
Whilst I do think that the Azure app with all the required permissions is the best way to 100% ensure there's no permissions getting in the way of things ... the Graph action should work to the user's perms.
So ... I'm making an assumption, but I'm assuming that @marciokataoka, is using that within a flow. I think that one is a safe assumption. A bigger assumption is that Marcio (more assumptions! this time the name! 😅) is at the right permissions level themselves.
However I'm literally the Global administrator, which *should* mean I'm good. Yet this still happens for me.
We're all not alone, either ... here's something on MS Q&A.
Possible Work Around
I'm still (foolishly) playing with mine trying to get it to work, though, Marcio. Because there's something that I've noticed with the SharePoint and Graph HTTP request actions is that if you play around with the URI and the various ways of hitting the right endpoints or HTTP encoding of '{' (and more), then suddenly things start work.
For example for this solution, I couldn't just send the number across, I had to HTTP encode curly brackets around it to get Graph to accept the call. Weird, but got there in the end.
Here, though, I'm trying to add rows (as that action is missing in the excel PA actions) with the values of site_id, drive_id, item_id, and table_name are all what you want them to be. I'm sending to this URI:
https://graph.microsoft.com/v1.0/sites/%7Bsite_id%7D/drives/drive_id/items/item_id/workbook/tables/table_name/rows/add
With this (generated) JSON:
{
"index": null,
"values": [["AA","05/01/2022","600"],["AA","05/02/2022","150"],["BB","05/03/2022","100"],["LB","05/15/2022","150"],["LB","05/16/2022","550"]]
}
One thing I'm about to try, though, is changing that API number to see if I can trick it a bit. 😈
So my current advice is to keep trying as many different combinations of the URI that you can, and maybe you'll get there. But like I say, I have a workaround for you in a second.
Otherwise, yeah, annoyingly maybe you'll have to make an Azure App. That isn't the worst thing in the world, though.
I'm wondering how one authorises external apps, though, because I already have a very sneaky, and easy, HTTP request solution for free users. But I'm not fond to post it on here for fear of Microsoft finding a way to block it. Anyway, if I can get that authorised easily enough, then it should make all of this really easy.
