AI tools are now part of everyday software development, but the names change fast and the overlap is confusing. This page is the map: the handful of concepts you need, and where GitHub Copilot, Claude and Microsoft Foundry each fit. Every section links to a deeper, hands-on post in this series.

Who this is for: developers and architects who want to use AI in real projects, not just read about it.

The core concepts in five minutes

Every AI product, whatever its brand, is built from the same eight ideas. Learn these once and each new tool becomes easier to place.

ConceptWhat it meansExample
Large language model (LLM)A model trained on huge amounts of text that predicts the next word; it can write, summarize, reason about and generate codeDrafting release notes from a list of merged pull requests
Tokens and context windowModels read text in chunks called tokens; the context window is how much they can consider at once, including your prompt, files and the replyWhether a whole codebase fits, or only the module you’re working on
Prompt and system instructionsThe prompt is your request; system instructions set standing rules the model follows for every request“Write C# with nullable reference types enabled and always add unit tests”
Retrieval-augmented generation (RAG)Search your own content first, then give the matching passages to the model so answers are grounded and citableAn internal assistant that answers only from your team’s documentation and cites the page
Tool use (function calling)The model decides to call a function you define, such as a search or an API, and uses the result in its answerThe model calls an order-status API to answer a customer’s question
AgentA model that works in a loop: plan, call tools, check results, repeat until the task is doneFixing a failing test: read the error, edit the code, rerun, repeat
Model Context Protocol (MCP)An open standard for connecting AI assistants to tools and data, so one integration works across many assistantsOne GitHub MCP server that Claude, Copilot and Foundry agents can all use
Evaluation and guardrailsTesting AI output against known cases, and limiting what it may see and doScoring answers against 50 known questions; keeping personal data out of prompts

How the three fit together

These aren’t three competing products. GitHub Copilot is where developers write code, Microsoft Foundry is where you build and run your own AI apps on Azure, and Claude is a model family you can use directly or inside both of them.

Claude, GitHub Copilot and Microsoft Foundry each play a different role

GitHub Copilot at a glance

GitHub Copilot is an AI assistant built into your editor and into GitHub itself. It’s the easiest starting point for most development teams, because it works inside the tools you already use.

Use it for: everyday coding, refactoring, unit tests, and routine tickets turned into pull requests.

Claude at a glance

Claude is a family of AI models from Anthropic, known for strong coding, long-document reasoning and agent work. You can use it in Anthropic’s own apps, call it from your code, or pick it inside Copilot and Foundry.

  • Model tiers: larger models (Opus) for the hardest reasoning and coding, mid-size models (Sonnet) for most production work, and small fast models (Haiku) for high-volume tasks. The current lineup includes Claude Opus 5.5 and Claude Sonnet 5.
  • Claude apps: chat on web, desktop and mobile, with connectors to your tools.
  • Claude Code: a coding agent that works in your terminal and IDE, reads the whole repository, runs commands and edits files. A CLAUDE.md file holds your project rules.
  • Claude API and Agent SDK: call Claude from your own services, give it tools to use, and build custom agents.
  • MCP: Anthropic introduced the Model Context Protocol, and Claude connects to MCP servers for tools such as GitHub, databases and your own APIs.
  • Where it runs: directly from Anthropic, inside GitHub Copilot, and in Microsoft Foundry, where some models support a 1M-token context window.

Use it for: complex refactors and code reviews, long specs and documents, content assistants, and agents that take multi-step actions.

Microsoft Foundry at a glance

Microsoft Foundry is Azure’s platform for building, running and governing your own AI apps and agents. It went by Azure AI Studio and then Azure AI Foundry, so older tutorials use those names.

Use it for: customer-facing AI features on Azure, such as a customer support assistant over your product documentation, where you need governance, monitoring and data residency.

Side by side, and which to use when

Most teams end up using all three: Copilot or Claude Code for building the solution, and Foundry or the Claude API for AI features inside the product.

GitHub CopilotClaudeMicrosoft Foundry
What it isAI assistant for developersAI model family, plus apps and APIAzure platform for AI apps and agents
Who uses itDevelopersDevelopers, content and business teamsDevelopers and architects building products
Where it runsIDE and GitHubClaude apps, API, inside Copilot and FoundryYour Azure subscription
Customize withcopilot-instructions.md, skills, MCPSystem prompts, CLAUDE.md, tools, MCPAgent instructions, tools, Foundry IQ knowledge
Best forDaily coding and pull requestsHard reasoning, long context, agentsGoverned, production AI features

Recent posts

Quote of the week

"People ask me what I do in the winter when there's no baseball. I'll tell you what I do. I stare out the window and wait for spring."

~ Rogers Hornsby