FortiSOAR Discussions

Enhancing Collaboration and Workflow Efficiency with FortiSOAR for Microsoft Teams

FortiSOAR for Microsoft Teams solution pack is a valuable integration that enhances collaboration and workflow efficiency within organizations. Here are some key points and benefits of the integration:

Seamless Integration: The solution pack seamlessly integrates Microsoft Teams with FortiSOAR, creating a bridge between the two platforms. This integration ensures that users can access FortiSOAR's capabilities directly from  their Microsoft Teams environment.

Workflow Streamlining: The integration allows organizations to streamline workflows, making it easier to manage tasks, approvals, and communication processes. Users can access FortiSOAR features without the need to switch between different platforms, reducing context-switching and improving overall efficiency.

Rich Inline Manual Input and Approval Forms: One of the notable features of this integration is the ability to send customized forms directly to Microsoft Teams users from FortiSOAR playbooks. This feature enables organizations to collect input and obtain approvals from both internal and external users. It enhances user experience and flexibility in gathering information.

Bi-Directional Integration: The integration is bi-directional, meaning that it allows for communication and data exchange between FortiSOAR and Microsoft Teams in both directions. This flexibility ensures that information flows smoothly between the two platforms, enabling efficient collaboration.

Creating Custom Playbooks:

Custom playbooks are specific workflows designed to automate and execute tasks within FortiSOAR. Here are the key steps and considerations for creating custom playbooks for use with the Microsoft Teams integration:

Add 'bot_enabled' Tag: Ensure that you add the default 'bot_enabled' tag to the playbook. This tag is crucial for the playbook to be recognized and triggered through the Microsoft Teams integration.

Define Action Tags: Create action-specific tags that represent the purpose or action to be performed by the playbook when triggered. For example, if the playbook is designed to seek user approval to block a particular indicator, you might create a tag like 'getApproval_BlockIndicator_msteams.'

Use Manual Input Step: Incorporate a manual input step within the playbook. This step is essential for passing inputs from Microsoft Teams users to FortiSOAR. The manual input step is configured to collect user responses effectively.

Leverage Context Information: To maintain context and identify the source of the trigger, use the {{vars.bot_context.conversation_id}} variable. This variable retrieves the ID of the team, chat, or group chat within Microsoft Teams that initiated the playbook.

Define Response Handling: Create a mechanism for handling and sending responses back to Microsoft Teams. A common variable, such as 'bot_response,' can be used to aggregate and send responses generated by the playbook back to Microsoft Teams.