Skip to content

Commit af0e6bb

Browse files
committed
formatting and readability
1 parent 36372fd commit af0e6bb

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/search/search-security-overview.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -15,13 +15,13 @@ ms.date: 08/15/2025
1515

1616
# Security in Azure AI Search
1717

18-
Azure AI Search provides comprehensive security controls across network access, authentication, authorization, and data protection to meet enterprise requirements. As a solution architect, you should understand three key security domains:
18+
Azure AI Search provides comprehensive security controls across network access, data access, and data protection to meet enterprise requirements. As a solution architect, you should understand three key security domains:
1919

20-
+ **Network traffic patterns and network security** (inbound client requests, outbound service connections, and internal Microsoft-managed traffic)
21-
+ **Access control mechanisms** (Microsoft Entra ID with role-based access control or API key authentication)
22-
+ **Data residency and protection** (encryption in transit via TLS 1.2/1.3, encryption at rest with optional customer-managed keys for double encryption).
20+
+ **Network traffic patterns and network security** - inbound requests, outbound service connections, and internal traffic
21+
+ **Access control mechanisms** - Microsoft Entra ID with roles, or API keys
22+
+ **Data residency and protection** - encryption in transit, and at rest with optional double encryption
2323

24-
A search service supports multiple network security topologies—from IP firewall restrictions for basic protection to private endpoints for complete network isolation. For enterprise scenarios requiring granular permissions, you can implement document-level access controls and leverage network security perimeters to create logical boundaries around your Azure PaaS resources. All security features integrate with Azure's compliance framework and support common enterprise patterns like multitenancy and cross-service authentication using managed identities.
24+
A search service supports multiple network security topologies—from IP firewall restrictions for basic protection to private endpoints for complete network isolation. Optionally, leverage network security perimeters to create logical boundaries around your Azure PaaS resources. For enterprise scenarios requiring granular permissions, you can implement document-level access controls. All security features integrate with Azure's compliance framework and support common enterprise patterns like multitenancy and cross-service authentication using managed identities.
2525

2626
This article details the implementation options for each security layer to help you design appropriate security architectures for development and production environments.
2727

@@ -121,9 +121,9 @@ While this solution is the most secure, using more services is an added cost so
121121

122122
### Network security perimeter
123123

124-
A network security perimeter is a logical network boundary around your platform-as-a-service (PaaS) resources that are deployed outside of a virtual network. It establishes a perimeter for controlling public network access to resources like Azure AI Search, Azure Storage, and Azure OpenAI. Inbound client connections and service-to-service connections occur within the boundary, which simplifies and strengthens your defenses against unauthorized access.
124+
A network security perimeter is a logical network boundary around your platform-as-a-service (PaaS) resources that are deployed outside of a virtual network. It establishes a perimeter for controlling public network access to resources like Azure AI Search, Azure Storage, and Azure OpenAI. You can grant exceptions through explicit access rules for inbound and outbound traffic. This approach helps prevent data exfiltration while maintaining necessary connectivity for your applications.
125125

126-
It's common in Azure AI Search solutions to use multiple Azure resources. The following resources can all be joined to an [existing network security perimeter](/azure/private-link/create-network-security-perimeter-portal):
126+
Inbound client connections and service-to-service connections occur within the boundary, which simplifies and strengthens your defenses against unauthorized access. It's common in Azure AI Search solutions to use multiple Azure resources. The following resources can all be joined to an [existing network security perimeter](/azure/private-link/create-network-security-perimeter-portal):
127127

128128
+ [Azure AI Search](search-security-network-security-perimeter.md)
129129
+ [Azure OpenAI](/azure/ai-foundry/openai/how-to/network-security-perimeter)

0 commit comments

Comments
 (0)