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
#customer intent: As a developer, I want to use keyless connections so that I don't leak secrets.
10
10
---
11
11
12
-
# Use Azure AI Search without keys
12
+
# Connect your app to Azure AI Search using identities
13
13
14
14
In your application code, you can set up a keyless connection to Azure AI Search that uses Microsoft Entra ID and roles for authentication and authorization. Application requests to most Azure services must be authenticated with keys or keyless connections. Developers must be diligent to never expose the keys in an unsecure location. Anyone who gains access to the key is able to authenticate to the service. Keyless authentication offers improved management and security benefits over the account key because there's no key (or connection string) to store.
Copy file name to clipboardExpand all lines: articles/search/search-get-started-rbac.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Quickstart RBAC
2
+
title: Quickstart keyless connection
3
3
titleSuffix: Azure AI Search
4
4
description: In this quickstart, learn how to switch from API keys to Microsoft Entra identities and role-based access control (RBAC).
5
5
author: HeidiSteen
@@ -12,9 +12,9 @@ ms.date: 11/26/2024
12
12
13
13
# Quickstart: Connect without keys
14
14
15
-
Configure Azure AI Search to use Microsoft Entra ID authentication and roles, including steps for connecting from your local system, running Jupyter notebooks, or using a REST client.
15
+
Configure Azure AI Search to use Microsoft Entra ID authentication and roles. Connect from your local system, running Jupyter notebooks, or using a REST client.
16
16
17
-
If you step through other quickstarts that connect using API keys, these steps show you how to switch to identity-based authentication and avoid hard-coded API keys in your example code.
17
+
If you stepped through other quickstarts that connect using API keys, this quickstart shows you how to switch to identity-based authentication so that you can avoid hard-coded API keys in your example code.
18
18
19
19
## Prerequisites
20
20
@@ -36,6 +36,8 @@ This step is necessary if you have more than one subscription or tenant.
36
36
37
37
1. Select the subscription name to view the parent management group (tenant ID).
38
38
39
+
:::image type="content" source="media/search-security-rbac/select-subscription-name.png" lightbox="media/search-security-rbac/select-subscription-name.png" alt-text="Screenshot of the portal page providing the subscription name":::
40
+
39
41
1. Identify the active Azure subscription and tenant on your local device:
40
42
41
43
`az account show`
@@ -68,7 +70,7 @@ This step is necessary if you have more than one subscription or tenant.
68
70
69
71
1. Select **+ Add** > **Add role assignment**.
70
72
71
-
1. Choose a role (Search Service Contributor, Search Index Data Contributor, Search Index Data Reader) and assign it to your Microsoft Entra user or group identity. These three roles provide the full set of permissions for creating, loading, and querying objects on Azure AI Search.
73
+
1. Choose a role (Search Service Contributor, Search Index Data Contributor, Search Index Data Reader) and assign it to your Microsoft Entra user or group identity. These three roles provide the full set of permissions for creating, loading, and querying objects on Azure AI Search. For more information, see [Connect using roles](search-security-rbac.md).
72
74
73
75
## Step 3: Connect from your local system
74
76
@@ -133,9 +135,9 @@ Several quickstarts and tutorials use a REST client, such as Visual Studio Code
133
135
134
136
Configure a managed identity for outbound connections:
135
137
136
-
-Assign a system-assigned or user-assigned managed identity to your search service.
137
-
- Use role assignments to authorize access to other Azure resources.
138
+
-[Configure a system-assigned or user-assigned managed identity](search-howto-managed-identities-data-sources.md) for your search service.
139
+
-[Use role assignments](keyless-connections.md) to authorize access to other Azure resources.
138
140
139
141
Network access configuration:
140
142
141
-
- Set up inbound rules to accept or reject requests to Azure AI Search based on IP address.
143
+
-[Set inbound rules](service-configure-firewall.md) to accept or reject requests to Azure AI Search based on IP address.
0 commit comments