Overview Use Power Automate to detect SharePoint files with file-level unique permissions by checking the HasUniqueRoleAssignments property on list items. REST API query Use the SharePoint REST endpoint to query items and include the fields needed for permissions evaluation. _api/web/lists/getByTitle('@{item()?['FolderName']}')/items?$select=ID,HasUniqueRoleAssignments,FileRef,FileLeafRef,FileSystemObjectType Method: GET SiteAddress: your SharePoint site Process each item Add an Apply to each action to iterate the results from the REST call. Set the input to: @{body('Get_unique_permissions')?['d']['results']} Check unique permissions Add a Condition action inside the loop and test whether the item has unique permissions.

Problem When a Power Automate flow uses a condition that evaluates to true, the flow may fail unexpectedly if the condition is not configured correctly in the new designer. Cause This issue often happens when the condition expression is not set up using the correct syntax or when the visual condition builder is unable to interpret the value as a Boolean. Fix In the condition action, switch to expression mode. Enter a valid expression that returns true explicitly.

Overview This post demonstrates how to create a SharePoint library using an out-of-the-box (OOB) list design via the Site Script ApplyListDesign REST API and how to call it from PnP PowerShell. While Invoke-PnPListDesign is useful for deploying custom list templates (see Custom document library template using PnP PowerShell), creating a library from an OOB list design requires calling the ApplyListDesign() REST endpoint. How it works (high-level) The front-end calls the REST endpoint: _api/Microsoft.