Getting 302 error code through Chat Agent using Microsoft Team integration for API actions

I’m trying to create an integration between Quick and Microsoft Teams to execute API actions via Chat Agent, but I’m having trouble. After setting up the integration with user authentication and logging in successfully, I consistently get a 302 error code when launching an API call through the Agent Chat. The only documentation I’ve found is this:

Has anyone else encountered this error? Is there any additional documentation that outlines the necessary configurations from Microsoft Teams step by step?

Thanks in advance.

Regards

Hello Dario,

I think A 302 error typically indicates a redirect issue during the OAuth authentication flow.

Although you have followed the official documents but the issue could be caused by incorrect or mismatched redirect URI. For Quick integrations, you need to ensure:

  • Correct Redirect URL: Use us-east-1.quicksight.aws.amazon.com/sn/oauthcallback Note: Please be mindful when interacting with displayed links. as your redirect URI in your Azure AD application registration

  • Exact Match: The redirect URI in your Azure AD app registration must exactly match what Quick expects

  • Region Consistency: Make sure you’re using the correct region (us-east-1 is the default)

Please check that and if it still does not work, Please reach out to AWS supportt by opening a case. the support engineer should be able to support you.

Cheers,

Deep

Hi @dromeroc,

Following up here as it’s been awhile since last communication took place on this thread; did you have any additional questions regarding your initial post?

If we do not hear back within the next 3 business days, I’ll close out this topic.

Thank you

Hi,

We are currently awaiting assistance through an open AWS support case to resolve the issue.

Thanks,

Regards