July 1, 2020 at 11:54 am
Hi,
This may seem a strange qustion but I'm struggling to get my head around it. I have created a storage account and container for my backups and all was working fine backing up to https://*****.blob.core.windows.net/mycontainer. There was then a question from the network admin around use of private endpoints and internal IP's to ensure data in transit went through our VPN rather than over the internet, data security and encryption in transit the main concern.
I then went on to create a private endpoint on one of the subnets which are categorized by our firewall as Azure traffic. I did not use the integrate with our DNS option but using the private IP address created a record in DNS using the *****.blob.core.windows.net but replacing the domain with our local domain eg *****.mydomin.myroot.com but my backups are failing when referencing this.
So my question is... How can I backup to the storage container using either my local dns creation or the IP? 10.0.0.0/mycontainer or **.mydomin.myroot.com/mycontainer both fail.
I am trying to do something completely unreasonable or unsupported
I appreicate the above may be confusing so if I can clear any questions up please let me know.
We have a VPN not express route
Thanks
V5
July 2, 2020 at 12:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
September 5, 2020 at 9:07 pm
Do you have a machine in Azure, can you ping from on-premise to check Azure network?
use PSPING to test the above to ensure that the VPN tunnel is used instead of internet. If all is good, try URL backup using SSMS to save the file in Azure container.
=======================================================================
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply