A third-party tide API will POST storm alerts to a URL the municipal harbor owns. Which Azure Functions trigger best implements that webhook?
Select an answer to reveal the explanation.
Short Explanation
When a partner says “we’ll POST to your URL,” that’s a webhook—and in Functions-land that’s an HTTP trigger. Skip the polling timer; let the tide API knock on the door.
Full Explanation
Webhook integrations map to HTTP-triggered Azure Functions that receive partner POSTs at a route the harbor controls. Authorization level and route templates are related configuration. Timer polling, unrelated blob triggers, or Cosmos triggers do not express a third-party HTTP webhook contract.