大网数据广告活动
服务器运维问答

Azure storage public endpoint exposed

· 52CE 我爱测

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 resol…

问题原文

原帖链接 · 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.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2020-08-12)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。