Share via

User Add/Delete Webhook Issue/Not Notify on my server

Charmi 0 Reputation points
2026-05-11T04:15:54.2466667+00:00

Hi, I want to use the user created and user deleted webhooks in Azure. I have successfully created the webhook subscription, but I am not receiving webhook triggers on my server when a user is created or deleted in Azure.

Azure API Management
Azure API Management

An Azure service that provides a hybrid, multi-cloud management platform for APIs.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Charmi 0 Reputation points
    2026-05-12T10:30:45.6533333+00:00

    Hi, I have set changeType = "created,updated,deleted" for the webhook subscription. However, whenever a user is created or deleted, I am always receiving the event with changeType = "updated" instead of created or deleted.

    Was this answer helpful?


  2. Siddhesh Desai 7,055 Reputation points Microsoft External Staff Moderator
    2026-05-11T08:56:07.0866667+00:00

    Hi @Charmi

    Thank you for reaching out to Microsoft Q&A.

    From your description, the webhook subscription is getting created successfully, but notifications are not reaching your server when users are created or deleted. In Azure (Microsoft Entra ID / Microsoft Graph change notifications), this usually happens due to either endpoint validation issues, event behavior limitations, or delivery constraints rather than a simple misconfiguration.

    Refer below points to resolve this issue:

    1. Validate Webhook Endpoint Accessibility

    Microsoft Graph sends notifications only if your endpoint is publicly accessible over HTTPS. If your server is behind a firewall, private network, or V-Net, notifications will not be delivered.

    Ensure:

    Endpoint is reachable from internet

    HTTPS is enabled (TLS 1.2)

    No firewall / WAF is blocking requests

    If using APIM / App Gateway → check inbound rules (common blocking cause)

    2. Ensure Proper Validation Handshake

    During subscription creation, Microsoft Graph sends a validation request with a token, and your endpoint must return that token immediately.

    If:

    Token is not echoed exactly

    Response is delayed

    Response format is incorrect

    3. Check Response Time (Critical – 3 seconds rule)

    Your webhook must respond within 3 seconds with a 200 or 202 status.

    If delayed → notifications may be dropped

    Graph retries, but eventually stops delivering

    4. Subscription Expiry / Renewal

    Graph webhook subscriptions are temporary (expire within hours/days depending on resource)

    If subscription expires → no notifications will be delivered

    Must renew subscription before expiry

    Failure to renew is a common reason why webhooks “stop working” suddenly

    5. User Deletion Behavior (Important for your scenario)

    For user deleted events in Azure AD:

    Most deletions are soft deletes first

    Webhook may send:

    updated event (for soft delete)

    deleted only after permanent delete (hard delete)

    Subscribe to:

    changeType = "created,updated,deleted"
    

    6. Delay in Event Delivery

    Graph notifications are not always instant for directory objects

    Delivery can sometimes take time (minutes to hours) depending on backend processing

    7. Verify Subscription Scope & Permissions

    Ensure:

    Resource:

    /users

    Permissions:

    User.Read.All

    Directory.Read.All (recommended)

    If permissions are insufficient → events won’t trigger even though subscription is created

    8. Check Filtering / Incorrect Configuration

    If using Event Grid / APIM along with Graph:

    Verify:

    Filters are not excluding events

    Event types match expected triggers

    Incorrect filters can block delivery entirely

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.