Add new flows Only Admins
Create new flows to track your integrations. With the right mapping, you see each message as it passes through.
| Property | Description |
|---|---|
| Flow Name | A Flow Name for the integration. Example: invoice request, invoice approval. |
| Folder | The Folder where to save the flow. See folders structures. |
| Mapping | Identifies a message in the flow. The Domain, Service, Action, and Version fields match a message to a flow. Set a Workflow name if the message ran through an Azure Logic App. |
| Business Properties | Metadata for the flow. Each Business property name gets its value from the message. |
| Advanced Settings |
|
| Alerts | See alerting |
Allow access to flow
Microsoft Entra ID groups and local users can access flows in the folder. Users get their flow permissions based on their role.
Users with the System admin role can see all flows in every folder.
Add an alert for a flow
Create Azure Monitor alerts right from the flow. Alerts track the health of your flows. You get notified when something needs attention. For example, when a flow goes inactive or starts to fail.
The Dashboard requires role assignments to add alerts to flows.
| Property | Description |
|---|---|
| Alert name | The Alert name must be unique per flow. The flow name becomes a prefix. |
| Description | The Description adds context to the alert. |
| Severity | The Severity level or urgency of the alert. |
| Schedule |
|
| Trigger | The Threshold and Threshold Operator set when the alert fires. |
| Throttling | Use Suppress alerts and Suppress alerts (minutes) to mute alerts for x minutes. This helps avoid alert fatigue. |
| Query |
Monitors flow activity via Azure logs. (Custom events named: If an alert runs every 60 minutes and finds no logs (threshold < 0), the flow is inactive. It then fires an alert. logging frequency Logging happens per flow, not per message. It can exceed one entry per hour due to scaling.
Reduce Monitors flow errors via Azure logs. (Custom events named: If an alert runs every 10 minutes and finds logs (threshold > 0), the flow has failed. It then fires an alert. Uses custom Azure alert syntax. See the Microsoft docs for details. |
| Recipients | Add an email Recipient. They get a mail with a Subject each time an alert fires. |