In this chapter, we started with understanding the architecture of Dynamics 365 for Finance and Operations. We covered the conceptual architecture, various components, their roles, and how they function. Dynamics 365 for Finance and Operations embraces modern architecture built for cloud-first deployment. New architecture, when deployed in the cloud, uses Azure AD for the identity model and Azure SQL as the database, and the application components get deployed using Azure VMs. On-premise deployment uses AD FS for authentication, SQL Server 2016 for database, and Service Fabric Standalone Cluster to deploy application components. In the new architecture, Application Object Server (AOS) is hosted on IIS and batch operations run as a Windows service. Application logic is now modular and separated into application platform, application foundation, and application suite.

Dynamics 365 for Finance and Operations clients now comprises of the modern HTML 5-based web client and mobile app and has seamless integration with Office 365. It uses an exclusively new development platform on Visual Studio. LCS is used to manage the cloud as well as the on-premise deployment application lifecycle--from project inception to upgrade.

You also learned about three deployment choices available: Cloud, Cloud and Edge, and local business data. The cloud deployment option is the preferred and recommended option, while the other options can be useful for the organization having reservations in moving to the cloud due to regulatory or other challenges.

In the next chapter, you will lean about project initiation and management for implementing Dynamics 365 for Finance and Operations.