Skip to main content
Participating Frequently
October 15, 2025
Solved

Oauth2 Microsoft Products and Connectors

  • October 15, 2025
  • 15 replies
  • 222 views

I am having issues setting up a Oauth2 for Microsoft products. I cannot get a successful API call even though I am able to with client credentials in Postman. Have others been having issues with this? Is there something I’m missing. I’ve been following this guide amongst trying many other things: Connector | Microsoft Graph

    This topic has been closed for replies.
    Best answer by afleury

    @bblanch I had a similar issue with a different API using OAuth2. Try creating it via HTTP connectors first instead of trying to create the connection via the Agent Studio Action. I think it’s a bug with Agent Studio.

     

     

    15 replies

    Angus Walker
    Inspiring
    October 20, 2025

    If it works though Postman (though it might not today, with postman being down because of the AWS outage 🤣), but not with identical settings from MoveWorks, maybe your Azure Application Registration has some security, blocking external requests?

    Check with your security guys (ours are always blocking access from URLs and ports, etc, for good reasons of course, but still a pain in the xxxx🤣) .

    Apart from that, I’m lost for suggestions.
    Maybe the Moveworks guys can see more information in the logs.

    Angus Walker
    bblanchAuthor
    Participating Frequently
    October 21, 2025

    That’s a good point I’ll look into security policies because I’m not having any issues in Postman, but getting this empty response every time in Moveworks.

    Kevin Mok
    Community Manager
    October 21, 2025

    Yeah, this is odd. If nothing works, I advise opening a support ticket. You can try rotating the secret as well and see if that works

    afleury
    afleuryAnswer
    Inspiring
    October 22, 2025

    @bblanch I had a similar issue with a different API using OAuth2. Try creating it via HTTP connectors first instead of trying to create the connection via the Agent Studio Action. I think it’s a bug with Agent Studio.

     

     

    bblanchAuthor
    Participating Frequently
    October 22, 2025

    That worked ​@afleury thank you so much to everyone who responded!