Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Unknown error comes when adding user to microsoft entra group using Add user group action spoke

Santosh Kumar 1
Giga Expert

Hi,
I'm trying  to add a user to a group using Microsoft Entra spoke and Add User to Group Action. it seems the actual step is getting completed but after that an error comes as "Unknown Error " thereby the flow gets exited by throw error exception. 
Then I'm not able to know the actual error or not able to resolve the issue. Your help will be appreciated.

Here is the screen capture

AddUserError.png


Thank you,

Sanotsh

 

1 ACCEPTED SOLUTION

Santosh Kumar 1
Giga Expert

Hi, 

The issue resolved after continuous explore and trialing different options.

The input parameters to the "Add User to Group" action under Microsoft Entra (Azure AD ) should be properly mentioned in the label header so that the user can understand the input parameters should be specific exactly what AzureAD expects and not from Servicenow user table parameters as most of the cases the parameters are having same names.
Here the UserID parameter is different in Servicenow than in AzureAD. So we have to user Lookup User to get the actual UserID from AzureAD and use that UserID parameter in Add User to Group Action.

I think the label can mention User ID from AzureAD instead of only "User ID" and the error message should mention properly on the invalid parameter or similar and not as "Unknown Error". This error message gives no clue how to troubleshoot and eats our hours time to know the RCA.
Thanks
San 

Thank you.

View solution in original post

6 REPLIES 6

Hi Mark,
Thanks for confirming. You need use the result of Lookup User action to retrieve the UserID in the Ass User action input. Let me know once you try this and I'm sure that will resolve this issue.

Mark Weber1
Tera Contributor

Hi Santosh, that's what I am doing, and it shows the correct user ID in the logs. I will pick this up again next week