Three places you can work
You can work in Foundry without code, or with code, or from your editor. Pick one to start.
| Where | Use it when | Start with |
|---|---|---|
| Foundry portal (ai.azure.com) | You want to set things up and test without writing code. | Create an agent in the Agents playground. |
| SDK or REST API | Your application needs to call an agent, or you want to automate setup. The SDK supports Python, C#, JavaScript, and Java. | The SDK quickstart. |
| Azure Developer CLI (azd) | You want to scaffold, run, test, and deploy hosted agent projects from a terminal. | Develop agents with azd. |
| VS Code with the Foundry Toolkit | You want to build, test, and debug agents in your editor. | Install the toolkit. |
Coding agents such as GitHub Copilot and Claude Code can use the Foundry Skill to help with Foundry work, such as deployment and evaluation. You can add these later.
- SDKs for Python, C#, JavaScript, and Java. SDK overview
- Azure Developer CLI: scaffold, run, test, and deploy hosted agent projects from the command line. Develop agents with azd
- VS Code extension: build and debug agents in your editor with the Microsoft Foundry Toolkit for VS Code. Install the toolkit
- Coding agents such as GitHub Copilot and Claude Code can use the Foundry Skill to help with Foundry workflows, such as deployment and evaluation: Use the Foundry Skill
- To give coding agents Foundry tools, set up the Foundry MCP Server: Get started with the Foundry MCP Server
Your first hour: from project to agent
Follow these steps in order. Each one depends on the one before it.
- Step 1, create a project. In the portal, create a project. If you don't have a Foundry resource, the portal creates one for you. Choose a resource group and a region.
- Step 2, deploy a model. Find a model under Discover or Build, then select Deploy and Default settings. Write down the deployment name, because your code uses it. Wait until the status shows Succeeded.
- Step 3, test it in the playground. Send a simple message, such as "Write me a poem about flowers," and check the reply.
- Step 4, create an agent. Go to Build, then Agents, and select Create agent. Name it, choose your deployed model, and write instructions. Say what the task is, how to answer, and to ask for missing information instead of guessing.
- Step 5, test a follow-up. Ask a question, then ask a follow-up such as "How about a haiku?" If the agent uses the first request to answer the follow-up, it keeps conversation history.
- Step 6, call it from code. Copy the project endpoint from the welcome screen. The SDK quickstart shows how to create an agent with a model and instructions, then send messages to it.
Each time you save an agent definition from code, Foundry stores a new version. You can compare versions and roll back, which matters when you publish later.
Who can do what
Access is set by role. A role is a bundle of permissions you assign to a person on a scope, such as a project or a resource.
| Role | What it lets you do |
|---|---|
| Foundry User (on the project) | Build in the project: create agents, use the playground, and run evaluations. |
| Reader (on the resource) | Read the resource. Developers need this together with the Foundry User role. |
| Foundry Project Manager (on the resource) | Create projects, and invite others to a project as Foundry User. |
| Foundry Account Owner (on the resource) | Manage the resource, deploy models, and create shared connections. They can't build in projects unless they also get the Foundry User role. |
If you can't see your project, or you can't run an evaluation, check your role first.
Common mistakes
- Calling a model by its model name instead of its deployment name. Requests use the deployment name.
- Choosing a model that isn't available in your region. In the CLI this shows up as DeploymentModelNotSupported, so pick a supported model, version, or SKU.
- Skipping the role check. Without the Foundry User role on the project, you can't build in it.
- Assuming free to explore means free to run. Model use and services are billed.
Where each role starts
Hover over a card, or tab to it. On a touch screen, tap a card to open its bullets. Find the card that matches your job, then follow its starting link.
Full Stack Developer
Full Stack Developer
- Build and debug agents in VS Code
- Use the SDKs for Python, C#, JavaScript, and Java
- Deploy hosted agents with the Azure Developer CLI
Start here
Foundry SDK quickstart →
Data Engineer
Data Engineer
- Ground agents with Foundry IQ, with no upfront indexing
- Search several sources in one request with multi-source selection
- Enrich agent context through Foundry Agent Service in one observable runtime
Start here
What is Foundry IQ? →
AI Engineer
AI Engineer
- Use built-in evaluations to measure quality
- Trace agent runs with OpenTelemetry-based tracing
- Benchmark, compare, and route models for each task
Start here
Run evaluations in Foundry →
Security and Governance Lead
Security and Governance Lead
- Assign Foundry roles with role-based access control
- Use Microsoft Entra identity for access
- Set guardrails and content filters
Start here
Role-based access control for Foundry →
Business Owner
Business Owner
- Estimate costs with the Azure pricing calculator
- The platform is free to use and explore, and each service is billed separately
- Check each service's pricing page before you build
Start here
Azure pricing calculator →