Recurring problem with the "List servicePrincipals" endpoint

Vasyl Artemiuk | Keepit 10 Reputation points
2024-10-29T12:27:59.8166667+00:00

When attempting to retrieve the list of service principals within the Microsoft organization, using the 

GET https://graph.microsoft.com/v1.0/servicePrincipals?$select=verifiedPublisher,servicePrincipalType,servicePrincipalNames,samlSingleSignOnSettings,replyUrls,preferredSingleSignOnMode,oauth2PermissionScopes,notificationEmailAddresses,loginUrl,logoutUrl,keyCredentials,signInAudience,info,id,homepage,displayName,tags,notes,disabledByMicrosoftStatus,deletedDateTime,appRoles,passwordCredentials,appRoleAssignmentRequired,appOwnerOrganizationId,tokenEncryptionKeyId,resourceSpecificApplicationPermissions,appId,appDisplayName,description,applicationTemplateId,alternativeNames,addIns,appDescription,accountEnabled&$top=999

endpoint, we encounter the following non-informative error in the response:

{
   "error":{
      "code":"UnknownError",
      "message":"",
      "innerError":{
         "date":"2024-10-28T10:41:32",
         "request-id":"30a45db3-bd23-43b5-a9d4-366483a8948b",
         "client-request-id":"30a45db3-bd23-43b5-a9d4-366483a8948b"
      }
   }
}

We first noticed this problem in early December 2023, but it resolved within a week. Unfortunately, the issue has reappeared, preventing us from delivering our service to customers. As a result, this regression is critical for us.

Is this a known issue? Does anyone else see the same problem?

Microsoft Security | Microsoft Graph
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. CarlZhao-MSFT 46,371 Reputation points
    2024-10-30T03:06:21.5666667+00:00

    Hi @Vasyl Artemiuk | Keepit

    I just made multiple calls to the API locally and it worked fine for me, so it doesn't look like a known issue. This should be related to your environment, calling the API in your context throws the above error.

    I suggest you open a support ticket to report the issue to the Microsoft support team, and the support team can help you pull the background log to find out the cause of the issue.

    {E3336CFD-3B92-474C-A302-271F35F38557}

    Hope this helps.

    If the reply is helpful, please click Accept Answer and kindly upvote it. If you have additional questions about this answer, please click Comment.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.