You are building a custom application in Azure to process resumes for the HR department. The app must monitor submissions of resumes. You need to…

Power Automate is the most suitable mechanism for this scenario. It provides a comprehensive, low-code solution for the entire process. It can be configured with a trigger to monitor various sources for resume submissions, such as an email inbox or a SharePoint folder. It can then use the AI Builder's prebuilt resume processing model to parse the document and extract relevant information. Finally, the native Microsoft Dataverse (formerly Common Data Service) connector can be used to create or update records with the extracted contact and skills data, fulfilling all requirements of the task.

B. Common Data Service plug-in: Plug-ins execute server-side code in response to events within Dataverse (e.g., creating a record), but they cannot monitor external sources like a file drop location.

C. Web API: The Dataverse Web API is a RESTful endpoint used to interact with data. It is a passive interface that must be called by another application; it does not actively monitor for new submissions.

D. Custom workflow activity: These are components of classic Dataverse workflows, which are triggered by internal Dataverse events. They are not designed to monitor external systems for new files.

1. Microsoft Learn, Power Platform documentation. "Use the resume processing prebuilt model in Power Automate". This document explicitly details the use case of creating a Power Automate flow that is triggered by a new email with an attachment, uses AI Builder to process the resume, and then saves the extracted information. This directly matches the question's scenario.

2. Microsoft Learn, Power Platform documentation. "Overview of cloud flows". This page describes how Power Automate cloud flows can be triggered automatically, instantly, or via a schedule, and can connect to hundreds of data sources, which is essential for the "monitor submissions" requirement.

3. Microsoft Learn, Power Platform documentation. "Use plug-ins to extend business processes". Section: "When to use plug-ins". This document clarifies that plug-ins are used to initiate automated processes when a specific event occurs on the Dataverse server, distinguishing them from Power Automate which connects external events to Dataverse.

4. Microsoft Learn, Power Platform documentation. "Use the Microsoft Dataverse Web API". This source describes the Web API as an OData v4 service endpoint, confirming its role as a programmatic interface for data operations, not an automation or monitoring engine.