Azure DevOps Service Hooks: No Event for Sprint (Iteration) Creation?

Question

I am working with Azure DevOps and trying to implement an event-driven integration using Service Hooks (webhooks).

My requirement is to trigger an event whenever a new sprint (iteration) is created in Azure Boards.

However, after reviewing the available Service Hook events, I could not find any event related to:

• Iteration (Sprint) creation
• Iteration updates or deletion

What I have checked:

• Service Hooks documentation
• Work Item events (created/updated)
• Team settings and iterations API

My understanding:

It seems that iterations are part of team configuration (metadata) and not treated as work items, so they do not emit Service Hook events.

Questions:

1. Is there any Service Hook event available for sprint/iteration creation?
2. If not, is there any recommended way to detect newly created sprints in near real-time?
3. Is polling the iterations API the only supported approach?

Any clarification or official confirmation would be helpful.

Thanks in advance!

Answer 1

Hi @Kroolo Dev

Thank you for reaching out to Microsoft Q&A.

At this time, Azure DevOps Service Hooks do not provide any event triggers for sprint (iteration) creation, updates, or deletion. This is because iterations are treated as project and team configuration metadata, not as work items. Service Hooks only fire for events that are explicitly published by Azure DevOps (such as work item created/updated, pipeline events, repository events, etc.). Since iteration paths are managed as classification nodes under project settings and not part of the work item store, no Service Hook publisher exists for iteration lifecycle changes. As a result, creating or modifying sprints does not emit any webhook or event natively.

Refer below points to resolve this issue or this is the workaround:

Polling Iterations (Classification Nodes) REST API (Recommended Approach)

• Since there is no Service Hook support, polling the Iterations API is the only supported and reliable solution.
• You can periodically call the Azure DevOps REST API for iterations and compare the results with a previously stored snapshot to detect newly created sprints.
• This approach is commonly used with Azure Functions, Logic Apps, Power Automate (scheduled flows), or background jobs.

Use Team or Process Automation as a Controlled Workaround

• If your organization controls how sprints are created, consider enforcing sprint creation through a script, pipeline, or internal automation.
• Your automation can then emit a custom webhook or event at sprint creation time, effectively filling the gap left by missing native events.

No Existing Service Hook or Event-Based Alternative

• Work Item Created/Updated events cannot be used because iterations are not work items.
• Pipeline, repository, or audit-related Service Hooks also do not capture iteration configuration changes.
• As of now, Azure DevOps does not offer any near real-time, event-driven trigger for sprint or iteration lifecycle changes outside of polling.

Answer 2

1. No service hook event exists for sprint/iteration creation, update, or deletion.

Service hooks in Azure DevOps expose events for builds, pipelines, code, service connections, work items, and advanced security alerts, as listed under Available event types. The work item category only covers:

• Work item created
• Work item deleted
• Work item restored
• Work item updated
• Work item commented on

Iterations/sprints are not listed as a supported event type and are not work items, so they do not emit service hook events.

2. There is no documented near–real-time event-based mechanism for sprint/iteration changes.

The service hook overview and event catalog only describe events for the supported publishers and event types shown (build, pipeline, code, work item, advanced security, etc.). Iteration metadata changes are not among them, and there is no separate “Boards/Iterations” publisher or event.

3. Polling the iterations API (or equivalent metadata source) is the supported pattern.

Given that:

• Service hooks only trigger on the documented event types
• Iterations are not represented there

The practical approach is to periodically poll the relevant Azure DevOps APIs for iteration changes and react when new or modified sprints are detected. Service hooks can still be used for other events (for example, work item created/updated within a sprint), but not for the creation of the sprint itself.

---

References:

• Service hook events
• Integrate with service hooks