Quick answer. If your account team pitches a Microsoft industry cloud: as of September 2026, Microsoft’s pages describe its industry offerings as combining Azure, Microsoft 365, Dynamics 365, Fabric and Power Platform. Adopt a prebuilt piece when it is generally available and fits your data model; otherwise build directly.
If a Microsoft account team or a partner has put an industry cloud in front of you as a faster route than building, you need to know what it is before a plan depends on it: a product, a set of templates, or a label on platforms you already run. Microsoft’s own Well-Architected for Industry overview, last updated April 9, 2026, puts it plainly: “Industry cloud solutions encompass Azure, Power Platform, Microsoft 365, and Dynamics 365 building blocks”. The sections below give what each offering is today in Microsoft’s words, what has changed, and when to build directly on the platforms instead. Each Microsoft page cited here was read on September 27, 2026.
What Each Microsoft Industry Offering Is Today
If you need the list first, Microsoft’s industry documentation hub states: “This documentation includes information about the Microsoft for Healthcare, Financial Services, Manufacturing, Nonprofits, and Sustainability.” It describes these solutions as built for your industry, “combining Microsoft Azure, Microsoft 365, Microsoft Dynamics 365, Microsoft Fabric, Microsoft Power Platform, and agentic AI.” Energy and government appear on the same hub only as architecture and solution pages for Azure and other products, not as offerings of their own. Sovereignty now sits in the Azure documentation under a new name. The table gives each offering in Microsoft’s words; where Microsoft’s page says nothing, the cell says so.
| Offering | What Microsoft says it is | How it is obtained, where Microsoft says | What changed, with Microsoft’s date |
|---|---|---|---|
| Microsoft for Financial Services | “a trusted financial services platform” whose foundation “is the hyperscale public cloud”, with sections on infrastructure, compliance, industry guidance and data and AI | Not stated on the overview; the Compliance Program for Microsoft Cloud is described as “a fee-based premium program” | No change dated on the pages read |
| Microsoft for Manufacturing | “a collection of Microsoft and partner solutions that you can deploy, configure, and use based on the specific capabilities you need” | “You don’t need a separate Cloud for Industry license.” | Manufacturing data solutions and two factory agent previews deprecated as of May 30, 2025; Factory Safety Agent preview deprecated as of June 23, 2025 |
| Microsoft Sovereign Cloud | “formerly Microsoft Cloud for Sovereignty”, with three deployment models and a Sovereign Landing Zone | Available across European datacenter regions for European customers | Renamed; Microsoft’s page gives no date |
| Microsoft for Sustainability | “a comprehensive suite of cloud-based services and platforms” | “You can buy Microsoft for Sustainability as part of an Enterprise Agreement (EA).” | No change dated on the pages read |
| Microsoft for Nonprofits | Connects “intelligent and integrated cloud capabilities of the Microsoft stack to the most common nonprofit organizational scenarios” | Not stated on the overview | Its Fabric data solution is listed as a preview |
For healthcare, Microsoft’s overview, last updated July 20, 2026, says: “Microsoft for Healthcare harnesses the power of the Microsoft cloud by bringing together capabilities from Microsoft Azure, Dynamics 365, Microsoft Power Platform, and Microsoft 365.” What Microsoft has changed in that offering, and how to choose between taking it over and building direct, is covered in Microsoft for Healthcare After the Managed Solutions End: A Guide to Taking Over Microsoft’s Package or Building Direct on Azure, Dataverse and Fabric.
Retail no longer appears in Microsoft’s industry documentation hub; its old Learn overview address now redirects to a Microsoft marketing page.
What Changed, and Why It Matters Before You Commit
If a plan depends on a packaged industry component, the risk is that Microsoft retires the component while you are still building on it. Microsoft’s What’s new in Microsoft for Manufacturing page, last updated August 19, 2026, records two such retirements: “The preview of Manufacturing data solutions, Factory Operations Agent in Azure AI, and Factory Operations Agent in Copilot Studio was deprecated as of May 30, 2025.” and “The preview of Factory Safety Agent in Copilot Studio was deprecated as of June 23, 2025.” The same page’s August 2026 entries are reference architectures for running engineering software on Azure.
If a proposal uses an offering name, check that name on Microsoft Learn. Microsoft’s What is Microsoft Sovereign Cloud? article, last updated July 15, 2026, opens: “Microsoft Sovereign Cloud, formerly Microsoft Cloud for Sovereignty, is an evolution and expansion of the original offering.” If a proposal or an older article uses a name you cannot find on Learn, confirm the current name and status there before a phase depends on it.
If you expected a prebuilt industry data model in Fabric, Microsoft’s Industry Solutions in Microsoft Fabric page, last updated April 5, 2026, lists healthcare data solutions, a DAX Copilot integration for healthcare organizations, and “Nonprofit data solutions in Microsoft Fabric (preview)”. As of that date the page lists no financial services or manufacturing data solution.
Microsoft for Financial Services: What You Get Today
If you run IT at a financial services firm, Microsoft’s What is Microsoft for Financial Services? article, last updated January 23, 2026, says: “Microsoft for Financial Services offers a trusted financial services platform that helps harness the innovation and cybersecurity benefits of the cloud while meeting stringent internal and external compliance requirements.” It organizes the offering in four sections: Microsoft Cloud infrastructure, compliance and transparency, industry guidance and accelerators, and data and AI platforms.
Most of that is material your team applies in its own tenant. The article points to control mappings, where “Regulatory Compliance in Azure Policy provides built-in initiative definitions to view a list of the controls and compliance domains based on responsibility”, to Azure landing zone guidance, and to reference architectures with “tooling and templates to accelerate your next projects”. It also names the Compliance Program for Microsoft Cloud, which it calls “a fee-based premium program offering personalized support to address compliance challenges”.
If new cloud services take a long time to approve inside your bank, Microsoft’s cloud service enablement framework, last updated March 30, 2026, names the problem: “Regulated banking enterprises face persistent friction when enabling new cloud services.” It is also clear about its limits: “This framework isn’t a prescriptive operating model, compliance checklist, or audit artifact.” Your team still owns the control baseline and the evidence behind it.
Microsoft for Manufacturing: A Collection, Not a Separate License
If you run engineering and plant systems, including at an aerospace and defense manufacturer, Microsoft’s What is Microsoft for Manufacturing? article, last updated July 27, 2026, says: “Microsoft for Manufacturing brings together Microsoft and partner solutions to accelerate Digital Transformation”. Its get-started page, last updated July 28, 2026, is plainer: “Microsoft for Manufacturing is a collection of Microsoft and partner solutions that you can deploy, configure, and use based on the specific capabilities you need. You don’t need a separate Cloud for Industry license.”
So the manufacturing offering is not a product with its own license, and there is no single thing to implement. With the data solutions preview deprecated, what you take from the offering is a set of Microsoft and partner solutions and reference architectures, each running on services you license on their own terms. Microsoft’s availability page, last updated August 6, 2025, says the same about geography: “International availability of the Microsoft for Manufacturing solutions is based on the availability of each of the individual products and services”.
Microsoft Sovereign Cloud and What It Means for a US Workload
If data sovereignty is on your requirements list, the same Microsoft Sovereign Cloud article states: “Microsoft Sovereign Cloud is available across European datacenter regions for European customers and supports enterprise services such as Microsoft Azure, Microsoft 365, Microsoft Security, and Power Platform.” It adds: “Although the foundation targets European datacenter regions, technical capabilities to enforce data sovereignty are available worldwide.” It names three deployment models: Sovereign Public Cloud, Sovereign Private Cloud and National Partner Clouds. The private model is “delivered via Azure Local, Microsoft 365 Local, GitHub Enterprise Local, and Foundry Local on Azure Local”. Its core component is the Sovereign Landing Zone (SLZ), described as a “Preconfigured Azure environment with policy-as-code templates to enforce compliance and security baselines.”
If your requirement is US federal data or controlled unclassified information, sovereignty in the US is a government-cloud question. The Microsoft industry pages read for this guide state no GCC, GCC High, DoD or Azure Government availability for any industry offering, so check each underlying service on its own. What changes when you build in the government cloud is covered in Building on Microsoft 365 GCC High: What Changes.
When to Adopt a Microsoft Industry Component and When to Build Direct
If you are deciding piece by piece, put each prebuilt component through four tests. Adopt it only if it passes all four; if it fails any one, regardless of how many others it passes, build that piece directly on the platforms.
- Is it generally available? Check its Learn page for a preview label. Manufacturing data solutions were a preview when Microsoft deprecated them.
- Does it match your data model? If your team would have to reshape its own entities to fit the component’s schema, build the schema you need in Dataverse or Fabric instead.
- Does it fit your control baseline? The component has to run under the policies and identity rules you already enforce, and produce the audit evidence you already collect, without exceptions written for it.
- Is it still listed on its Learn page? Re-read the page before each phase. A component that has left Microsoft’s documentation, or that Microsoft hands back to you as source code to run, is now your code to maintain.
When you build direct, you build on the same platforms the industry offerings sit on. For app-layer templates and data models, the destination is Dataverse, set out in Enterprise Dataverse Development & Integration Services for a Governed Data Foundation. For CRM and ERP processes, it is Dynamics 365, set out in Enterprise Dynamics 365 Development Services That Align CRM and ERP to How You Operate. i3solutions has delivered Dynamics 365 integration engagements for regulated enterprises across healthcare, defense and aerospace manufacturing, and financial services. i3solutions builds Dynamics 365 integrations using named Microsoft mechanisms including Dataverse, dual write, virtual tables, Azure Logic Apps, Azure Service Bus, and Power Automate connectors.
For industry analytics and data products, the destination is Fabric, set out in Enterprise Microsoft Fabric Development & Integration Services for Unified, AI-Ready Analytics. i3solutions has delivered Microsoft Fabric work for clients.
Whichever way you go, own the data model. Document the entities, who owns each one and how each maps to your controls, so that a later change by Microsoft replaces a component rather than your foundation.
When Adopting Microsoft’s Offering Makes Sense
If the offering’s templates and data model already match yours, the component is generally available, and your team would otherwise rebuild the same Dataverse or Fabric schema, adopting it saves that work. Because Microsoft describes manufacturing as “a collection” of solutions, you can take one piece without the rest. And if your need is a single workload that a landing zone plus standard Azure, Microsoft 365 or Dynamics 365 services already covers, you need neither an industry offering nor a custom build: deploy the standard services under the controls you already run.
How i3solutions Approaches the Decision
If you want a second view on which pieces to adopt and which to build, i3solutions implements whatever Microsoft technology a customer needs. i3solutions maps governance to named control families, enforces it in the platform through Entra ID, Purview, and Azure Policy, and evidences it continuously rather than reconstructing it at audit. i3solutions has been a Microsoft partner since 1997 and has delivered 600+ implementations across aerospace and defense, financial services, and health sciences. Delivery is senior and US-based.
Key Takeaways
- If you keep one point: Microsoft describes its industry offerings as combinations of the platforms, and for manufacturing it says “You don’t need a separate Cloud for Industry license.”
- Microsoft Sovereign Cloud, formerly Microsoft Cloud for Sovereignty, is available across European datacenter regions for European customers.
- Microsoft deprecated the Manufacturing data solutions preview as of May 30, 2025; read a component’s Learn page before a phase depends on it.
- Adopt a component only when it is generally available, matches your data model, fits your control baseline and is still listed; otherwise build directly on Dataverse, Dynamics 365, Fabric and Azure.
Frequently Asked Questions
What happened to Microsoft Cloud for Sovereignty?
If you search for it under that name, Microsoft now calls it Microsoft Sovereign Cloud. Microsoft’s overview describes Microsoft Sovereign Cloud, formerly Microsoft Cloud for Sovereignty, as an evolution and expansion of the original offering, available across European datacenter regions for European customers, with Sovereign Public Cloud, Sovereign Private Cloud and National Partner Clouds as its deployment models. The overview gives no date for the name change.
Do I need a separate license for a Microsoft industry cloud?
If the offering is Microsoft for Manufacturing, Microsoft says no: “You don’t need a separate Cloud for Industry license.” Microsoft for Sustainability is different, because Microsoft says you can buy it as part of an Enterprise Agreement (EA). For the other industry offerings, Microsoft’s pages, as read on September 27, 2026, state no license term, so ask your Microsoft account team in writing.
Is Manufacturing data solutions still available?
If you planned around it, no. Microsoft’s What’s new page for manufacturing states that the preview of Manufacturing data solutions, Factory Operations Agent in Azure AI and Factory Operations Agent in Copilot Studio was deprecated as of May 30, 2025. Microsoft’s list of industry solutions in Fabric, last updated April 5, 2026, names healthcare and nonprofit solutions only, so a manufacturing data model in Fabric is one your team builds.
Are Microsoft’s industry clouds available in GCC High?
If you work in GCC High, do not assume they are. Microsoft’s industry documentation pages, as read on September 27, 2026, state no GCC, GCC High, DoD or Azure Government availability for any industry offering, and Microsoft Sovereign Cloud targets European datacenter regions. Check the government availability of each underlying Azure, Microsoft 365, Dynamics 365 and Power Platform service instead.
Bring Your Industry Offer to an Architect
If an industry offering is in a proposal on your desk, bring the proposal, the components it names, your data model and your control baseline. An architect works through those facts with you and sorts which pieces to adopt and which to build. Talk to a senior architect
Sources
- Microsoft Learn: Microsoft industry documentation and resources (no date shown); Overview of Well-Architected for Industry, last updated April 9, 2026; What is Microsoft for Financial Services?, last updated January 23, 2026; Cloud service enablement framework for regulated financial institutions, last updated March 30, 2026; What is Microsoft for Manufacturing?, last updated July 27, 2026; How do I get started with Microsoft for Manufacturing?, last updated July 28, 2026; What’s new in Microsoft for Manufacturing, last updated August 19, 2026; International availability of Microsoft for Manufacturing, last updated August 6, 2025; Industry Solutions in Microsoft Fabric, last updated April 5, 2026; What is Microsoft for Healthcare?, last updated July 20, 2026; What is Microsoft for Sustainability? and How to buy Microsoft for Sustainability, each last updated March 24, 2026; What is Microsoft for Nonprofits?, last updated January 23, 2026.
- Microsoft Learn, Azure: What is Microsoft Sovereign Cloud?, last updated July 15, 2026. Each Microsoft page read September 27, 2026. Microsoft revises these pages; confirm the current wording before you rely on it.
