Azure reference architectureContent production and editorial calendar
A Azure reference architecture for content production and editorial calendar in Marketing. Triggered by new brief or scheduled editorial slot, Padiso orchestrates 3 specialist agents on Azure AI Foundry, reaching cms and your tools through the Model Context Protocol, with budgets, approvals and an audit trail throughout.
AzureRuntime: Azure AI FoundryTrigger
New brief or scheduled editorial slot
Marketing
Orchestration
Padiso Orchestrator
goals · tasks · heartbeat
Governance
budgets · approvals · audit
Runtime & agents
Agent runtime
Azure AI Foundry
Content agent
agent
SEO agent
agent
Campaign agent
agent
Integrations · MCP
MCP gateway
Your systems
CMS
Content calendar
Analytics
How the data flows
Trigger: New brief or scheduled editorial slot
- 1
Content agent drafts against the brief, brand voice and existing assets
- 2
SEO agent checks keywords, structure and internal links
- 3
Assembles the draft with metadata into the CMS as a draft
- 4
Editor approves before anything publishes
Agent team
- Content agent
- SEO agent
- Campaign agent
Integrations
Reached through the Model Context Protocol, scoped and governed.
Runtime & data
Azure AI Foundry
CMS
Content calendar
Analytics
Security & operational considerations
- Brand and claims guardrails on every draft
- Nothing publishes without human approval
- Source attribution on factual claims
Azure deployment
Deployed in your Azure tenant on AI Foundry, with Entra ID scoping, Private Endpoints into your VNet, and Azure Monitor for audit and observability.
Run this blueprint anywhere
More Marketing blueprints
Run your business on agents.
Start free, or talk to us about putting an agent workforce to work across your operations.