All use cases

Private Security Messaging

This automation sends a personalized, one-to-one security card to a specified recipient while checking whether the security bot is installed and requesting installation when needed. It locates the private conversation, sends the notification, and returns the delivery status and conversation identifier.

Notification

Integration

Provisioning

Collaborative workspaces

Trigger

The flow is triggered with a recipient user principal name and message text, with optional card title, facts, link URL, and link label.

Outcome

The flow returns the private conversation identifier, a delivery status, and whether the bot was installed during the request.

Trigger

The flow is triggered with a recipient user principal name and message text, with optional card title, facts, link URL, and link label.

Outcome

The flow returns the private conversation identifier, a delivery status, and whether the bot was installed during the request.

Before

Security staff had to locate the recipient’s private bot chat before sending each notification. They also needed to check whether the bot was installed and handle installation when it was missing, creating a repeated dependency before delivery.

How it works

Build a personalized security card from the recipient, message, supporting facts, and optional link.
Check the recipient’s bot installation and request installation if it is missing.
Find the private chat, send the card, and return the delivery result.

Workflow details

Message preparation: The workflow accepts a recipient, required message text, and optional title, facts, and link. It assembles these inputs into a structured security card with contextual details and an optional action button.
Installation check: It checks whether the security bot is already installed for the recipient. If no installation is found, the workflow requests installation for that person before continuing.
Private conversation lookup: After validating or arranging the installation, it finds the one-to-one chat associated with the recipient and the bot so the message is routed to the correct private conversation.
Delivery: The prepared card is sent through the bot to the identified chat. The workflow treats a returned message identifier as evidence that delivery was accepted.
Result reporting: The caller receives whether the message was delivered, whether installation was needed during the process, and the conversation identifier. The supplied demonstration replays integration responses locally with synthetic results.

What changed

Each notification now follows one automated path that performs the installation check, handles a missing installation, finds the correct private conversation, sends the card, and returns the delivery details to the caller.

Work removed

Manually checking bot installation, requesting installation when needed, locating the recipient’s private chat, and confirming the message delivery result.

Expected outcome

One recurring private-chat search and associated installation check are removed from each notification request, producing a consistent handoff with delivery status.

Connected tools

Microsoft Graph - Teams

Related flows

All use cases

Explore more workflows with similar topics or tools.

Automated Notable Event Status Updates

This automation receives notable security alerts, locates the corresponding notable event through a controlled search process, and updates its status with a comment in the security platform. It also monitors search completion and emails an administrator when the search fails.

Explore use case

Phishing Email Risk Triage

This automation analyzes reported phishing emails by checking sender reputation, scanning embedded URLs, evaluating attachments, and using an AI agent to determine whether security involvement is required. It consolidates the findings into a report and posts the assessment to a Slack channel for team awareness and action.

Explore use case

Remote Device DNS Resolver Investigation

This automation investigates a remote user's current DNS resolver by retrieving the user's managed device inventory, extracting and parsing resolver data, and comparing it with the authorized resolver. If the resolver is unauthorized, it sends a notification to the initiating Slack channel.

Explore use case

Less busywork. More possibility.

Let your agents handle the routine. Make room for what comes next.

Let’s talk