No middleman
Messages go from the user's browser to your Azure AI Foundry project, within your Microsoft environment.
Open source · MIT licence
Foundry Agents: your Azure AI Foundry agents in SharePoint and Teams
Foundry Agents is an open source SharePoint Framework solution (MIT licence) that puts agents built in Azure AI Foundry on a SharePoint page, in a Teams tab or in the Teams personal app. Each user chats with their own Microsoft 365 identity: no server to host, no API key to store.
HR Assistant · SharePoint pageSample data
How many remote working days can I take per week?
Principles
Your agents, where your teams already work
Each user's permissions
The agent acts with the signed-in user's permissions: it only sees what that person can see.
Nothing to run
No server, no database, no keys to rotate: just a client-side web part.
Comparison
Foundry Agents vs a separate chat portal
| Criterion | Foundry Agents | Separate chat portal |
|---|---|---|
| Where users chat | In SharePoint and Teams | Yet another site or app |
| Identity | The user's Microsoft 365 account | Shared accounts or keys |
| API keys | None | To store and renew |
| Infrastructure | None | Server, database, updates |
| Code | Open source, auditable | Often closed |
Chat
- Streamed answers with citations
- Conversation history per agent
- Attachments and document preview
- Configurable voice dictation
Configure
- Several agents in one web part
- Audience per agent: users or groups
- User context sent to the agent
- Configuration export and import
Act
- Microsoft Graph and SharePoint calls with the user's permissions
- HTTP methods blocked by default
- OAuth sign-in to MCP servers
- Follows the SharePoint and Teams theme
Questions
Frequently asked questions
Is Foundry Agents free?
Yes. The code is published under the MIT licence. The models used by your agents are billed to your Azure subscription, as with any Azure AI Foundry agent.
Do I need a server to use it?
No. It is an SPFx web part running in the browser; it calls your Azure AI Foundry project directly with the user's identity.
Which permissions are required?
An administrator approves the API permissions requested by the solution, and users are given an Azure role on the Foundry resource. The installation guide covers each step.
Can you help us deploy it?
Yes: installation, building the agents, connecting them to your business tools and training the IT team.
Support
Get help with the rollout
Installation in your tenant, building your first agents, connecting them to your business tools via MCP and training the team that will evolve them.