Business Central 27 On-Premises Production Support for Docker-based NST

Dan Koci 0 Reputation points
2026-07-30T07:50:54.6466667+00:00

Hello,

I have a question regarding Business Central 27 On-Premises environments and the use of Docker containers.

As an Infrastructure Administrator, I try to follow Microsoft best practices and official documentation when designing and operating production environments.

Our development team would like to use Business Central Server (NST) instances running in Docker containers for deploying extensions. My understanding is that Business Central containers are primarily intended for development, testing, CI/CD, and sandbox scenarios, while production workloads should typically run on standard Windows Server installations.

In our current production environment, all Business Central Server instances (user services, OData/SOAP services, and NAS/background processing services) are hosted on dedicated Windows Server 2025 machines.

Could you please clarify the following:

  1. Is running Business Central NST in Docker containers officially supported in a production on-premises environment?
  2. If it is supported, are there any limitations, prerequisites, or recommended architectures?
  3. If it is not supported, could you provide the official Microsoft documentation or support statement confirming this?
  4. Are Docker containers supported only for development and testing scenarios, or are there production use cases supported by Microsoft?

I would appreciate any documentation links, official recommendations, or architecture guidance you can share.

Thank you for your assistance.

Windows for business | Windows Server | Devices and deployment | Set up, install, or upgrade

1 answer

Sort by: Most helpful
  1. Allan Solomon Mejia 7,915 Reputation points
    2026-08-14T20:17:32.66+00:00

    Hi @Dan Koci

    Thanks for raising this question. This is an important distinction because Microsoft provides Business Central container images, but their intended use depends on the deployment scenario.

    Based on the current Microsoft documentation, Business Central containers are primarily intended for development, testing, demonstrations, CI/CD, and sandbox environments. Microsoft provides official container images and tools (such as BcContainerHelper) to streamline these scenarios.

    For Business Central On-Premises production deployments, Microsoft's documented guidance continues to focus on installing and operating Business Central Server (NST) directly on supported Windows Server operating systems. I haven't seen documentation explicitly stating that Docker-based NST deployments are a supported architecture for production on-premises environments.

    Before adopting containers for production, I would recommend obtaining clarification from Microsoft on:

    • Whether Business Central Server (NST) running in Windows containers is officially supported for production.
    • Any support limitations related to Windows containers, networking, service isolation, upgrades, monitoring, or troubleshooting.
    • Whether Microsoft Support will fully support production incidents occurring on a containerized NST deployment.

    Until there is explicit documentation confirming production support, a conservative approach would be to continue hosting production NST instances on supported Windows Server installations while using containers for development, automated testing, and CI/CD pipelines.

    It would be helpful if a Microsoft moderator could confirm the official support stance for Business Central 27 On-Premises production deployments using Docker-based NST instances and provide any relevant support statements or architecture guidance.

    Hello Marcin Policht, can you please confirm? Thank you.

    Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.