AI Agent Orchestration Platform  ·  View 01 of 32  ·  1 · Context and scope

System Context

Who uses the platform, what it depends on, and where the boundary is drawn.

Editable source SVG draw.io All views
Identity and governance Microsoft Entra ID SSO · OIDC · agent ID Microsoft Purview classification Microsoft Sentinel SIEM People Agent Developer SDK · CLI · builder Business User chat · app · API Approver Teams card Platform Admin console SRE on call Model providers Azure AI Foundry GPT · embeddings Foundry Models partner catalogue Open-Weight Models AKS · KAITO External LLM APIs egress controlled AI Agent Orchestration Platform Azure · control + execution Tools and systems of record MCP Tool Servers internal + partner SaaS Applications SAP · SFDC · SNOW Enterprise APIs via APIM Content Estate SharePoint · ADLS Microsoft Teams Graph tokens labels security events defines agents runs agents approves actions sets policy operates inference specialist routes sovereign routes fallback only tool calls actions read and write grounding notifications AI Agent Orchestration Platform — System Context External / third party Person or role synchronous event / async Model and tool endpoints are reached only through the platform gateway. No agent holds a provider key. v 1.0 · owner Data & AI Global Practice · date 2026-08

In scope

  • Defining, versioning and publishing agents, workflows, tools, models and policies
  • Executing single-agent and multi-agent workloads, synchronous and asynchronous
  • Governing what an agent may use, spend and do, and proving it afterwards

Out of scope

  • Model training and fine-tuning — Azure Machine Learning remains the home for that
  • Systems of record — the platform acts on SAP, Salesforce and ServiceNow, it does not replace them
  • Content authoring and knowledge curation — the platform indexes the existing estate

Assumptions

  • Microsoft Entra ID is the single identity provider for people, services and agent identities
  • Azure AI Foundry is the default inference surface; other providers are reachable but exceptional
  • Purview sensitivity labels already exist on the content estate and can drive routing policy
All views High-Level Architecture  ▶
Solution Architecture v1.0 · Data & AI Global Practice · 2026-08 · 32 views · Microsoft Azure01-system-context