Page Templates & Live Pages
Ready-made live dashboards for Databricks, Jira, Azure DevOps and GitHub that refresh on their own, and that you can make your own.
Pages are small apps the agent builds for you. Page templates give you ready-made ones that read your real data live — Databricks spend and job health, a SQL studio, Jira, Azure DevOps and GitHub radars — and that you can change any way you like, by hand or by asking the agent.
New in 0.14.4
Page templates, live (auto-refresh) pages and the page kit arrive in Fabric Agents 0.14.4.
Start from a template
- Open Pages in the sidebar and click Templates.
- Pick a template. Templates are grouped as Data, Engineering, Cloud and Yours (templates your workspace saved).
- Point each connection at one of your sources and fill in the settings (for Databricks, pick a SQL warehouse — Fabric lists them for you).
- Click Create page, then Connect live data on the page and approve access once.
The page then refreshes on its own while it is open. The chip in its header shows when it last updated; Refresh updates it now.
| Template | What it shows | Needs |
|---|---|---|
| Databricks Cost Radar | Spend at list price from system.billing: daily trend, products, SKUs, jobs, SQL warehouses, model serving, people, your cost tag, workspaces | A Databricks SQL source + warehouse |
| Databricks Jobs Health | Lakeflow runs from system.lakeflow: success rate, jobs failing now, flaky and slow jobs, failed runs, pipeline updates | A Databricks SQL source + warehouse |
| Databricks SQL Studio | Unity Catalog browser, read-only SQL editor with results, column details, your query history | A Databricks SQL source + warehouse |
| Jira Issues Radar | Any JQL: status, owners, overdue, stale and blocked issues | A Jira API source |
| Azure DevOps Radar | Active pull requests with reviewer votes, what waits on review, merge conflicts, pipeline runs | An Azure DevOps API source (PAT) |
| GitHub PR Radar | Open PRs for an org or repos, what needs your review, stale PRs, what merged this week | A GitHub API source |
The Databricks templates read system tables. Your user needs SELECT on system.billing, system.lakeflow, system.query and system.information_schema (an admin can grant this).
Live data, safely
When a page asks to refresh automatically, the approval dialog says so. Approving it lets the page read without a click — and only read. Fabric checks every call it makes:
- web requests that read (
GET) are allowed; - query requests are allowed only when they read: Databricks SQL (
SELECT,WITH … SELECT,SHOW,DESCRIBE,EXPLAIN— one statement), Azure DevOps WIQL, GitHub GraphQL queries and Jira search; - MCP tools are allowed only when their server marks them read-only;
- anything that could change data —
DELETE,UPDATE,DROP, scripts, writes — is refused, even from a button on that page.
Pages built on the page kit (all templates) also have no network access of their own: they can't send what they read anywhere else or load code from the internet. Approvals belong to this version of the page and expire after 30 days. Remove them any time from the page menu → Approved actions.
Warehouse cost
A page that runs Databricks SQL keeps the warehouse busy while it refreshes. The dialog warns you, the same query can't re-run more than every 15 seconds, and pages stop refreshing when they aren't visible. Use a serverless warehouse and keep the refresh interval sensible (the templates default to 10–30 minutes).
Make it yours
A page made from a template is your page:
- Ask the agent — "add a column for the reporter", "only show Prod EU", "make a version of this for our Jira project ABC". The agent knows the page kit and keeps live data working.
- Page settings (page menu) — point the page at other sources or change its settings without touching code. Changing a source asks you to approve access again.
- Save as template (page menu) — turn a page into a template for your workspace. Sources, approvals and data are not included; whoever installs it connects their own.
- Export / Import (Templates gallery) — share a template as a
.fabric-template.jsonfile with your team.
Template updates
When a newer version of a template ships, its pages show Update available:
- If you never changed the page, it's updated in place.
- If you did, Fabric merges the update with your changes.
- If your changes touch the same parts as the update, Fabric asks the agent to merge them — click Merge with the agent, then Mark merge done once you're happy.
Build your own live pages
Any page can use the same building blocks the templates use: the page kit (header, number tiles, tables, filters, detail panel, charts, live refresh) that follows your theme and company branding. Ask the agent for "a live page that shows …" and name the source — Databricks, Jira, Azure DevOps, ServiceNow, an MCP server — and it will build it with the kit.