Business Central Cloud OR Business Central On Premise

Business Central Cloud OR Business Central On Premise Differences in These 2 Dynamics Flavors

Session Objectives § Confirm the product offerings for Microsoft Dynamics 365 Business Central (BC) § Understand the differences between the Cloud version and On Premise version § Understand the availability and capability of migrating between Business Central Cloud and Business Central On Premise

What’s in a Name?

History of Business Central On Premise § Mid 90’s = Avista § Still Mid 90’s = Navision § Mid 2000’s = Microsoft Dynamics NAV §… § Oct. 2016 = Microsoft Dynamics NAV 2017 § Oct. 2017 = Microsoft Dynamics NAV 2018 § Oct. 2018 = Microsoft Dynamics 365 Business Central (Product was re-branded by Microsoft)

What’s in a Name? § Microsoft Dynamics 365 Business Central § Hosted by Microsoft on Microsoft’s Azure Cloud § For this presentation = “Cloud” (blue) § Microsoft Dynamics 365 Business Central On Premise § Hosted by the client at any location § For this presentation = “On Premise” (red)

Licensing

Licensing Options (if Buying New) CLOUD § Subscription § Named Users § Full: $70(E)/$100(P) § Team: $8 § Subscription only § Includes Hosted Environment ON PREMISE § Subscription (Lease) § Named Users § Full: $60/$85 § Team: $10 § Perpetual (Purchase) § Named Users § Full: $2, 000/$2, 800 § Team: $400 § 16% per year § No Hosted Environment

Licensing Options (Upgrade) CLOUD § Subscription § Named Users § Full: $45(E)/$60(P) § Team: $8 § Based on new 1: 3 User Count! § Subscription only ON PREMISE § Subscription § Named Users § Full: $45/$60 § Team: $8 § Perpetual § Maintain Annual Enhancement Plan § Purchase or Subscription

Migration Paths

Features not intended for use in on-premises deployments §From BC Cloud to BC On Premise § No defined migration path § A custom plan may need to be developed to migrate existing extensions/apps and data from Cloud to On Premise. § Request a copy of the SQL database backup from Microsoft to be restored On Premise?

Features not intended for use in on-premises deployments §From BC On Premise to BC Cloud § Migration Path available § Establish a “Cloud Ready” environment in BC On Premise § No modified objects, only Extensions § Sync your On Premise data via “Setup Intelligent Cloud” to establish data replication to the BC Cloud. § Switch to using BC Cloud as the primary “source” environment

Deployment

Deployment Options CLOUD § Hosted by Microsoft on the Microsoft Azure Cloud ON PREMISE § Hosted by the Client § Hosting fee included in the monthly user subscription § Hosting fee paid by client in addition to user licenses § “Multi-Tenant” § “Saa. S” § Physical/Virtual Server located on premise § Private Virtual Server located in the cloud: § Microsoft Azure § Other hosting provider

Software Updates

Software Updates and Upgrades CLOUD § Applied automatically by Microsoft § 2 major releases per year § Periodic updates to deploy new features § Notifications regarding update plan/status § Partner Services Required? ON PREMISE § Applied by the client in coordination with partner § 2 major releases per year § Monthly/Quarterly cumulative updates available per release § Upgrades significantly easier/faster with all Extensions § Partner Services Required

Development

Development CLOUD § “Modern development environment” § Visual Studio Code with AL Language § Creates Extensions § No changes to standard Microsoft code § Client has same availability as Partners § No development license required ON PREMISE § “Modern Development environment” or C/SIDE Development Environment modifying objects § Version 14 - objects § Version 15 – no objects! § Development license required for many C/SIDE changes

Integration Capabilities

Integration Capabilities CLOUD § Requires the use of Web Services/o. Data § No direct access to SQL Server database § Verify Performance ON PREMISE § Web Services/o. Data, ODBC SQL Queries and Views, SQL Linked Tables § i. e Data Whse. /Whse. Mgmt. integrations § Direct access to SQL Server database § i. e. UPS Worldship integrations § Fewer options due to multitenant environment § Private tenant provides more options

User Interface

User Interface CLOUD 1) Web Client 2) App Client ON PREMISE 1) Web Client 2) App Client 3) Windows Client - Version 14: Yes - Version 15: No

Capabilities & Features

Capabilities & Features Shared source code! Same features! Except…

Capabilities & Features § Two types of limitations for Business Central On Premise: § Features that require specific circumstances § Features not intended for use with On Premise deployments https: //docs. microsoft. com/en-us/dynamics 365/businesscentral/dev-itpro/features-not-implemented-on-premises

Features that require specific circumstances §Read/write data with Excel add-in § The Excel add-in that enables update of data requires Azure Active Directory as the authentication mechanism

Features that require specific circumstances §Excel Financial Reports § The Excel add-in that is used with the predefined Excel-based financial reports requires Azure Active Directory as the authentication mechanism.

Features that require specific circumstances §Coversheets for contact management § The integration with Word to create the coversheets requires Azure Active Directory as the authentication mechanism.

Features that require specific circumstances §Built-in Power BI reports and charts § The integration with Power BI requires Azure Active Directory as the authentication mechanism.

Features that require specific circumstances §Built-in Microsoft Flow Management § You can use the built-in workflows in on-premises deployments of Business Central, provided that you connect to Microsoft Flow using Azure Active Directory as the authentication mechanism. § This can be done using the Azure Active Directory Assisted Setup guide in Business Central. Microsoft Azure and Microsoft Flow require Azure Active Directory authentication; however, your Business Central on-premises deployment does not have to use Azure Active Directory as the general authentication mechanism.

Features that require specific circumstances §Built-in web services § A number pages and queries are exposed as web services. However, the default endpoint must be manually updated before the web services can be consumed.

Features that require specific circumstances §Outlook add-in § The Outlook add-in requires Dynamics NAV User/Password or Azure Active Directory as the authentication mechanism.

Features that require specific circumstances § Standard REST API § Business Central contains new standard REST APIs. However, onpremises deployments cannot be reached through Microsoft Graph or the common endpoint, https: //api. businesscentral. dynamics. com/v 1. 0/api/beta. Instead, you must connect directly to the on-premises deployment, just as when you connect to web services.

Features that require specific circumstances §Sales and Inventory Forecast § This functionality requires an Azure Machine Learning subscription. § Machine learning is a data science technique that allows computers to use existing data to forecast future behaviors, outcomes, and trends. By using machine learning, computers learn without being explicitly programmed. § Azure Machine Learning is a cloud service that you use to train, deploy, automate, and manage machine learning models, all at the broad scale that the cloud provides.

Features that require specific circumstances §Cortana Intelligence in Cash Flow Forecast § This functionality requires an Azure Machine Learning subscription.

Features that require specific circumstances § Image Analyzer § This functionality requires an Computer Vision service. § Azure's Computer Vision service provides developers with access to advanced algorithms that process images and return information. To analyze an image, you can either upload an image or specify an image URL. The images processing algorithms can analyze content in several different ways, depending on the visual features you're interested in. For example, Computer Vision can determine if an image contains adult content, or it can find all of the human faces in an image.

Features not intended for use in on-premises deployments §Default Power BI reports § Automatic deployment and configuration of Power BI reports is not supported in on-premises deployments of Business Central.

Features not intended for use in on-premises deployments §Late Payment Prediction § The Late Payment Prediction functionality is not supported in on-premises deployments of Business Central.

Features not intended for use in on-premises deployments §In-product search § In online deployments of Business Central, Tell Me, the in-product search, also searches in content on the docs. microsoft. com site. For on-premises deployments, this is not supported.

Features not intended for use in on-premises deployments §Create workflow from Flow § Microsoft Flow does not integrate with on-premises workflow functionality. You cannot create new workflows based on existing Microsoft Flow templates in on-premises deployments of Business Central.

Features not intended for use in on-premises deployments §Sandbox environments § The sandbox environment that you can use to develop extensions against for the new developer experience cannot connect to an on-premises deployment. § However, for On Premise, clients can still manually create an unlimited number of sandbox environments.

Features not intended for use in on-premises deployments §Inviting the external accountant § Integration with Dynamics 365 — Accountant Hub is not supported in on-premises deployments of Business Central.

Features not intended for use in on-premises deployments §Bulk Invoicing from Microsoft Bookings § Integration with the Bookings app in Office Business Premium is not supported.

Q&A Time