Skip to content

Commit 8821f34

Browse files
committed
Security doc edits, promote network access
1 parent b8e44d0 commit 8821f34

File tree

2 files changed

+21
-11
lines changed

2 files changed

+21
-11
lines changed

articles/search/TOC.yml

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -420,28 +420,28 @@
420420
href: index-add-scoring-profiles.md
421421
- name: Security
422422
items:
423-
- name: Enable role-based access control
423+
- name: Configure network access
424+
href: service-configure-firewall.md
425+
- name: Enable role-based access
424426
href: search-security-enable-roles.md
425-
- name: Configure a managed identity
426-
href: search-howto-managed-identities-data-sources.md
427+
- name: Assign roles (users and groups)
428+
href: search-security-rbac.md
427429
- name: Inbound connections
428430
items:
429431
- name: Connect using API keys
430432
href: search-security-api-keys.md
431-
- name: Connect using Azure roles
432-
href: search-security-rbac.md
433433
- name: Code without keys
434434
href: keyless-connections.md
435435
- name: Configure apps for Microsoft Entra ID
436436
href: search-howto-aad.md
437-
- name: Configure an IP firewall
438-
href: service-configure-firewall.md
439437
- name: Create a private endpoint
440438
href: service-create-private-endpoint.md
441439
- name: Troubleshoot private connections
442440
href: troubleshoot-shared-private-link-resources.md
443441
- name: Outbound connections
444442
items:
443+
- name: Configure a managed identity
444+
href: search-howto-managed-identities-data-sources.md
445445
- name: Connect as a trusted service
446446
href: search-indexer-howto-access-trusted-service-exception.md
447447
- name: Connect using a managed identity

articles/search/service-configure-firewall.md

Lines changed: 14 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,17 +10,19 @@ ms.service: cognitive-search
1010
ms.custom:
1111
- ignite-2023
1212
ms.topic: how-to
13-
ms.date: 06/18/2024
13+
ms.date: 06/27/2024
1414
---
1515

1616
# Configure network access and firewall rules for Azure AI Search
1717

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:
1921

2022
+ Inbound rules listing the IP addresses, ranges, or subnets from which requests are admitted
2123
+ 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)
2224

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.
2426

2527
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).
2628

@@ -34,6 +36,14 @@ This article assumes the Azure portal for network access configuration. You can
3436

3537
+ Owner or Contributor permissions
3638

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+
3747
<a id="configure-ip-policy"></a>
3848

3949
## Configure network access in Azure portal
@@ -140,7 +150,7 @@ Once a request is allowed through the firewall, it must be authenticated and aut
140150

141151
+ [Key-based authentication](search-security-api-keys.md), where an admin or query API key is provided on the request. This is the default.
142152

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.
144154

145155
> [!div class="nextstepaction"]
146156
> [Enable RBAC on your search service](search-security-enable-roles.md)

0 commit comments

Comments
 (0)