In the Solution Blueprint Review Strategy section of the Implementation Portal, partners are currently required to respond to all subareas and related questions, regardless of whether they are relevant to the specific implementation. As a partner, we aim to deliver high-quality, context-driven SBR reviews. Being forced to comment on irrelevant subareas reduces clarity and adds time without adding value — especially in projects with focused workloads and tight timelines.

However, not all projects include every product, feature, or process covered in the full SBR structure. For example, a customer might only be implementing D365 Customer Service with chat and email, yet still be prompted to fill out strategy responses related to Field Service, Project Operations, or IoT scenarios.

Our proposed enhancement is to introduce an “Out of Scope” option for each subarea in the Strategy section.

This would:

• Let partners focus the workshop and the review report on what’s truly in scope
• Avoid unnecessary noise and reduce ambiguity in documentation
• Improve the accuracy and relevance of partner deliverables
• Provide clearer expectations for Microsoft reviewers, FastTrack, and the customer

(A filter or visual indicator (e.g., strikethrough or badge) for “Out of Scope” subareas could help readers scan the SBR output more efficiently.) 

Thanks in advance.