Monitor a DfE web page for changes automatically
A scheduled Power Automate flow checks a specified DfE page, compares the current content with the previously stored version, alerts the policy team when something changes and optionally uses AI to explain the difference.
Where the action happens
Power Automate
Product or feature needed
Scheduled flow, HTTP/API or suitable external connector, comparison logic, optional AI prompt
AI required
Optional - AI can explain a detected change but is not required to fetch or compare the page
Extra credits
No for simple fetch/compare; Copilot Credits or AI capacity may apply if an AI prompt is added
Technical skill
Medium to high
Risk level
Low to medium - public source, but missed/false changes and website structure changes need monitoring
Licence dependency
Build business tools / premium integration stage — a generic HTTP/API route may require Power Automate Premium depending on the specific action or connector. Check the connector classification before deployment.
Credit dependency
No AI credits are needed for a simple scheduled fetch/compare/notify design. AI consumption applies only if an AI step is added.
UK availability
available
What it can do
- Runs on a schedule without a person remembering to check.
- Retrieves a public source using an approved HTTP/API or connector route.
- Compares the current version with a stored previous version or relevant extracted content.
- Can notify staff with the source URL and detected difference.
- Can optionally pass changed content to AI for a human-readable explanation.
Limitations
- AI Builder or a prompt action does not itself fetch the DfE page; the flow needs a separate integration/fetch step.
- Website HTML and page structure can change, which may break extraction or cause false alerts.
- A public web page is not always a stable API and may have rate, access or terms-of-use considerations.
- An AI-generated explanation of the change must not replace checking the original DfE source.
Prerequisites
- Identify the exact DfE page or API endpoint to monitor.
- Confirm the organisation permits automated access to the source.
- Choose an approved HTTP/API action or connector and confirm its licensing classification.
- Store the previous version/hash/content somewhere controlled for comparison.
- Assign an owner and review the flow when the source page or project changes.
Workarounds
If Power Automate Premium or HTTP access is not available, use a web-grounded Copilot Agent for a manual periodic check and record the result.
No premium licensing needed. External dependency: Copilot web search/Agent knowledge policy.
Notes
Key teaching point: AI interpretation and external connectivity are separate. Fetch first; use AI only if interpretation is useful.
Watch-outs for Build business tools
- Production Power Apps often create a user-licensing commitment that should be understood before rollout.
- Dataverse and premium connectors change the cost and governance profile.
- Apps handling regulated decisions need audit trail, retention, access design and clear human accountability.
- Treat business-system integrations as lifecycle-managed services with named owners and review dates.
Sources
- https://learn.microsoft.com/en-us/training/modules/http-connectors/
- Overview of HTTP connectors in Power Automate checked 2026-09-05
- AI Builder in Power Automate overview checked 2026-09-05
- Add knowledge sources to your declarative agent in Microsoft 365 Copilot checked 2026-09-05
Last checked: 2026-09-05
Community feedback
Has your organisation tried this? Confirm whether it's possible, whether it's useful, and share any tips.
0
Confirmed possible
0
Reported not possible
0
Found it useful
0
Not useful
Loading feedback…