Dataverse Table Row Count Growth Monitor

Overview

A daily scheduled flow that monitors row counts across key Dataverse tables and projects future storage capacity. When any table's growth rate indicates it will exceed a configurable threshold (default 80%) within a projection window (default 30 days), the flow posts a formatted capacity warning to a Teams admin channel with table name, current count, usage percentage, growth rate, and projected breach date.

Use Case

Proactive storage governance — catch runaway table growth before it impacts org capacity limits, giving admins time to archive, clean up, or request additional storage.

The flow is ideal for teams that:

• IT admins responsible for Dataverse capacity and storage governance
• Teams managing large Dataverse tables (cases, accounts, contacts) at risk of hitting capacity limits
• Organizations that need proactive alerts before storage breaches impact users
• Admins who want a daily snapshot history for audit and trend analysis

Flow Architecture

Environment Variables

Connectors & Connections

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Create the growth-tracking Dataverse table

Create flowlibs_dvrowcountsnapshot (or your preferred name) with columns flowlibs_tablename (Single Line of Text) for the monitored table's logical name, flowlibs_rowcount (Whole Number) for the daily count, flowlibs_snapshotdate (Date and Time) for the timestamp, and a primary name column flowlibs_name for a descriptive label like 'account - 2026-04-12'.

Update environment variable current values

Set flowlibs_DvMonitoredTables to your comma-separated list of tables, flowlibs_DvGrowthTrackingTable to your tracking table's logical name, and flowlibs_AdminTeamsGroupId / flowlibs_AdminTeamsChannelId to your admin channel. Adjust flowlibs_DvStorageThresholdPct and flowlibs_DvProjectionDays as needed.

Authorize connections

Open the flow in the designer and authorize the Dataverse and Teams connections so the daily run can read counts, write snapshots, and post to the admin channel.

Adjust varMaxRowEstimate

The default is 500,000 rows. Edit the Initialize Variable action to match your org's per-table storage allocation so the usage percentage and projection math reflect your real capacity.

Turn the flow on

After the tracking table, env vars, and connections are in place, turn the flow on so the daily 6 AM run begins capturing snapshots.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

concat('<fetch aggregate="true"><entity name="', tableName, '"><attribute name="createdon" alias="recordcount" aggregate="count"/></entity></fetch>')

(newest snapshot count − oldest snapshot count) / number of snapshots

(maxRows × thresholdPct / 100 − currentCount) / dailyGrowthRate

replace(replace(replace(string(body('Select')), '{"html":"', ''), '"},{"html":"', ''), '"}', '')