Planning data - budgets, forecasts, headcount, demand, and capital plans has always been rich in business context but difficult to manage as structured enterprise data. As AI agents and Copilots move from reporting numbers to explaining variances, assumptions, and “why” questions, the challenge is no longer just accessing planning data, it is understanding the context behind the numbers.
Microsoft Fabric provides a foundation for connecting enterprise data, business meaning, governance, and AI experiences. Capabilities such as OneLake, semantic models, Copilot, Fabric data agents, and Microsoft Foundry bring planning information together with the context needed for AI-driven analysis and decision support. Recent Fabric announcements, including those at FabCon Atlanta in March 2026, further reinforce this direction, with capabilities such as OneLake security, Copilot-generated semantic model descriptions, and OneLake catalog APIs supporting governed, AI-driven discovery and access.
Planning data carries scenarios, assumptions, manual adjustments, approvals, and business rules many of which traditionally exist outside the data itself. For an AI agent to move beyond simply retrieving numbers and reason about a planning decision, that context needs to be explicitly captured and connected to the data.
This article explores a practical framework for making planning data agent-ready in Microsoft Fabric so AI can understand not just what the number is, but why it changed, what it represents, and how it should influence a planning decision without losing business context.
AI doesn't become trustworthy because data is centralized. It becomes trustworthy when the decision context surrounding that data is explicitly modeled.
Before the framework, it's worth naming what makes planning data uniquely difficult:
- It's inherently versioned. A plan isn't one truth: it's Budget v1, Reforecast Q2, Scenario A, Scenario B, Actuals-to-date. An agent that doesn't know which version it's looking at will confidently answer the wrong question.
- It mixes hard numbers with soft judgment. A demand plan is part historical data, part human adjustment ("sales says add 8% for the new contract"). That adjustment logic is rarely captured as structured data.
- It's assembled late and by hand. Planning cycles often end in Excel, where formulas, hidden rows, and tribal knowledge live outside any governed system.
- Its grain shifts. Finance plans by cost center and month; supply chain plans by SKU and week. Reconciling grain is a prerequisite for any cross-domain AI reasoning.
These challenges are not unique to Fabric, they are inherent to how planning data is created and managed. The framework below focuses on how to use that foundation to make planning data understandable and actionable for AI agents.
Decision Context framework
Think of agent readiness as a progression, where each layer adds the context an AI agent needs to reason reliably. Skipping a layer can lead to outputs that are technically accurate but lack the business context needed for trustworthy decisions.
Layer 1: Unified Ingestion and Landing (the prerequisite for trustworthy planning agents)
Goal: Every planning source (ERP, EPM/FP&A tools, Excel plans, CRM forecasts, external market data) lands in OneLake once, in open Delta format, without silent duplication.
Use Fabric Data Factory pipelines to land source data once, or OneLake shortcuts (including multi-cloud shortcuts to S3/GCS where planning inputs live outside Azure) to reference it in place without copying it at all.

Layer 1 in practice: the LH_Meridian_Analytics lakehouse of Meridian Consumer Brands, a fictional household and personal care maker. Dimension and fact tables land once as Delta tables in OneLake; the tables with the shortcut glyph read the Fabric SQL writeback database in place instead of copying it.
- Preserve source lineage and timestamps at ingestion: planning data is meaningless to an agent without knowing when a number was captured relative to the plan cycle.
- Apply sensitivity labeling and classification at ingestion (Purview integration), not after the fact: planning data is often the most sensitive data in the company (comp, M&A, capital plans).
Layer 2: Structural Normalization (one grain, one calendar, one hierarchy)
Goal: Resolve the grain and hierarchy conflicts before any modeling happens.
- Standardize fiscal calendars, cost center/org hierarchies, and product/SKU hierarchies into shared dimension tables. This is the single highest-leverage step for cross-domain AI reasoning later.
- Explicitly model plan versions as a first-class dimension (scenario, version, cycle, status: draft/submitted/approved), not as separate tables or file names.

Plan versions as first-class scenarios: the Q4 reforecast planning sheet of Meridian Consumer Brands in Fabric Plan carries Base, Q4 Working Reforecast and Q4 Stretch as scenario tabs beside actuals and budget, rather than as separate files. Fictional data.
- Separate "actuals," "plan," and "forecast" into clearly typed records rather than blended columns: an agent should never have to infer which number is which.

Layer 2 in practice: every row of fact_budget_vs_actuals carries the fiscal calendar labels (period, quarter, year) beside the computed variance amount, variance percent and an explicit Over Budget or Under Budget flag, at one grain (month, customer, category). The actual and budget amounts the variance is computed from sit in separately typed columns of the same table, to the left of this frame. Fictional data.
Layer 3: Semantic Modeling (definitions an agent can trust)
Goal: Encode business meaning so AI doesn't have to guess it.
- Build governed semantic models (Power BI semantic models, which Fabric IQ can extend into a cross-domain ontology, in preview) that define metrics like "variance," "run-rate," or "committed pipeline" once, centrally, so every agent and Copilot instance uses the same definition instead of reinventing it per report.

Layer 3 in practice: Meridian_Revenue_Ontology, a Fabric IQ ontology (preview), defines the estate's entity types and their relationships once over the same lakehouse tables, here fact_budget_vs_actuals linked to date, category and customer, so an agent reasons in business terms rather than table names. Fictional data.
- Document business logic for manual adjustments as structured metadata (who adjusted, why, what assumption) rather than leaving it as an unexplained delta between two numbers.
- Tag key planning metrics with descriptions and synonyms on the semantic model itself, and finish the job with Power BI's Prep data for AI (preview), so natural-language queries ("what's driving the Q3 miss in EMEA?") resolve to the right fields. Copilot and the Fabric data agent both read that metadata.
Layer 4: Governance and Trust Controls
Goal: Make sure an agent's access mirrors the access a human would legitimately have.
- Enforce row- and object-level security so an agent answering a regional manager's question can't surface global comp or M&A data.
- Apply sensitivity labels and Microsoft Purview protection policies so an agent cannot reach data above the asking user's clearance: the Fabric data agent queries with the user's own permissions, and Purview DLP and access-restriction policies can block or trim what it returns (access restriction policies are in preview).
- Maintain an audit trail of what data an agent read and what it produced from it. This is critical for planning data, where a wrong AI-generated forecast narrative carries real business consequences.

Layer 4 in practice: the audit log of the governed forecast sheet in Fabric Plan records each change with the old value, the new value, who updated it and who approved it (the two name columns are blurred here). Fictional data from the Meridian estate.
Layer 5: Agent reasoning layer (where Copilot/agents actually operate)
Goal: Expose the now-clean, modeled, governed data to AI surfaces without giving them a shortcut back to the messy source.
- Connect governed semantic models to Copilot in Fabric, Fabric data agents, or Microsoft Foundry agents: agents should query the semantic layer (a semantic model or, in preview, a Fabric IQ ontology), not raw landed tables.

Layer 5 in practice: Meridian_Revenue_Agent, a Fabric data agent, answers a planning question (which Q4 2026 forecast cells are approved) by reading the governed forecast table through the ontology rather than raw landed data: one approved cell, its month, its budget and the approved value. Fictional data.
- Use retrieval scoped to the catalog metadata (the OneLake catalog search API, also exposed as a tool on the Fabric Core MCP server, both in preview) so agents discover the right dataset rather than being manually pointed at it every time. Catalog search returns metadata only; it grants no access to the data itself.
- Build feedback loops: capture when an agent's variance explanation or forecast draft was corrected by a human, and route that correction back into the semantic layer's documentation. Without this feedback loop, even well-modeled planning data can quickly become disconnected from business reality.
Decision-Ready Planning Framework
Before exposing planning data to AI agents in Fabric, validate each of the following readiness criteria:

A “no” at any layer is a signal to pause and address the underlying gap. AI can amplify the quality of your planning data, but it can amplify poor context just as confidently.
Closing Thought
Microsoft Fabric can unify planning data, business context, governance and AI, but technology is only the foundation. The real advantage comes from making planning context structured, trusted, and actionable for AI-driven decisions.
Ready to assess Fabric Plan for your organization?
Our Data & AI team can map your current planning environment to Fabric Plan’s capabilities and outline a practical implementation path. No commitment required
Author

Sowjanya BNK, Director, Business Analytics & Client Solutions Partner at iLink Digital, blends business strategy, data, analytics, and AI. She partners with global leaders to drive data/AI transformation, GTM, and modern BI—turning complex challenges into measurable, outcome-driven business value.




