You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/search/search-indexer-troubleshooting.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ Indexers can run into a number of issues when indexing data into Azure Cognitive
22
22
## Connection Errors
23
23
24
24
> [!NOTE]
25
-
> Indexers have limited support for accessing data sources and other resources that are secured by Azure network security mechanisms. Currently, indexers can only access data sources via corresponding IP whitelisting mechanisms or NSG rules when applicable. Details for accessing each supported data source can be found below. Full featured support is currently planned for release at a future date.
25
+
> Indexers have limited support for accessing data sources and other resources that are secured by Azure network security mechanisms. Currently, indexers can only access data sources via corresponding IP address range restriction mechanisms or NSG rules when applicable. Details for accessing each supported data source can be found below. Full featured support is currently planned for release at a future date.
26
26
>
27
27
> You can find out the IP address of your search service by pinging its fully qualified domain name (eg., `<your-search-service-name>.search.windows.net`).
28
28
>
@@ -35,17 +35,17 @@ Azure Storage, CosmosDB and Azure SQL provide a configurable firewall. There's n
35
35
There are 2 options for allowing indexers to access these resources in such an instance:
36
36
37
37
1. Disable the firewall, by allowing access from **All Networks** (if feasible).
38
-
2. Alternatively, you can IP whitelist the IP address of your search service and the IP address range of `AzureCognitiveSearch`[service tag](https://docs.microsoft.com/azure/virtual-network/service-tags-overview#available-service-tags) in the firewall rules of your data source.
38
+
2. Alternatively, you can allow access for the IP address of your search service and the IP address range of `AzureCognitiveSearch`[service tag](https://docs.microsoft.com/azure/virtual-network/service-tags-overview#available-service-tags) in the firewall rules of your resource (IP address range restriction).
39
39
40
-
Details for configuring IP whitelisting for each data source type can be found from the following links:
40
+
Details for configuring IP address range restrictions for each data source type can be found from the following links:
**Limitation**: As stated in the documentation above for Azure Storage, IP whitelisting will only work if your search service and your storage account are in different regions.
48
+
**Limitation**: As stated in the documentation above for Azure Storage, IP address range restrictions will only work if your search service and your storage account are in different regions.
49
49
50
50
Azure functions (that could be used as a [Custom Web Api skill](cognitive-search-custom-skill-web-api.md)) also support [IP address restrictions](https://docs.microsoft.com/azure/azure-functions/ip-addresses#ip-address-restrictions). The list of IP addresses to configure would be the IP address of your search service and the IP address range of `AzureCognitiveSearch` service tag.
0 commit comments