Skip to content
Code To Cloud
8 min read

Microsoft Foundry Solution Accelerators by Industry

Looking for Microsoft Foundry examples for your industry? Here is what the 15 official accelerators cover for energy, insurance, healthcare, banking, and more.

By Kevin Evans

What's Inside

  • How Microsoft's official accelerator catalog is actually organized
  • What exists for energy, insurance, healthcare, banking, retail, telecom, manufacturing, and life sciences
  • How strong each industry match really is, stated plainly
  • What to check before you build on one

The question comes up in nearly every Microsoft Foundry conversation: is there an official example for my industry? The answer is more useful than a plain yes or no, and it is not on one page, so this post lays it out.

Microsoft lists its Foundry-era solution accelerators at accelerators.ms. The page is rendered in the browser, so the catalog data is easier to read in the Solution-Accelerators repository that powers it. Everything below was checked against that data and each accelerator's own repository on September 26, 2026.

How the catalog is organized

There are 15 accelerators, all labeled Live, all MIT-licensed, none archived. Each is built around a functional pattern, not an industry: chat over your own data, content processing, knowledge mining, multi-agent automation, code modernization, data governance, and so on.

Industry appears in three weaker ways, and the difference matters:

  • A dedicated walkthrough deck for an industry, attached to a functional accelerator
  • A named use case in the accelerator's description
  • A scenario pack inside the repository, such as sample data and agent instructions for one industry

None of these is a separate, production-ready industry product. They are starting points, and a few are stronger starting points than others.

What exists, by industry

IndustryBest official starting pointHow strong the match is
EnergyChat with your data, Energy walkthrough deck; Microsoft IQDedicated deck; named use case ("unified data and analytics agents for energy")
InsuranceAgentic Applications for Unified Data Foundation; Content ProcessingDedicated Insurance deck; named use case (claims processing)
HealthcareContent Processing; Customer Chatbot; Prior Authorization Multi-Agent (outside the catalog)Named use case (clinician-patient visit documentation); scenario pack on sample data; a payer-side prior authorization reference
Banking and financial servicesChat with your data, Financial Advisor deck; Customer ChatbotDedicated deck; scenario pack on sample data; Document Knowledge Mining carries a "banking" tag only
RetailCustomer Chatbot; Agentic Applications for Unified Data Foundation; Microsoft IQScenario pack; named use cases (product discovery, retail supply chain)
TelecomConversation Knowledge Mining, Telco deckDedicated deck
Manufacturing and industrialsReal-Time Intelligence for Operations; Microsoft IQ; Data and Agent Governance and SecurityNamed use cases; no dedicated deck
Life sciencesDocument Knowledge MiningNamed use cases (drug discovery, research)
AutomotiveMicrosoft IQOne named use case

Three notes on reading that table honestly. First, "dedicated deck" means a Microsoft-authored presentation, not a separate repository. Second, the healthcare and banking scenarios in the chatbot accelerator run on fictional sample companies, so they demonstrate the pattern rather than a regulated product. Third, the prior authorization accelerator is a separate repository, not one of the 15 catalog entries. It is active and MIT-licensed, built as a payer-side review flow with multiple hosted agents and human-in-the-loop oversight, and it is the clearest example of an accelerator built for one regulated vertical.

The horizontal accelerators

Several accelerators have no industry framing at all and are useful across all of them:

  • Multi-Agent Custom Automation Engine, with RFP reviewer and contract compliance reviewer walkthroughs
  • Modernize your Code and Container Migration, for code and platform migration
  • Multi-Agent Content Generation, for marketing content
  • Deploy Your AI Application in Production, for a secure production environment
  • Data and Agent Governance and Security, for Purview-based governance and compliance guardrails
  • Unified Data Foundation with Fabric, the data layer several others build on

What to check before you build on one

Treat an accelerator as a fast way to see a pattern working, not as a shortcut past design decisions. Before committing:

  • Read the accelerator's own repository, not just its catalog card. Status, last commit, and open issues tell you more than the summary.
  • Replace the sample data early. A scenario that works on fictional data proves the wiring, not the fit.
  • Run it on a governed platform. Every accelerator here deploys onto infrastructure someone has to secure. The same identity, networking, and policy decisions from Azure AI Landing Zones apply regardless of which accelerator you pick, and running agentic AI at enterprise scale explains why they have to come first.
  • Do not skip a compliance review. An industry deck is not one.

If you would rather learn the platform hands-on first, our open-source Introduction to Microsoft Foundry workshop takes about an hour.

For a worked example of choosing a starting point and putting a governed platform under it, see how we approached standing up a governed agentic AI platform for an oil and gas environment. If you want help mapping your industry to the right accelerator and the platform under it, see our Agentic DevOps work or book a discovery call.

Kevin Evans

Kevin Evans — Fractional CTO and founder of Code To Cloud Fractional CTO & Founder, Code To Cloud Inc. Kevin Evans is a fractional CTO and technology advisor based in Calgary, Alberta. He spent nearly five years at Microsoft, rising to Senior Solutions Engineer, leading cloud and AI platform strategy, and now leads enterprise and mid-market engagements at Code To Cloud. More about Kevin

Frequently Asked Questions

Does Microsoft publish industry-specific Microsoft Foundry accelerators?

Not as separate codebases per industry. Microsoft's catalog has 15 accelerators, each built around a functional pattern such as chat over your data, content processing, or multi-agent automation. Industry shows up as walkthrough decks and named use cases layered on those accelerators, plus a few scenario packs, so the honest answer for most industries is "a real starting point, not a finished product."

Where is Microsoft's official list of solution accelerators?

At accelerators.ms. The page is rendered in the browser, so the underlying catalog data is easier to read in Microsoft's Solution-Accelerators repository on GitHub, which is the code behind the site. This post was checked against that data and each accelerator's own repository on 2026-09-26.

Can I use these accelerators in production?

They are MIT-licensed starting points, not supported products. The chatbot accelerator's healthcare and banking scenarios, for example, run on sample "Contoso" data. Plan to adapt the data, security, and compliance layers to your environment before anything customer-facing goes live.

Which accelerator has the most community adoption?

By GitHub stars on 2026-09-26, Chat with your data leads at about 1,181 (in the Azure-Samples organization), followed by Multi-Agent Custom Automation Engine at about 886 and Conversation Knowledge Mining at about 474. Stars are a rough signal of interest, not of quality or fit.

How current are these accelerators?

All 15 were labeled Live in the catalog and had commits within roughly the last ten days as of 2026-09-26, and none are archived. The catalog changes, so check it before relying on any specific accelerator.

  • 6 min read

    A Hands-On Introduction to Microsoft Foundry

    Our open-source Foundry workshop: deploy with Bicep, build a versioned agent, then gate it with an evaluation. About 60 minutes, Python, MIT-licensed.

  • 8 min read

    Inside the Azure AI Foundry Workshop

    A hands-on look at Microsoft's Azure AI Foundry Workshop — agent development, RAG, and evaluation in Python. Archived, but still worth using.

  • 10 min read

    GitHub Agentic DevOps in Production

    What 'agentic DevOps' means on GitHub — agent mode vs. coding agent, how MCP extends reach, and the governance controls enterprise teams need.

Have a technology decision to make?

Book a discovery call — no pitch, just a straight conversation.