问题原文
原帖链接 · UserControl · CC BY-SA 4.0
I have a storage account configured to be accessible via Private Link only as depicted below. Within the VNET MYSTORAGE.table.core.windows.net resolves to a private IP and the application works just fine. On the internet it resolves like this:
C:\>nslookup MYSTORAGE.table.core.windows.net 8.8.8.8
Server: dns.google
Address: 8.8.8.8
Non-authoritative answer:
Name: table.sat03prdstr20a.store.core.windows.net
Address: 20.150.38.xxx
Aliases: MYSTORAGE.table.core.windows.net
MYSTORAGE.privatelink.table.core.windows.net
which I don't mind. But I don't understand why I'm able to connect to it:
C:\>telnet MYSTORAGE.table.core.windows.net 443
In my understanding once I disable 'All networks' I shouldn't be able to connect to it from the world. What am I missing?
已采纳解答
原帖链接 · Sam Cogan · CC BY-SA 4.0
Yes, this is by design. Azure Storage is a multi-tenant service. I would imagine that the endpoints you connect to to get into the service are shared between many customers and so allow all connections. It is at the point you try to access your specific storage account, that the network rules are applied and access is allowed or not.
If you cannot connect using storage explorer then it is working as expected.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
