A Power Platform solution architect turns business needs into an end-to-end design that can be built, secured, operated and changed. The role is not simply a senior maker with a different title.
One major update changes the career advice in the old article: Microsoft retired the Power Platform Solution Architect Expert certification and PL-600 renewal route on 30 June 2026. You can no longer earn or renew it.
What the architect is accountable for
Microsoft's retired certification page still gives a useful description of the work: facilitate decisions across development, configuration, integration, infrastructure, security, licensing, storage and change management.
In practice, the architect should produce evidence such as:
- a problem statement and measurable acceptance criteria
- system context and data-flow diagrams
- environment and application lifecycle management strategy
- identity, role and permission model
- integration contracts and failure handling
- data classification, retention and audit decisions
- capacity, licensing and support assumptions
- test, cutover, rollback and operational ownership plans
The design is not finished when the app works in a demo environment.
The skills that matter
Discovery
Separate the requested feature from the underlying job. Map users, exceptions, volumes, sensitive data and the current source of truth.
Platform choice
Know when to use Dataverse, SharePoint, SQL, Azure services or an existing line-of-business system. Power Platform is part of the architecture, not automatically the whole architecture.
Security and governance
Design least-privilege access, environment boundaries, data policies, connection ownership and auditability. Microsoft's Power Platform Well-Architected guidance provides a current framework for reliability, security, operational excellence, performance efficiency and experience optimisation.
Application lifecycle management
Use solutions, source control, environment variables, connection references and deployment pipelines appropriate to the organisation. Define who can approve and roll back a release.
Communication
Record decisions in language that makers, administrators, security reviewers and business owners can challenge. Architecture hidden in one person's head is not architecture the organisation can operate.
What replaces PL-600?
Microsoft's retirement notice confirms what ended, but the old certification page does not name a direct one-for-one replacement. Do not advertise a successor unless Microsoft publishes one.
For now, build a role-relevant evidence portfolio:
- an anonymised end-to-end design
- a security and data decision record
- an ALM and recovery plan
- a trade-off where you rejected Power Platform for part of the solution
- proof that the implemented system met agreed tests
Existing credentials can still be listed with their earned dates, but do not imply that the retired certification is currently available.
A practical development path
Start by owning small solution designs, not by memorising every product feature. Ask an experienced architect to review your assumptions. Sit with support teams after launch. The failures you observe there will improve your next design more than another perfect demo.
If you are moving from maker to architect and want to test a real design decision, join Power Automate Builders.