Survey Actionable Email not working as expected
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2021 10:19 PM
We are configuring Actionable email notifications from ServiceNow and as expected we are able to receive emails with questions and with submit button.
When we try to submit the form, we are receiving “The remote endpoint returned an error (HTTP 403). Please try again later” and ServiceNow is suggesting connecting with internal email admins to check if actional messages are enabled in the environment and we don't have clear documentation on what configuration needs to be enabled at O365 side.
Can someone help to troubleshoot this issue?
- Labels:
-
Incident Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2021 08:08 AM
Please check if you have an entry for "outlook" under "Syatem oauth>>Application registry"
Raghav
MVP 2023
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2021 11:16 AM
I have this same issue after upgrading our Dev instance to Quebec. I checked to make sure we still have an entry for "Outlook Actionable" under "System oauth>>Application registry". I'm not sure whether it's populated correctly, but it's there.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2021 03:34 AM
There is a possibility that the credentials have been overwritten.
To populate it correctly there is an OOB fix script. You can remove the client secret from the application registry and run the fix script to check if it is working.
I am pasting the screenshot of the script below:
Before executing this script, check that the sys_id is same as the record in application registry and also remove the "client secret" from the already existing record.
Please mark this correct/helpful accordingly
Raghav
MVP 2023
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-10-2021 03:10 PM
It turns out the problem for us was the wrong URL was inserted into the Client ID field on the OAuth OIDC Entity - Outlook Actionable configuration.