PL-600: Microsoft Power Platform Solution Architect-Apr 2025

Skills at a glance

• Perform solution envisioning and requirement analysis (45–50%)

• Architect a solution (35–40%)

• Implement the solution (15–20%)

Perform solution envisioning and requirement analysis (45–50%)

Initiate solution planning

• Evaluate business requirements

• Identify Microsoft Power Platform solution components

• Identify and select components from existing apps, Microsoft Dynamics 365 apps, AppSource apps, Azure, third-party components, and independent software vendors (ISVs)

• Identify and estimate migration and integration efforts and alternatives

Identify organization information and metrics

• Guide the process of collecting the current state business processes

• Assess an organization’s risk factors

• Review key success criteria

Identify existing solutions and systems

• Evaluate an organization’s enterprise architecture

• Identify data sources needed for a solution

• Define use cases and quality standards for existing data

Capture requirements

• Refine high-level requirements

• Identify functional requirements

• Identify non-functional requirements

• Guide the process of designing and improving the future state business processes

Perform fit/gap analyses

• Determine the feasibility of meeting specific requirements

• Evaluate Dynamics 365 apps and AppSource options to solve requirements

• Address functional gaps through alternate solutions

• Determine the scope for a solution

Architect a solution (35–40%)

Lead the design process

• Design the solution topology

• Identify customization approach for existing apps

• Design and validate user experience prototypes

• Identify opportunities for component reuse

• Communicate system design visually

• Design a data migration strategy

• Design apps by grouping required features based on role or task

• Design a data visualization strategy

• Design an automation strategy

• Design environment strategy

Design the data model

• Design relationships and relationship behaviors

• Determine when to connect to external data versus import data

• Design data models to address complex sets of requirements

Design integrations

• Design collaboration suite integration including Microsoft Teams and SharePoint

• Design integrations between Microsoft Power Platform solutions and Dynamics 365 apps

• Design integrations with an organization’s existing systems

• Design third-party integrations

• Design an authentication strategy

• Design a business continuity strategy

• Design robotic process automation (RPA)

• Assess possibilities of networking to support integrations

Design the security model

• Design the business unit and team structure

• Design security roles

• Design column and row level security

• Design security models to address complex sets of requirements

• Determine security model management policies and processes

• Identify Microsoft Entra ID groups and app registrations required to support a solution

• Identify data loss prevention (DLP) policies for a solution

• Determine how external users will access a solution

Implement the solution (15–20%)

Validate the solution design

• Evaluate detailed designs and implementation

• Review the security across the solution including business rules, user roles, Entra ID requirements and security boundaries

• Ensure that the solution conforms to API limits

• Assess the solution performance and impact on resources

• Resolve automation conflicts

• Resolve integration conflicts

Support go-live

• Identify and resolve potential and actual performance issues

• Escalate and provide options to resolve data migration issues

• Resolve any identified issues with deployment plans

• Identify factors that impact go-live readiness and remediate issues

Enroll Now