Azure 搜索索引 Cosmos DB 所需的 IP 地址/范围
IP addresses / ranges required for Azure Search to index Cosmos DB
我有一个锁定到 vnet（及其子网）的 Cosmos DB，我希望这个 Cosmos DB 成为 Azure 搜索的数据源。
当我尝试配置它时，它抱怨被防火墙阻止。
- 如果我启用 "Accept connections from within public Azure datacenters" 它仍然抱怨被防火墙阻止。
- 如果我删除“接受来自 public Azure 数据中心的连接
" 设置并授予对以下 IP 13.76.208.129 的访问权限它有效。
集成实际上只需要 13.76.208.129 还是我需要添加到防火墙中的更大范围？
如本文所述documentation page：
If your search service has only one search unit (that is, one replica
and one partition), the IP address will change during routine service
restarts, invalidating an existing ACL with your search service's IP
address.
One way to avoid the subsequent connectivity error is to use more than
one replica and one partition in Azure Search. Doing so increases the
cost, but it also solves the IP address problem. In Azure Search, IP
addresses don't change when you have more than one search unit.
我有一个锁定到 vnet（及其子网）的 Cosmos DB，我希望这个 Cosmos DB 成为 Azure 搜索的数据源。
当我尝试配置它时，它抱怨被防火墙阻止。
- 如果我启用 "Accept connections from within public Azure datacenters" 它仍然抱怨被防火墙阻止。
- 如果我删除“接受来自 public Azure 数据中心的连接 " 设置并授予对以下 IP 13.76.208.129 的访问权限它有效。
集成实际上只需要 13.76.208.129 还是我需要添加到防火墙中的更大范围？
如本文所述documentation page：
If your search service has only one search unit (that is, one replica and one partition), the IP address will change during routine service restarts, invalidating an existing ACL with your search service's IP address.
One way to avoid the subsequent connectivity error is to use more than one replica and one partition in Azure Search. Doing so increases the cost, but it also solves the IP address problem. In Azure Search, IP addresses don't change when you have more than one search unit.