A walkthrough
Everything FlowAdmin watches, screen by screen.
FlowAdmin is one console for Microsoft Dynamics 365 Finance & Operations: the business events arriving from the environment, the batch jobs and workflows they feed, the telemetry it publishes back on forms, data management, metrics and server requests, and the system users behind that access — read as they land and kept on record. This is the whole tour, screen by screen, in the order people actually use it.
01·/assistant
Insights
Live priorities ranked across every source, each one opening the screen where it is fixed. Inside the console, any priority can be handed to the assistant, which reaches Dynamics 365 Finance & Operations through the MCP server — ask what sits behind it, what to do first, or have the problem actioned there and then. The queue, the AI, and the access to act on it all sit on one screen.
02·/analysis/batch
Batch job analysis
Batch telemetry aggregated: finished runs, success rate, average run time and failed tasks, then runs per interval by outcome, the jobs failing most often and the slowest runs. Every figure opens the records behind it.
03·/jobs
Batch jobs
Every job the environment reports as a card: last outcome, owner, when it started, how long it took and the tasks it carried, with search, status tabs and a legal-entity filter over the whole estate.
04·/events
Business events
Notifications kept as they arrived: when, which event type, the source system, the severity and whether a run has handled it, filtered by severity with the payload one click away.
05·/telemetry/metrics
Custom metrics
The numeric metrics the environment publishes — counters and per-operation timings — with how many signals arrived, the distinct metrics behind them and the newest values.
06·/analysis/dmf
DMF analysis
Data management analysed: import and export executions, the time each stage took and the entities moved most often, with the failures grouped so a repeating problem stands out.
07·/analysis/dmf-errors
DMF errors analysis
The failures behind those runs, counted by error and by entity, so a staging or target problem that keeps returning is visible in one look rather than one log line at a time.
08·/telemetry/dmf
Data management
The data management events the environment publishes — import and export job and target starts — with the newest messages in a log underneath.
09·/analysis/forms
Form run analysis
Form opens analysed: how many, how many distinct forms, average and P90 load, the slow opens, then the busiest forms and the people behind them, every counter opening its records.
10·/telemetry/forms
Form runs
The forms people opened, how often and when last, then who is behind those opens once the page views are matched to Dynamics system users.
11·/telemetry/other
Other signals
Everything the environment publishes that belongs to no single family, listed with the table it arrived from, so nothing is quietly left unread.
12·/telemetry/performance
Requests and SQL
Server requests and the SQL calls behind them, read exactly as they arrive. When a signal has not landed, the page says so plainly rather than leaving a blank screen that could pass for everything being fine.
13·/telemetry/traces
Traces and warnings
Platform traces and warnings, with the same honesty: F&O raises warnings as exceptions or custom events, so the page says where that content actually lives.
14·/users
Users & security
Every Dynamics 365 system user with company, account state and the security roles behind their access — searchable, filterable by state and exportable to CSV.
15·/admin
Console settings
The palette every screen renders in, which screens appear in the navigation, and how long each log and telemetry class is kept.
Events in, triage across the estate, drill to the record, act on it, then govern who sees what and how long it is kept — all in one console.
Get in contact