MB-700: Microsoft Dynamics 365: Finance and Operations Apps Solution Architect Training

• Define skill areas for solution architect role
• Explain instances & deployment models recommendations by Microsoft
• Understand cloud solution, CDM & CDS
• Get more info on Licensing, AppSource & Support for Dynamics 365
• Use Lifecycle services as solution architect
• Know the considerations for blueprinting Dynamics 365 solution
• Understand the concepts and tools used for data management
• Explain the Integration options & Business events on solutions
• Know the available options on solution localization, compliance & reporting
• Have architectural conversations on extensibility, security, & performance
• Know what is ALM application lifecycle management
• Identify opportunities for automated testing and using RSAT

• Recorded Videos After Training
• Digital Learning Material
• Course Completion Certificate
• 24x7 After Training Support

• Professional who want to be solution architect and work on Microsoft Dynamics Projects
• Solution Architects with knowledge and experience spanning business needs and product capabilities.

• Participants should have some functional or technical experience in Microsoft Dynamics 365 Finance and Operations.

• Multisoft Systems will provide training certification after completion of MB-700: Microsoft Dynamics 365: Finance and Operations Apps Solution Architect Online Certification Training Course.

Module 1. Architect solutions 

1. Gather requirements

• identify operational and organizational challenges that may affect a business
• identify existing business processes and opportunities to optimize business processes
• gather information about expected transaction volume
• categorize business requirements and perform gap fit analyses
• review and validate business requirements throughout the solution lifecycle

1. Define the solution architecture

• map business requirements to functional components
• evaluate whether to build versus buy for selected business requirements
• identify opportunities to integrate other Microsoft technologies
• select the appropriate implementation tools including LCS and Azure DevOps
• describe the Success by Design process
• create solution architecture diagrams

1. Describe and document the solution blueprint

• define an organization including company information, locations, and structure
• document the implementation timeline including roll-out strategies
• define the business process catalog and document solution gaps
• define instances, environments, and solution components
• develop a disaster recovery strategy
• identify required security roles

Module 2. Define solution strategies

1. Select a deployment strategy

• develop a process to manage solution code and deployment
• select a deployment model and identify instances and environments required for the selected deployment model
• describe the One Version strategy for Dynamics 365 and the effects of One Version on solutions
• 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

1. 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

1. Determine a data management strategy

• differentiate between transactional and historical 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 and data retention plans

1. Define the security architecture

• differentiate between Azure, Dynamics 365, and infrastructure security
• describe Azure and infrastructure security-related elements
• describe use cases for and capabilities of record-level and role-based security in Dynamics 365

1. Define the integration architecture

• select an integration pattern including OData, Microsoft Power Platform, Batch Data API, Azure Data Lake, Business events, and Dual-write
• identify required integration and interface details
• design integrations
• define an integration testing strategy

1. Define the business intelligence and reporting architecture

• gather business intelligence and reporting requirements
• 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 Print management, Document Routing Agent (DRA), modern report design layout templates, check printing, and label printing

Module 3. Manage implementations

1. Describe Lifecycle Services (LCS) tools

• understand the use cases and capabilities of different LCS tools
• understand the use cases and capabilities Business Process Modeler (BPM)
• understand the use cases and capabilities LCS Methodologies
• create a usage profile to describe current or projected usage

1. Manage interactions with FastTrack    

• identify the value proposition for FastTrack
• identify FastTrack engagement types and personnel roles
• describe typical types of FastTrack workshops and the inputs for each workshop
• describe go-live checklist elements

1. 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 LCS Support tool    

1. 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

Module 4. Manage testing

1. Define 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, and other tools

1. 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