1. What is the FTRSA Program?

The FastTrack Recognized Solution Architect (FTRSA) program honors solution architects who consistently deliver high-impact solutions using Microsoft Dynamics 365 and Power Platform. Launched in 2019, it recognizes technical excellence, customer success, and architectural leadership across Microsoft’s services ecosystem.

2. Who is eligible to apply?

See detailed requirements listed in the respective product(s) nomination pages.

3. What benefits do FTRSAs receive?

  • Benefits may include:
    • Credly badge and public recognition
    • Profile on the FTRSA website
    • Access to product previews and feedback loops
    • Invitations to exclusive Microsoft programs and events
    • Ask Me Anything (AMA) sessions and community engagement opportunities

4. How long is the recognition valid for?

Each nomination cycle will award candidates with the designation of FastTrack Recognized Solution Architect for one fiscal year and candidates will need to be apply for renewal every year.

5. How do I submit a nomination?

  • Candidates can submit their nomination using the links below:
  • The FY27 nomination window runs October 1, 2026 - February 15, 2027.
  • Supporting documents must follow the format outlined in the nomination form. Failure to adhere to the format may result in exclusion from the vetting process.

6. Can I renew my FTRSA status?

  • Yes. Renewals must submit the nomination form and meet requirements to be considered for the award in the next fiscal year.
  • Renewals do not require interviews if minimum requirements are met.

7. What is the evaluation process?

  • The process includes:
    • Eligibility validation
    • Interviews (for new nominees only)
    • Final review and award coordination

8. How do I submit my peer and field validation?

  • Your endorser emails their endorsement directly to FastTrackRecognized@microsoft.com and puts you on CC, so that you can see it was sent.
  • The endorsement must come from a named Microsoft FastTrack or CAT team member, or from a currently recognized FTRSA. Self-endorsement is not accepted.
  • Send the endorsement before the nomination window closes. You can upload a screenshot of the sent email on the nomination form, but the emailed endorsement is what is assessed.
  • If your endorsement relates to work covered by an NDA, ask your endorser to describe the engagement in the email rather than attaching customer material to the form.

9. Who can I contact for help?

For questions or clarification, email the FTRSA team at FastTrackRecognized@microsoft.com.

10. I’m a renewing FTRSA. Do I have to meet all the requirements?

Net new and renewing FTRSAs have to meet all the requirements to be eligible for the award.

Certification

11. Which certification do I need to nominate for FY27?

An active AB-100 — or an existing PL-600 or MB-700, which was active before June 30th, 2026. Active is measured at nomination open, 1 October 2026.

12. What happens to PL-600 and MB-700 holders after June 30th 2026?

The two certifications have been retired effective June 30th, 2026. Holders keep the credential on transcript till the expiration date but cannot renew it.

13. How do I achieve the Solution Architect certification?

14. What should I submit as proof of certification?

Nominees can submit a screenshot of the certificate they received on clearing the exam, or a screenshot of their Microsoft Learn transcript with their name and the relevant certification clearly visible.

AI and Agentic Design

15. What exactly do I have to submit?

One agentic reference architecture you authored and implemented, for a real customer scenario delivered within 18 months or for your organisation’s internal processes, along with a business value case study. The architecture needs to follow the published reference architecture guidelines — use the Dynamics 365 reference architecture template or the Power Platform reference architecture template.

The submission can be a PowerPoint presentation or a Word document that follows this structure:

  • The actual reference architecture (a link to the article in the case of published work)
  • The before and after view of the implementation
  • A case study of the implementation
  • (Optional) a short video walkthrough of the above details

16. Does the agentic reference architecture have to be published to qualify?

The reference architecture and supporting case study do not have to be published. NDA work is accepted. For non-published, NDA work, please clearly indicate so in the submission.

17. What should the case study showcase?

The case study should cover the following details:

  • How did you get to this design?
  • Why was this implemented?
  • A business value case on the design.
  • Any cost savings.

Delivery and outcomes

18. What counts as delivery evidence?

Any one of the following:

  • A published customer story along with a customer endorsement, covering scope, the nominee’s role and one or more outcome metric; or
  • A case study on Microsoft Learn in the Power Platform and/or Dynamics 365 guidance hub; or
  • An up-to-date Implementation Portal engagement.

19. I have a Dynamics 365 project on the Implementation Portal. Which framework do I have to follow?

All Dynamics 365 engagements must follow the Success by Design framework.

20. I have a Power Platform project on the Implementation Portal. Which framework do I have to follow?

All Power Platform engagements must follow the Power Platform Well-Architected framework.

21. My engagement is on the Implementation Portal. How do I reference it for my nomination?

Nominees can submit the following from their project(s) on the Implementation Portal:

  • Implementation Portal Project ID: [ID]
  • Project name: [Project name]
  • Customer/organization: [Customer]
  • Implementation Portal LCS ID (Finance & Operations projects): [ID]

22. How can I submit a customer success story for publication?

You can submit a story for publication on the Microsoft customer stories portal — see Partners, nominate your customers for a success story. Questions can go to CXGTStoryNomination@service.microsoft.com.

We also accept partner success stories submitted through Explore Microsoft Partner Success Stories.

23. I have a customer story posted to my partner organization website. Will that suffice?

Customer success stories published on non-Microsoft managed channels are accepted, provided that they are supplemented by a customer endorsement from the customer mentioned in the story. The endorsement should reference the project’s scope, the nominee’s role, and one or more outcome metrics.

24. How should I format my submission against this category?

Please create a PDF or PowerPoint presentation which includes the preferred proof, along with a screenshot of the customer reference that was sent to FastTrackRecognized@microsoft.com with you on CC.

You can include the link to any published material(s) you want to showcase within the PDF or PowerPoint presentation.

Reusable IP and leadership

25. What counts as a qualifying asset for this category?

A publicly accessible URL naming you as the author or co-author of any of the following will suffice as proof:

Peer and field validation

26. Who is eligible to endorse my FTRSA nomination?

  • Renewing FTRSAs require an endorsement from a Microsoft FastTrack / CAT team member.
  • Net-new FTRSAs require an endorsement from a Microsoft FastTrack / CAT team member or an existing FTRSA.

27. Where do I need to send the endorsement?

Candidates can have the endorsement sent to FastTrackRecognized@microsoft.com with themselves on CC.

For the nomination form, please attach a screenshot of the email that shows the sender, the above email, you on CC, and the endorsement email itself.