We have a servers running in Azure with a B2B. Recently they started using BLOB storage and to load the data into the blob it goes to a public IP outside of our B2B. We like to control where our Servers go out to the internet but the problem is that there 100's of addresses (maybe a 1000) that are used by AZURE in North America)
Does anyone have a good way to get this under control with a policy of some sort so we can say Server X can to to Azure but only these azure IPs in the public internet?
Thanks for your time
If I understand the question correctly you can use User Defined Routes in the route table. You can state the IP's that have internet access to go to the internet gateway for 0.0.0.0/0.
You may have more context but based on what I see this would be the way to move forward.
Also you can force static IP's onto your Azure servers so that they wont change. Another way would be to use dynamic IP's and use the automaticlly created DNS entries as your allow source/destinations.
Just some thoughts.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!