In this section, we provide details of the solution architecture that we are going to build for the customer. The main objective of this architecture is to provide all project team members with an understanding of the proposed system. This solution architecture should include all of the major components and integration details. For example, the following is a sample solution architecture diagram for HIMBAP Auto Service Center:

In the diagram, we can see that the first section shows the types of Users we can have for our application. They can use different clients to access Dynamics 365 CE applications, such as a web browser, Outlook, mobile, and tablet applications. There will be an authentication layer that will use Azure Active Directory (Azure AD), as we are using online deployment. We will also have the Dynamics 365 CE Security Model, which will control the visibility of the data based on the user security roles. The Application Layer will contain the user interface (UI) components and Dynamics 365 configurations. It will also contain business entities with their customization and extensions, as well as Dynamics 365 CE databases. The Integration Layer contains integration logic, and we will be using Microsoft Flow for integration in our case.