Integrate your agent with Microsoft 365 | AI-103 | Episode 11

Building an agent is only half the job. Publishing turns a tested Foundry agent into something users can access through Microsoft 365 Copilot and Teams.

The publish pipeline

Agent Version → Publish → Agent Endpoint → Azure Bot Service → M365 / Teams

When publishing to Microsoft 365/Teams, Foundry handles several integration steps:

• validates the selected agent version and metadata

• creates/configures an Azure Bot Service for channel routing

• generates and submits the Teams app manifest

• enables the Activity protocol for message exchange

• configures authorization based on the selected publishing scope

Azure Bot Service is the bridge between Microsoft 365/Teams and the Foundry agent.

Publishing scope = access model

With organization-wide publishing, the agent becomes discoverable to users in the tenant after approval in the Microsoft 365 admin center.

Identity & versions

A published agent has a dedicated Entra agent identity and a stable endpoint. Resources accessed using that identity need the appropriate RBAC permissions.

Also distinguish saving/versioning from publishing: agent versions can evolve independently from what users currently consume.

Remember the flow:
Version → Publish → Bot Service → Activity protocol → M365/Teams

And the key mapping: Shared → RBAC; Tenant → tenant access + admin approval.