Dynamics Community Forum Thread Details

BC cloud or OnPrem deployment and costs comparison

Hi All,

Please can you explain the best practice if client will upgrade from NAV2013 R2 to BC, but which deployment (BC Saas or OnPrem, or Hybrid) is best in this case.

Currently 3 companies (USA, CAN, MX) are already on BC SaaS and they are using few cloud flows in the Power Automate to integrate data from/to 3rd party app <-> BC SaaS. Everything works as expected.
They do not care if they will use BC SaaS/OnPrem.

Companies in the EU (GER, SK, PL) are using NAV2013 R2 (multi-company deployment). This works as expected. Database size is at 600GB.
Those are upgrading to the BC, but company owner does not like cloud deployments, since he has a business partner in Sweden who told him that they (Swedish client) had 24 hour downtime of BC SaaS and they could not do their daily work, and Microsoft did not mark this as business critical issue, so they didn't receive any compensation for their loss of income.
They would like to have clear info if BC SaaS is 100% sure and what are the service agreement rules.

Companies located in Asia (RUS, CH) plan to use the BC (I guess there is no option of cloud deployment in China)?
Is BC SaaS available in RUS and China?

Another question? Can same client use BC SaaS in the USA, CAN, MX, and BC OnPrem in the EU? And can then be data integrated with these companies in BC SaaS and BC OnPrem? This is basically one global company (HQ in GER) that has multiple subsidiaries in the world.

IT Manager is sceptical to pay for any additional thing:
- database capacity limit to 100GB per environment? If database of BC is increased it costs about 10 EUR/1GB (I am not sure about the pricing).
- Azure Blob Storage (50GB 2 EUR/month)
- backup of Azure Blob Storage is an additional costs, etc.

IT Manager says that they have invested a lot in the hardware and now the costs to have deployed BC in cloud and database size is limit to 100GB and if BC database size exceeds this quota then additional fees apply.

Current schema is to easily understand current situation: