Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
Thanks for reaching out and for sharing the details — including the IP rule that got things working again. Glad to hear it's back up!
The issue you're seeing is common with Azure App Service access restrictions (inbound firewall rules). Once you add any allow rules, the default behavior becomes "deny all" for other traffic. Power Automate (and Logic Apps) calls your web app from dynamic Microsoft-managed IP addresses, so you need to explicitly allow them.
Recommended Fix (Best Practice)
Instead of adding individual IP addresses (which can change), use Azure Service Tags. These are Microsoft-maintained groups of IP ranges that update automatically.
In your App Service > Networking > Access restrictions (Inbound traffic):
- Add an Allow rule with Type = Service Tag.
- Use the following tags (start with these):
- AzureConnectors (primary one for managed connectors)
- LogicApps
- PowerPlatformPlex (recommended for broader Power Platform traffic)
- LogicApps
- AzureConnectors (primary one for managed connectors)
Set a sensible priority (lower numbers = higher priority) and give the rule a clear name like "Allow Power Automate".
This should resolve the connectivity without manual IP maintenance
Reference :
https://learn.microsoft.com/en-us/power-automate/ip-address-configuration
https://learn.microsoft.com/en-us/connectors/common/outbound-ip-addresses
https://learn.microsoft.com/en-us/azure/app-service/app-service-ip-restrictions?tabs=azurecli
If the answer is helpful, Please do click "Accept the answer” and Yes, this can be beneficial to other community members.
If you have any other questions, let me know in the "comments" and I would be happy to help you