Hi David Michaelis,
I understand that this is incredibly, it's odd that the same ISP would have different policies for different locations. Hopefully, their escalation will resolve the issue soon.
In the meantime, you might consider using an alternative method to access your Azure file storage. I Suggest a couple of options:
VPN: Set up a VPN connection from your Oakland office to a location where port 445 is not blocked. This can help bypass the restriction.
Azure File Sync: Use Azure File Sync to synchronize your Azure file shares with an on-premises server. This way, your users can access the files locally without needing to connect directly to Azure file storage.
SMB over QUIC: If you have Windows Server 2022, you can use SMB over QUIC, which allows SMB traffic to be encapsulated in a QUIC connection, bypassing the need for port 445.
I hope one of these solutions can serve as a temporary workaround until your ISP resolves the issue. Let me know if you need more details on any of these options.
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.