E-commerce sales orders: Azure Logic Apps is the standard integration tool for connecting external e-commerce platforms to Dynamics 365, enabling automated workflow orchestration and data synchronization.

Vendor purchase orders: Electronic Data Interchange (EDI) is the industry-standard protocol for the computer-to-computer exchange of business documents (like POs) between vendors and partners in a structured format.

User2's issue: This refers to the manual entry of paper or PDF invoices. Optical Character Recognition (OCR) is the specific technology used to automate data extraction from these physical or digital documents into Dynamics 365

Microsoft Learn: "Choose an integration strategy for Dynamics 365 Finance and Operations apps" (Logic Apps for asynchronous integration).

Microsoft Learn: "Supply Chain Management - EDI overview" (Electronic Data Interchange for B2B procurement).

Microsoft Learn: "Vendor invoice automation - OCR integration" (Using OCR to eliminate manual entry of vendor invoices).

IEEE Xplore: "Automated Data Capture for ERP Systems using OCR Technologies," https://doi.org/10.1109/ICIM52187.2021.9397034

The solution correctly meets the goal. Azure Active Directory (Azure AD) Conditional Access policies are the designated tool for enforcing granular access control to applications integrated with Azure AD, such as Dynamics 365 Finance and Operations. These policies can be configured to require specific conditions to be met before access is granted. The two requirements, mandating company-managed devices and enforcing multi-factor authentication (MFA) for administrative roles, are standard use cases for Conditional Access policies. A policy can be set to grant access only from compliant or hybrid Azure AD-joined devices, and another policy can be targeted at users with administrative roles to require MFA.

B. No: This is incorrect. Azure AD Conditional Access is the specific Microsoft technology designed to implement the exact security controls described in the requirements for cloud applications like Dynamics 365.

1. Microsoft Learn: What is Conditional Access in Azure Active Directory?

Reference: This document provides the foundational concept. It states, "Conditional Access policies... allow you to enforce controls on the access to apps in your environment, all based on specific conditions." This confirms it is the correct tool for the scenario.

2. Microsoft Learn: Conditional Access: Conditions

Reference: Under the "Device state" section, the documentation explains that policies can be configured to "require a device to be marked as compliant" or "require a hybrid Azure AD joined device." This directly addresses the requirement for using company-managed devices.

3. Microsoft Learn: Conditional Access: Grant

Reference: This document lists "Require multi-factor authentication" as a primary access control that can be enforced by a Conditional Access policy. This directly addresses the MFA requirement for administrators.

4. Microsoft Learn: Common Conditional Access policies

Reference: This page provides templates for common security scenarios, including "Requiring MFA for administrators" and "Requiring a compliant or hybrid Azure AD joined device for all users." This validates that the proposed solution aligns with Microsoft's recommended security practices.

The question asks for the tool to migrate master data and opening balances during an upgrade from AX 2012 R3 to Dynamics 365 Finance. The official path for this is the upgrade process managed through Lifecycle Services (LCS). This process includes a specific "Data upgrade" step which utilizes a data upgrade toolset (in the form of a deployable package) to migrate the entire AX 2012 database to the Dynamics 365 online environment. Although the scenario mentions a selective migration (master data and opening balances), which is more characteristic of a reimplementation using the Data Management Framework, among the choices provided, the "Data upgrade tool" is the only option designed for moving data from AX 2012 to Dynamics 365 as part of an upgrade project.

B. Business process modeler: This LCS tool is used to define, view, and manage business process hierarchies and workflows for an implementation; it is not a data migration tool.

C. Usage profiler: This is a data-gathering tool within AX 2012 that captures system usage metrics to help with infrastructure sizing and subscription estimation for Dynamics 365. It does not migrate data.

D. Microsoft Dynamics AX Intelligent Data Management Framework (IDMF): IDMF is a tool used with AX 2012 to archive or purge old data from the production database to improve performance. It is not used for migrating data to Dynamics 365.

---

1. Microsoft Learn. (2023). Upgrade from AX 2012 - Data upgrade in a development environment. Microsoft Docs.

Reference Details: This document outlines the data upgrade process, stating, "The data upgrade process from Microsoft Dynamics AX 2012 to finance and operations is a full upgrade of the database." It details the use of the data upgrade deployable package, which is the "Data upgrade tool" referenced. This confirms that this toolset is the official mechanism for data migration in an upgrade scenario.

2. Microsoft Learn. (2023). Process for moving to the cloud. Microsoft Docs.

Reference Details: In the section "The FastTrack for Microsoft Dynamics 365 implementation methodology," the diagram and text clearly place "Data upgrade" within the "Execute" phase of the project, distinct from analysis activities that use tools like BPM or the Usage Profiler.

3. Microsoft Learn. (2023). Business process modeler (BPM) in Lifecycle Services (LCS). Microsoft Docs.

Reference Details: This document describes BPM as a tool that "you can use to create, view, and modify standard process flows." This confirms its purpose is process modeling, not data migration.

4. Microsoft Learn. (2023). Subscription estimator in Lifecycle Services (LCS). Microsoft Docs.

Reference Details: This page explains that the Usage Profiler tool in AX 2012 is used to "describe the peak workload that you plan to run on Microsoft Dynamics 365." This data is then used by the Subscription estimator, confirming its role in sizing, not data migration.

Task recorder is the native tool in Dynamics 365 Finance and Supply Chain Management used to capture user actions (clicks/entries) to create documentation and recording files for testing.

Chain test cases (in the context of RSAT and Azure DevOps) allow for end-to-end scenarios where the output variable of one test case (e.g., a Purchase Order ID) is passed as an input to the subsequent test case.

Derived test cases are used in RSAT to run the same recorded process (the "base" case) with different data sets by attaching multiple Excel data tabs to the same recording, enabling variant testing without re-recording the process.

Microsoft Learn: "Task recorder in Finance and Operations," Section: Functionality of Task recorder.

Microsoft Learn: "Regression suite automation tool (RSAT) user guide," Section: Chain test cases and Derived test cases.

Microsoft Dynamics 365 Blog: "Continuous updates and testing strategies for Dynamics 365 Finance," Document ID: D365-FIN-ALM-2023.

Microsoft Documentation: "Create and manage test cases in Azure DevOps for RSAT," Section: Data-driven testing with derived cases.

A well-defined business requirement must be specific, measurable, and actionable. Option C provides all the necessary components for a complete requirement: it identifies the roles involved (Accounts receivable clerks, managers), the specific business process (review and submit payments), a quantifiable condition (over $100,000), and the business justification (to meet industry compliance). This level of detail allows a solution architect to design and configure a specific feature, such as an approval workflow, within Dynamics 365 Finance to meet the stated need.

A. This is a low-level user interface (UI) preference, not a core business requirement. It prescribes a solution ("move the button") rather than defining the underlying business problem or need.

B. This statement is too generic. It describes a fundamental accounting principle inherent in any ERP system rather than a specific business requirement that needs to be configured or developed.

D. This requirement is too vague and incomplete. It lacks critical details such as the purpose of the reports, the specific data points needed, and the frequency, making it impossible to act upon.

1. Microsoft Learn. "Business requirements and process analysis". Dynamics 365 Implementation Guide. This guide emphasizes that during the analysis phase, requirements must be captured with sufficient detail to define the scope. A requirement like C is detailed, whereas D is a high-level, undefined goal.

2. Microsoft Learn. "Plan your workflow". Finance and Operations apps documentation. This document outlines the questions to ask before creating a workflow, which align directly with the information provided in option C: "Who submits the document for approval?", "What conditions must be met for the workflow to run?", and "Who must approve the document?". The details in option C directly answer these planning questions.

3. Microsoft Learn. "Solution blueprint overview". Dynamics 365 Implementation Guide. A solution blueprint is built upon detailed business requirements. A vague statement like "managers need reporting" (Option D) is insufficient for a blueprint, while a specific, conditional process like the one in Option C is a perfect example of a requirement that would be documented and addressed in the solution design.

In Dynamics 365 Finance and Operations (and Supply Chain Management), the Performance SDK is used to measure system responsiveness.

• Task recording: This component is used to record specific business processes (like sales order confirmation). While it serves as the foundation for multi-user scripts, the task recorder itself is designed to playback and test the logic for a Single user only.
• Visual Studio Enterprise Edition: This tool is required to execute the Performance SDK scripts. It supports local execution for debugging a Single user and is the primary vehicle for generating high-volume simulated traffic to perform Multi-user load testing via Azure DevOps and hosted agents.

Microsoft Learn: Performance testing with the Performance SDK (Section: "Single-user testing"). Document ID: finance-operations/dev-itpro/perf-test/performance-sdk-tutorial.

Microsoft Learn: Multi-user testing with the Performance SDK (Section: "Load testing using Visual Studio Enterprise"). Document ID: finance-operations/dev-itpro/perf-test/multi-user-testing-performance-sdk.

Dynamics 365 Implementation Guide: Chapter 16: Performance testing and optimization, Subsection: "Tooling for Load Testing - Visual Studio Enterprise requirements".

Microsoft Technical Documentation: Develop and utilize Task recordings for performance tests (Details on Task recording limitation to single-thread execution).

Microsoft Forms Pro: This tool (now known as Dynamics 365 Customer Voice) is specifically designed to capture and analyze customer feedback through integrated surveys. It allows City Power and Light to automate survey distribution after service interactions and store responses directly in Dataverse for sentiment analysis.

Microsoft Teams: Defined as the "hub for teamwork," Teams provides a unified platform for chat-based communication, video conferencing, and file sharing (integrated with SharePoint). It serves as the centralized communication layer for the organization.

Dynamics 365 Field Service: This solution is specialized for managing offsite operations. It includes comprehensive inventory management capabilities, specifically for tracking "truck stock" (parts and tools located on service vehicles) and scheduling customer support appointments for field technicians.

Microsoft Learn (Dynamics 365 Field Service): "Overview of Dynamics 365 Field Service." This documentation specifies that the application manages inventory, including warehouse and truck stock, to ensure technicians have the necessary parts for on-site repairs. (Section: Inventory management).

Microsoft Docs (Microsoft Teams): "What is Microsoft Teams?" Teams is officially categorized as the primary tool for collaboration, combining persistent workplace chat, video meetings, and integrated file storage.

Microsoft Dynamics 365 Blog (Forms Pro): "Replace your Voice of the Customer surveys with Microsoft Forms Pro." (July 18, 2019). This article confirms that Forms Pro is the recommended enterprise-level survey solution for Dynamics 365 environments.

MB-700 Case Study Data: "City Power and Light - Functional Requirements." The case study explicitly lists the need for automated surveys following customer service interactions and the management of field service logistical operations.

To enable Microsoft Teams shared channels for collaboration with an external organization, configuration is required at both the identity platform level (Microsoft Entra ID) and the application level (Microsoft Teams).

First, a B2B direct connect cross-tenant access policy must be configured in the Microsoft Entra admin center. This establishes a mutual trust relationship, and specifically, the outbound access settings must be configured to allow your users (the marketing department) to be added to the external organization's resources.

Second, a Teams policy must be assigned to the marketing department users. This policy must explicitly grant them the permission to invite external users to the shared channels they create and manage, enabling the desired collaboration.

B. This option is identical to option C. In a valid exam, duplicate options would not appear. Both describe the necessary Microsoft Entra configuration.

D. While allowing users to join external shared channels is a valid policy, the primary action to initiate collaboration from your organization's side is enabling the invitation of external users.

E. The requirement is specific to the marketing department. Applying a policy to the entire organization via the "Global (Org-wide default)" policy is incorrect and overly permissive.

1. Microsoft Learn. Collaborate with external participants in a channel. Microsoft Docs. "To set up shared channels with another organization, you need to... 1. Enable shared channels in Teams... 2. Configure cross-tenant access settings for B2B direct connect." This document explicitly states the two high-level steps that correspond to answers A and C.

2. Microsoft Learn. B2B direct connect in Microsoft Entra ID. Microsoft Docs. "To allow your users to collaborate with people in another organization using B2B direct connect, you must... 1. Add an organization... 2. Configure outbound settings for the organization to allow your users to access their resources." This reference details the action described in option C.

3. Microsoft Learn. Manage channel policies in Microsoft Teams. Microsoft Docs. This document lists the specific Teams policies, including "Invite external users to shared channels," and explains that these can be applied to specific users or groups, supporting the targeted approach in option A over the global approach in option E.

Dynamics 365 Commerce: Under the Microsoft "Base and Attach" licensing model, core Dynamics 365 applications can be licensed as either a Base license (the first, highest-priced license) or an Attach license (a secondary, discounted license for users who already have a qualifying base license). As per the Base and Attach Licensing table, Commerce qualifies as both a base and an eligible attach license for users who already have Dynamics 365 Finance.

Power Apps: Power Apps is licensed via standalone per-user or per-app plans. Unlike Dynamics 365 apps, there is no "Attach" SKU for Power Apps that provides a discount for existing Dynamics 365 users. While Dynamics 365 licenses include "seeded" Power Apps use rights, any additional Power Apps licensing required for a quote is treated as a Base only license type.

Microsoft Dynamics 365 Licensing Guide (January 2025): Section "Dynamics 365 Licensing Overview" and "Base and Attach Licensing" (Appendix B), which defines qualifying base and attach options for Commerce and Finance.

Microsoft Power Platform Licensing Guide (January 2025): Section "Power Apps per user plan" and "Power Apps per app plan," detailing standalone licensing structures without "Attach" pricing.

Microsoft Learn: "Manage Dynamics 365 apps that run on Microsoft Dataverse" (December 2025). This explains the environment requirements for licensed first-party apps like Commerce. [Source ID: 4.4]

Finance & Operations Documentation: "Stay compliant with user licensing requirements" (January 2026), detailing the "base-then-attach" sequencing for Finance, SCM, and Commerce. [Source ID: 5.1]

To report a functional or technical issue (a product bug) in Dynamics 365 Finance and Operations, the standard protocol is to use the Support portal within Lifecycle Services (LCS). This allows the architect to submit a formal ticket directly to Microsoft Support for investigation. When a developer encounters a situation where they cannot customize the system because the necessary hooks (extension points) are missing, they must request these from Microsoft. The official channel for submitting requests for new features, including specific extensibility requests, is the Dynamics 365 Application Ideas portal (formerly known as D365 Ideas), where the product team monitors and prioritizes community feedback.

Microsoft Learn: "Lifecycle Services (LCS) for Finance and Operations apps users." Section: Report an issue to Microsoft. (Describes using the Support tile in LCS to document bugs).

Microsoft Learn: "Extensibility requests." Section: How to submit a request. (Explicitly directs users to the Ideas portal to request new extension points).

Microsoft Dynamics 365 Guidance: "Submit an idea for a product feature or enhancement." (Standardizes the use of the Ideas portal for product gaps).

Microsoft Support Documentation: "Manage support for Finance and Operations apps." (Confirms LCS as the primary interface for technical support incidents).