- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-15-2023 12:01 PM
Microsoft have changed their User Privisioning via the ServiceNow application in the Marketplace. It no longer allows basic authentication and instead uses oAuth. No problem as it's more secure, but following the Microsoft guide it points to some generic ServiceNow docs. I've since been able to get Azure to connect to ServiceNow, I get the Access Token but Azure will not complete the configuration with the following error:
You appear to have entered invalid credentials. Please confirm you are using the correct information for an administrative account.
{"error":{"message":"Requested URI does not represent any resource","detail":null},"status":"failure"}
I'm on San Diego and wondering if Microsoft have made these changes for SCIM in Tokoyo/Utah as there's a lot of missing SCIM pages when you select San Diego in the ServiceNow docs.
Anyone had a similar issue?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-19-2023 03:36 PM
We have noticed the change in the Azure AD provisioning feature in the Azure Active Directory "ServiceNow" Enterprise application; It appears that during mid-March 2023, Microsoft changed the provisioning setup and documented to use OAuth authentication instead of Basic authentication. As of March 17, Microsoft seems to have switched back to basic authentication.
The relevant documentation from the Microsoft site is as follows:
https://learn.microsoft.com/en-us/azure/active-directory/saas-apps/servicenow-provisioning-tutorial
You can follow the instruction from KB1282230 to continue the configuration. If you have seen this changed back to Basic authentication, otherwise, you should need to contact Microsoft support for further assistance.
KB1282230: Microsoft's Azure AD User Provisioning Temporarily Switched to OAuth Authentication in March 2023
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1282230
Please be aware the Azure AD "ServiceNow" Enterprise Application is not a ServiceNow product; it was developed by and is supported by Microsoft; if you have future questions, please get in touch with Microsoft support.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-19-2023 03:36 PM
We have noticed the change in the Azure AD provisioning feature in the Azure Active Directory "ServiceNow" Enterprise application; It appears that during mid-March 2023, Microsoft changed the provisioning setup and documented to use OAuth authentication instead of Basic authentication. As of March 17, Microsoft seems to have switched back to basic authentication.
The relevant documentation from the Microsoft site is as follows:
https://learn.microsoft.com/en-us/azure/active-directory/saas-apps/servicenow-provisioning-tutorial
You can follow the instruction from KB1282230 to continue the configuration. If you have seen this changed back to Basic authentication, otherwise, you should need to contact Microsoft support for further assistance.
KB1282230: Microsoft's Azure AD User Provisioning Temporarily Switched to OAuth Authentication in March 2023
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1282230
Please be aware the Azure AD "ServiceNow" Enterprise Application is not a ServiceNow product; it was developed by and is supported by Microsoft; if you have future questions, please get in touch with Microsoft support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-20-2023 01:15 AM - edited ‎03-23-2023 08:23 AM
Thank you for the confirmation and links, really helpful.
Edit: Since 2023/03/20 we have reinstalled the app in Azure and Basic Auth is back on the menu!