Azure Functions often run the small jobs that hold a system together: webhooks, scheduled syncs and internal APIs. Connecting them lets an agent see which function apps exist, check recent deployments, call an HTTP-triggered function and adjust settings, with every change recorded.
Deployment checks
List recent deployments for a function app and report who shipped what, and whether it succeeded.
Run internal endpoints
Invoke an HTTP-triggered function, such as a cache refresh or a report job, without hunting for its URL and key.
Slot swaps
Create a staging slot, verify it, then swap it into production as part of a reviewed release.
Settings and key hygiene
Audit app settings across function apps and rotate function or host keys that have been shared too widely.
Tools to start with
- Invoke Function: Calls an HTTP-triggered function directly.
- Manage Deployment Slots: List, create, delete and swap slots.
- Manage Access Keys: Function-level and host-level keys.
Sign-in and permissions
Azure Functions connects through Microsoft Entra ID, and what the agent can do follows the Azure role assignments on the subscription or resource group. A reader role is enough to list apps and deployments; starting, stopping, swapping slots or changing keys needs a contributor-level role, so grant that only to the groups that should operate production.
Sign-in options on Metorial: Work Only, Work & Personal.