Power Automate - New IP Address Ranges for Power Automate flows using HTTP Actions [MC1045179]

Message ID: MC1045179

Beginning May 1, 2025, Power Automate flows will be leveraging additional service pools to execute flows. This change will impact flows with HTTP actions that connect to resources within your network, if you are restricting inbound traffic into endpoints using firewall rules.

What action do I need to take?
We have detected you are using flows which utilize HTTP actions. To identify flows with HTTP action(s), you can use the available PowerShell cmdlet.

Please update your network firewall configuration to permit traffic from ALL the service tags listed below:

LogicApps
PowerPlatformPlex

If you are not restricting inbound traffic using firewall rules to endpoints that HTTP actions are calling into, no action is required.

More information on Service Tags and how to retrieve associated IP address ranges via API or by downloading the information.

Why is this action needed?
Power Automate needs to update and expand its services infrastructure to maintain its service levels with anticipated usage growth. While we try very hard to ensure services infrastructure updates are transparent to our customers, in this scenario it was not possible to do so.

Failing to update the firewall configuration can cause Power Automate flows using HTTP actions to fail if you are restricting inbound traffic disrupting your business processes that depend on the flows.

Please contact Microsoft Support if you have questions or need assistance.

Source: Microsoft

Mike Rosoft

1 April 2025, 7:14 am

The recent announcement regarding the new IP address ranges for Power Automate flows utilizing HTTP actions is sure to stir up some conversation among both admins and users alike. Starting May 1, 2025, this update will require a bit of proactive attention, particularly for those of you who are managing firewall configurations.

For admins, this means rolling up your sleeves and ensuring that your network firewall is ready to welcome the new service pools. If your organization restricts inbound traffic, the need to adjust your firewall rules to allow traffic from the designated service tags—LogicApps and PowerPlatformPlex—cannot be overlooked. It’s a bit like inviting new friends to a party; you want to make sure the door is open so they can join the fun!

On the user side, the impact may be less direct, but it’s still significant. If your flows are reliant on HTTP actions and the appropriate firewall configurations aren’t set up in time, you may find your automated processes hitting a wall—quite literally! The last thing anyone wants is for their carefully crafted workflows to come to a screeching halt. So, it’s a good idea to keep an eye on these changes and communicate with your IT team to ensure everything is in place.

In terms of overall impact, this update is a necessary step for Power Automate to expand its service infrastructure in response to anticipated growth. While it may require some adjustments now, it’s ultimately a move toward a more robust and scalable platform. Think of it as upgrading your vehicle to a more powerful engine; it might take some time to tune up, but the performance boost is worth it!

As we dive into these changes, I encourage everyone to share their thoughts and experiences. Have you started preparing your firewall configurations? What challenges do you foresee? Let’s keep the conversation going and help each other navigate this transition!

For more insights and updates, don’t forget to check out other posts on mwpro.co.uk!

1 Comment

Mike Rosoft


1 April 2025, 7:14 am

The recent announcement regarding the new IP address ranges for Power Automate flows utilizing HTTP actions is sure to stir up some conversation among both admins and users alike. Starting May 1, 2025, this update will require a bit of proactive attention, particularly for those of you who are managing firewall configurations.

For admins, this means rolling up your sleeves and ensuring that your network firewall is ready to welcome the new service pools. If your organization restricts inbound traffic, the need to adjust your firewall rules to allow traffic from the designated service tags—LogicApps and PowerPlatformPlex—cannot be overlooked. It’s a bit like inviting new friends to a party; you want to make sure the door is open so they can join the fun!

On the user side, the impact may be less direct, but it’s still significant. If your flows are reliant on HTTP actions and the appropriate firewall configurations aren’t set up in time, you may find your automated processes hitting a wall—quite literally! The last thing anyone wants is for their carefully crafted workflows to come to a screeching halt. So, it’s a good idea to keep an eye on these changes and communicate with your IT team to ensure everything is in place.

In terms of overall impact, this update is a necessary step for Power Automate to expand its service infrastructure in response to anticipated growth. While it may require some adjustments now, it’s ultimately a move toward a more robust and scalable platform. Think of it as upgrading your vehicle to a more powerful engine; it might take some time to tune up, but the performance boost is worth it!

As we dive into these changes, I encourage everyone to share their thoughts and experiences. Have you started preparing your firewall configurations? What challenges do you foresee? Let’s keep the conversation going and help each other navigate this transition!

For more insights and updates, don’t forget to check out other posts on mwpro.co.uk!

Power Automate – New IP Address Ranges for Power Automate flows using HTTP Actions [MC1045179]

1 Comment

Leave a Reply Cancel reply