Update the certification assumption first

Microsoft retired the Power Platform Solution Architect Expert credential and PL-600 on 30 June 2026. New learners cannot use an old domain-weighted study plan as a current booking route. The architecture discipline remains useful. Use the historical guide as a skills reference, current product documentation for implementation and the live catalogue to choose any new credential.

Envision the outcome with the business

For a suggested scenario, a service company wants one process for enquiries, delivery and customer follow-up. Interview the fictional stakeholders and write success criteria, constraints and exclusions before naming components. Identify where the organisation needs a standard process and where differences are legitimate. A solution architect should challenge unnecessary customisation rather than accept every requested field as a fixed requirement.

Design data, integration and ownership together

Map the authoritative source for customers, orders and service activities. Decide where each update originates and how conflicts are resolved. Compare configuration, extensions and external services against the requirements. For an integration, specify authentication, validation, retry and reconciliation. A diagram containing every product logo is not an architecture if no one can explain who owns the data or how a failed handover is recovered.

Make non-functional requirements testable

Convert broad terms into measurable expectations: which users, what response behaviour, which operating hours, what recovery objective and what data access restrictions? Use illustrative values only when labelled as assumptions. Describe how you would validate them in a pilot. Include environment strategy, change control and support ownership so that the design can be operated after its original maker leaves.

Study the decision process rather than retired percentages

Organise continued learning around discovery, architecture and implementation governance. Write an architecture decision record for a choice between two plausible designs, including rejected alternatives and consequences. Discuss the case with developers and business users; their questions expose hidden assumptions. A retired exam’s domain percentages can describe its historical emphasis but should not be marketed as the scoring blueprint for a current assessment.

Choose the next route deliberately

A current AI architecture credential such as AB-100 may be relevant to some solution architects, but it has its own objectives and prerequisites and is not automatically equivalent to PL-600. Existing holders should preserve their accurate transcript status and show recent design evidence. Finish the portfolio with requirement traceability, risks, acceptance tests and an implementation handover. The transferable value is the ability to make a coherent, maintainable business design.

Choose a boundary for shared data

Two departments want separate applications over a shared customer record. Sketch data ownership, access requirements, environment strategy and integration responsibilities before recommending a platform arrangement. Test whether an apparently convenient shared component creates an unwanted dependency between release schedules. Explain the alternatives in an architecture decision record. This lets reviewers assess how you balance reuse, governance and maintainability rather than judging architecture by the number of services drawn on a diagram.

Official references

Certification requirements and programme terms can change. Use the issuer’s current page and your account to confirm details before applying or paying.