PL-600 : Microsoft Power Platform Solution Architect

Learning path 1: Becoming a Solution Architect

• What is a Solution Architect
• Role of a Solution Architect on projects
• Pillars of great architecture
• Getting to know your customer

Learning Path 2: Conceptualizing the design from requirements

• How to lead the requirement collection effort
• Using fit gap analysis
• Blueprinting the solution architecture

Learning Path 3: Implement project governance

• Discuss the Solution Architect’s role in project governance
• Discuss techniques for keeping a project on track
• Explore scenarios that could cause a project to fail

Learning Path 4: Microsoft Power Platform architecture

• Environments
• Understand how platform design and limits influence solution architectures
• Understand how to communicate with the customer on how the platform meets their needs

Learning Path 5: Model data for Power Platform solutions

• Data modeling influences
• Data modeling strategy
• Data types
• Data relationships

Learning Path 6: Evaluate Power Platform analytics and AI

• Planning and evaluating requirements
• Operational reporting
• Power BI
• Enterprise BI
• Pre-built insights and custom AI

Learning Path 7: Explore Power Apps Architecture

• Discuss options for apps and how to choose where to start
• Discuss app composition options
• Using components as part of your app architecture
• Considerations for including Power Pages in your architecture

Learning Path 8: Plan application lifecycle management

• Microsoft vision and Solution Architect’s role in ALM
• Environment strategies
• Defining a solution structure for your deliverable

Learning Path 9: Explore Power Automate Architecture

• Discuss options for automation and custom logic
• Review considerations for using triggers and common actions

Learning Path 10: Model security for Power Platform solutions

• Solution Architect’s role in security modeling
• Discovery and learning your client’s environment
• Controlling access to environments and resources
• Controlling access to Microsoft Dataverse data

Learning Path 11: Implement integrations with Power Platform

• Solution Architect’s role with integrations
• What is integration and why do we need it
• Platform features that enable integration
• Microsoft Dataverse event publishing

Learning Path 12: Explore Dynamics 365 applications architecture

• Solution Architect’s role when deploying Dynamics 365 apps
• Architecture considerations for each of the primary apps
  • Environments
  • ALM
  • Config data

Learning Path 13: Explore Power Virtual Agents

• Chatbot building options
• Best practices
• Integrate chatbots
• Power Virtual Agents in Microsoft Teams

Learning Path 14: Explore robotic process automation

• Review the need for robotic process automation
• Explore Power Automate Desktop
• Considerations for running desktop flows
• Process advisor

Learning Path 15: Testing and go-live

• Solution Architect’s role with testing and go live
• Planning for testing
• Planning for go live