← Other Athentra features

Hub: Intelligence · Actions

Azure Function Actions

An event can invoke an Azure Function, so teams can run their own code in response to a governance signal. The function is called with the event payload, using your key and your timeout, and its outcome is recorded alongside every other action. Engineering gets an escape hatch without stepping outside the record.

  1. 01

    Pain Point

    What's the problem?

    Some responses need logic no configuration screen can express, and no vendor can anticipate in advance.

  2. 02

    Remedy

    How do we attack it?

    Run your own code against an event, with your own key and your own timeout

  3. 03

    Your Value

    What do you get out of it?

    Gives engineering an escape hatch when the built-in actions do not fit, without leaving the audit trail