≈181 tokens on demand. Your agent reads this file only when SKILL.md points to it.
HTTP trigger auth bridge checklist
- Bridge choice is explicit: Azure Functions, Logic Apps, or API Management.
- Caller authentication is separated from SRE Agent trigger authentication.
- Token audience for the final SRE Agent call is verified against current Microsoft Learn guidance.
- Correlation and replay-control headers are required and logged.
- Trigger remains disabled until the bridge is tested with non-production payloads.
- Managed identity or secret-store path is defined; no bearer token is stored in logs or static config.
- Downstream response plans and HTTP triggers remain in Review until auth, payload shape, and cost are proven.
- Rollback path exists for bridge disablement and caller cutback.