Whether connecting to Business Central Cloud, Business Central on-premises, or Dynamics NAV, you will require a Windows service running on your on-premises network in order to communicate with Business Central or NAV.
You can think of this service like an app you use to communicate with Business Central, but rather than install the app on every device/terminal, it only needs to be installed on a single network PC. Once the service is installed, all devices on the network will communicate with the service and the service will communicate with Business Central. This approach consolidates the logins and communication to dramatically simplify the device/terminal deployment.
The Windows service has a small footprint with low overhead and does not require a dedicated server. It is typical to have this Windows service deployed On-Premise where you have high network availability between the scanning stations to the server to Business Central/NAV.
If using Azure Windows Servers, ensure to use a good VPN between the site to the cloud, a sufficient whitelist, or other sufficient security.
When provisioning an empty Azure Windows Server for this portion, the Standard_B2ms as a technical minimum, with Standard_B4ms template being recommended, is sufficient.
These standard Azure templates typically translate into:
- Windows Server 2019 (or newer)
- Minimum 16 GB RAM (or more)
- Dual core 2.3 GHz CPU (or more)
- 8 GB available disk space (after all other OS and other system requirements)
These are general guidelines.