Introduction to Success by Design

One of the primary goals of the implementation guide is to democratize the practice of Success by Design by making it available to the entire community of Dynamics 365 implementers.

Microsoft created Success by Design, a framework and practice, to help project teams implement Dynamics 365.

Based on thousands of real-world customer projects, Success by Design is the sum of Microsoft's Dynamics 365 implementation experience. It offers topic-specific reviews and prescriptive guidance, including approaches and recommended practices, which provide a reliable path to project success. Dynamics 365 system integrators, independent software development companies, and customers can use Success by Design to better architect, build, test, and deploy Dynamics 365 solutions.

Microsoft recognizes that Success by Design doesn't guarantee implementation outcomes for customers. But it can help you achieve your project's goals while enabling the desired digital transformation for your organization.

For partners, Microsoft is confident that Success by Design, coupled with your implementation methodology and skilled resources, increases your team's effectiveness in delivering successful Dynamics 365 projects to your customers.

This article focuses on the fundamentals and practice of Success by Design and its desired result: Dynamics 365 projects whose technical and project risks are proactively addressed, solutions that are roadmap aligned, and project teams that are successful in maximizing their organization's investment in Dynamics 365 cloud services.

Success by Design history

As demand for Dynamics 365 cloud services increased across the enterprise, Microsoft identified the clear need to change the way it thought about evolving its services and its responsibility to customers and partners. Microsoft recognized that it wasn't enough to design a platform containing a set of features. The company needed to also understand what it takes to deliver a fully functioning, end-to-end solution that runs the mission-critical processes of its customers' businesses. This need led to the creation of Success by Design.

Microsoft believes that customer success is the precursor to every Dynamics 365 product development decision. As a result, questions fundamental to product development now challenge its engineers at every step of the process:

In what way must each product feature be delivered to ensure customer success?
How do we make Dynamics 365 apps valuable, durable, reliable, and performant?
Which features, customizations, or design choices should be improved, modernized, or optimized with AI to better support measurable customer outcomes?

Such questions led to the successful transition of 100 percent of Microsoft Dynamics 365 online customers to run on one version for the first time in decades. And there are more benefits, such as the following items:

A dependable and safe deployment process
A steady and coherent feature release cadence (including many overdue feature deprecations)
A reliable and performant platform that delivers customer value

But product is only one half of the customer success equation. Over the past few years, Microsoft has put equal emphasis on two needs that it must provide:

Prescriptive guidance and recommended practices to ensure a smooth implementation project
A properly designed and built Dynamics 365 solution that successfully transforms business operations

This push also resulted in the transformation of Microsoft's FastTrack for Dynamics 365 service. The goal is that the community of Dynamics 365 implementers, customers, and partners has access to Success by Design.

Make Success by Design your own

When Microsoft enables Dynamics 365 project teams to practice Success by Design, it means an ongoing commitment to provide the community of implementers, customers, and partners with best-in-class business applications, along with the latest in Success by Design project resources.

It also means project team willingness to incorporate the practice of Success by Design into their overall project approach, regardless of implementation methodology or the Dynamics 365 product being implemented. At its best, Success by Design fortifies a project team's chosen implementation methodology with a model for product-aligned project governance.

No matter where you find yourself in your Dynamics 365 implementation, it's critical that the project teams remain focused. The common pressures of time, budget, and resources can prevent the teams from pausing to understand and address technical and project risks before it's too late in the project lifecycle.

To this end, the sections in this article define the following items:

What Success by Design is
Which benefits it can bring to implementations
How project teams can use it to accelerate customer success throughout the implementation of Dynamics 365

Note

FastTrack for Dynamics 365 is a customer success program run by Microsoft's Dynamics 365 product engineering team that helps customers implement Dynamics 365 apps and realize business value faster. The practice of Success by Design is fundamental to FastTrack's approach, but the Success by Design framework is recommended for use on all Dynamics 365 implementation projects.

Success by Design objectives

Success by Design is agent-assisted prescriptive guidance (approaches and recommended practices) for successfully architecting, building, testing, and deploying AI-first Dynamics 365 and Power Platform solutions. Success by Design comes from the experience of Microsoft's FastTrack program, which has helped customers and partners deliver thousands of Microsoft's most complex Dynamics 365 cloud deployments. It's the sum of Microsoft's AI business solution implementation experience.

In Success by Design, reviews are exercises in reflection, discovery (observation), and alignment (matching to known patterns). Project teams can use reviews to assess whether their implementation project is following recommended patterns and practices. Reviews also help project teams to identify (and address) issues and risks that may derail the project.

Success by Design should be used as an adjunct to the project team's chosen implementation methodology for the following benefits:

Reduced risk due to early detection of problems
Alignment to recommended practices
Proactive guidance powered by AI-driven telemetry and autonomous agents

The result is a roadmap aligned solution architecture that is performant, scalable, and future-proof. (Acknowledging the possibility that feature deprecations or other changes to product roadmap in compliance with Microsoft policy may occur.)

For interested customers, Microsoft recommends that project leaders team up with their implementation partner to enable Success by Design within their project. In addition to the guidance that we provide here on Microsoft Learn, it's highly recommended that project teams ready themselves by enrolling in the Success by Design training.

Tip

Across Dynamics 365 guidance content, the term finance and operations apps covers Dynamics 365 Finance, Dynamics 365 Supply Chain Management, Dynamics 365 Commerce, Dynamics 365 Human Resources, and Dynamics 365 Project Operations.

Success by Design in the AI era

The rise of AI agents and autonomous systems is reshaping how implementation teams architect, deploy, and operate Dynamics 365 solutions. Success by Design is evolving to meet this new reality by embedding agentic principles into every phase of the implementation lifecycle.

From static reviews to a living solution blueprint

Traditionally, Success by Design relied on point-in-time Solution Blueprint Reviews: structured workshops conducted at discrete project milestones. In the AI era, this model is evolving toward a Living Solution Blueprint—a continuously refined view of the project that AI-driven telemetry, meeting transcripts, document artifacts, and autonomous agent analysis update.

Principle	From	To
Solution blueprint	Point-in-time review	Living, continuously refined blueprint
Workshops	Static, scheduled	Continuous, AI and data-driven updates
Guidance	Human-centric, manual	Dynamic recommendations from autonomous agents
Risk detection	Reactive, end-of-phase	Real-time, proactive throughout the lifecycle

Success by Design: Agentic Design Principles

Success by Design now includes Agentic design principles to support the unique demands of AI-first and agent-powered implementations. Key principles include:

Integrate agents: Treat agents as first-class components of the solution architecture, not add-ons.
Embrace agent-first experiences: Design business processes with agent-assisted and autonomous execution patterns in mind.
Model business processes for agents: Ensure process designs account for human-agent collaboration, exception handling, and escalation paths.

Important

Moving Success by Design to an agent-assisted model doesn't remove human accountability. Implementation teams remain responsible for validating agent outputs, defining agent scope and data access, and maintaining oversight throughout the project lifecycle.

AI adoption maturity

Organizations are at different points on their AI journey. Success by Design recognizes a spectrum of AI maturity stages that influence how you approach an implementation:

Level	Description
Level 1 – Human first	People perform tasks; AI isn't yet embedded in processes.
Level 2 – Copilot assisted	AI assists humans through Copilot suggestions and recommendations.
Level 3 – Humans with agents	Agents execute discrete tasks; humans direct and review outcomes.
Level 4 – Agent first with human oversight	Agents drive processes end-to-end; humans monitor and intervene when needed.

Understanding where your organization sits on this maturity curve helps your project team set realistic scope, governance requirements, and success criteria for AI capabilities in the implementation.

Built-in agents in Dynamics 365 apps

Dynamics 365 includes a growing set of agents built-in by Microsoft across all workloads, enabling implementation teams to deliver agent-powered solutions without building from scratch:

Workload	Example agents and Copilot capabilities
Sales	Sales Qualification Agent, Opportunity Research Agent, Sales Chat, Sales Agent, AI Powered Data Enrichment Agent, Sales Research Agent, Recommended Actions Agent
Customer Service	Customer Intent Agent, Case Management Agent, Customer Knowledge Management Agent
Field Service	Scheduling Operations Agent, Inspection Builder, Work Order Summary
Customer Insights	Proactive Engagement, Segmentation NL Query, Journey Copilot
Commerce	Store Operations Agent, Copilot POS Insights, Site Builder Copilot
Finance	Account Reconciliation Agent, Copilot for Finance
Supply Chain	Supplier Communications Agent, Sales Order Agent
Business Central	Sales Order Agent, Payables Agent

Organizations can also extend first-party agents or build custom agents using Microsoft Copilot Studio to address business-specific processes that drive high value and measurable outcomes.

Success by Design phases

Success by Design maps the Dynamics 365 implementation lifecycle into five methodology-agnostic phases: Discover, Initiate, Implement, Prepare, and Operate. This section outlines the Success by Design phases, their relationship to Success by Design reviews, and the desired outputs and outcomes.

Discover

In the Discover phase, the project team gathers and validates business requirements and finalizes the high-level solution approach. All implementations should have a well-rounded implementation strategy that delivers on the promise of digital transformation. This section also covers the environment strategy and the organizational strategy.

The Solution Blueprint Review (SBR) begins in the Discover phase. As the project team shapes the high-level solution approach and defines key workstreams, the SBR process should be initiated—not deferred to the Initiate phase. Starting the SBR in Discover allows the team to surface architectural risks and alignment gaps early, before design decisions become costly to reverse.

When planning an AI-first solution, include the following activities in the Discover phase:

AI use case prioritization: Identify which business processes have the highest potential value from agent automation or Copilot assistance.
AI maturity baseline and adoption constraints: Assess the organization's current AI maturity level, identify perceived and real barriers to AI adoption, and define mitigation actions in Discover with explicit follow-through in subsequent phases to drive sustained AI maturity.
Data readiness assessment: Evaluate data quality and governance gaps that could affect agent accuracy and reliability.
AI governance requirements: Identify regulatory, compliance, and responsible AI considerations that apply to the solution.

Initiate

In the Initiate phase, the project team defines all in-scope workstreams and updates the project plan to reflect these updates. When the project team produces the high-level solution design (in the Discover phase) and more or less defines the related project workstreams, Success by Design begins with the Solution Blueprint. For more information, see Success by Design reviews.

For AI-enabled implementations, address the following considerations in the Initiate phase:

Agent scope definition: Clearly define which agents are in scope, the processes they own, their boundaries, and escalation paths to human reviewers.
Responsible AI review: Ensure the solution design addresses fairness, transparency, privacy, and accountability for all AI components.
Human-in-the-loop design: Define where human oversight and approval are required in agent workflows.

Implement

In the Implement phase, the project team focuses on building the solution according to the agreed-upon solution design and scope. This phase introduces Implementation Reviews that come from the findings and recommendations of the Solution Blueprint. Implementation Reviews help you more deeply address questions related to the specific aspects of the solution design (data model, security, and integration) and implementation practices (ALM, testing strategy). Implementation Reviews are meant to fully address the risks identified during or after the Solution Blueprint Review but before the solution build is too far along.

When building AI-first solutions, include the following in the Implement phase:

Agent prototyping and evaluation (evals): Build and evaluate agent behavior against defined scenarios before integrating into core workflows. Evals should cover accuracy, coverage, safety, and latency.
Non-deterministic behavior management: Account for the non-deterministic nature of AI outputs in your testing strategy. Define acceptable thresholds and fallback paths.
Security and access control: Review data access scope granted to agents, ensure role-based access controls are applied, and audit agent permissions against the principle of least privilege.

Prepare

By the Prepare phase, the project team has built and tested the solution and is preparing for the final round of user acceptance testing (UAT) and training. Additionally, the project team has granted all necessary customer approvals, completed information security reviews, defined the cutover plan (including go/no-go criteria), scheduled mock go-lives, readied the support model, and completed the deployment runbook with tasks, owners, durations, and dependencies defined. At this point, the project team uses the Success by Design Go live Readiness Review to identify any remaining gaps or issues.

For AI-enabled solutions, Go-Live readiness should additionally confirm:

Pre-production validation: Agents are validated against production-representative data and scenarios, not just development or test datasets.
Responsible AI sign-off: Responsible AI review and residual risk acceptance are documented and approved by accountable business stakeholders.
Monitoring and observability readiness: Telemetry, logging, and alerting for agent outputs are in place before go-live.
Incident response plan: The support team understands how to detect, triage, and respond to agent behavioral anomalies post-deployment. For example, use telemetry queries to distinguish a single task failure from a broader pipeline stoppage.

Operate

In the Operate phase, the customer solution is live. The goal of this phase is stabilization and a shift in focus towards functionality and enhancements that are planned for the next phase of the project.

For AI-enabled solutions, the Operate phase must also include continuous evaluation:

Ongoing agent monitoring: Continuously monitor agent behavior, output quality, and usage patterns. Track fairness drift, unexpected outputs, or changes in model behavior after platform updates.
Telemetry-based health checks: Use platform telemetry to correlate agent performance with business outcomes. Use structured telemetry queries across scale units and time windows to distinguish isolated task failures from systemic pipeline issues.
Continuous evaluation: Establish a regular cadence for re-running evaluations against live agent behavior. Flag and investigate degradation in accuracy or safety scores.
Expansion roadmap: As agents demonstrate value and reliability, identify opportunities to extend agent scope, add new use cases, or upgrade to higher automation maturity levels.

Success by Design reviews

With a high-level understanding of Success by Design phases, you can now turn to Success by Design reviews, which are also sometimes referred to as Success by Design workshops.

Each review raises questions that serve as points of reflection that project teams can use to generate important discussion, assess risk, and confirm that best practices are being followed.

The Solution Blueprint Review serves as the starting point of Success by Design. Make the Solution Blueprint Review a mandatory review for the project because findings that come from it lead to Implementation Reviews. These reviews offer project teams the opportunity to drill down into topic-specific areas where deeper dives are deemed necessary for further understanding project and solution risk. Finally, the Go live Readiness Review, which is also a mandatory review, is the last stop for assessing any remaining risks before go live.

The following image illustrates that Success by Design reviews aren't abstract exercises separated from the project. Rather, the scheduling and implementation of each review relies on the availability of key project artifacts and the readiness of the project team to discuss them.

Note

In the AI era, Success by Design reviews evolve from static workshops to continuous, agent-assisted assessments. Organic discovery through project profiling, telemetry analysis, and meeting transcript processing allows recommendations to surface in real time—not just at scheduled review gates. This approach doesn't replace formal reviews; it enriches them with data-driven insights.

Success by Design outputs

After you gain a basic understanding of Success by Design's objectives, phases, and review flow, take a moment to understand the makeup of review outputs and their purpose, findings, and recommendations.

As described in the section Success by Design reviews, reviews include project artifacts that the project team produces, and other information such as formal or informal project touchpoints. The availability of such information points to the readiness of the team to schedule and conduct Success by Design reviews. Additionally, project teams might rely on Microsoft for telemetry and other tools to inform review discussions and generate review outputs.

The primary review outputs fall into two related categories: findings and recommendations.

Findings come in three types:

Assertions - Findings that capture noteworthy aspects of the solution or approach. Assertions highlight what the project team is doing right, typically in line with best practices.
Risks - Findings that could potentially influence the implementation negatively if not mitigated.
Issues - Findings that are currently impacting implementation negatively or will do so if not resolved.

Include as much detail as possible in findings and match them to known patterns. Findings matched to known patterns often yield insights that lead to recommendations or actions necessary to resolve the issues identified.

To better illustrate this point, consider this customer example:

A global corporate travel company is implementing Dynamics 365 Customer Service to drive its call center transformation. As the project team digs into the business's requirements, they learn that the Dynamics 365 solution must account for integration with multiple legacy systems (many with high transaction volumes). Additionally, the requirements point to a business-mandated customization that the project team agreed couldn't be achieved using out-of-the-box functionality.

In preparation for the Solution Blueprint Review, the project team parses these and other details. They must also confirm that solution performance testing was purposely left out of the project scope on the assumption that Microsoft's Dynamics 365 cloud service should be performant on its own.

Tip

It's true that Microsoft is responsible for delivering a reliable and performant cloud service to its customers. But it's our experience that solution design and the resulting configurations, customizations, and partner solutions to achieve that design might play a role in impacting overall Dynamics 365 solution performance.

In this example, the Dynamics 365 solution is projected to support 4,000 users at scale, including the multiple integrations and a key customization mandated by the business. So the project team's findings are clear: keeping solution performance testing out of scope is a risk that negatively impacts the project. Among other findings and recommendations not covered in this example, the project team's architect (who led the Solution Blueprint Review) recommends that the project Steering Committee approves adding solution performance testing into the test cycle.

The architect's findings are summarized as follows:

The solution requires custom development to meet its business requirements.
Performance testing isn't included in the test cycle.
Following best practices, solution performance testing should be added to the test cycle.

If necessary, the solution performance workshop should be scheduled to further explore the risk and report any other findings back to the project Steering Committee.

The architect's findings and recommendations are based on careful review that calls out the lack of solution performance testing as a risk, which the project team must address to avoid downstream impact on the project.

In Success by Design, findings link observations to known patterns that invite actions necessary to address project risks and issues.

Track success measures

One more step remains in the Success by Design process: tracking success measures. After completing Success by Design training, you might decide to create your own success measure tracking template or use FastTrack's template. Otherwise, project teams can use Success by Design tooling (as served by FastTrack or your implementation partner) to track success measures for their project.

What are success measures?

By its very nature, Success by Design is a project specific endeavor. For anyone practicing Success by Design across one or many Dynamics 365 projects, the question arises: How do we measure the health of just one of those many projects? Success measures allow us to do just that.

Success by Design empowers project teams to track the health of projects across seven categories and over 30 success measures. The following figure highlights these categories and related success measures.

Tracking success measures is simple: After a Success by Design review or other compelling project event, your FastTrack Solution Architect or partner architect accesses Microsoft's Success by Design tooling and updates the relevant success measures for the project. Success measure updates are red, yellow, or green, and include project-related details relevant to the success measure.

Why are success measures important?

Success measures are important because they provide access to micro and macro project health trends. Tracking success measures for a single project allows stakeholders to assess the overall health of the project at a glance. Similarly, the benefit of tracking success measures over 10, 20, or 100 projects is that Microsoft, the partner, or the customer project team can see patterns that might be impacting them. For example, macro-level tracking might yield an application lifecycle management (ALM) problem. Access to this data allows Microsoft or the partner to understand whether it's a project or product problem, and gain insights on how to fix it.

Success measures for AI-enabled solutions

AI-first implementations require additional success measures beyond traditional project health indicators. When your solution includes agents or Copilot capabilities, track the following supplementary categories:

Category	Example measures
Agent readiness	Agent scope defined, responsible AI sign-off completed, human escalation paths validated
Evaluation quality	Eval pass rate, accuracy threshold met, safety violations at zero
Operational health	Agent uptime, average handle time, escalation rate to human agents
Business impact	Process cycle time reduction, user adoption rate, cost per transaction
Responsible AI	Fairness drift indicators, audit log completeness, governance review cadence

Telemetry-based monitoring is central to tracking AI solution health in production. Teams should establish structured queries against platform telemetry to monitor pipeline continuity, detect anomalies, and correlate individual task failures with broader business impact—before escalating concerns to engineering.

Conclusion

Success by Design equips project teams with a model for technical and project governance that invites questions and reflection, which leads to critical understanding of risks that might otherwise go unnoticed until too late in the project.

Considering the pace of cloud solutions and the investment that organizations make in Dynamics 365 software and implementation costs, even the most experienced customers and partners with the best methodologies benefit by incorporating Success by Design into their projects.

As AI agents and autonomous systems become integral to business operations, the stakes for getting implementations right have never been higher. Success by Design evolves with this reality—from point-in-time reviews to a living, agent-assisted guidance model that proactively detects risk, continuously measures solution health, and empowers teams to navigate the journey to AI-first operations with confidence.

The path to what Microsoft calls the Frontier Firm—an organization that is AI-enabled, agent-empowered, and continuously improving—runs through disciplined implementation. Success by Design is the framework that makes that journey predictable and successful.

Microsoft believes that every organization is in the business of creating great customer experiences. To achieve that goal, business applications must do more than just separately run your back office, marketing, supply chain, or even field operations. They must give you the agility to remove every barrier in your way. When this happens, business applications become more than just operational solutions. They become resilient solutions that enable the digital feedback loop and adapt to customer demands, delivering stronger, more engaging experiences around the products you make and services you provide.

Success by Design evolution

From the moment that FastTrack for Dynamics 365 was born, Microsoft began to ask itself: How can we change the FastTrack approach so that our solution architects can address technical and project risks of a project before they manifest as problems impacting our customer's investment in Dynamics 365? Our internal process evolves, team members learn and share their knowledge, and Success by Design evolves over time. Get an inside look into how we developed the Success by Design framework. Otherwise, check the links in the next section.

Next steps

Comentarios

¿Le ha resultado útil esta página?

Last updated on 2026-06-23