ALM Components for Copilot Studio and D365 SCM Integration
Short answer
CE Include a Microsoft Power Platform solution and an X++ model in the ALM process.
Question
This is a case study. Case studies are not timed separately from other exam sections. You can use as much exam time as you would like to complete each case study. However, there might be additional case studies or other exam sections. Manage your time to ensure that you can complete all the exam sections in the time provided. Pay attention to the Exam Progress at the top of the screen so you have sufficient time to complete any exam sections that follow this case study.
To answer the case study questions, you will need to reference information that is provided in the case. Case studies and associated questions might contain exhibits or other resources that provide more information about the scenario described in the case. Information provided in an individual question does not apply to the other questions in the case study.
A Review Screen will appear at the end of this case study. From the Review Screen, you can review and change your answers before you move to the next exam section. After you leave this case study, you will NOT be able to return to it.
To start the case study
To display the first question in this case study, select the "Next" button. To the left of the question, a menu provides links to information such as business requirements, the existing environment, and problem statements. Please read through all this information before answering any questions. When you are ready to answer a question, select the "Question" button to return to the question.
Overview
Contoso, Ltd. is a high-tech manufacturing company that uses Microsoft Dynamics 365 Finance. Dynamics 365 Supply Chain Management, and Dynamics 365 Commerce for its North American operations. The company designs and develops innovative products that have many patents and proprietary technologies. The patents and engineering designs are closely guarded secrets.
Contoso executives want to integrate and adopt AI solutions to help scale the company in preparation for an anticipated period of rapid growth.
The company has multiple legal entities and Azure subscriptions that will be used in the adopted AI solutions.
Requirements
AI Adoption
The following executives will have specific responsibilities in the overall AI adoption:
• Chief Technology Officer (CTO): Select one Dynamics 365 Finance, Dynamics 365 Supply Chain Management or Dynamics 365 Commerce prebuilt AI agent and one custom Microsoft Copilot Studio AI agent to prioritize and deploy during the initial AI adoption phase.
• Chief Information Officer (CIO): Ensure that appropriate security labels are assigned to the data used by the AI agents.
• Chief Financial Officer (CFO): Analyze the return on investment (ROI) for the AI agents being deployed.
• Chief Information Security Officer (CISO): Discover and inventory AI resources for auditing.
• Chief Executive Officer (CEO): Ensure that all solutions adhere to industry-standard responsible AI practices.
All AI initiatives and agents will have a detailed business use case, a defined audience profile, and an estimated ROI that will compare the cost savings of the current process against the estimated costs of using the new AI solutions.
The company's research and development (R&D) department already has a custom Model Context Protocol (MCP) server that contains comprehensive product specifications and compliance data.
Prebuilt AI Agent
The CTO has NOT yet selected which prebuilt AI agent to use in Dynamics 365 Supply Chain Management. The CTO wants to view available agent templates to identify which agent will add the most business value.
Depending on which high-priority AI agents are identified, its agent capabilities must be previewed in a discovery meeting with the relevant business operation stakeholders.
Custom AI Agent
Contoso has identified the following custom AI agent requirements:
• The custom AI agent will use data from Dynamics 365 Supply Chain Management to answer questions for the manufacturing team as a low-code solution.
• The custom AI agent will be accessible from within Microsoft Teams.
• The custom AI agent must be designed to eventually connect to other agents that can be selected based on their description.
• The topics used in the custom AI agent will be selected based NOT on a trigger phrase, but on a description of the purpose of the query, to make the interactions more conversational.
• The custom AI agent must be able to answer questions about product specifications by using existing technologies. The product specifications are maintained by the R&D department.
• The custom AI agent must be integrated with and accessible from Dynamics 365 Supply Chain Management.
• The custom AI agent must be able to use Dynamics 365 Supply Chain Management business logic that is stored outside of the application.
Analysis, Reporting, and Troubleshooting
Contoso has identified the following analysis, reporting, and troubleshooting requirements:
• The CISO will audit all the AI solutions monthly for compliance and security.
• The CFO will analyze all the AI solutions quarterly to compare the estimated ROI against actual measured efficiencies and adoption. The CFO will use the Copilot Studio agent usage estimator to perform this analysis.
• The CISO wants to identify how much sensitive data was accessed for a given AI agent run and who accessed the data. Too much sensitive data accessed by a single user might indicate a high security risk.
• The CTO wants to track user feedback on the quality of the AI agent responses during user interactions with the agents. Consistently poor feedback will trigger an escalated reengineering discussion.
• The CEO wants a quarterly assessment of all the required metrics for their specific responsibilities. The tools used for the assessments must be Microsoft-recommended and must verify reliability, interpretability, fairness, and compliance.
• The CFO wants to identify how many interactions with the AI agents are abandoned on a given day as compared to resolved conversations. Too many abandoned sessions might indicate that Copilot Studio credits are being used inefficiently by end users.
Which two components for the custom AI agent should you include in the application lifecycle management (AIM) process? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
Key Takeaways
The trap is confusing the transport format (ZIP) with the ALM component (Solution) and overlooking that external D365 logic requires an X++ model for ALM.
Identify the correct ALM components for a custom AI agent in Copilot Studio integrated with Dynamics 365 SCM. The solution requires a Power Platform solution and an X++ model.
Common mistake: Selecting 'ZIP package' instead of 'Power Platform solution' because they are often used together, but the ZIP is just the file format, not the ALM entity.
Expert Analysis
The scenario involves a custom AI agent built with Microsoft Copilot Studio that must integrate with Dynamics 365 Supply Chain Management (SCM) and use external business logic. The question asks for two components to include in the Application Lifecycle Management (ALM) process.
First, identify the platform: Copilot Studio agents are managed within the Power Platform. In Power Platform ALM, the standard unit for packaging, versioning, and moving solutions between environments is a Microsoft Power Platform solution (Option C). This allows for proper governance, dependency management, and deployment pipelines.
Second, address the integration requirement: The agent must "use Dynamics 365 Supply Chain Management business logic that is stored outside of the application." In the D365 Finance & Operations architecture, custom business logic is developed using X++ and packaged into an X++ model (or model store file) for deployment. To ensure the agent can access this specific external logic as part of the ALM process, the X++ model containing that logic must be included or coordinated in the deployment strategy. Therefore, an X++ model (Option E) is the correct component for managing that specific piece of infrastructure/logic.
Why other options are incorrect:
- A ZIP package (Option B): While Power Platform solutions are often exported/imported as.zip files, the ZIP is merely the transport container format, not the logical ALM component itself. The component is the Solution.
- An Azure package (Option A): This is too generic and does not represent the specific packaging units for Copilot Studio or D365 F&O customization.
- A Cloud Scale Unit (CSU) package (Option D): CSUs are used for Commerce/retail extensions, not general SCM business logic or Copilot Studio agents.
Exam Strategy
When asked about ALM packaging, distinguish between the logical component (e.g., Power Platform Solution, X++ Model) and the physical transport file (e.g., .zip). Always map the technology stack to its native ALM artifact: Copilot Studio uses Power Platform Solutions, while D365 F&O customizations use X++ Models.
Frequently Asked Questions
Why isn't a ZIP package the correct ALM component?
What is the role of the X++ model in this scenario?
Discussion 6 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 6
-
24b8eec 👍 5Why not the others A. Azure package — a generic Azure deployment artifact; not the packaging mechanism for either a Copilot Studio agent or D365 F&O business logic. B. ZIP package — Power Platform solutions export as .zip files, but the component in the ALM process is the solution (C), not the raw ZIP. ZIP is the transport format, not the ALM component. D. Cloud Scale Unit (CSU) package — used specifically for Dynamics 365 Commerce headless commerce (store components, CDX, etc.). Contoso's agent is in SCM, not Commerce.
-
Ninashnash 👍 2C. Microsoft Power Platform solution — The agent is built in Copilot Studio, part of the Power Platform. Power Platform solutions are the standard ALM packaging unit for Copilot Studio agents, enabling versioning and promotion across environments. E. an X++ model — The agent must use D365 SCM business logic stored outside the app. Custom business logic for D365 Finance & Operations apps is packaged as X++ models, the standard ALM unit deployed via LCS/Azure DevOps.
-
Ninashnash 👍 2B (A ZIP package) is not correct : While solution files or custom connectors are exported as .zip archive files during transit, the underlying operational ALM component used for environment management is the Power Platform solution itself. E should be selected not C
-
omath 👍 1✅ B. a ZIP package This is required because Copilot Studio exports agents as ZIP files when: - Moving between tenants - Backing up agents - Importing into another environment - Packaging custom connectors (OpenAPI definitions are also ZIP‑based) ✅ C. Microsoft Power Platform solution This is mandatory for ALM of Copilot Studio agents. Copilot Studio agents are packaged and moved between environments only through Power Platform solutions. Solutions provide: - Versioning - Dependency tracking - Managed/unmanaged deployment - Environment promotion (Dev → Test → Prod)
-
Aarch 👍 1A CSU package is a deployable package used to install or update Commerce/retail extensions and customizations in the Cloud Scale Unit environment.
Show 1 more comment
-
Luweho 👍 1An X++ model is required "to use Dynamics 365 Supply Chain Management business logic that is stored outside of the application"
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.