SharePoint Permissions in Power Automate
Which account really runs each action, and why a flow that works for you returns 403 for everyone else.
If you want to master something, you have to understand its fundamentals deeply. They are the building blocks you stand on to reach the more complex ideas. Knowledge is like a house: you lay strong foundations first, then build upward. It sounds like a cliche, but it holds true, and solid fundamentals are what make good professionals. Under this tag I work on bringing you the fundamentals of each technology, from the small details that quietly make all the difference to the bigger concepts. My focus is mostly the Power Platform, but I will happily write about other things I find interesting along the way. Expect a mix drawn from technology and productivity. What matters most to me is that you walk away having learned something new you can build on.
Which account really runs each action, and why a flow that works for you returns 403 for everyone else.
Sums the values that meet several conditions at once. All conditions combine with AND, not OR.
Starts a workflow instantly when an HTTP request hits its URL. Test and production URLs behave differently.
Exports an Outlook email as a binary EML file by Message ID. Attachments are included inside the file.
Returns the current timestamp plus a number of time units. Always counts from UTC now.
Read optional manual trigger inputs safely with ?[] and avoid the missing-property error.
Provider SDKs often pull in dozens of dependencies when a simple HTTP request to the API would do.
Copies a file to another library or site. Version history and metadata don't carry over.
Converts a UTC timestamp into a target time zone. Returns a string with no offset or Z marker.
Move files past the 100 MB limit by splitting them into chunks, and know when to switch to Graph.
Returns one of two values based on whether a condition is true or false.
Starts a workflow at fixed times or intervals, like Unix cron. Missed runs are skipped, not backfilled.