Microsoft SharePoint Online Spoke: action "Look up File Permissions" returning blank/null [] arrayProblem: The "Look up File Permissions" action returns a blank/null [] array.Cause: When the Azure application is configured, all the permissions are provided as delegated permissions. This application is used to fetch the OAuth tokens using the Authorization Code grant type. However, if the user's credentials do not have the necessary access to the files (such as being the owner or editor permissions directly or via Group), they will not be able to fetch the permissions of the files. In such cases, the response returned will be an empty list (blank/null [] array).This is the expected default behaviour, that is, users can access only those files for which they have the necessary permissions.Solution: To resolve this access issue, it is suggested to use the Client Credentials type instead of Authorization Code and provide the API permissions on the application level as shown in the screenshot below where the type is application. Configuration (Azure portal side) : Provide the permissions on the application level similar below as the type is application (refer link for more details on SharePoint Online Spoke configuration). Note: The permissions suggested in the screenshot are for the "Look up File Permissions" action. For the successful execution of other actions, the respective API permissions should be added (For example Sites.ReadWrite.all, Files.ReadWrite.All, etc). To determine the exact permissions required based on your organizational policies, please contact your SharePoint and Azure Administrators. if an issue is occurring with the Connector app, use the screenshot below for an example however if it is required to execute write/create actions along with the Connector app, a higher level of permissions will be needed. Please contact your SharePoint and Azure Administrators to determine the exact permissions required based on your organizational policies. Configuration (ServiceNow Side): Post creation of the Graph Application Registry (refer to the link for more details on SharePoint Online Spoke configuration), instead of Authorization Code, please select "Client Credentials" as highlighted below, all other steps will remain as it is. Note: Customers will need to work closely with their Azure and SharePoint admins to set up and understand access levels and other security-related parts.