Install Microsoft Dynamics 365 Business Central Safely

TL;DR

You can install Business Central in two supported ways: Business Central online (cloud) or Business Central on-premises. Choose cloud for speed, lower maintenance, and Microsoft-managed updates; choose on-prem for strict data residency, offline requirements, or SQL control. This guide lists prerequisites, a decision matrix, and clear step-by-step instructions.

If you just need the essentials, start with the prerequisites table, pick cloud or on-prem, then follow that section. For hands-on help, contact our Business Central implementation services.

Cloud vs On-Prem: Which Should You Install?

Pick cloud when you want rapid provisioning, automatic updates, built-in disaster recovery, and predictable operating costs. Pick on-prem when regulations or latency demand local control, when you need SQL-level access, or when sites operate offline. If uncertain, start in cloud and revisit on-prem only for specific, validated constraints.

Scenario	Choose Cloud	Choose On-Prem	Why
Compliance and data residency	Industry needs are met by Microsoft’s certifications and regional data options	A regulator mandates local storage or sovereign-only networks	Cloud meets common certifications; on-prem satisfies strict residency rules
IT operations capacity	You prefer Microsoft to manage infrastructure and patches	You have a team for OS/SQL/IIS and backups	Cloud reduces operational overhead; on-prem requires full operations
Connectivity reliability	Internet is stable across sites	Sites are offline often or air-gapped	Cloud depends on reliable connectivity; on-prem tolerates isolation
Customization and data access	Extensions/APIs meet needs; no direct SQL required	You need SQL-level access or strict LAN-only integrations	Cloud restricts direct SQL; on-prem grants local control

Prerequisites

Before installing, validate accounts, licensing, and infrastructure. Cloud needs a Microsoft 365 tenant, global admin, and user licenses. On-prem needs supported Windows Server and SQL Server plus service accounts. Both paths require SMTP, TLS 1.2, identity in Microsoft Entra ID (Azure AD), and a tested networking plan (VPN/firewall). Confirm versions on Microsoft Learn.

Item	Cloud	On-Prem
Microsoft 365 tenant and global admin	[x]	[ ]
Entra ID (Azure AD) users with BC licenses	[x]	[x]
Supported Windows Server (for BC components)	[ ]	[x]
SQL Server 2019+ and backups	[ ]	[x]
IIS with HTTPS certificate	[ ]	[x]
Static IP and firewall rules	[ ]	[x]
SMTP service or Exchange Online	[x]	[x]
TLS 1.2 enabled end-to-end	[x]	[x]

Supported OS, SQL Server versions, browsers, and regional availability are listed by Microsoft (Microsoft Learn: https://learn.microsoft.com/dynamics365/business-central/dev-itpro/deployment/system-requirements).

Step-by-Step: Cloud Installation

Cloud setup centers on tenant configuration and environment creation. You will sign in as a global admin, create a production or sandbox environment, assign licenses, and complete assisted setup. Microsoft ships monthly service updates and applies them on a managed schedule you control in the admin center (Microsoft Learn: https://learn.microsoft.com/dynamics365/business-central/dev-itpro/administration/tenant-admin-center).

1. Sign in to the Business Central admin center with a global admin account (Microsoft 365).
2. Create a new environment (Production or Sandbox), selecting region and application version.
3. Assign Business Central licenses to users and groups in Microsoft 365 admin.
4. Open the environment URL and run Assisted Setup to configure company basics, finance, and bank connections.
5. Configure update windows and environment settings in the admin center; review the update schedule notes (Microsoft Learn: https://learn.microsoft.com/dynamics365/business-central/dev-itpro/administration/update-versions-availability).
6. Set up telemetry (optional) and review health metrics for sign-in, sessions, and web client responsiveness.
7. Validate with a test company: post a sample invoice, reconcile a bank feed, and export a report.

Step-by-Step: On-Prem Installation

On-prem installation means preparing Windows Server and SQL Server, running the Business Central setup media, and configuring service tiers and the web client. Plan ports, service accounts, and backups. Follow Microsoft’s supported topology and confirm requirements before installing (Microsoft Learn: https://learn.microsoft.com/dynamics365/business-central/dev-itpro/deployment/deploy-on-premises).

1. Prepare Windows Server, join the domain, reserve static IPs, and open required firewall ports.
2. Install SQL Server 2019+ with a case-insensitive collation and enable backups and maintenance plans.
3. Download the Business Central on-prem installation media from Microsoft Volume Licensing Service Center or Partner Center.
4. Run setup: install Business Central Server, Web Server (IIS), Administration Shell, and development components if required.
5. Configure the Business Central Server (NST): service account, database connection, ports, and certificates for HTTPS.
6. Create or restore the Business Central database in SQL; ensure compatibility and set required permissions.
7. Publish and synchronize base applications if prompted; verify application versions align with the platform.
8. Test the Web Client URL, confirm sign-in, and post a sample transaction.
9. Enable monitoring, backups, and, if needed, SQL Agent jobs for maintenance.

Post-Install Configuration

After installation, finalize company data, security, and integrations. Complete Assisted Setup pages, configure fiscal calendars, posting groups, dimensions, and bank services. Add users, assign permission sets, enable approvals and workflows, set up SMTP and email accounts, and review environment telemetry. Install only supported extensions that match your version and region.

• Company basics: name, number series, fiscal year, currencies.
• Security: users, permission sets, environments, and environments’ access policies.
• Finance: posting groups, VAT/tax, bank accounts, payment methods.
• Integrations: Excel add-in, Power BI, Dataverse (if applicable).
• Telemetry: Application Insights or Azure Monitor (Microsoft Learn: https://learn.microsoft.com/dynamics365/business-central/dev-itpro/administration/telemetry-overview).
• Extensions: evaluate AppSource offers; confirm publisher, version, and dependencies.

Troubleshooting and Verification

Expect most issues to trace to identity, networking, or version mismatches. For cloud, confirm license assignment, conditional access, and region quotas. For on-prem, check services, certificates, SQL connectivity, and firewalls. Validate with a posted document, a backup test, and a sign-in from a non-admin user to prove end-to-end readiness.

• Cloud: environment creation blocked? Review capacity and region availability (Microsoft Learn: https://learn.microsoft.com/dynamics365/business-central/dev-itpro/administration/tenant-admin-center).
• Sign-in issues: verify Entra ID, conditional access, and browser policies; test InPrivate.
• On-prem services won’t start: review Windows Event Viewer, service account rights, port bindings, and certificate trust.
• Report printing: ensure RDLC prerequisites and print server settings are installed and accessible.
• Performance: confirm SQL maintenance (indexing, logs) and size the NST for expected sessions.
• Availability: Dynamics 365 online targets a 99.9% uptime SLA (Microsoft: https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements).

Related Business Central reading

Use what Business Central is to validate product fit, and how to void a check in Business Central for a related finance operation.

FAQ

This section answers common choices and gotchas you will face during a first installation. It focuses on clarity: what to pick, how long it takes, and how to change course later. Each answer links to the most relevant Microsoft documentation so you can validate the recommendation quickly.

• Q: Can we start on-prem and move to cloud later? A: Yes. Microsoft provides migration tooling to move data from on-prem to Business Central online; plan a pilot and reconcile balances after cutover (Microsoft Learn: https://learn.microsoft.com/dynamics365/business-central/dev-itpro/administration/migrate-data).
• Q: Do we need IIS? A: Cloud does not require IIS. On-prem uses IIS for the Web Server component and HTTPS termination; use a certificate from a trusted CA and enforce TLS 1.2 (Microsoft Learn: https://learn.microsoft.com/dynamics365/business-central/dev-itpro/deployment/deploy-on-premises).
• Q: How long does cloud setup take? A: Often under an hour for a small tenant once licensing is in place, excluding data migration and approvals. Time increases with integrations and security reviews.

Resources and References

Use these references to confirm requirements, plan updates, and administer environments. Favor vendor documentation for anything involving security, availability, or support boundaries; it is authoritative and stays current. Keep these links handy when validating findings from community posts or partner guidance.

• Microsoft Learn: System requirements for Business Central: https://learn.microsoft.com/dynamics365/business-central/dev-itpro/deployment/system-requirements
• Microsoft Learn: Update policy and availability: https://learn.microsoft.com/dynamics365/business-central/dev-itpro/administration/update-versions-availability
• Microsoft Learn: Admin center for Business Central online: https://learn.microsoft.com/dynamics365/business-central/dev-itpro/administration/tenant-admin-center
• Microsoft Learn: Deploy on-premises: https://learn.microsoft.com/dynamics365/business-central/dev-itpro/deployment/deploy-on-premises
• Microsoft SLA overview: https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements
• Services: Business Central Implementation Services

---

UpdatedAt: 2026-06-24T11:00:00Z