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/service-configure-firewall.md
+14-4Lines changed: 14 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,17 +10,19 @@ ms.service: cognitive-search
10
10
ms.custom:
11
11
- ignite-2023
12
12
ms.topic: how-to
13
-
ms.date: 06/18/2024
13
+
ms.date: 06/27/2024
14
14
---
15
15
16
16
# Configure network access and firewall rules for Azure AI Search
17
17
18
-
As soon as you install Azure AI Search, you can set up network access to limit access to an approved set of devices and cloud services. There are two mechanisms:
18
+
By default, Azure AI Search is configured for connections over a public endpoint. Access to a search service *through* the public endpoint is protected by authentication and authorization protocols, but the endpoint itself is open to the internet at the network layer.
19
+
20
+
If you aren't hosting a public web site, you might want to configure network access to automatically refuse requests unless they originate from an approved set of devices and cloud services. There are two mechanisms:
19
21
20
22
+ Inbound rules listing the IP addresses, ranges, or subnets from which requests are admitted
21
23
+ Exceptions to network rules, where requests are admitted with no checks, as long as the request originates from a [trusted service](#grant-access-to-trusted-azure-services)
22
24
23
-
Network rules aren't required, but it's a security best practice to add them.
25
+
Network rules aren't required, but it's a security best practice to add them if you use Azure AI Search for intranet or internal corporate network scenarios.
24
26
25
27
Network rules are scoped to data plane operations against the search service's public endpoint. Data plane operations include creating or querying indexes, and all other actions described by the [Search REST APIs](/rest/api/searchservice/). Control plane operations target service administration. Those operations specify resource provider endpoints, which are subject to the [network protections supported by Azure Resource Manager](/security/benchmark/azure/baselines/azure-resource-manager-security-baseline).
26
28
@@ -34,6 +36,14 @@ This article assumes the Azure portal for network access configuration. You can
34
36
35
37
+ Owner or Contributor permissions
36
38
39
+
## Limitations
40
+
41
+
There are a few drawbacks to locking down the public endpoint.
42
+
43
+
+ It takes time to fully identify IP ranges and set up firewalls, and if you're in early stages of proof-of-concept testing and investigation and using sample data, you might want to defer network access controls until you actually need them.
44
+
45
+
+ Some workflows require access to a public endpoint. Specifically, the [Import and vectorize data wizard](search-get-started-portal-import-vectors.md) in the Azure portal currently connects to embedding models over the public endpoint. You can switch to code or script to complete the same tasks, but if you want to try the wizard, the public endpoint must be available.
46
+
37
47
<aid="configure-ip-policy"></a>
38
48
39
49
## Configure network access in Azure portal
@@ -140,7 +150,7 @@ Once a request is allowed through the firewall, it must be authenticated and aut
140
150
141
151
+[Key-based authentication](search-security-api-keys.md), where an admin or query API key is provided on the request. This is the default.
142
152
143
-
+[Role-based access control (RBAC)](search-security-rbac.md) using Microsoft Entra ID, where the caller is a member of a security role on a search service. This is the most secure option. It uses Microsoft Entra ID for authentication and role assignments on Azure AI Search for permissions to data and operations.
153
+
+[Role-based access control](search-security-rbac.md) using Microsoft Entra ID, where the caller is a member of a security role on a search service. This is the most secure option. It uses Microsoft Entra ID for authentication and role assignments on Azure AI Search for permissions to data and operations.
144
154
145
155
> [!div class="nextstepaction"]
146
156
> [Enable RBAC on your search service](search-security-enable-roles.md)
0 commit comments