Azure AD create entry snap failed unexpectedly

Hi, Please provide boolean value for accountEnabled with expression disabled.

You can also trying sending value from upstream as shown in below screenshot.

Hello,

I’ve tried changing to expression disabled and I receive the following error:
“Failure: REST API service endpoint returned error result: status code = 403, Reason: REST API service endpoint returned error result: status code = 403, reason phrase = Forbidden, refer to the error_entity field in the error view document for more details, Resolution: Please check the values of Snap properties.”
or I receive the following error:
“Failure: REST API service endpoint returned error result: status code = 400, Reason: REST API service endpoint returned error result: status code = 400, reason phrase = Bad Request, refer to the error_entity field in the error view document for more details, Resolution: Please check the values of Snap properties.”
I’ve checked the Azure account setup and it follows the below documentation on having the right access also I have access to data from the AD account by using the List Entries Azure AD snap and I receive the correct information.
https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/1249608011/Application+Configuration+in+Azure+Portal+for+OAuth2+Account+to+use+in+Azure+Active+Directory

P.S In the second print you posted I’ve noticed that you receive the same error as I have initially.

Hello,
I have tried with different permissions and found that if ’ Directory.ReadWrite.All’ permissions is configured in azure portal then there is no permissions issue.


When only Directory.Read.All permission is configured in azure portal there would be 403 error.

In case there is no issue with app registration and permissions, then there could be issue with Snap configuration. Please provide a complex password for create user instead of ‘password’.
for example : xAA45WwvJ]6NMw+bWH-d

Hello,

I have the Directory.ReadWrite.All permission in azure portal, attached screenshot below of all permissions granted.

I’ve changed the password to a more complex one but unfortunately I still get the 403 error:

Hi,
Can you please try to re-authorise the account once and give it a try.
If it doesn’t work the only issue would be scope and Tenant domain name. Please try with specific tenant domain name.

Hi,

Re-authorised the account but still got the same 403 error.

The scope is exactly as the one you provided in the last screenshot but the the tenant domain name is not with “.onmicrosoft.com” at the end but more like “example.abc”. This being the primary domain name.
Don’t know if that could affect the snap and throw the error.

Hi,
I agree tenant domain name shouldn’t be causing 403 error.
I am not sure if you are using client credentials or authorisation code grant type. When I tried with client credentials I got 403 error.

But when I tried the same with authorization_code as grant type it worked for me.

Please try with authorization_code and re-authorise the account. Hope this will help you, if you are already working with authorization_code and still facing 403 error, I might need more information to check the issue. As of now with provided permissions at app level and scope in account level there shouldn’t be any 403 error.

Hello,

With both authorization code and client credentials I get the 403 error. I can refresh the token and authorize the account but get the same error.
Please let me know what other information I can provide to better help with understanding the situation and finding a resolution to the issue.

Hello, can you please share exact error details from snap output and account settings. So that I can see what am I missing.

Hello,

I’ve attached the the json output from the creaty entry snap and a print of the account setup.

Create_Entry output0_error.json (4.0 KB)