Pages
Context from Fabric IQ, governed action from Exosphere Agentic
One agent reads context from your ontology and acts through a governed path
One agent, two MCP surfaces: Fabric IQ tells the agent what your business means, and Exosphere Agentic decides what it may do about it, carrying every action through TM Forum Open APIs. Exosphere Agentic runs on Azure and integrates with the Microsoft AI platform, deployed into the customer's own tenant — so context, data and governance stay where they belong.
Updated
One agent, two surfaces, a clean division of labour
Agents built in Microsoft Copilot Studio or Microsoft Foundry can register more than one MCP server as tools. Exosphere Agentic uses that to keep two jobs apart: context comes from your Fabric IQ ontology, and governed action comes from Exosphere, the judgment layer inside Exosphere Agentic.
| Aspect | Context surface | Governed action surface |
|---|---|---|
| Served by | The Fabric IQ ontology MCP endpoint | The Exosphere Agentic MCP and tool gateway |
| Answers | What does this enterprise mean by this term, and how do the records relate? | What may this loop do, under whose authority, and what actually happened? |
| Grounded in | Entity types, relationships and bindings over OneLake | The telecom ontology for BSS and OSS, operator policy and cited industry standards |
| Reaches | Business context, read only | Your systems of record, through TM Forum Open APIs |
The principle is simple: separate retrieval of context from authority to act. An agent can read widely. It can change only what its loop was granted, and only on a path that is authorised, recorded and confirmed.
Context from Fabric IQ: your business vocabulary, ready for agents
In Microsoft Fabric, the ontology item is the business vocabulary of Fabric IQ. It defines entity types, properties and typed, directional relationships with their constraints, then binds them to real data in OneLake: lakehouse tables, eventhouse streams and Power BI semantic models. People, tools and agents share one language.
- One endpoint per ontology. An ontology item can be exposed as an MCP endpoint. In Copilot Studio the ontology endpoint is added as an MCP tool, signs in with Microsoft Entra ID, and gives the agent tools to list entity types and search the ontology.
- Four ways to consume it. Foundry IQ for Microsoft Foundry agents, Copilot Studio for conversational agents, the Fabric data agent for questions inside Fabric, and the Fabric operations agent for continuous monitoring.
- What to have in place. A Fabric capacity with the ontology tenant setting enabled, an existing ontology item, and the same identity signed in to Copilot Studio and Fabric.
- Pick the right server. Microsoft also offers a Fabric IQ MCP server for Power BI reports and semantic models. Ontology context comes from the ontology endpoint described here.
Fabric carries context and measurement: it tells the agent what things mean and reports how an outcome moved. The governed write path runs through Exosphere.
Governed action from Exosphere: every write on a policy path
Exosphere decides what a loop may reach, and MCP is how that catalogue is offered to the agent. Four gateway properties hold whatever the transport:
- Capability is granted per loop, not per platform. A loop reaches only the tools it was given.
- Reads and writes are separate permissions. Retrieving a bill and issuing a credit are different grants.
- Systems of record stay authoritative. Exosphere proposes, governs and records; it does not take custody of data that belongs elsewhere.
- Every call is attributable: which loop, under which authority, on whose behalf, against which system.
Propose, approve, execute
- The agent proposes, with evidence. Proposing never changes data.
- Policy decides: execute, route to the role with authority, or block. Thresholds are set per loop and per commercial exposure, not per model.
- An approval is signed, single-use and expiring, bound to one exact action.
- At execution, Exosphere re-checks the facts. If anything changed, the approval lapses.
- The write lands once per proposal through TM Forum Open APIs, and the outcome is reported as applied, refused or unconfirmed.
- One audit record links intent, actor, authority, API operation and record.
The result: the blast radius of a new loop is knowable before it runs, and reviewable afterwards without reading the prompt. See Propose, approve, execute, and the audit record.
Two MCP surfaces, one agent
flowchart LR
U["Care rep or<br/>NOC engineer"]
subgraph MSFT["MICROSOFT AI PLATFORM"]
AGT["Copilot Studio or<br/>Microsoft Foundry agent"]
MMCP["Fabric IQ ontology<br/>MCP endpoint"]
ONT["Fabric IQ ontology<br/>bound to OneLake"]
end
subgraph EXOS["EXOSPHERE AGENTIC"]
EMCP["MCP and tool gateway<br/>grants per loop"]
GOV["Exosphere<br/>authorise · observe · audit"]
RAG["Telecom grounding<br/>cited standards"]
APIS["TM Forum Open APIs"]
end
HUM["Approver with authority<br/>Microsoft Teams · Sherpa Approvals"]
OPS["Systems of record<br/>unchanged"]
U --> AGT
AGT -->|"context · read"| MMCP
MMCP --> ONT
AGT -->|"action · scoped grant"| EMCP
EMCP --> GOV
GOV --> RAG
GOV -->|"route"| HUM
GOV --> APIS
APIS -->|"governed write"| OPS
classDef ms stroke:#4A5F7A,stroke-width:2px
classDef exos stroke:#0077B6,stroke-width:2px
classDef std stroke:#005F8A,stroke-width:1px
classDef sor stroke:#7A8DA5,stroke-width:1px
classDef human stroke:#009688,stroke-width:3px
class AGT,MMCP,ONT ms
class EMCP,GOV,RAG exos
class APIS std
class OPS sor
class HUM humanMicrosoft controls and Exosphere authority, stacked
Exosphere Agentic is built to sit inside the controls the Microsoft AI platform already provides, and to add business authority on top.
| Layer | What it governs |
|---|---|
| Foundry Agent Service | Which MCP tools an agent may call: an allowed-tools list, approval of tool calls by default, and identity through agent identity, managed identity or on-behalf-of pass-through |
| Azure API Center | A private catalogue of MCP servers, discoverable under Azure role-based access. Register the Exosphere Agentic surface there alongside your own. |
| Azure API Management | The access layer: MCP endpoint, Microsoft Entra ID authentication, quotas, tracing and versioning. Exosphere builds on it, not around it. |
| Foundry IQ | Permission-aware, cited retrieval of policies and documents |
| Exosphere | Business authority: value against limit, customer segment, cumulative exposure, the approver with authority, and the audit record |
The platform confirms that a tool may be called. Exosphere confirms that the business action is within the authority of the person and the loop. Identity is carried on behalf of the real person through Microsoft Entra ID, so an agent never acts with more authority than the person it serves. For new multi-agent work, Microsoft recommends Microsoft Agent Framework.
Context, then governed action: one order end to end
sequenceDiagram
autonumber
actor Rep as Care rep
participant AG as Agent on the Microsoft AI platform
participant ONT as Fabric IQ ontology endpoint
participant EXO as Exosphere
participant APR as Approver with authority
participant SOR as Order management via TMF622
Rep->>AG: Add the 5G add-on from the next bill cycle
AG->>ONT: Look up the offer, customer and product
ONT-->>AG: Offering, customer and product context
AG->>EXO: Propose the product order
EXO->>EXO: Check principal, scope, threshold, exposure
alt Above the loop threshold
EXO->>APR: Signed single-use approval request
APR-->>EXO: Approved
end
EXO->>EXO: Re-check the facts at the moment of action
EXO->>SOR: Create the product order, once
SOR-->>EXO: Order acknowledged
EXO->>EXO: Write the audit record, intent to record
EXO-->>AG: Order state and audit reference
AG-->>Rep: Order placed for the next cycleThe industry draws the same line
- TM Forum IG1445 positions MCP as complementary to the Open API programme: it adds value to existing APIs rather than replacing them.
- ODA Component Accelerator decision 0016 provides MCP servers for TM Forum Open APIs, treated as one more API type with versioning, governance and lifecycle management.
- Operator architects describe the same split, between services that can see and services that can change, with agents reading and acting through MCP wrappers over existing APIs.
- Microsoft publishes ODA Canvas operators for Azure API Management and Microsoft Entra ID.
Two surfaces is the pattern the industry is converging on. Exosphere Agentic delivers the governed half against each operator's own stack.
Microsoft product names are used descriptively.
Take the next step
Walk through both surfaces against your own tenant and systems of record.