Continuous Copilot Readiness monitoring
A Copilot Readiness assessment is a snapshot. Continuous Monitoring re-runs it every 30 days while your purchase is active, plots the score over time, lets you compare any two runs, and emails you when new must-do findings appear or the score drops. Use it to keep a tenant on track through a Copilot rollout, or to catch drift between engagements.
Example only. Numbers are illustrative.
WHAT YOU'LL SEE
The Continuous Monitoring page has three parts: Monthly auto-monitoring (one row per active purchase, where you turn scheduled runs on or off), Score trend (every completed assessment in your account), and Compare two runs (new, resolved and persistent findings plus per-module score changes).
Before you start
- An active governance purchase. Monitoring runs on a purchase: a single report pack (90 days of access) or Tenant Suite (1 year). The free snapshot can't be monitored. See pricing.
- One completed assessment for that report pack. Scheduled runs re-use the tenant from your last completed run of the same pack. Until you've run it once yourself, nothing is scheduled.
- A working scan connection. Scheduled runs use the connection you pick, the same read-only MigrationFox Assessment connection you use for assessments. If consent is removed or the connection stops working, the scheduled run fails.
- An alert email address (one address per purchase).
Turning on monitoring
- Open Governance and click the Continuous Monitoring tile (
/governance/monitoring). - Under Monthly auto-monitoring, find the row for your purchase. It shows the product, "Purchase valid until" and, once runs have happened, the date of the last auto-run.
- Enter the Alert email and pick the Scan connection.
Alert email:alerts@contoso.comScan connection:Contoso assessment
- Switch the toggle from Off to Enabled. You'll see "Monthly monitoring enabled". To change the email or connection later, edit them and click Save changes.
Status✓ Enabled
When runs happen
MigrationFox checks every hour for purchases that are due. A run is due when monitoring is enabled, the purchase hasn't expired, and the last scheduled run was more than 30 days ago (or there hasn't been one yet). So the first scheduled run starts within about an hour of turning monitoring on, then every 30 days after that. The cadence is fixed at 30 days. Scheduled runs stop when the purchase expires.
Scheduled runs appear in your assessment list labeled Auto monitoring re-run, with a full report like any other run.
The score trend
The Score trend chart plots the overall score (0 to 4) of every completed assessment in your account, oldest to newest, whether you started it or it was a scheduled run. Hover a point to see its date, score and number of findings. With only one completed run, the page shows that single point and a reminder to run again after you've worked through some findings.
Comparing two runs
Under Compare two runs, pick a Prior run and a Current run. The comparison shows:
| Section | What it contains |
|---|---|
| Overall score change | The current score minus the prior score. |
| New | Findings in the current run that weren't in the prior run. Often caused by a configuration change, a new site, or a policy that drifted. |
| Resolved | Findings in the prior run that are gone from the current run. Evidence that remediation is working. |
| Persistent | Findings present in both runs: the backlog still to clear. |
| Module score changes | Prior and current score per module, with a direction: improved, regressed, unchanged, or new (module only in one of the runs). |
Findings are matched between runs by their finding ID. Compare runs of the same report pack for a meaningful result: comparing, say, a Teams run with a Copilot Readiness run lists most findings as new or resolved.
Email alerts
After each scheduled run, MigrationFox compares it with the previous completed run of the same pack. An email goes to the alert address only when at least one of these is true:
- A finding with priority Must Do Before Copilot appears that wasn't in the previous run.
- The overall score dropped by more than 0.3.
Otherwise no email is sent. The first scheduled run with no earlier run to compare against is recorded as the baseline, without an email. Subject lines:
[MigrationFox Monitoring] <N> new must-do Copilot finding(s) [MigrationFox Monitoring] Copilot readiness score dropped
The email shows the score change, the number of new must-do findings with up to five examples, and links to the full report and to the trend view. Each run's alert decision (sent or not needed) is recorded in the Activity log.
To stop monitoring, switch the toggle back to Off. Past runs stay in the trend chart.
Troubleshooting
Monitoring is on but no run appeared
Check that you have completed at least one assessment of that pack yourself, that the purchase hasn't expired ("Purchase valid until"), and that the scan connection still works. Runs start within about an hour of being due.
A run completed but no email arrived
That usually means nothing qualified: no new must-do findings and no score drop larger than 0.3. Improvements don't trigger an email. Check the Activity log for "Monitoring run reviewed, no alert needed", and check your spam folder.
Many "new" findings at once
Either a real tenant change, or the two runs you're comparing are different report packs. Compare runs of the same pack. MigrationFox also adds and refines checks over time (the suite has 100+ checks), which can show up as new findings.
What's next
- M365 Assessment Suite overview: the report packs and what each covers.
- Running an assessment: first-time setup.
- Exports: PDF, CSV and JSON formats.
- Dependency Graph scan: find flows, apps and Teams tabs that reference a site before you restructure it.