Microsoft Teams

Send messages and notifications to your team members.

Category

Messaging and Conferencing

Pack

MicrosoftTeams

Configuration parameters

• credentials — Bot ID
• bot_id — Bot ID
• bot_password — Bot Password
• auth_type — Authentication Type
• redirect_uri — Application redirect URI (for Authorization Code mode)
• auth_code_creds —
• team — Default team (required)
• incident_notifications_channel — Notifications channel (required)
• creds_certificate — Certificate (Required for HTTPS)
• certificate — Certificate (Required for HTTPS)
• key — Private Key (Required for HTTPS)
• is_single_tenant_bot_type — Bot Type Converted to Single-Tenant
• min_incident_severity — Minimum incident severity to send notifications to Teams by
• auto_notifications — Disable Automatic Notifications
• allow_external_incidents_creation — Allow external users to create incidents via direct message
• external_form_url_header — The header of an external form hyperlink.
• insecure — Trust any certificate (not secure)
• proxy — Use system proxy settings
• new_incident_welcome_message — Custom New Incident Welcome Message
• longRunning — Long running instance
• longRunningPort — Listen port
• incidentType — Incident type

Commands (28)

• add-user-to-channel — Adds a member (user) to a private/shared channel.
• close-channel — Deletes the specified Microsoft Teams channel.
• create-channel — Creates a new channel in a Microsoft Teams team.
• microsoft-teams-add-user-to-channel — Adds a member (user) to a private/shared channel.
• microsoft-teams-auth-reset — Run this command if you need to rerun the authentication process.
• microsoft-teams-auth-test — Tests the connectivity to MicrosoftTeams.
• microsoft-teams-channel-user-list — Retrieves a list of members from a channel.
• microsoft-teams-chat-add-user — Adds a member (user) to a group chat. Notes: - This command works with the consent user, not with the bot. Which means, the member will be added to the given chat by the consent user, not the bot. - This command will fail if the consent user is not a member of the destination chat.
• microsoft-teams-chat-create — Creates a new chat. Note: Only one oneOnOne chat can exist between two members. If a oneOnOne chat already exists, it will be returned.
• microsoft-teams-chat-list — Retrieves a list of chats that the consent user is a member of. If 'chat' is specified, retrieves this chat only.
• microsoft-teams-chat-member-list — Retrieves a list of members from a chat. Notes: - This command works with the consent user, not with the bot. Which means, that the chat must include the consent user.
• microsoft-teams-chat-message-list — Retrieves a list of messages in a chat. Notes: - This command works with the consent user, not with the bot. Which means, that the chat must include the consent user.
• microsoft-teams-chat-update — Updates the chat name. It can only be set for group chats. Notes: - This command works with the consent user, not with the bot. Which means, that the chat must include the consent user.
• microsoft-teams-create-channel — Creates a new channel in a Microsoft Teams team.
• microsoft-teams-create-meeting — Creates a new meeting in Microsoft Teams.
• microsoft-teams-create-messaging-endpoint — Generates the messaging endpoint, based on the server URL, the server version, and the instance configurations. Note: The messaging endpoint should be added to the Demisto bot configuration in Microsoft Teams as part of the prerequisites of the integration's setup. For more information, see - https://xsoar.pan.dev/docs/reference/integrations/microsoft-teams#create-the-demisto-bot-in-microsoft-teams.
• microsoft-teams-generate-login-url — Generate the login url used for Authorization code flow.
• microsoft-teams-integration-health — Returns real-time and historical data on the integration status.
• microsoft-teams-list-messages — Retrieves a list of messages in a chat or channel. Notes: - When retrieving messages from a chat, this command works with the consent user, not with the bot. Which means, that the chat must include the consent user.
• microsoft-teams-message-send-to-chat — Sends a new chat message in the specified chat. Notes: - This command works with the consent user, not with the bot. Which means, the message is sent to the given chat by the consent user, not the bot. - This command will fail if the consent user is not a member of the destination chat. - This command may fail if the bot app has not yet appeared in the "built for your org" section in teams. - This command can only send messages from type 'message'.
• microsoft-teams-message-update — Updates a message.
• microsoft-teams-ring-user — Ring a user's Teams account. Note: This is a ring only! no media will play in case the generated call is answered. To use this make sure your Bot has the following permissions - Calls.Initiate.All and Calls.InitiateGroupCall.All
• microsoft-teams-send-proactive-message — Sends a proactive message to any Microsoft Teams user across the organization. This command enables direct communication with users without requiring them to be in a specific team or channel. Note: Either 'message' or 'adaptive_card' must be provided, but not both.
• microsoft-teams-token-permissions-list — Retrieves the API permissions associated with the used graph access token. Note: Use this command if you encounter insufficient permissions error when attempting to execute an integration command. Compare the permissions list obtained for the token with the permissions required for the desired command (can be found in the integration documentation). If there are missing API permissions, add them to your application, and then run the `microsoft-teams-auth-reset` command (as described here - https://xsoar.pan.dev/docs/reference/integrations/microsoft-teams#microsoft-teams-auth-reset).
• microsoft-teams-user-remove-from-channel — Removes a member (user) from a private/shared channel.
• mirror-investigation — Mirrors the XSOAR investigation to the specified Microsoft Teams channel. Supports only standard channels.
• send-notification — Sends a message to the specified teams. To mention a user in the message, add a semicolon ";" at the end of the user mention. For example: @Bruce Willis;. If sending a reply to a message, the message ID must be provided and the reply will be sent via the Graph API which means the message will appear from the account used to authorize the integration instance and not the bot. Setting the account's name and picture to match the bot will make it appear to be from the same source.
• teams-send-notification-quick-action — Sends a message to the specified teams.