How to handle 'meeting_requires_sign_in' error for Microsoft Teams calls

Last updated: October 24, 2024

When recording Microsoft Teams calls, you may encounter a meeting_requires_sign_in sub-code error. This article explains how to handle this error and provides important information about using signed-in Teams bots.

Using Signed-in Teams Bots

To bypass the meeting_requires_sign_in error for Teams calls, you can use signed-in Teams bots. Here's what you need to know:

  1. Signed-in Teams bots allow you to join meetings that require authentication.

  2. You can set up a signed-in Teams bot by following the instructions in our Signed-in Teams Bots Overview documentation.

  3. Currently, only a single Microsoft Teams account can be used for authentication.

Important Considerations

  • The bot will be associated with a single MS Teams account, which means you cannot customize the bot name for different clients or rotate sign-in credentials for different users.

  • By default, the bot will only sign in when it's required to join a meeting. It won't automatically sign in for all Teams calls.

Configuring Sign-in Behavior

You can configure when the bot signs in to Teams calls:

  • Default behavior: The bot only signs in when required to join a meeting.

  • Optional: You can configure the bot to always sign in for all Teams calls, regardless of whether it's required.

For more detailed information on configuring sign-in behavior, please refer to our documentation on Will the bot always sign into Teams calls?

Remember to check the configuration options when setting up your Teams credentials to ensure the bot behaves as expected for your use case.