Microsoft PL-600 - Microsoft Power Platform Solution Architect

Scenario: Ensure that employees can sign in to all Microsoft apps by using one set of credentials per employee.

Synchronized identity. Synchronize on-premises directory objects with Microsoft 365 and manage your users on-premises. You can also synchronize passwords so that the users have the same password on-premises and in the cloud, but they will have to sign in again to use Microsoft 365.

Scenario: IT specialists want to design Power BI reports. They need to understand the underlying table relationships of the system.

Business process modeler (BPM) in Microsoft Dynamics Lifecycle Services (LCS) is a tool that you can use to create, view, and modify repeatable implementations that are based on business process libraries. BPM helps you align your business processes with industry-standard processes that are described by the American Productivity & Quality Center (APQC)

Business rule can create business recommendations based on business intelligence.

Scenario: Analytics and reporting

The solution must:

Provide metrics including existing and upcoming demand by inspection station, average time spent per user at a station, and average time a machine spends at each inspection point.

Provide metrics per inspector including number of inspections performed by month, and number of inspections per rating type (pass, fail).

Provide a printed quality certificate to be included with each machine.

Box 1: Schedule board

The Dynamics 365 Field Service schedule board provides an overview of resource availability and bookings you can make.

Box 2: Azure IoT Central connector

Information about each machine produced must be transferred to Dynamics 365 Field Service.

The difference between IoT hub and IoT central is that IoT is an application platform that simplifies the creation of Internet of Things solutions. IoT central helps to reduce the challenges of implementing IoT development, operations, and management. IoT Central is a fully managed Software as a Service solution.

Note: There are three ways you can use to connect IoT-enabled devices into the Field Service solution:

Connected Field Service for Azure IoT Central

Connected Field Service for Azure IoT Hub

Connected Field Service for non-Azure IoT providers using the extensible IoT provider framework

Microsoft Dynamics 365 Customer Service is a module for customer service automation that streamlines case and knowledge management, enables personalized customer service with a 360-degree customer view, and provides visibility into customer service department performance with dashboards and reports.

Box 1: Create a lookup to Dynamics 365 Field Service

Scenario: Machines are assigned serial numbers and placed in stock until they are shipped to customers.

Entity lookup: Allows technicians to choose a Dynamics 365 record. In the inspection designer interface, admins must select an entity and a field to display. For a chosen entity, the Name field and mandatory fields are the entity attributes that can be displayed in the lookup.

Box 2: Create a one-to-many relationship and set the behavior to Parental

Scenario: Inspection orders must:

Allow entry of quality ratings of passed or failed for each quality metric identified for the machine being rated.

Be automatically marked as failed if one inspection step rating is marked as failed.

Each inspection order can have one or many inspection steps, and each inspection step has a rating.

Note: Each pair of tables that are eligible to have a 1:N relationship can have multiple 1:N relationships between them. Yet usually only one of those relationships can be considered a parental table relationship.

A virtual table is a custom table in Microsoft Dataverse that has columns containing data from an external data source. Virtual tables appear in your app to users as regular table rows, but contain data that is sourced from an external database, such as an Azure SQL Database. Rows based on virtual tables are available in all clients including custom clients developed using the Dataverse web services.

Scenario:

First Up uses an on-premises system to manage current and historical patient data including medications and medical visits.

The company plans to reference historical data in the existing system. The records held in these systems will not be migrated to the new solution except for medication information.

The solution must provide a worker appointment booking system that can access worker historical job placement data.

First Up staff members must be able to view and update worker records. They must be able to see current and historical job placement data on the same form in the new solution.

Box 1: Omnichannel for Customer Service dashboard

Scenario: Workers must be able to communicate in near real-time with worker support agents.

The company has a team or worker support agents that respond to inquiries from current and prospective workers. Some of the worker support agents are multilingual.

If you choose to expand your customer service offering to provide chat and channels, the Customer Service workspace seamlessly adjusts to support managing conversations as well.

Note: As an agent with the Customer Service Representative security role, when you open Customer Service workspace, you start on the Customer Service Agent Dashboard unless your administrator has changed the default view. This dashboard shows you your active cases, cases you can work in queues you are assigned to, and your open activities. You can open existing cases and activities or begin working new cases from the queues you are assigned to and create activities.

Box 2: Dynamics 365 Customer Service

Scenario: First Up uses an on-premises system to manage current and historical patient data including medications and medical visits.

Box 1: Add users to Microsoft 365.

Scenario: Users cannot view Power BI reports within the Power Platform apps.

Issue: The people you share with may see a locked tile in a dashboard, or a "Permission required" message when they try to view a report.

Solution: You need to grant them permission to the underlying dataset.

Go to the All or the Datasets + dataflows tab in your content list.

Select More options (...) next to a dataset, then select Manage permissions.

Select Add user.

Enter the full email addresses for individuals, distribution groups, or security groups.

Select Grant access.

Box 2: Configure an on-premises data gateway.

Scenario: The company plans to reference historical data in the [on-premises] existing system. The records held in these systems will not be migrated to the new solution except for medication information.

The on-premises data gateway acts as a bridge to provide quick and secure data transfer between on-premises data (data that isn't in the cloud) and several Microsoft cloud services. These cloud services include Power BI, PowerApps, Power Automate, Azure Analysis Services, and Azure Logic Apps. By using a gateway, organizations can keep databases and other data sources on their on-premises networks, yet securely use that on-premises data in cloud services.

Scenario:

Audit teams must have the ability to view worker information on their mobile devices.

Audit teams must be able to record data during visits to locations where workers are placed.

When you create an app, or someone shares an app with you, you can run that app on the Power Apps mobile app or in a web browser.