Which Azure service and trigger sends Teams alerts from App1 webhooks?

Why the Answer Is Correct

App1 already supports webhooks, so it can push an HTTP POST to an endpoint the moment a record is created, and Azure Logic Apps exposes exactly that entry point through the built-in Request trigger (When an HTTP request is received). Logic Apps also ships a first-party Microsoft Teams connector with an out-of-the-box Post message in a chat or channel action, so no custom code is needed for authentication, payload shaping, or retry handling. Combining the Request trigger with the Teams action means App2 is pure configuration: register the Logic App's callback URL in App1's webhook, and the workflow completes the Teams notification. That is why Logic Apps plus the HTTP request trigger is the design that satisfies 'minimize development effort' while remaining a fully managed Azure service in the subscription. The same pairing also gives built-in run history, which is useful for verifying that each App1 record actually produced a message.

Why Other Candidate Answers Are Wrong

Azure Functions can receive an HTTP request and post to Teams, but the developer must write code for the Teams payload, the webhook secret, and error handling, which is more effort than the Logic Apps connector path. Power Automate has the same Teams connector, yet the requirement is a service in the Azure subscription hosting App2 for a system-to-system flow, which points to Logic Apps rather than a per-user flow. Azure Event Grid can route the event but has no native Teams message action, so it must hand off to another compute service, adding moving parts without removing code. A recurrence (polling) trigger is the wrong trigger type: App1 already emits webhooks, so polling its REST API adds interval logic, latency, and duplicate-handling code that the push model avoids. An Office 365 Outlook or generic SMTP trigger is also wrong because the target channel is Microsoft Teams, not email.

Community Comment Notes

As gpais noted, Logic Apps is "a no-code/low-code workflow orchestration service" that "features a built-in, out-of-the-box connector for Microsoft Teams," which is precisely the reason it minimizes development effort here. The same comment stresses that no custom code is required to handle authentication or payload delivery to Teams — the exact differentiator against a Function-based host. Because the vote count on the thread is minimal, the verdict should rest on the vendor documentation and the wording of the requirement, not on majority sentiment. Taken together, the comment aligns with the documented Logic Apps Request-trigger plus Teams-action pattern rather than a polling or code-first design.