Skip to content

Commit 760144e

Browse files
committed
rbac updates
1 parent ec9814b commit 760144e

File tree

1 file changed

+10
-12
lines changed

1 file changed

+10
-12
lines changed

articles/search/search-get-started-rbac.md

Lines changed: 10 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ You need this step if you have more than one subscription or tenant.
3434

3535
1. Notice the subscription name and ID in **Overview** > **Essentials**.
3636

37-
1. Now select the subscription name to confirm the parent management group (tenant ID) on the next page.
37+
1. Now select the subscription name to show the parent management group (tenant ID) on the next page.
3838

3939
:::image type="content" source="media/search-get-started-rbac/select-subscription-name.png" lightbox="media/search-get-started-rbac/select-subscription-name.png" alt-text="Screenshot of the portal page providing the subscription name":::
4040

@@ -52,12 +52,6 @@ You need this step if you have more than one subscription or tenant.
5252
az login --tenant <your-tenant-id>
5353
```
5454

55-
1. Verify your tenant ID:
56-
57-
```azurecli
58-
az account show --query tenantId --output tsv
59-
```
60-
6155
## Step 2: Configure Azure AI Search for RBAC
6256

6357
1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to your Azure AI Search service.
@@ -122,19 +116,21 @@ az login
122116

123117
### Using a REST client
124118

125-
[Several quickstarts](search-get-started-vector.md) and tutorials use a REST client, such as Visual Studio Code with the REST extension. Here's how you connect to Azure AI Search from Visual Studio Code.
119+
Several quickstarts and tutorials use a REST client, such as Visual Studio Code with the REST extension. Here's how you connect to Azure AI Search from Visual Studio Code.
120+
121+
You should have a `.rest` or `.http` file, similar to the one described in [Quickstart: Vector search](search-get-started-vector.md).
126122

127-
1. Get a personal identity token:
123+
1. Get an access token:
128124

129125
```azurecli
130126
az account get-access-token --scope https://search.azure.com/.default --query accessToken --output tsv
131127
```
132128

133-
1. Set variables used for the connection, pasting the full search service endpoint and the token you got in the previous step. Make sure neither value is quote-enclosed.
129+
1. At the top of your file, set variables used for the connection, pasting the full search service endpoint and the access token you got in the previous step. Your variables should look similar to the following example. Notice the values aren't quote-enclosed.
134130

135131
```REST
136-
@baseUrl = PUT-YOUR-SEARCH-SERVICE-URL-HERE
137-
@token = PUT-YOUR-PERSONAL-IDENTITY-TOKEN-HERE
132+
@baseUrl = https://contoso.search.search.windows.net
133+
@token = <a long GUID>
138134
```
139135
140136
1. Specify the authorization bearer token in a REST call:
@@ -153,6 +149,8 @@ az login
153149
}
154150
```
155151

152+
If the call fails, revisit the previous steps to make sure you didn't skip any. You might also want to restart your device.
153+
156154
## Additional configuration
157155

158156
Configure a managed identity for outbound connections:

0 commit comments

Comments
 (0)