MB-700 Retired: What Replaced It and What Carries Over

MB-700

Retired exam

MB-700 was retired on June 30, 2026

Microsoft retired MB-700 and the Finance and Operations Apps Solution Architect Expert certification on June 30, 2026. Microsoft lists AB-100 as a collective replacement for MB-700 and several other retired business application credentials.

Explore the broader replacement path AB-100: Agentic AI Business Solutions Architect

Historical MB-700 Scope

MB-700 was Microsoft's Microsoft Dynamics 365: Finance and Operations Apps Solution Architect exam until its retirement on 2026-06-30. Its final published scope covered Architect solutions, Define solution strategies, Manage implementations, Manage testing. This page preserves that dated outline for historical comparison and curriculum cleanup. It is not a schedulable exam, and its prices, delivery details, registration links, and practice calls to action must not be used for a new certification plan.

Who MB-700 Was For

Nobody should start a new certification plan around MB-700. This page serves former candidates, credential holders, training teams removing stale material, and practitioners deciding whether prior preparation is reusable for AB-100. New candidates should verify the active Microsoft page and current dated study guide before booking.

Skills You Should Be Ready to Demonstrate

How to Reuse Your Preparation

Do not rename an old MB-700 checklist or question bank as AB-100. Compare the two official guides objective by objective and classify each historical skill as transferable, changed, or absent. Use transferable experience as a diagnostic baseline, then rebuild labs and review around AB-100's current domain weights, products, role expectations, security controls, and operational tasks. Because Microsoft identifies AB-100 as the broader replacement path, review the skill map below before assuming equivalence.

What changed from MB-700 to AB-100

Historical MB-700Current AB-100Practical impact
Architect solutions
25-30%
Design AI-powered business solutions
25-30%
Architecture judgment transfers, while AB-100 adds agentic patterns, model choices, orchestration, grounding, and AI-specific controls.
Define solution strategies
45-50%
Plan AI-powered business solutions
25-30%
Strategic discovery remains important but is reframed around AI value, readiness, responsible use, data, and adoption.
Manage implementations and testing
25-35% combined
Deploy AI-powered business solutions
40-45%
The replacement increases deployment weight and adds evaluation, observability, governance, security, and lifecycle management for agents.

Migration checklist

  1. Stop scheduling, selling, or presenting MB-700 as a current exam.
  2. Compare completed MB-700 preparation with the current AB-100 guide; do not carry over obsolete weighting or mechanics.
  3. Create a fresh AB-100 plan around its current domains and hands-on role expectations.
  4. Remove or quarantine practice content that cannot be mapped to a current objective with source evidence.
  5. Recheck Microsoft's dated AB-100 study guide before booking because role-based exams change over time.

Open the official AB-100 study guide

Historical Domain Guide

Architect solutions: Historical Scope

Historically, Architect solutions required candidates to connect configuration choices with operational outcomes. The official outline included Gather requirements; Define the solution architecture. Preserve hands-on understanding of those tasks where the successor comparison shows overlap, but do not treat this retired weighting or terminology as a current exam blueprint.

Define solution strategies: Historical Scope

Historically, Define solution strategies required candidates to connect configuration choices with operational outcomes. The official outline included Select a deployment strategy. Preserve hands-on understanding of those tasks where the successor comparison shows overlap, but do not treat this retired weighting or terminology as a current exam blueprint.

Manage implementations: Historical Scope

Historically, Manage implementations required candidates to connect configuration choices with operational outcomes. The official outline included Manage interactions with FastTrack. Preserve hands-on understanding of those tasks where the successor comparison shows overlap, but do not treat this retired weighting or terminology as a current exam blueprint.

Manage testing: Historical Scope

Historically, Manage testing required candidates to connect configuration choices with operational outcomes. The official outline included Define a testing strategy. Preserve hands-on understanding of those tasks where the successor comparison shows overlap, but do not treat this retired weighting or terminology as a current exam blueprint.

How this page was made

Cert Atlas compared Microsoft's final MB-700 study guide with the current AB-100 guide at the domain and objective level, then checked Microsoft's retirement list and transition announcement. OpenAI Codex assisted with extraction, normalization, comparison, and drafting. Claims were reviewed against the linked official sources; no exam stems, answers, choices, or explanations were used.

Historical MB-700 Domains

Architect solutions Architect solutions 25-30%
  • Gather requirementsGather requirements
    Identify operational and organizational challenges that may affect a business; Identify existing business processes and opportunities to optimize business processes; Gather data migration requirements and expected data migration volumes; Categorize business requirements and perform gap fit analyses; Review and validate business requirements throughout the solution lifecycle
  • Define the solution architectureDefine the solution architecture
    Map business requirements to functional components and business process catalog; Evaluate whether to build versus buy for gap business requirements; Identify solution components including other Microsoft and independent software vendor (ISV) technologies based on customer requirements; Describe the Success by Design framework; Create overall solution architecture diagrams; Describe and document the solution blueprint; Review an organization including company information, locations, and organizational hierarchy in finance and operations apps; Document the implementation timeline including roll-out strategies; Define the business process catalog and document solution gaps; Define instances, environments, and solution components; Identify required security strategy
Define solution strategies Define solution strategies 45-50%
  • Select a deployment strategySelect a deployment strategy
    Review a process to manage solution code and deployment; Select a deployment model and identify instances and environments required for the selected deployment model; Plan the One Version strategy and release process for service updates; Segment solution development and delivery into logical phases; Provide alternative methodologies and approaches for deploying modifications; Determine solution maintenance cadence and timelines; Identify upgrade scenarios and select appropriate tools; Define an application lifecycle management (ALM) strategy; Define a code management and data flow strategy; Define a Microsoft Power Platform solution management strategy; Determine which build automation capabilities to implement; Define a roll-back strategy for solution code and data; Determine a data management strategy; Differentiate between transactional, historical, and master data; Define data quality and data validation process; Define data cleansing and transformation strategies; Define data dependencies; Develop a data migration strategy for master, transactional, reference, parameter, and document data entities; Develop data cut-over, verification and data retention plans; Define the security architecture; Differentiate between Azure, finance and operations apps, and infrastructure security; Describe Azure and infrastructure security-related elements; Review security design and performance implications of record-level security in Dynamics 365; Review security design and license implications of custom and standard role-based security in Dynamics 365; Identify use cases for segregation of duties; Define the integration architecture; Select an integration pattern including OData, Microsoft Power Platform, Batch Data API, custom services, external web services, office integrations, business events, Azure Synapse Link, and dual-write with Microsoft Dynamics 365 apps; Identify required integration and interface details; Design integrations; Define an integration testing strategy; Define error handling and troubleshooting strategy for integrations; Define use cases for integration requirements with Microsoft Power Platform and finance and operations apps; Define the business intelligence and reporting architecture; Define data sources required to meet business intelligence and reporting requirements; Select appropriate business intelligence and reporting tools including Power BI, organizational workspaces, financial reports, SQL Server Reporting Services (SSRS), and the Electronic Reporting tool; Define printing requirements including, Document Routing Agent (DRA), modern report design layout templates, check printing, and label printing
Manage implementations Manage implementations 10-15%
  • Manage interactions with FastTrackManage interactions with FastTrack
    Identify the requirements for FastTrack eligibility; Identify FastTrack engagement types and personnel roles; Describe typical types of FastTrack workshops and the inputs for each workshop across the phases; Describe go-live checklist elements; Utilize Dynamics 365 Implementation Portal; Determine support options; Develop a support plan and strategy; Define post-go-live support plans including response times and service-level agreements (SLAs); Describe use cases and capabilities for the Power Platform Admin Center Support tool; Determine licensing requirements; Determine the types of licenses required; Estimate the number of licenses required by using the License Sizing estimator; Describe the process for estimating ongoing software licensing costs
Manage testing Manage testing 15-20%
  • Define a testing strategyDefine a testing strategy
    Define a testing strategy that includes all required types of testing; Define a regression testing strategy; Identify opportunities for automated testing; Review use cases and test coverage for business scenarios; Determine when to use RSAT, SysTest, Postman, ATL, Azure DevOps Test Plans, Leapworks, and other tools; Define a performance testing strategy; Define performance goals and requirements; Identify performance monitoring and testing tools; Define performance benchmarks and success criteria; Design a performance and load testing strategy; Troubleshoot performance issues