Hi Nana Poku ,
your understanding is correct Yes having both public access and a private endpoint enabled on your Azure storage account can indeed cause connectivity issues. When a private endpoint is configured, it creates a private IP address within your virtual network, and the storage account should ideally be accessed through this private endpoint. If public access is also enabled, it can lead to conflicts and connectivity problems because the traffic might not be routed correctly. I suggest few key points to consider,
When a private endpoint is created, a private DNS zone is typically configured to resolve the storage account's FQDN to the private IP address. If public access is enabled, DNS resolution might still point to the public endpoint, causing connectivity issues
Ensure that your storage account's firewall and virtual network rules are configured to allow access only through the private endpoint. Public access should be disabled to avoid conflicts
If you have service endpoints configured, they might interfere with the private endpoint. It's generally recommended to use either service endpoints or private endpoints, but not both simultaneously
Please disable public access on your storage account and ensure that all traffic is routed through the private endpoint. This will help maintain a consistent and secure connection to your storage account.
For more information:
https://learn.microsoft.com/en-us/azure/private-link/tutorial-private-endpoint-storage-portal?tabs=dynamic-ip
Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
If you have any other questions or are still running into more issues, let me know in the "comments" and I would be happy to help you.