This guide exists to prevent a mistake: tenant webhook delivery is planned and unavailable in this release, so there is nothing to configure — and building alerting on it would leave your incident path silently broken.
Read it as a boundary map: what is explicitly disabled today, and how to prepare without depending on delivery that has not been released.
1. Confirm the current boundary
- Do not register an endpoint or depend on a configured subscriber: tenant delivery is disabled.
- Use GitHub PR gating for the integration that is available today.
- For an integration requirement, contact us with the target system and operational need.
Do not register an endpoint or depend on a configured subscriber — tenant delivery is disabled. The integration available today is GitHub PR gating; for a specific requirement, contact us with the target system and the operational need.
2. Prepare without relying on delivery
- Do not treat any event name, signing header, retry policy, or delivery status as a released contract yet.
- Review a run through its authenticated detail page and, when eligible, its Evidence Pack.
- Keep your existing incident path active until tenant delivery is released and independently validated.
Treat every event name, signing header, retry policy, and delivery status as unreleased until documented otherwise. Review runs through the authenticated detail page and, when eligible, its Evidence Pack, and keep your existing incident path active until tenant delivery is released and independently validated.