In this module, we covered: defining a Solution Architect, role of a Solution Architect on projects, project methodology, getting to know your customer.

In this module, you will be reviewing project details for Contoso. This includes a set of requirements gathered from customer workshop sessions. You will use this information to design a high-level architecture and complete a fit gap analysis.

A Microsoft Power Platform Solution Architect plays a key role on a project. The solution architect will end up implementing governance, change processes and monitoring the project progress.

A Microsoft Power Platform Solution Architect Solution Architect is responsible for the overall design of the solution. Understanding the architecture of the Microsoft Power Platform, how it is designed, and its limits are very important when designing solutions based around the Microsoft Power Platform. As you consider your solution’s design, you need to understand the components and capabilities of the Microsoft Power Platform and how these control the design of your solution.

The Solution Architect is responsible for the overall high-level design of the data model for the solution. Understanding the capabilities of Microsoft Dataverse is imperative when designing the data model for the solution. This module addresses the trade offs for modeling data in Microsoft Power Platform solutions.

Analytics play a major role in solutions that are developed for Microsoft Power Platform. Analytics and insights can be delivered with Microsoft Power Platform in several different ways. The solution architect will need to evaluate the ways for implementing reporting and analytics in the solution. AI is becoming more important in enhancing the apps and data in business solutions. Accordingly, the solution architect will need to evaluate the options for using AI within Microsoft Power Platform solutions.

This module provides technical details around Power Apps but doesn’t discuss best practices because they consistently change in Microsoft Power Platform. A solution architect should always check the latest information for Power Apps.The main objective of this module is to ensure that solution architects learn how to decide which app type to use.

This module is about defining your environment structure, how you compose your solutions, your application lifecycle management (ALM) strategy, and then how to use Azure DevOps Build and Release pipelines.

The Solution Architect is responsible for the overall design of the solution. Understanding the capabilities of Power Automate is imperative when designing the automation for the solution. This module is concerned with Power Automate and its capabilities.

The Microsoft Power Platform has many different security features in environments, in data, and in application deployment. Security is a fundamental component in the design in a Microsoft Power Platform solution. Too often security requirements are ignored until later on in a project. By including security modeling in designing of the solution, the need for significant change late in a project can be avoided.

The solution architect leads the identification of integrations both in and out of the Microsoft Power Platform. The solution architect will guide how implementations are designed as part of the overall architecture. In this module, you will learn the different ways to integrate with the Microsoft Power Platform and the solution architect’s role in integration. You will learn about what is integration and why do we need it, Microsoft Power Platform features that enable integration, leveraging the capabilities of Azure.

Dynamics 365’s customer engagement applications are customer focused business first-party applications that are built on the Microsoft Power Platform. They are designed to help organizations more effectively engage their customers. The sales and marketing applications help identify sales prospects and turn them into long lasting relationships. The service focused applications help your organization service your customers, whether you have a call center, service center, or are providing service in the field. Dynamics 365 customer engagement applications ensure that you have the tools necessary to fully engage your customers across all aspects of your business. This module is all about choosing the right Dynamics 365 app and any particular issues with deploying the apps.

We now use multiple communications channels such as email, webchat, telephone, and platforms such as Slack, Teams, and Facebook. Organizations need to be able to contactable by their customers over these multiple channels and they need to respond consistently no matter which channel a customer decides to use. Users and customers are becoming more demanding, they require 24×7 response, responses that are tailored to their behaviors and characteristics, and to respond to more and more complex requests. Conversational AI is the use of AI powered agents, known as chatbots, to respond to human questions and requests in an intelligent way. Organizations use chatbots to provide the first line of response to customers, handling common enquiries across multiple channels. Chatbots instigate a conversational dialog with the human whether that is over the web or another channel such as the SMS text service.

This unit introduces Robotic Process Automation (RPA) and the use cases for Power Automate desktop flows.
There are many legacy applications that do not have a method for accessing their data or functionality except through their user interface. RPA solutions operate by generating a list of actions by capturing the steps a user performs in an application’s user interface. The RPA solution then performs the automation by repeating the steps in the application’s UI, effectively simulating the user’s actions in software. RPA enables the automation of applications that do not have an API that can be used for such automation tasks. Robotic Process Automation (RPA) is garnering a lot of interest and attention. By automating simple tasks, RPA solutions promise to lower costs while reducing errors.

A solution architect’s work continues after the system has been designed. Their next task is to ensure that the system is deployed and used by real users.