The ‘request blocked’ error usually occurs due to blocked HTTP methods, geo restrictions, or missing headers like User-Agent
To fix it:
- Check your CDN or firewall logs using identifiers like the Cloudflare Ray ID to find out which rule caused the block.
- Adjust your security rules to allow SCIM requests.
- Test SCIM operations (fetch, create, update) using Postman to verify the issue.
Download Postman Collection to Test
While performing the test configuration in the SCIM application within Azure AD, you may encounter a ‘request blocked’ error similar to the one shown below.
The error message will typically include details about why the SCIM request from Azure was blocked by your CDN or reverse proxy (such as Cloudflare or AWS CloudFront).
Common reasons for such blocks include restrictions based on the HTTP request type, geolocation, or missing/incorrect headers (e.g., User-Agent). To investigate further, you can extract identifiers from the blocked request (e.g., Cloudflare Ray ID) and review your CDN logs to determine which specific rule caused the block.
Additionally, you can simulate Azure SCIM requests using Postman. I’ve included a Postman collection that allows you to test, fetch, create, and update operations.
Download Postman Collection to Test
Any restrictions applied by your reverse proxy will appear in a similar way to the screenshot below.
