A cloud-based identity and access management service for securing user authentication and resource access
Hello 43091962,
Your setup looks correct. This behavior is expected for /users.
From the documentation:
Creation and soft deletion of users also trigger the updated changeType. Reference: https://learn.microsoft.com/en-us/graph/change-notifications-overview#supported-resources
When a user is created, the system usually performs a few additional updates right after. Because of that, Graph often sends only an updated notification, and created may not come separately.
So "changeType": "created" may not trigger, while "changeType": "created,updated" works.
This is expected behavior. Creation can show up as an updated event, so it’s recommended to include updated when subscribing to /users. There’s no real difference between creating users via Graph API or the Portal in this case.
You can continue with:
"changeType": "created,updated"
Then fetch the user (GET /users/{id}) and use createdDateTime to identify newly created users.