Power Automate is the Microsoft Power Platform tool specifically designed to automate repetitive tasks and workflows between applications and services. Its core architecture relies on triggers (events that start a flow) and actions (steps the flow performs in response). Therefore, it is the correct tool for both "Automate workflows" and "Trigger an action from an event."

Power Apps provides a rapid development environment to build custom business applications. It allows users to create custom mobile-optimized interfaces (Canvas apps) for data entry and interaction without extensive coding.

Power BI is utilized for business analytics, data visualization, and reporting, and is not used for workflow automation or creating data entry screens.

Microsoft Learn. (2023). What is Power Automate?. Retrieved from https://learn.microsoft.com/en-us/power-automate/getting-started ("Power Automate is a service that helps you create automated workflows...")

Microsoft Learn. (2023). Get started with Power Automate - Triggers and Actions. Retrieved from https://learn.microsoft.com/en-us/power-automate/get-started-logic-flow ("Every flow starts with a trigger, and then you can add one or more actions.")

Microsoft Learn. (2023). What is Power Apps?. Retrieved from https://learn.microsoft.com/en-us/power-apps/powerapps-overview ("...suite of apps, services, and connectors... provides a rapid application development environment to build custom apps...")

Model-driven apps are designed with a component-focused approach where the layout is largely determined by the underlying data model (specifically the Common Data Service, now Microsoft Dataverse). They are ideal for complex business processes and require little to no code. Canvas apps provide a blank surface that allows creators to design highly customizable user interfaces (UI) with pixel-perfect control, enabling the arrangement of controls and fields exactly as desired, often for task-specific scenarios.

Microsoft Learn. (n.d.). Overview of building apps in Power Apps. Retrieved from https://learn.microsoft.com/en-us/power-apps/maker/

Relevance: Defines the three types of apps: canvas, model-driven, and cards.

Microsoft Learn. (n.d.). What are model-driven apps in Power Apps? Retrieved from https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/model-driven-app-overview

Quote: "Model-driven app design is a component-focused approach to app development... Model-driven design is a process that centers on your data model."

Microsoft Learn. (n.d.). What are canvas apps? Retrieved from https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/getting-started

Quote: "Canvas apps give you a blank canvas... You can drag and drop elements onto a canvas, just as you would design a slide in PowerPoint... gives you the flexibility to arrange the user experience and interface the way you want it."

Custom connector: Used to connect Power Platform services to external REST or SOAP APIs (such as those hosted in Azure) when no official pre-built connector exists.

Standard connector: The SharePoint connector, which is required to manage and update files in document libraries, is classified as a Standard connector in the Power Platform licensing model.

Power Query: This is the data transformation and preparation engine used within Dataflows to clean, reshape, and ingest data into Microsoft Dataverse.

Microsoft Learn (Custom Connectors): "Use custom connectors ... to communicate with services that aren't available as prebuilt connectors."

Source: Create a custom connector from scratch. (https://learn.microsoft.com/en-us/connectors/custom-connectors/define-blank)

Microsoft Learn (Connector Classification): "Standard connectors are available in the standard Power Automate ... plans. Examples include: SharePoint, Outlook..."

Source: Licensing overview for Microsoft Power Platform. (https://learn.microsoft.com/en-us/power-platform/admin/power-automate-licensing)

Microsoft Learn (Dataflows & Power Query): "Dataflows are a self-service, cloud-based, data preparation technology... Dataflows use the Power Query online mashup engine."

Source: Introduction to dataflows and self-service data prep. (https://learn.microsoft.com/en-us/power-query/dataflows/overview-dataflows-across-power-platform-dynamics-365)

Power BI dashboards are the correct solution for analyzing high-level KPIs. A dashboard is a single-page canvas in the Power BI service specifically designed to monitor business status at a glance. It aggregates the most important metrics (KPIs) from various reports into a unified, high-level view for decision-making.

Power BI reports are the correct solution for drilling down into details. Reports are multi-perspective views of a dataset that offer deep interactivity. The "Drill mode" (drill down, drill up, and drill through) is a specific feature of Power BI report visuals, allowing users to explore granular data hierarchies. While dashboard tiles generally link to reports, the actual action of drilling into visual details occurs within the report environment.

Microsoft. "Introduction to dashboards for Power BI designers." Microsoft Learn. Accessed November 28, 2025. https://learn.microsoft.com/en-us/power-bi/create-reports/service-dashboards

Relevance: Defines dashboards as a single canvas to "monitor your business and see all of your most important metrics at a glance."

Microsoft. "Dashboards vs. reports." Microsoft Learn. Accessed November 28, 2025. https://learn.microsoft.com/en-us/power-bi/consumer/end-user-dashboards#dashboards-vs-reports

Relevance: Explicitly compares features, noting that dashboards provide a "high-level" view while reports provide "more detail" and interactivity.

Microsoft. "Drill mode in the Power BI service." Microsoft Learn. Accessed November 28, 2025. https://learn.microsoft.com/en-us/power-bi/consumer/end-user-drill

Relevance: Confirm that drill actions (drill down/up) are operations performed on visuals within a report.

Synchronize account information: Yes. Microsoft Power Platform (specifically Power Automate and Dataflows) provides hundreds of standard Connectors (e.g., SQL Server, Oracle, MySQL) that allow you to synchronize data between Dataverse (the backend for Dynamics 365 Sales) and third-party databases. This can be achieved through scheduled or trigger-based flows without using "development tools" (like Visual Studio) or custom plug-ins (C# code), adhering to the company's "no-code/low-code" constraint.

Create invoices and send via flow: Yes. Power Automate is designed to automate business processes across apps. You can configure a cloud flow that triggers when an Order is processed, uses the Dataverse connector to create a corresponding Invoice record (and lines), and then uses the Outlook (or SMTP) connector to send that invoice to the customer. This entire workflow is built in the Power Automate Maker Portal, requiring no professional development tools.

Microsoft Learn, "Connect to other data", Power Automate documentation. This section details using connectors to integrate with external systems (including databases) without custom code. https://learn.microsoft.com/en-us/power-automate/desktop-flows/connect-to-data

Microsoft Learn, "Create a cloud flow in Power Automate", Power Automate documentation. Describes creating automated workflows to manage records (like Invoices) and send notifications. https://learn.microsoft.com/en-us/power-automate/get-started-logic-flow

Microsoft Learn, "Dataverse Virtual Tables", Power Apps documentation. Mentions accessing and interacting with data in external SQL databases as if it were local, facilitating integration without coding. https://learn.microsoft.com/en-us/power-apps/maker/data-platform/virtual-entities/overview

Statement 1 (No): The scenario explicitly states the company does not plan to use development tools or plug-ins. While the Power Platform allows connectivity to many systems via Standard Connectors, a "proprietary database" implies a non-standard system for which no pre-built connector exists. To synchronize with such a database, one would typically need to build a Custom Connector (which often requires defining API specifications/OpenAPI, a development task) or write a Plug-in (custom code). Since these methods are restricted by the "no development tools or plug-ins" constraint, this action cannot be performed using only out-of-the-box configuration.

Statement 2 (Yes): Creating invoices from orders and sending them is a core capability of Power Platform apps (specifically Model-driven apps and Dynamics 365 Sales). The conversion of an Order to an Invoice is a standard business process flow available via the command bar configuration. Furthermore, sending the invoice can be automated using a Power Automate cloud flow with a standard email connector (e.g., Outlook), which is done via the visual designer (low-code), satisfying the "no development tools" requirement.

Microsoft Learn - Connectors overview: "Connectors provide a way for users to connect their accounts and leverage a set of prebuilt actions and triggers... [Custom connectors] allow you to connect to services that aren't available as prebuilt connectors." (Since the database is proprietary and not prebuilt, and custom connectors involve development effort/API definitions, this is not possible under the constraints).

Source: https://learn.microsoft.com/en-us/connectors/connectors

Microsoft Learn - Manage sales orders: "Create or edit an invoice... You can create an invoice from an order or a quote." This confirms the native capability to process orders into invoices without code.

Source: https://learn.microsoft.com/en-us/dynamics365/sales/create-edit-invoice

Microsoft Learn - Use a flow to update a row: Demonstrates using Power Automate (visual designer, no code) to automate tasks related to Dataverse records (like Orders/Invoices).

Source: https://learn.microsoft.com/en-us/power-automate/dataverse/update-row

Microsoft Power Automate provides Flow Checker to validate a flow’s configuration and identify errors or warnings before execution. To execute a flow using previously processed or sample data, the Test tool is used, as it supports running the flow manually or with recent trigger data. The Test tool also displays real-time run progress and output, allowing you to monitor the flow as it runs. Since only two tools are provided in the question, Test is the appropriate utility for both execution and monitoring activities.

Microsoft Power Automate Documentation

“Use Flow Checker to validate your flow for errors and warnings.”

Microsoft Docs → Power Automate > Cloud flows (Section: Flow Checker).

Microsoft Power Automate – Testing Flows

“Use the Test feature to run your flow with previously used trigger data and view detailed run information.”

Microsoft Docs → Test a cloud flow (Step-by-step instructions).

Microsoft Learn – Monitor cloud flow runs

“Flow run details show execution progress, inputs, and outputs for each action.”

Learn Module: Monitor and troubleshoot flows.

Microsoft Power Pages is a low-code, Software as a Service (SaaS) platform used to create, host, and manage modern, external-facing business websites. This directly aligns with it being a low-code website solution hosted as a service. A key feature for reaching a global audience is its built-in capability to support multiple languages, allowing creators to present content, forms, and lists in various languages within a single website instance. These two features are fundamental capabilities of the Power Pages platform.

B. Creating customized styling for each user: Styling in Power Pages is applied at the site or web role level, not on an individual, per-user basis.

D. Supplying OData feeds: Power Pages is designed to build user interfaces (like forms and lists) on top of Dataverse data, not to primarily act as a service for supplying OData feeds.

1. Microsoft Learn. (2023). What is Power Pages? Microsoft Documentation. Retrieved from https://learn.microsoft.com/en-us/power-pages/introduction.

Reference for C: The first paragraph states

"Microsoft Power Pages is a secure

enterprise-grade

low-code software as a service (SaaS) platform for creating

hosting

and administering modern external-facing business websites."

2. Microsoft Learn. (2023). Enable multiple-language support. Microsoft Documentation. Retrieved from https://learn.microsoft.com/en-us/power-pages/configure/enable-multiple-language-support.

Reference for A: The "Overview" section explicitly details the feature: "Enabling multiple languages on your website creates a version of your pages for each language you support."

3. Microsoft Learn. (2023). Overview of the Styling workspace. Microsoft Documentation. Retrieved from https://learn.microsoft.com/en-us/power-pages/getting-started/style-site.

Reference for B: This document describes applying themes

branding

and custom CSS to the entire site

confirming that styling is not a per-user feature.

4. Microsoft Learn. (2023). Add a list to a page. Microsoft Documentation. Retrieved from https://learn.microsoft.com/en-us/power-pages/getting-started/add-list.

Reference for D: This document illustrates the primary

low-code method for displaying Dataverse data on a page is through components like lists

not by supplying raw OData feeds.

To allow coworkers to view a Power BI dashboard, you must Share it using Power BI’s sharing permissions. To bring Excel-based data into Power BI for visualization on the dashboard, the correct action is Get Data, which supports importing or connecting to Excel workbooks. To place visual content—such as charts, reports, or individual visuals—onto the dashboard, you must Pin items from a report to the dashboard.

Microsoft Documentation – Share dashboards and reports

Section: Share your dashboard

https://learn.microsoft.com/power-bi/collaborate-share/service-share-dashboards

Microsoft Documentation – Get data from Excel files

Section: Connect to Excel data

https://learn.microsoft.com/power-bi/connect-data/desktop-import-excel

Microsoft Documentation – Pin a tile to a dashboard

Section: Pin visuals to dashboards

https://learn.microsoft.com/power-bi/create-reports/service-dashboard-pin-tile

The issue described is that the flow "does not properly extract birth dates." This points to a problem with data manipulation or logic within the flow, not connectivity. In Power Automate (formerly Microsoft Flow), expressions are used to perform operations on data, such as formatting dates, converting data types, or extracting specific parts of a text string. An incorrect expression is the most likely reason the birth date is not being processed correctly for the comparison or for use in the email greeting.

A. Connectors: A connector is responsible for establishing the connection to the data source (e.g., SharePoint, Dataverse). A connector issue would likely result in a failure to retrieve any data, not an incorrect extraction of it.

C. Templates: Templates are pre-built flows that serve as a starting point. The flow has already been created and is running, so modifying a template would not fix the logic within this specific, existing flow.

1. Microsoft Learn. "Use expressions in conditions to check multiple values in Power Automate." Get started with Power Automate. This document details how expressions are fundamental for manipulating and evaluating data

such as dates

within a flow's logic. It states

"In any flow

you use expressions to work with data."

2. Microsoft Learn. "Reference guide for workflow expression functions in Azure Logic Apps and Power Automate." Power Automate Documentation. This guide provides a comprehensive list of functions available in expressions

including date and time functions like formatDateTime() and addToTime()

which are essential for handling date-based logic like a birthday check.

3. Microsoft Learn. "Connectors overview." Power Automate Documentation. This source defines connectors as proxies or wrappers around an API that allow the underlying service to talk to Power Automate. Their role is connectivity

not data processing logic within the flow itself.