Discovery Subscription Error : Failed to execute API - Missing service principal field: ClientId - if your Azure credential (service principal) was imported, please restart your MID server and try again
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-23-2020 11:31 PM
Discovery Subscription Error : Failed to execute API - Missing service principal field: ClientId - if your Azure credential (service principal) was imported, please restart your MID server and try again.
We had cloned our sub prod instance and upgraded to Paris, after upgrading the cloud discovery is not working and getting the above error.
I had deleted the cloned credentials from prod and re created and restarted the MID Server, but still same issue. is anything newly introduced in Paris version.
Same credentials are working fine in production.
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-24-2020 03:40 AM
Hope you have recreated the Service Account Also?
Mid Server is also restarted?
Refer this KB for more troubleshooting.
https://hi.service-now.com/kb_view.do?sysparm_article=KB0723531
*Please mark as Correct and or helpful if appropriate.
Regards
RP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-05-2021 11:49 PM
Hi Rahul,
Yes, i had restarted the MID server and re created the Azure credentials again after upgrading and cloning the non production instance.
the same credentials are working fine in production instance.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-26-2020 05:49 AM
Hi,
According to me this can be the credentials issue and also rights assigned to that account in azure.
Thanks,
Ashutosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-05-2021 11:54 PM
Yes, i had restarted the MID server and re created the Azure credentials again after upgrading and cloning the non production instance.
the same credentials are working fine in production instance.