search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.22k stars 21.38k forks source link

How to configure Azure Storage firewall with AzureCognitiveSearch IP address Ranges #59666

Closed kspoojary closed 4 years ago

kspoojary commented 4 years ago

How to configure Azure Storage firewall with AzureCognitiveSearch IP address Ranges when storage account has the IP rule limited to 100, where as AzureCognitiveSearch has more then 100 IP address ranges?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

NavtejSaini-MSFT commented 4 years ago

@kspoojary We are checking this and we will get back to you regarding the same.

BryanTrach-MSFT commented 4 years ago

There are a few options that you have.

  1. Use this document. Find the region that your Azure Cognitive Search service is running in. Each region only has a few IPs for Cognitive Search, which makes life easier.
  2. Place your cognitive search service into a virtual network and then add the virtual network to your Azure Storage Account firewall.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

kspoojary commented 4 years ago

Hi @BryanTrach-MSFT , The link you shared https://docs.microsoft.com/en-us/azure/cognitive-services/cognitive-services-virtual-networks?tabs=portal is to set up virtual network for Azure Convective Services but I am using Azure Search service and we do not have option to set the vnet in search service. But I tried using Private endpoint for search service and added the subnet used for private endpoint to the storage Vnet rules and added all the AzureCognitiveSearch IPs in IP Rule, but I am not able to create the indexer , I am always getting below error Error with data source: Credentials provided in the connection string are invalid or have expired.\r\nFor more informatio n on troubleshooting connection issues to Azure Storage accounts, please see https://go.microsoft.com/fwlink/?linkid=2049388 Please adjust your data so urce definition in order to proceed.

Subnet1 address space : 10.2.3.0/24 PrivateEndpoint1 private IP : 10.2.3.5 Subnet1 is already added to storage vnet rule along with IP rule (Azure cognitive Search IPs)

Can you please let me know what IP rule and Vnet rule I have to set , If my search service is using PrivateEndpoint1 in Subnet1

Note: Storage account and search service are in the same region

sandeep57 commented 1 year ago

Creating shared private access from cognitive search to the blob storage should solve the issue