Foundry: the governance that turns agents into real enterprise resources

So far, we’ve discussed MCP as the standard that allows agents to work with real business tools.
But every capability needs structure.
Every action needs control.
And every automation needs accountability.

That’s where Foundry comes in.

Foundry is not a tool for creating agents.
It is the environment that defines how those agents live, act, are supervised and integrated into the organisation.
It’s the difference between having experimental agents and having trusted enterprise resources.

1. What Foundry is — in functional terms

Foundry is the framework that allows agents to:

• maintain persistence (remember context and state)
• operate within boundaries (never act beyond their scope)
• use approved tools (only what the business authorises)
• provide auditability (every action is recorded)
• comply with corporate security (respect policies and permissions)
• achieve scalability (grow without losing control)

In short:
Foundry turns automation into a governed enterprise practice.

2. Why governance is the critical point

Automation without governance is an empty promise.
It can be fast, but not reliable.
Efficient, but not secure.
Useful, but not sustainable.

Foundry solves that dilemma.

It defines a framework where every agent has:

• identity
• purpose
• responsibility
• boundaries
• traceability

And that completely changes how functional and technical teams collaborate.

3. Functional examples of governance in action

Example 1: Purchasing agent with controlled access

The agent can review orders and validate prices, but cannot approve or modify records.
Foundry ensures the agent acts within its role — just like a human user with defined permissions.

Example 2: Finance agent with full traceability

Every action —query, validation, alert— is logged.
This enables real audits and compliance without extra effort.

Example 3: Support agent with contextual persistence

The agent remembers previous interactions, but only within authorised boundaries.
It never accesses data outside its scope.
Foundry keeps memory under control.

4. What Foundry brings to enterprise architecture

• Structured security — Agents operate under corporate policies, not improvisation.
• Controlled scalability — You can have dozens of agents without losing traceability or coherence.
• Operational accountability — Each agent has a purpose and a record of actions.
• Natural integration with MCP — Foundry doesn’t replace MCP; it complements it. MCP defines how agents communicate. Foundry defines how they are governed.
• Functional trust — Teams can delegate tasks knowing the agent acts within safe boundaries.

5. What changes for functional and business teams

With Foundry, functional teams stop seeing automation as a technical matter and start seeing it as an extension of the process.

They can:

• design agents with defined roles
• audit their behaviour
• adjust boundaries without technical intervention
• integrate agents into real workflows

And most importantly:
they can trust them.

6. Foundry and the future of enterprise automation

Foundry represents a new stage — automation with accountability.

It’s no longer about creating agents that “do things”.
It’s about creating agents that do the right things, under rules, limits and traceability.

It’s the step that turns artificial intelligence into a mature enterprise practice.

To Conclude

Foundry is the missing piece.
The one that turns automation into governance.
The one that transforms experimental agents into real enterprise resources.
The one that allows functional teams to work with confidence, security and control.

MCP enables action.
Foundry ensures responsibility.
Together, they define the future of automation in Business Central and across the Dynamics ecosystem.

In recent years we have seen agents that answer questions, generate text or explain concepts.
Interesting, yes.
Occasionally useful.
Transformational? Not really.

The real transformation begins when an agent stops being a “conversational assistant” and becomes a worker inside the operational process.

And that is only possible because of MCP.

MCP is not a technical detail.
It is the bridge between an agent’s intention and the organisation’s real tools.
It is the line that separates a chatbot from an operational agent.

Once you understand that, the true potential becomes visible.

1. MCP turns automation into something governed, not improvised

Before MCP, most automation efforts depended on:

• isolated scripts
• fragile connectors
• undocumented automations
• custom integrations
• processes that broke when a field changed

It was an ecosystem full of good intentions and bad habits.

MCP introduces order where creativity used to run unchecked.

It defines:

• what an agent can do
• which tools it can use
• under which permissions
• with what limits
• with what traceability

In short: it brings automation into the domain of enterprise governance.

2. What “using real business tools” actually means

When we say an agent “uses tools”, we are not talking about magic.
We are talking about actions that people perform every day.

Actions that consume time.
Actions that require precision.
Actions that repeat endlessly.

For example:

✔ Checking the status of an order and validating conditions

✔ Reviewing an attached document and spotting inconsistencies

✔ Searching for information in a corporate system

✔ Executing a business rule before approving something

✔ Preparing an operational summary for a manager

✔ Triggering an action that starts a process

This is not “generative AI”.
This is real work.

And MCP is the standard that allows an agent to do it without breaking anything.

3. Functional examples that reveal the real potential

This is where functional readers start to see the impact.

Example 1: A purchasing agent acting as the first filter

• Automatically checks if a supplier has delayed deliveries
• Validates prices against the commercial agreement
• Detects quantity discrepancies
• Suggests actions to the buyer

This agent does not replace the buyer.
It frees them from mechanical tasks so they can focus on strategic decisions.

Example 2: A finance agent preparing partial closing work

• Retrieves open invoices
• Identifies documents pending approval
• Flags potential delays
• Prepares a summary for the finance lead

It does not decide.
It prepares the ground so decisions are faster and better informed.

Example 3: An inventory agent anticipating issues

• Checks stock levels
• Detects potential shortages
• Suggests internal movements
• Recommends urgent purchase orders

It is a silent analyst working 24/7.

4. MCP redefines the role of the functional team

Here is the challenging part.

With MCP, the functional team stops being:

• the one documenting processes
• the one validating data
• the one checking rules
• the one performing repetitive tasks

And becomes:

• the one deciding what tasks to delegate
• the one defining which tools an agent can use
• the one supervising the quality of automated work
• the one deciding where human intervention is essential

It is a shift in role.
A shift in mindset.
A shift in responsibility.

5. MCP is not technology: it is process architecture

MCP is not understood through code.
It is understood through functional architecture.

Because MCP:

• standardises
• structures
• limits
• enables
• protects
• governs

And that allows agents to integrate into real processes without creating chaos.

It is the difference between “automating” and automating well.

6. What comes next

In the third part we will explore Foundry, the capability that turns these agents into governed enterprise resources:

• persistence
• auditability
• security
• boundaries
• approved tools
• scalability
• operational accountability

If MCP is the language, Foundry is the organisation where that language is used with clear rules.

To Conclude

MCP is not a technical feature.
It is the foundation that allows agents to perform real operational work inside the business.

It turns automation into something secure, governed and scalable.
It allows functional teams to delegate tasks without losing control.
It enables specialised agents that work inside the process, not outside it.

And it is, without doubt, one of the most important shifts in how organisations design and execute their work.

For years we have talked about automation, assistants and “intelligent agents”, yet most of those ideas remained as prototypes or isolated experiences. The reason was simple: there was no standard, secure and governed way for an agent to interact with real business tools.

This is where MCP and Foundry come in.

They are not new concepts. MCP has been around since 2024. Foundry has been maturing for some time. But now, with agents becoming more integrated into Business Central and the wider Dynamics ecosystem, these two capabilities are starting to have a real functional impact.

And that impact deserves to be explained from a business perspective, not a technical one.

1. What MCP is (explained for functional teams)

At its core, MCP is a standard that allows an agent to use business tools in a secure, structured and predictable way.

It is not an API. It is not a connector. It is not a plugin.

It is a common language that enables an agent to:

• retrieve information
• perform actions
• validate data
• interact with systems
• all within clear permissions, limits and rules

For functional teams, MCP means something very straightforward: agents stop behaving like “black boxes” and start acting as part of the process.

2. What Foundry is (without technical jargon)

If MCP is the language, Foundry is the platform that turns agents into governed enterprise resources.

Foundry allows an agent to:

• maintain context over time
• operate within defined boundaries
• use approved tools
• be audited
• comply with corporate security
• scale without breaking processes

In other words: Foundry makes an agent trustworthy, manageable and suitable for real business workflows.

3. Why this matters now (even though MCP has existed since 2024)

Because until recently, MCP was available… but without an ecosystem capable of fully leveraging it.

Today the situation is different:

• Business Central now includes agents that can use MCP
• Foundry provides real governance
• Organisations are demanding more mature automation
• Processes require agents that work with real data, not examples

So even if MCP is not new, its functional relevance is.

4. What changes for functional teams

Here is where the real value appears:

✔ Agents can work with real business tools

Not just “answer questions”, but perform actual tasks.

✔ Processes can delegate repetitive work

Data validation, document review, status checks, summaries.

✔ Automation no longer depends entirely on technical teams

MCP standardises interaction. Foundry governs it. Functional teams define the process.

✔ Security and auditability are built‑in

No more “shadow automations”. Everything is traceable.

✔ Specialised agents become possible

Not a generic assistant, but agents for purchasing, sales, finance, inventory…

5. What to expect in the next posts

This is only the beginning. The next posts will explore:

Post 2 — How MCP enables agents to work with real business tools

Functional examples, no code.

Post 3 — How Foundry provides governance, security and persistence

Why this changes how we design processes.

Post 4 — What this means for Business Central and functional roles

Impact on consulting, architecture and operations.

To Conclude

MCP and Foundry are not new technologies. What is new is their functional impact.

For the first time, agents can integrate into real processes with security, governance and approved tools. And that changes how functional teams design, execute and supervise work.

This is the starting point. The interesting part begins now.

In ERP projects, document attachments often become a blind spot: they take up space, slow down the system and complicate administration. Until recently, Business Central stored files directly within the environment, which could affect performance and increase cloud storage costs.

The new External Storage capability changes that paradigm. It allows attachments to be stored outside the main environment, maintaining traceability and access from Business Central while freeing the system from the physical weight of the files.

1. What external storage solves

Internal document storage typically faces three recurring challenges:

• Limited space — large attachments quickly consume capacity.
• Performance impact — every stored file adds load to the environment.
• Cost — more space means higher infrastructure costs.

External Storage addresses all three with a simple, elegant approach: keep the reference inside the ERP, but move the file outside.

Almacenar archivos adjuntos en archivos externos – Business Central | Microsoft Learn

2. How it works

You can configure an external storage provider (Azure Blob, SharePoint, OneDrive or any compatible service) and link it to Business Central entities.

When a user attaches a document:

• the file is saved in the external repository
• Business Central retains the link and metadata
• access remains seamless for the user

From the interface, the experience is identical — users open, download or view documents as usual. Behind the scenes, the ERP stays lighter and more efficient.

3. Benefits for architecture and governance

✔ Operational efficiency

Less load on the main environment, better overall performance.

✔ Scalability

Document volume can grow without compromising system stability.

✔ Security and compliance

External repositories allow advanced access, encryption and audit policies.

✔ Cost optimisation

External storage is typically more flexible and cost‑effective than internal SaaS space.

✔ Clear governance

Separating transactional data from physical files improves traceability and risk management.

4. Real impact on projects

For architects and consultants, this functionality brings tangible improvements to solution design:

• simpler environment administration
• fewer incidents caused by space saturation
• smoother user experience
• easier audits and compliance management

In projects with high document volume — invoices, contracts, purchase orders, reports — the change translates into greater stability and lower operational cost.

5. What it means for the future of ERP

External Storage is not just a technical enhancement. It’s a step towards a more modular architecture, where Business Central acts as the core for processes and data, while files live in specialised repositories.

This separation between structured data and document data is key to the evolution of modern ERP: more agile, more secure and better prepared for integration with other platforms.

To Conclude

External Storage redefines how Business Central manages attachments. It’s not only about freeing space — it’s about gaining efficiency, security and control. For those designing enterprise solutions, this capability opens the door to a cleaner, more sustainable and scalable architecture.

The integration between Business Central and Dataverse has always been a strategic pillar within the Dynamics ecosystem. It connects the ERP with Power Apps, Power Automate and Dynamics 365, shaping how information flows across processes, teams and business applications.

Recent improvements introduce a more refined approach to data consistency, integration stability and architectural clarity. These changes are not loud or flashy, but they make a meaningful difference for those of us who design, implement and govern enterprise solutions.

1. Clearer and more predictable field mapping

One of the most valuable enhancements is the expansion and reorganisation of field mapping between Business Central and Dataverse. This results in:

• less ambiguity when synchronising entities
• fewer unnecessary customisations
• reduced risk of inconsistencies
• better alignment with the Dynamics 365 data model

For architects and consultants, this translates into something very simple: less friction and more control.

When the data model is clearer, integrations become more stable and design decisions more predictable.

2. More consistent synchronisation across platforms

The synchronisation logic has been refined to better handle key fields, especially those related to:

• contacts
• accounts
• addresses
• commercial information
• entity relationships

This addresses one of the most common challenges in hybrid projects: data divergence between systems that should remain aligned.

When Dataverse and Business Central speak the same language, the entire architecture becomes more robust.

3. A step towards a unified architecture

Although these changes are subtle, they are undeniably strategic.

Microsoft continues to move Business Central towards a more natural integration with:

• Power Apps
• Power Automate
• Dynamics 365 Sales
• Dynamics 365 Customer Service
• Custom applications built on Dataverse

Every improvement in mapping and synchronisation is another building block in that unified architecture.

For solution designers, this means:

• fewer ad hoc connectors
• fewer manual transformations
• fewer fragile dependencies
• more standardisation

And ultimately, a stronger foundation for scalable, long‑term solutions.

4. Real impact on projects: less customisation, more stability

In real-world projects, these improvements lead to:

• fewer development hours
• fewer post go‑live incidents
• fewer integration adjustments
• fewer surprises in scheduled synchronisations
• fewer “patches” to fix inconsistent data

Most importantly, they provide a more reliable base for building business applications on Dataverse without compromising ERP integrity.

5. Why these changes matter more than they seem

Because the integration between Business Central and Dataverse is not just a connector. It is the backbone of:

• mobile applications
• automation flows
• customer experiences
• hybrid processes
• low‑code solutions
• enterprise extensions

When that backbone becomes stronger, everything built on top becomes more trustworthy.

These enhancements may not be headline-grabbing, but they represent a quiet and necessary step towards a more mature integration model.

To Conclude

The recent improvements in Dataverse integration bring a cleaner, more coherent and more sustainable architecture to Business Central. For architects, consultants and integration teams, they offer an opportunity to design more stable solutions, reduce customisations and strengthen interoperability across platforms.

In an ecosystem where data flows through multiple applications, every improvement in Dataverse is an improvement in business quality.

Business Central has been evolving for years towards a more intelligent, automated and connected ERP. But with the arrival of Agents (Payables Agent, Sales Agent, and others), Microsoft opened an entirely new chapter: assisted automation embedded directly into everyday operational processes.

Until now, the challenge wasn’t automation itself — it was how to govern it. How do you control what an agent does? How do you audit its actions? How do you stop it if something behaves unexpectedly? How do you ensure AI doesn’t become a “black box” inside your ERP?

With Business Central 28.0, Microsoft introduces a governance layer that genuinely changes the landscape: a centralised panel for control, audit and operational security across all active agents.

For anyone working in ERP projects, this is a significant milestone.

1. Why governance matters so much

Because automation without control creates risk. Automation with control creates trust.

In an ERP environment — where every action touches financial data, inventory, payments or sales — it’s not enough for an agent to “work”. We need to know:

• What it did
• When it did it
• Which data it touched
• Under what conditions
• And whether we should stop it or adjust it

Update 28.0 delivers exactly that: visibility, traceability and the ability to intervene.

2. The new Agents panel: a real command centre

For the first time, Business Central offers a centralised panel where you can see:

• All active agents
• Their running tasks
• Their history
• Their errors
• Their decisions
• Their recommendations
• Their impact on data

It’s genuinely a command centre.

No more jumping from module to module. No more guessing what an agent did. No more scattered logs.

Everything is in one place.

3. Full audit trail: every action recorded

Update 28.0 brings much clearer traceability:

• Which task the agent executed
• Which records it modified
• Which conditions it evaluated
• Which recommendation it produced
• How the user responded
• Which errors occurred

This isn’t just useful for support teams. It’s essential for:

• Compliance
• Internal audits
• Security reviews
• Quality assurance
• Corporate governance

AI stops being a black box. It becomes an auditable process.

4. Operational safety: “Stop all active tasks”

One of the most powerful — and least discussed — features in Update 28.0 is the ability to:

Stop all active agent tasks with a single click.

This is invaluable in scenarios such as:

• An agent entering a loop
• A large-scale data error
• Unexpected behaviour
• Processes affecting inventory or payments
• A production incident

Previously, stopping an agent could be complex. Now it’s immediate.

5. What this means for project teams

Quite a lot.

✔ For functional consultants

More control, less uncertainty. You can see what the AI is doing and when.

✔ For solution architects

A governance layer that didn’t exist before. You can design safer automation.

✔ For support teams

Faster diagnosis. Fewer “we don’t know what happened” cases.

✔ For auditors

Complete traceability. Documented decisions.

✔ For end users

More confidence. Less fear of “AI touching my data”.

6. What this means for the future of Business Central

It means Microsoft isn’t just adding AI. It’s adding governed AI.

And that’s exactly what organisations need:

• Automation
• Intelligence
• But with control, security and traceability

Update 28.0 marks the beginning of a new stage: the stage where AI stops being an experiment and becomes a trusted component of the ERP.

To Conclude

Agent governance in Business Central 28.0 is not a minor enhancement. It’s a strategic capability that:

• Strengthens security
• Improves auditability
• Reduces operational risk
• Brings transparency
• Enables confident adoption of AI

If you work with Business Central, this is a topic you need to master. Because agents aren’t going away — they’re going to multiply.

And governance will be the key to ensuring they work for the business, not against it.

When an ERP system goes live, teams inevitably face a surge of incidents, questions, micro‑errors and functional adjustments that never appeared in test environments. This does not mean the project was poorly executed; it simply means the system is experiencing real‑world conditions for the first time.

Business Central Update 28.0 introduces improvements that—although Microsoft does not label them this way—enable a concept that implementation teams should adopt immediately:

The Stabilisation Backlog

A parallel, temporary backlog designed exclusively to absorb, classify and resolve everything that happens between day one of go‑live and the moment the system stabilises.

1. What Is the Stabilisation Backlog?

It is an independent backlog, separate from the traditional Product Backlog, created to:

• Capture real incidents occurring in the production environment
• Separate “stabilisation noise” from genuine product evolution
• Prevent the Product Owner from being overwhelmed with non‑enhancement tickets
• Provide traceability for everything happening in the first weeks
• Prioritise based on operational impact rather than user pressure

This backlog does not compete with the Product Backlog; it protects it.

2. Why Does Update 28.0 Make It Possible?

Update 28.0 introduces key improvements that allow stabilisation to be managed with far greater precision:

✔ Richer, more accessible telemetry

It helps identify error patterns, response times, integration failures and abnormal behaviour. Official link: Monitorización y análisis de telemetría – Business Central | Microsoft Learn

✔ Better environment administration

It is now easier to clone, restore and compare environments to reproduce incidents. Official link: Comprendiendo la infraestructura de Business Central online – Business Central | Microsoft Learn

✔ Improved event traceability

System event logs are clearer, making it easier to distinguish functional errors from data or configuration issues. Official link (Update 28.0): Qué hay de nuevo o cambiado en Business Central 2026 ola de lanzamiento 1 – Vista previa de la actualización 28.0 – Business Central | Microsoft Learn

✔ Performance and UI consistency improvements

These reduce user friction, which in turn decreases the number of false incidents.

3. How to Build the Stabilisation Backlog (Step by Step)

Step 1 — Create a dedicated board

Use Azure DevOps or Jira with a board named: “Stabilisation Backlog – Go‑Live + 30 Days”

Step 2 — Define stabilisation‑specific categories

Avoid standard categories. Use these instead:

• Real incident (bug)
• Functional adjustment
• Data error
• Process error
• User friction
• Training gap
• Unexpected behaviour

Step 3 — Connect telemetry to incidents

Every incident should include a mandatory field: “Is there telemetry evidence?”

This eliminates subjective debates.

Step 4 — Prioritise based on operational impact

Not based on who shouts the loudest.

Step 5 — Review the backlog every 48 hours

This is where your “48‑hour meeting” fits perfectly.

4. Realistic Example of How the Stabilisation Backlog Works

Incident: “Users report slow performance when opening the Customer List.”

Before the Stabilisation Backlog:

• Mixed with enhancement requests
• Product Owner overwhelmed
• No evidence
• Time wasted

With the Stabilisation Backlog:

1. Logged as “User friction”.
2. Telemetry reviewed → SQL query spikes detected.
3. Issue reproduced in a cloned environment.
4. Misconfigured filter identified.
5. Fix validated within 24 hours.

Outcome: Less noise, more control, faster stabilisation.

To conclude

The Stabilisation Backlog is not a trend or a theoretical concept. It is a practical tool that, thanks to Update 28.0, becomes more powerful and more necessary than ever.

It enables teams to:

• Bring order to go‑live chaos
• Protect the Product Backlog
• Accelerate stabilisation
• Make decisions based on data
• Reduce user friction
• Prevent minor issues from becoming crises

In essence, it is the difference between surviving go‑live and mastering it.

The day an ERP goes live is not the end of the project; it is the beginning of its most sensitive phase: stabilisation. From day one, organisations must ensure visibility, communication and incident control to prevent issues from escalating into crises.

This post combines best practices from Project Management (PMI) and Scrum, backed by official sources, to show how incidents can be managed strategically in ERP SaaS projects.

Visibility: Transparency as the First Principle

According to the PMBOK Guide (PMI), incident management is closely tied to risk and communications management, stressing that every issue must be visible to stakeholders from the outset.

In Scrum, transparency is one of the three pillars (alongside inspection and adaptation). Incidents should be added to the backlog, discussed in daily stand‑ups, and prioritised based on impact.

Practical example:
During a Business Central SaaS go‑live, an error in Excel integration should be logged in a visible board (Azure DevOps, Jira). Both the Project Manager and Product Owner must see its status in real time.

Communication: From Noise to Clarity

The PMBOK Guide emphasises that communication must be structured and tailored to the audience. Not everyone needs the same level of detail, but all stakeholders require clear, timely information.

In Scrum, communication is continuous and concise: daily stand‑ups allow the team to share blockers and progress in under 15 minutes.

Practical example: After go‑live, a critical billing incident should be communicated to the sponsor with an executive summary (impact, estimated resolution time), while the technical team receives detailed instructions.

Control: From Reaction to Discipline

The PMBOK Guide states that incident control requires defined processes: logging, classification, assignment, monitoring and closure. This prevents improvisation and ensures traceability.

In Scrum, control is achieved through inspection and adaptation: each sprint reviews open incidents, adjusts priorities and measures resolution speed.

Practical example: In an ERP SaaS project, a minor reporting issue may be scheduled for the next sprint, while a critical payment incident is addressed immediately with a hotfix.

Tenant and Stabilisation in Business Central SaaS

In ERP SaaS, incident management also depends on proper tenant configuration and environment administration. Microsoft explains that a tenant is automatically created when cloud licences are acquired, and environment management is key to post go‑live stability.

To conclude

Go‑live is not the end of the project but the start of its most delicate phase. Organisations that apply PMI and Scrum best practices achieve:

• Full visibility of incidents from day one.
• Clear communication across teams and stakeholders.
• Disciplined control that turns problems into learning opportunities.

The combination of project discipline (PMI) and agility (Scrum) is the formula for transforming go‑live chaos into confidence and stability.

Migrating from Microsoft Dynamics NAV to Dynamics 365 Business Central SaaS is far more than a technical upgrade; it is a strategic shift that reshapes how an organisation operates, integrates and scales in the cloud.
Many companies (*) that have relied on NAV for years — and have not maintained BREP — now face a scenario where they must purchase new licences at full cost while simultaneously making critical decisions about their Microsoft ecosystem.

Below are the three key areas every organisation must address before migrating, along with Microsoft’s recommended approach and official documentation to validate each decision.

(*) Post developed specifically for companies in Latin America.

1. Perpetual Office vs Microsoft 365 SaaS: The Turning Point for Modern Integrations

The problem

Many organisations (*) still use Office 2019, Office 2021 or Office LTSC, assuming they will integrate seamlessly with Business Central SaaS.
In reality, these perpetual versions are not compatible with the cloud‑based integrations of the ERP, including:
– Outlook add‑ins
– Excel data export with live connection
– OneDrive
– Teams
– Native automation features

The strategic solution

Microsoft recommends migrating to Microsoft 365 Apps (subscription).
This ensures full compatibility with Business Central SaaS and unlocks all cloud‑native integrations.

Official documentation: 

Requisitos del sistema para Business Central – Business Central | Microsoft Learn

2. Windows Server 2019 Perpetual: Is It Required for Business Central SaaS?

The problem

Many organisations (*) believe they must upgrade Windows Server or purchase online server licences to use Business Central SaaS.

The reality

Business Central SaaS does not depend on Windows Server.
The ERP runs entirely in Microsoft’s cloud and only requires a modern browser.

Windows Server 2019 perpetual remains valid for:
– Local Active Directory
– File servers
– On‑premise integrations
– Internal applications

But it is not a requirement for Business Central SaaS.

3. Do Perpetual Licences Create a Tenant? How Do You Unify Microsoft 365 + Business Central SaaS?

The problem

Many organisations assume that owning perpetual licences (Office, Windows Server, NAV) means they already have a Microsoft 365 tenant.

The reality.

A tenant only exists when the organisation has purchased cloud services, such as:

– Microsoft 365
– Dynamics 365
– Azure

If the company has never purchased cloud subscriptions, it does not have a tenant.

The strategic solution

The tenant is automatically created when the organisation acquires its first cloud licences through a CSP (*).

This enables:

– Unified identity
– Centralised security
– Native integrations
– Simplified administration
– Business Central environment creation

Official documentation:

Comprendiendo la infraestructura de Business Central online – Business Central | Microsoft Learn

To Conclude:

Migrating to Business Central SaaS is not merely an upgrade; it is an opportunity to modernise the entire Microsoft ecosystem.

Organisations (*) that resolve these three areas before migrating:

– Reduce risk,
– Accelerate adoption,
– Avoid unnecessary costs,

and ensure a smooth, future‑proof transition to the cloud.This is Microsoft’s recommended path for a solid, sustainable and cloud‑aligned migration.

Implementing or migrating to Dynamics 365 Business Central SaaS is a major step for any organisation. Yet one of the most common challenges I see—across industries, sizes and maturity levels—is that teams underestimate the breadth of the platform. Business Central is not just a finance system; it is a complete operational backbone that touches every part of the business.

Microsoft has built a comprehensive learning ecosystem that brings together documentation, structured learning paths, capability guides, release notes and practical examples. This ecosystem is the most reliable and up‑to‑date source of truth for organisations preparing for an implementation, planning a migration, or onboarding end users.

Below is a structured overview of this “official library” and why it matters for project teams, decision‑makers and everyday users.

1. Understanding the Full Scope of Business Central

Before any workshops, configuration or data migration, organisations need clarity on what Business Central can actually do. The official documentation provides a complete view of the platform’s capabilities across:

• Finance and accounting
• Sales and customer management
• Purchasing and vendor management
• Inventory and warehouse operations
• Manufacturing and production
• Project accounting
• Service management
• Reporting, analytics and automation
• Security, administration and environments

This is not marketing material; it is detailed, practical and continuously updated by Microsoft.

2. Role‑Based Learning Paths for Every Type of User

One of the strengths of Microsoft Learn is that it recognises the different roles involved in an ERP project. Whether you are a functional consultant, a finance user, a warehouse supervisor or a system administrator, there is a dedicated learning path designed for your responsibilities.

These modules are:

• Practical
• Scenario‑driven
• Easy to follow
• Continuously updated
• Ideal for onboarding and adoption

For organisations preparing for go‑live, these learning paths reduce training time and increase user confidence.

3. Capability Guides for Scoping and Decision‑Making

During early discovery and scoping, teams often struggle to understand what Business Central delivers out of the box versus what requires configuration or extension. Microsoft’s capability guides help bridge this gap.

They provide:

• Functional summaries
• Process overviews
• Feature explanations
• Industry‑agnostic examples

These guides are especially useful for fit‑gap analysis and for aligning expectations between business stakeholders and the project team.

4. Staying Ahead with “What’s New” and Release Notes

Because Business Central SaaS evolves monthly, staying informed is essential. Microsoft maintains a dedicated “What’s New” section that outlines:

• New features
• Improvements
• Deprecations
• Roadmap items
• Release timelines

This allows organisations to plan enhancements, anticipate changes and take advantage of new capabilities as soon as they are available.

5. Visual and Media Resources for Practical Understanding

For teams that prefer visual learning, Microsoft also provides:

• Official demos
• Feature walkthroughs
• Scenario videos
• Release overviews

These resources help users understand processes in a more intuitive way and are excellent for internal training sessions.

6. Official Microsoft Documentation and Learning Links

Here are the official links, all from Microsoft:

6.1 Official Business Central Documentation

Complete functional documentation across all modules.

👉 Microsoft Dynamics 365 Business Central documentation – Business Central | Microsoft Learn

6.2 Microsoft Learn – Business Central Training Paths

Role‑based learning for end users, consultants and administrators.

👉 Training for Dynamics 365 Business Central | Microsoft Learn

6.3 What’s New in Business Central

Latest features, improvements and roadmap updates.

👉 New and planned features for Dynamics 365 Business Central, 2025 release wave 2 | Microsoft Learn

6.4 Business Central Product Page

High‑level overview of capabilities and value.

👉 Agentic CRM and ERP Solutions | Microsoft Dynamics 365

6.5 Official Dynamics 365 Videos

Walkthroughs, demos and feature explanations.

👉 Microsoft Dynamics 365 Business Central – YouTube

6.6 Official Business Central playlist on the Microsoft Dynamics 365 channel

This is an official playlist within the general Microsoft Dynamics 365 channel, focused on Business Central: overview, cloud migration, integrations, improvements, etc.

👉 Business Central – YouTube

7. Why This Matters for Organisations and End Users

A successful ERP project is not defined by configuration alone. It is defined by:

• How well users understand the system
• How clearly the organisation aligns processes with capabilities
• How effectively decisions are made
• How quickly teams adapt to change
• How confidently the business adopts new features

Microsoft’s official learning ecosystem gives organisations the structure, clarity and depth they need to achieve this.

To Conclude:

Mastering Business Central is not about memorising screens or menus. It is about understanding the platform’s capabilities, aligning them with business goals and empowering users with the right knowledge. Microsoft’s official library provides everything organisations need to build confidence, accelerate adoption and unlock the full value of Business Central SaaS.