Azure AD SCIM provisioning calls not made from documented CIDR range IP addresses

Connected Identity 40 Reputation points

Our SCIM server is deployed in an environment which is not exposed to public internet (SCIM APIs only accessible internally via company VPN if IPs not whitelisted). For Azure AD SCIM provisioning to work, we have whitelisted the Microsoft Azure CIDR ranges so that calls originating from these IPs will be able to access our SCIM endpoints.

We have picked the CIDR blocks to whitelist from

But, we see that calls are made from different IPs which are not in the CIDR range documented (IPs with which calls were made by Azure AD SCIM provisioning are listed below). Due to this, provisioning is failing.
Azure Active Directory
Azure Active Directory
An Azure enterprise identity service that provides single sign-on and multi-factor authentication.
16,677 questions
0 comments No comments
{count} votes

Accepted answer
  1. Danny Zollner 8,406 Reputation points Microsoft Employee

    The IP addresses ranges that can be used change over time, and the documentation is updated ahead of time to include those new ranges. In the current JSON file I see the ranges and in the AzureActiveDirectory tag, and those ranges combined cover all of the IP addresses you listed above.

    0 comments No comments

0 additional answers

Sort by: Most helpful