Microsoft Entra ID User Provisioning
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
18m ago
Hi everyone,
We are facing a similar scenario where we have configured IP restrictions in ServiceNow using Adaptive Authentication > IP Filter Criteria, and we need to whitelist Microsoft Entra ID provisioning IP ranges to allow SCIM-based user provisioning.
We noticed that the Microsoft Entra provisioning IP list includes both IPv4 and IPv6 ranges. However, ServiceNow's IP Filter Criteria (Subnet/CIDR tab) does not appear to support IPv6 addresses.
Could anyone advise:
1. How did you resolve the IPv6 limitation in ServiceNow's IP Filter Criteria?
2. Was the solution handled at the network/firewall level instead of within ServiceNow?
3. Did whitelisting only the IPv4 ranges suffice for Entra provisioning to work, or are the IPv6 ranges critical?
Any guidance from those who have successfully implemented this would be greatly appreciated.
Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
41 seconds ago
Fortunately When we did AZURE Entra ID integration, we did not face IP address related issue .
We faced similar kind of issue for other tool like Workday,power automate.
That time once we Added Allow rule for the shared IP from 3rd party in Navigate to All > System Security > IP Address Access Control
Check for you if this article is helpful: SCIM Provisioning from Microsoft Entra ID
