Alerts and notifications in Dynamics 365 Finance

For users working in Dynamics 365 Finance and Supply Chain, much of the day-to-day intelligence comes from being told when something happened — a sales order shipped, a credit limit exceeded, a customer overdue, a production order completed, a workflow approval needed. The alert framework is the platform's built-in subscription mechanism that delivers these notifications without requiring custom integration.

The model. A rule specifies what to watch for. Each user can create rules against:

• Field changes — when a specific field on a record changes (e.g. "alert me when this customer's credit limit is reduced").
• Due dates — when a record's due date approaches (e.g. "alert me 7 days before the sales order delivery date").
• Creation / deletion — when records of a type are created or deleted.
• Workflow events — when a workflow stage transitions.

Users create rules through the Manage Alert Rules action; admins can create system-wide rules that apply to all users matching criteria.

Delivery. Alerts deliver to:

• Action centre — the bell icon in the F&O UI shows pending alerts.
• Email — configurable per rule.
• Mobile push — through the F&O mobile companion.
• Application Insights telemetry — for system-level monitoring.

A single rule can fire to multiple channels.

Common alert scenarios.

• Credit risk — alert credit manager when a customer's overdue balance exceeds a threshold.
• Delivery promises at risk — alert customer service when a sales order's expected ship date is in the past with the order still unshipped.
• Inventory shortages — alert procurement when stock falls below safety stock.
• Workflow timeouts — alert manager when an approval hasn't been acted on within N days.
• Posting failures — alert operations when batch job errors.
• High-value events — alert leadership when a sales order over a threshold posts.

Rules at scale. F&O's alert framework is fine for individual user rules and a moderate number of system rules. For larger volumes — many users with many rules — performance can degrade because the framework checks every applicable rule on every change.

For high-volume scenarios, alternative patterns:

• Power Automate flows triggered by F&O events via virtual entities or Dual-write — more flexible, scales better.
• Application Insights alerts — for system-level health rather than business events.
• Service Bus integration — for downstream systems consuming events.

Alert delivery preferences. Users can configure per-rule:

• Active hours (don't notify outside working hours).
• Channels (Action Centre only, or also email).
• Aggregation (one alert per event, or batched daily summary).

Avoid alert fatigue — users overwhelmed with notifications start ignoring them, including the important ones.

System-wide alerts. Beyond per-user rules, system-wide alerts cover:

• Service health — Microsoft-driven notifications for service issues.
• Critical batch failures — operational-impact failures.
• Security events — unusual access patterns, failed login attempts at scale.
• Capacity thresholds — Dataverse storage approaching cap, API call usage approaching limit.

These typically route to administrators or operations teams via configured action groups.

Mobile and Teams. Modern F&O integrates with Microsoft Teams for alert delivery:

• An adaptive card in a Teams channel.
• Interactive — user can act on the alert directly from Teams.
• Coordinates with the broader Microsoft 365 notification surface.

Mobile push notifications surface alerts on the user's phone, with one-tap navigation to the relevant record in the F&O mobile experience.

Limits.

• Rule complexity is bounded — sophisticated conditional logic across multiple records typically needs Power Automate.
• Visibility into rule firing is limited — debugging "why didn't I get this alert" is harder than equivalent Power Automate flow run history.
• Performance at scale — every change touches every applicable rule.

Common pitfalls.

• Alert overload — users create dozens of rules, get hundreds of alerts daily, ignore them all.
• Stale rules — rules created for a long-gone process still fire and confuse users.
• No system-wide health alerts — operations team finds out about problems from user reports rather than alerts.

Operational discipline. Curate alert rules deliberately. Audit periodically — retire what's not useful. Combine with Power Automate flows for complex cross-system orchestration. The framework is the daily-pulse mechanism for the operational team.