AIS Monitor
Azure Logic Apps workflow chain explorer
Visualise how your Logic Apps connect to each other via Service Bus queues and Event Grid, inspect live run history per chain, trigger HTTP workflows with saved payloads, and monitor deployed workflow states — all from a single desktop view.
Free for personal, educational and non-profit use. Commercial use — including a solo consultant on client work — requires a licence. Every build is produced by release CI and served from mayorana.ch.
The macOS build is signed with an Apple Developer ID and notarized, so it opens with a normal double-click.
Read the release notesHow AIS Monitor compares
Only the things AIS Monitor is strong at are listed. The others do plenty it doesn't — this table is about why you would pick it.
| Feature | AIS Monitor | Azure portal | Turbo360 | Azure Monitor workbooks |
|---|---|---|---|---|
| Workflow chain graph derived from the deployed definitions (Service Bus, Event Grid) | Grouping you assemble by hand | |||
| Run history of a whole chain, in order | One workflow at a time | Needs BAM instrumentation | With your own KQL | |
| App settings compared against App Configuration (config drift) | ||||
| Failing runs, dead letters, drift, RBAC gaps and cost on one screen | Separate blades | Dashboards you configure | With your own queries | |
| Trigger HTTP workflows with saved, named payloads and watch the run | Run with payload, nothing saved | |||
| Terminal edition: one static binary for SSH and jumpboxes | ||||
| Runs on your az login, no third-party access to your subscription |
Compared in October 2026 from each product's public documentation. Something out of date? Tell us
Claude skill
Lets Claude help you with AIS Monitor: how it works, the known errors and their fixes, and a bug report you review before sending it yourself.
How to install it
- claude.ai or the Claude app: Customize → Skills → + → Create skill → Upload a skill, then choose the .zip. “Code execution and file creation” must be on in Settings → Capabilities.
- Claude Code: unzip it into ~/.claude/skills/, so that the skill ends up in ~/.claude/skills/ais-monitor/.
Overview
A Logic Apps estate of any size stops being a list of workflows and becomes a graph: this workflow drops a message on a queue, that one picks it up, a third reacts to an Event Grid topic. The Azure portal shows you the workflows. It does not show you the graph.
AIS Monitor builds that graph from your deployed workflows and lets you walk it — pick a chain, see every run that flowed through it, drill into a run's action timeline, and trigger the entry point yourself with a payload you saved earlier.
It ships in two editions sharing one Azure backend and one on-disk cache: a desktop console with twelve tabs, and ais-monitor-tui, a single static binary for SSH sessions, jumpboxes and Windows Server where there is no desktop to run.
What it does
Workflow chain graph
Renders how deployed Logic Apps connect via Service Bus queues and Event Grid subscriptions, derived from the definitions by ais-chain rather than hand-drawn. Workflows linked by something undetectable, like a dynamic queue name, can be joined with a .ais-chain hint file.
Run history per chain
Follow one chain and see the runs of every workflow in it, in order, with per-run action timelines and KPIs — success rate, average and p95 duration, failure streak.
A terminal edition
ais-monitor-tui is a single static binary for machines with no desktop: chain browsing, run history and triggering over SSH, with a watch mode that auto-refreshes the focused step. Device-code sign-in covers hosts with no browser.
Config drift and health
Live app-settings values compared against App Configuration, managed-identity and app-setting health checks, and resource health across the whole group.
RBAC and cost
Managed identity role assignments in one view, plus a live log tail and month-to-date cost.
A dashboard that stays current
The home tab — failing workflows, live runs, dead letters, drift, RBAC gaps and cost together — polls in the background with adaptive backoff when Azure throttles, so it works unattended as a wall display.
Trigger panel
Fetch the callback URL for any HTTP-triggered workflow, edit the JSON payload in place, save named payloads per workflow, and watch the resulting run status appear live.
Requirements
- macOS on Apple Silicon, Windows, or Linux x86_64 for the desktop console; the terminal edition runs anywhere its static binary does
- Azure CLI signed in (az login) — both editions use your existing session
- Reader on the resource group for read-only use: chains, KPIs, run and action detail, resources, observability, diagnostics
- Contributor for the actions that change Azure state, plus User Access Administrator for the RBAC tab
- A deployed Logic Apps Standard environment
Built with
Rust · Dioxus · Azure CLI · ais-chain · D3.js
What's new
Version 0.3.44, released 7 October 2026. AIS Monitor ships often; every version and what it changed is listed on the release notes page.
Read the release notesLicence
Source-available under the PolyForm Noncommercial License 1.0.0: free for personal use, learning, research and hobby projects, and for charities, schools, universities and government institutions. Companies using it for work buy a licence.
Source
The source is public and readable. Fork it and rebrand it — the name and logo are trademarks and are not covered by the licence.
View on GitHubQuestions
Can it change things in my Azure environment?
Yes — this is not a read-only tool. The desktop console can trigger workflows, reset app settings, purge and requeue Service Bus messages, and assign RBAC roles. Each of those is gated behind a confirm dialog that shows the exact az command it is about to run, and read-only use needs only Reader.
What is the difference between the desktop and terminal editions?
The desktop console is the full twelve-tab tool. The terminal edition is deliberately smaller — chain browsing, run history and triggering for when there is no GUI available — not a shrunken copy of every tab. They share one Azure backend and one on-disk cache.
Does it work against local workflows too?
The desktop edition can scan a local logic_apps/ folder as well as a subscription, but it is aimed at deployed environments. For the local development loop, AIS Runner is the tool that covers that.
How does it work out the chains?
ais-chain reads the workflow definitions and matches the queues and topics one workflow writes to against the ones another triggers on. Nothing is configured by hand, though you can add a .ais-chain hint for links it cannot see.
Why is run history slower than the rest?
It goes through the Logic App's hostruntime API, which needs more than Reader and is throttled per subscription. The dashboard's background poll backs off automatically when it gets rate-limited.
Questions about this tool?
Ask about a commercial licence for your team, report an issue, or tell us what is missing. We read every message.
Get in touch