Skip to main content
Question

Incompatible built-in connector???

  • March 23, 2026
  • 5 replies
  • 56 views
eberteo

I have the following built-in connectors, and I have no customized connectors yet.

  1. ms_graph    Microsoft Graph (built-in connector)
  1. msgraph_teams    Microsoft Graph (built-in connector)
  1. msteams    Microsoft Teams (built-in connector)

And I’m working setting up the following plugin https://marketplace.moveworks.com/plugins/outlook-lookup-availability. However I noticed that I already have the Microsoft Graph built-in connector, therefore I was wondering if I need to set up a customized connector even thought I have an existing pre-built one. Or if I need to configure a customized connector to build the mentioned plugin? The reason why I’m asking this, it’s because am getting different answers when using Moveworks Agent Architect.

    5 replies

    Kevin Mok
    Forum|alt.badge.img+1
    • Kevin Mok
    • Community Manager
    • March 24, 2026

    Hey ​@eberteo - can you please work with your Customer Success team so they can enable built-in connectors in Agent Studio?

    eberteo
    • eberteo
    • Author
    • Known Participant
    • March 24, 2026

    Hey ​@Kevin Mok I have the built-in connector enabled on Agent Studio, I get to the point where I inherit the existing connector, the issue comes when I need to set up the body for the request. According Agent Architect, it says that I have to set up a Oauth 2.0 verification process manually although I have the built-in connector, which is the reason why my json payload fails. 

     

    Here’s the message (AI disclaimer): 

    I can absolutely help you build this! However, before we dive into the architecture, there is an important platform limitation to note regarding your connector strategy.

    ⚠️ Built-in Connector Limitation
    While you have enabled Built-in Connectors for Agent Studio, the documentation explicitly states that the Microsoft Exchange Online and Microsoft Teams built-in connectors are not supported in Agent Studio. To achieve this use case, you will need to create a custom HTTP Connector using OAuth 2.0 Authorization Code to authenticate with the Microsoft Graph API so the assistant can securely query calendars on behalf of the user.

    Kevin Mok
    Forum|alt.badge.img+1
    • Kevin Mok
    • Community Manager
    • March 24, 2026

    ​@eberteo You have to use your ms_graph connector which is most likely the OAuth 2.0 one… Please share the base url, endpoint, and payloads you are using in your http connector. Also any documentation about the endpoint

    eberteo
    • eberteo
    • Author
    • Known Participant
    • March 25, 2026

    Hey ​@Kevin Mok , I just noticed that a new update has been released on https://marketplace.moveworks.com/plugins/outlook-lookup-availability and now I’m able to install it directly instead of building it. However I still need it to set it up with a Connector after installing the plugin.

    Therefore I used the one you recommended ms_graph. The plugin installed: 

    • One HTTP Action.
    • Two Compound Actions.

    and when testing its HTTP action, I got the following error:
     

     

    So my guess would be that the existing built-in connector does not work, and I might have to set up a new one. (this means create a new account in Teams and API keys. Am I correct?

    Kevin Mok
    Forum|alt.badge.img+1
    • Kevin Mok
    • Community Manager
    • March 26, 2026

    Hey ​@eberteo - that’s right. For calendar plugins, the connector uses a different type of authentication which uses delegated auth -- meaning it’s a connector that uses only the user’s permissions. The built-in ms_graph connector has a different type of OAuth 2.0 authentication and it has different scopes.

    Please take a look at this guide that explains how to set it up - also the link you provided has a “How to implement” section

    Terms & ConditionsCookie settingsAccessibility statement