Getting issues after Microsoft SharePoint Online Spoke is configured
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2023 10:20 AM
I have done the spoke setup and tested the connection after creating the credentials. Below is Get OAuth token success message.
When I test with the Get List Action from the flow, am getting the 404 error like below.
If i use Look up sites action am getting Invalid token as below.
Can anyone help me what is happening and what is the mistake?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2024 01:54 AM
Same issue here. Did anyone find a solution?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2024 04:56 AM
Hi all, in my case the issue came from missing site permissions.
In the past SharePoint only supported the setting "Sites.FullControl.All". There is a new and safer option "Sites.Selected". But if you use that, you also need to grant specific write access by running the following command in PowerShell:
Grant-PnPAzureADAppSitePermission -AppId '{AppID}' -DisplayName '{AppName}' -Site 'https://{TenantName}.sharepoint.com/sites/{SiteName}' -Permissions Write
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2024 08:11 AM
Same error here. OAuth token successful. But running test actions and getting Invalid authorization code. Any idea?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2024 12:14 AM
@Paul Kunze I have all the required permissions but still getting the same error. And further couldn't get the New access token using postman. Postman Error states 'HTTP Error 400. The request URL is invalid'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2024 11:23 AM
ServiceNow support was able to help me get this issue cleared. There was an issue with the certificate uploaded