@Josh H I just tested using VMs in both East and West and am able to access https://carefirst.com from both the regions. I would suggest looking into the VMs Security group policies/ Routing rules etc., Does this traffic exit directly to the internet or go through a Firewall or something? Do you have any other firewall/security restrictions on these VMs? A good idea is to use Network Watcher to log traffic to/from these VMs and capture them to understand the flow of traffic. Please let us know if you have any further questions or need any further assistance. Thank you!
How to resolve not being able to access a site from an Azure machine. Note: DNS is resolving the IP properly
We have several machines in Azure (Eastern US) and none of them are able to browse to https://carefirst.com. I have pinged from inside an Azure machine and my local machine and the website resolves to the same IP address. This is not a website that is being hosted by our tenant and we have no relationship with CareFirst other than them being an insurance provider. That being said this would not be an internal DNS problem since it is looking to public DNS and resolving properly. We have attempted to run TRACERT but it never responds from any of the Azure machines. I recently did a search and found some information that at least some of the CareFirst infrastructure is being hosted in Azure too. Another step in troubleshooting was moving a VM to the Western US and the site loads properly from there. Has anybody else run into a problem like this? Any tips for resolving?
2 answers
Sort by: Most helpful
-
-
David Tapuchi 6 Reputation points
2021-01-25T16:09:51.587+00:00 I've seen the same issue with provider.carefirst.com being inaccessible. This is most likely due to misconfiguration by Carefirst, not an Azure issue.
I tried contacting their support, but all I got was a ticket number..... Maybe if enough tickets are opened, the issue will be dealt with.