Hi,
I’m trying to troubleshoot a 401 error that I receive, without any further error message. Here’s my situation:
We’re trying to connect Make.com to Microsoft Dynamics 365, but the client has no budget for Make.com enterprise to use the Dynamics premium app. So instead, we figured we can set up a custom HTTP request through OAuth 2.0.
I’ve basically followed Make.com’s documentation on creating an Azure AD app for OAuth, up until step 8 (changing the redirect URI to Make’s default one for OAuth 2.0 instead of the Microsoft Dynamics specific one, and OAuth 2.0 requests for setting up the HTTP module in a Make.com scenario. Following the Dynamics documentation, I’ve added the scope .default, so the connection inherits the Azure AD app’s scopes for the required endpoints.
So far so good, this connection worked and I am able to reauthorize and reverify without issue.
But now I’m setting up a module inside my scenario to create a Lead in Dynamics 365, and when I try to run the module it returns a 401 error. There’s no further message attached, so I have no idea where in the process it’s getting stuck. This is what my module config looks like:
The additional headers are added based on Microsoft Dynamics documentation, and as far as I can tell, everything should be there. But the result is this:
Spoke to the integration partner, other than the original authentication they don’t see anything in the logs on their end.
Has anyone tried this before and able to tell me what’s the problem here?
