IP Address access controlled instance integrating with Microsoft Power Automate
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2024 12:20 PM
We are currently working building an integration utilizing Microsoft Power Automate to facilitate the communication between ServiceNow and our system of entry but running into a hiccup. We have IP Address Restriction turned on in our instances to limit the traffic of our instances to only our company's IP range and then we whitelist third party integration IPs as needed (normally a small range or just one IP).
When allowing Microsoft to communicate with ServiceNow, Microsoft provided a list of 24+ ranges and then additional 20 standalone IPs. They have also stated that these are subject to change over time.
This raised my eyebrow as that is a lot of upkeep and a lot of open connections to allow. Does anyone have experience with integrating with with Microsoft and/or encountered this same challenge? Shy of just whitelisting every single one and maintaining it over time, the thought of a custom REST message to Microsoft to gather all IPs and then script the entry into the IP table on some schedule crossed our mind, but also seems like a lot of development and up keep.
- Labels:
-
Architect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2025 12:15 PM
@burnworthr were you able to find a better solution? I'm in a similar situation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2025 07:52 AM
Hi Jessica,
Yes we came up with a solution that fit our needs. We ended up cutting out the middle man (Power Automate) and now have ServiceNow call a PowerShell script on the mid server to call directly to the system via ECC Queue. Being an outbound call, IP range is not a factor and this also simplified our integration flow taking out a potential point of failure.
