Turn business intent into a secure, supportable Power Platform design. Start with an outcome, explore a design guide, and choose supporting skills and resources.
Choose a topic for a suggested sequence of design guides, Microsoft Learn articles, and tools.
A suggested path through design guides and resources, not a final solution design. Product choices, licensing, and organizational policy still need validation before implementation.
Answers stay in this page's memory and are not sent to a service or analytics. Reloading clears them.
These are portal-authored planning guides, not published skill names. Each connects a design decision to relevant skills, documentation, or an assessment.
Power CAT links open marketplace details and prerequisites, not a running skill. Review requirements and permissions before using a skill in a compatible host.
Solution blueprints, integration patterns, and Well-Architected design reviews.
Translate a business scenario into platform boundaries, components, integrations, and key decisions.
Bring goals, users, constraints, and systems. Aim for a component blueprint and decision log.
Supporting skillpowercat-pp-architecture-advisor supports discovery and architecture review for a composed Power Platform solution.
Plan Managed Environments, environment groups and inherited rules, maker routing, personal developer environments, and a deliberate reduction of default-environment use.
Bring the environment inventory, maker populations, business-unit and region boundaries, licensing constraints, current default-environment assets, data policies, and delivery model. Aim for a target topology, group-and-rule matrix, routing scope, exception path, default-environment reduction plan, and named owners.
Documentation-led guide
Use Managed Environments as the governance foundation. Group environments by purpose, business unit, project, or region; published group rules are inherited and cannot be overridden per environment. Use a separate group when a legitimate exception needs different rules. Route eligible makers to managed personal developer environments, and inventory, govern, migrate, quarantine, or retire default-environment assets according to business need. Confirm Managed Environments licensing before rollout.
Turn business concepts into tables, relationships, ownership choices, and a maintainable data model.
Bring entities, rules, and reporting needs. Aim for a logical model and implementation notes.
Supporting skilldv-metadata covers Dataverse tables, columns, relationships, forms, and views. Review environment permissions before applying changes.
Choose between canvas, model-driven, Power Pages, code app, or agent-led experiences.
Bring user context, tasks, devices, and access needs. Aim for a recommended experience pattern with tradeoffs.
Code app supporting skilldesign-guide turns brand assets, audience needs, and experience goals into reusable design tokens and implementation guidance. Use it after selecting a code app; use the architecture patterns for other experiences.
Match latency, volume, ownership, and failure needs to the right Power Platform integration pattern.
Bring source systems and service expectations. Aim for a pattern recommendation and documented tradeoffs.
Microsoft architecture guidance
Compare system boundaries, latency, volume, data-access options, ownership, and failure handling before selecting an integration pattern.
Map personas, responsibilities, records, and operations into least-privilege access decisions.
Bring personas, data sensitivity, and actions. Aim for an access matrix and a list of open security decisions.
Supporting skilldv-security covers Dataverse roles, users, business units, and access. It is not a security mapper for every Power Platform product; review permissions before changes.
Plan source control, solution boundaries, pipelines, approvals, and release responsibilities.
Bring team topology and release requirements. Aim for a delivery topology and agreed control points.
Product-specific supporting skillplan-alm covers solution boundaries, pipelines, and deployment topology for Power Pages. For other workloads, use the platform ALM guidance.
Challenge a proposed solution across reliability, security, operations, performance, and experience.
Bring the proposed design and known constraints. Aim for findings, risk priorities, and next actions.
Well-Architected assessment
Review the proposed design across reliability, security, operational excellence, performance efficiency, and experience optimization. Use the findings to prioritize next actions; the assessment supports structured review rather than automatic approval.
Combine design guides, supporting skills, and reference material. Keep decisions, assumptions, and evidence with the solution.
State the business result, users, boundaries, constraints, and measures of success.
Compare viable platform, data, experience, and integration choices using evidence.
Capture assumptions, consequences, and rejected options alongside the decision.
Run an independent design check and resolve material risks before delivery starts.
Choose a design topic for a guided resource sequence, or open Skills Mission Control for the current skill catalog.
