Escalations
This page is for administrators and developers building an endpoint to receive these events.
EasyLife 365 Identity sends this payload when an ownership rule escalates on an application: the owners were reminded, the reminders ran out, and the application still does not meet the rule. How to configure the webhook, and how it authenticates, is described in Overview.
HTTP request
POST YourApiUrl
Content-Type: application/json
{
"eventType": "MinimumOwnersPolicyEscalation",
"appName": "Contoso Payroll",
"appObjectId": "8f4d0e7a-1234-1xw2x-yz34-9b2c5de61f08",
"escalationType": 1,
"policy": {
"pId": "fa2c0672-1234-1xw2x-yz34-aa09fc31672b",
"owSt": "escalate",
"owSta": "incompliant",
"owStCh": "2026-09-11T08:30:00Z"
},
"tenantId": "1840b34e-1234-1xw2x-yz34-0b7b58c49dc7"
}
Fields
| Field | Description |
|---|---|
eventType | The rule that escalated, as a readable name. Use this to route the event. |
appName | The display name of the application at the time of the escalation. |
appObjectId | The object ID of the application in Microsoft Entra ID. Use this to look the application up, because a display name can change. |
escalationType | The same information as eventType, as a number. Retained for receivers built before eventType existed. |
policy | The application's current policy state. See The policy object. |
tenantId | The Microsoft Entra ID tenant the application belongs to. |
Event types
eventType | escalationType | Rule |
|---|---|---|
MinimumOwnersPolicyEscalation | 1 | Minimum Application Owners |
MinimumTechnicalOwnersPolicyEscalation | 2 | Minimum Technical Owners |
MinimumBusinessOwnersPolicyEscalation | 3 | Minimum Business Owners |
InactivityPolicyEscalation | 4 | Activity |
BaselineConfigurationPolicyEscalation | 5 | Baseline Configuration |
eventType and escalationType always describe the same escalation, and both are always sent. Prefer eventType: it is readable, and it matches how the other EasyLife 365 products name their escalations.
The policy object
policy is the policy state recorded on the application at the moment the escalation was raised. It is the same record EasyLife 365 Identity uses internally, so its property names are abbreviated and it carries state for every rule the policy evaluates, not only the one that escalated.
The names follow a pattern. A two-letter rule prefix is followed by what the value holds:
| Prefix | Rule |
|---|---|
ow | Minimum Application Owners |
to | Minimum Technical Owners |
bo | Minimum Business Owners |
in | Activity |
bc | Baseline Configuration |
| Suffix | Holds |
|---|---|
St | The step the rule has reached: reminder0 through reminderN while the owners are still being reminded, then escalate. |
Sta | The compliance state of the rule: compliant or incompliant. |
StCh | When that step last changed, in UTC. |
pId is the identifier of the policy governing the application.
Treat everything inside policy as informational. It is an internal record, the set of properties present depends on which rules the policy configures, and property names may change. Route on eventType and identify the application with appObjectId.
Response
Answer with a 2xx status within 30 seconds. No response body is expected.
Anything else is treated as a failed delivery and retried, as described in Delivery and retries.