Hi all
I recently added ip restrictions to our dev and test sites in Azure. However it had a side effect of causing Courier to also return a 403 error even though I granted access to any applications inside the Azure Resource Group. Anyone else have experience of this?
I have the answer. It's a bit tedious, but....
In Azure, open one of your web apps and go to the Properties blade.
Copy all the IP addresses listed as ADDITIONAL OUTBOUND IP ADDRESSES.
Then open the Networking blade and add a rule allowing each IP address.
You will also have to set these rules on all your other apps where you want to courier content. If they are inside the same Resource Group they should be the same IPs.
We had a similar issue on an IP protected site on Azure but somehow it was working fine until a few days ago. Something in Azure must have changed in the last few days affecting the IP ranges. After reading this thread I added the additional outound IPs and is all good now.
Good stuff. It's a shame you can't just set this at a resource group level. It's bad enough with 3 web apps to cover, but if we had loads more it would get really difficult. I think you can do it programatically via the Azure API but haven't ventured there yet.
IP Restriction causes Courier 403
Hi all I recently added ip restrictions to our dev and test sites in Azure. However it had a side effect of causing Courier to also return a 403 error even though I granted access to any applications inside the Azure Resource Group. Anyone else have experience of this?
Paul
Same issue here, it works fine without the ip restriction. I will search a bit and come back. If you find something please let me know.
Thanks, Giuliano
Hi Giuliano
I have the answer. It's a bit tedious, but.... In Azure, open one of your web apps and go to the Properties blade.
Copy all the IP addresses listed as ADDITIONAL OUTBOUND IP ADDRESSES. Then open the Networking blade and add a rule allowing each IP address.
You will also have to set these rules on all your other apps where you want to courier content. If they are inside the same Resource Group they should be the same IPs.
Courier will then work.
We had a similar issue on an IP protected site on Azure but somehow it was working fine until a few days ago. Something in Azure must have changed in the last few days affecting the IP ranges. After reading this thread I added the additional outound IPs and is all good now.
Good stuff. It's a shame you can't just set this at a resource group level. It's bad enough with 3 web apps to cover, but if we had loads more it would get really difficult. I think you can do it programatically via the Azure API but haven't ventured there yet.
https://docs.microsoft.com/en-us/azure/app-service/app-service-ip-restrictions#programmatic-manipulation-of-ip-restriction-rules
is working on a reply...