Skip to content

Commit ec9814b

Browse files
committed
resource demo sites link update
1 parent 83b809f commit ec9814b

File tree

3 files changed

+17
-23
lines changed

3 files changed

+17
-23
lines changed

articles/search/resource-demo-sites.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: azure-ai-search
99
ms.custom:
1010
- ignite-2023
1111
ms.topic: conceptual
12-
ms.date: 10/07/2024
12+
ms.date: 12/02/2024
1313
---
1414

1515
# Demos - Azure AI Search
@@ -20,5 +20,5 @@ The Azure AI Search currently builds and hosts the following demos.
2020

2121
| Demo name | Description | Source code |
2222
|-----------|------------ |-------------|
23-
| [Chat with your data](https://entgptsearch.azurewebsites.net/) | An Azure web app that uses ChatGPT in Azure OpenAI with fictitious health plan data in a search index. | [https://github.com/Azure-Samples/azure-search-openai-demo/](https://github.com/Azure-Samples/azure-search-openai-demo/) |
23+
| [Chat with your data](https://aka.ms/officialazsdemo) | An Azure web app that uses ChatGPT in Azure OpenAI with fictitious health plan data in a search index. | [https://github.com/Azure-Samples/azure-search-openai-demo/](https://github.com/Azure-Samples/azure-search-openai-demo/) |
2424
| [Semantic ranking for retail](https://brave-meadow-0f59c9b1e.1.azurestaticapps.net/) | Web app for a fictitious online retailer, "Terra" | Not available |

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

Lines changed: 10 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.date: 11/29/2024
1212

1313
# Quickstart: Connect without keys
1414

15-
Configure Azure AI Search to use Microsoft Entra ID authentication and role-based access control (RBAC). Connect from your local system with your personal identity, using Jupyter notebooks or a REST client to interact with your search service.
15+
Configure Azure AI Search to use Microsoft Entra ID authentication and role-based access control (RBAC) so that you can connect from your local system with your personal identity, using Jupyter notebooks or a REST client to interact with your search service.
1616

1717
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 keys in your example code.
1818

@@ -22,7 +22,7 @@ If you stepped through other quickstarts that connect using API keys, this quick
2222

2323
- [Azure AI Search](search-create-service-portal.md), any region or tier, but you need Basic or higher to configure a managed identity for Azure AI Search.
2424

25-
- A command line tool, such as the [Azure CLI](/cli/azure/install-azure-cli).
25+
- A command line tool, such as PowerShell or Bash, and the [Azure CLI](/cli/azure/install-azure-cli).
2626

2727
## Step 1: Get your Azure subscription and tenant IDs
2828

@@ -38,13 +38,13 @@ You need this step if you have more than one subscription or tenant.
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

41-
1. You now know which subscription and tenant Azure AI Search is under. Switching to your local device and a command prompt, identify the active Azure subscription and tenant on your device:
41+
1. You now know which subscription and tenant Azure AI Search is under. Switch to your local device and a command prompt, and identify the active Azure subscription and tenant on your device:
4242

4343
```azurecli
4444
az account show
4545
```
4646

47-
1. If the active subscription and tenant differ from the information obtained in the previous step, change the subscription ID. Next, sign in to Azure using the tenant ID also found in the previous step:
47+
1. If the active subscription and tenant differ from the information obtained in the previous step, change the subscription ID. Next, sign in to Azure using the tenant ID that you found in the previous step:
4848

4949
```azurecli
5050
az account set --subscription <your-subscription-id>
@@ -110,12 +110,12 @@ az login
110110
from azure.search.documents import SearchClient
111111

112112
service_endpoint = "https://<your-search-service-name>.search.windows.net"
113-
index_name = "<your-index-name>"
113+
index_name = "hotels-sample-index"
114114

115115
credential = DefaultAzureCredential()
116116
client = SearchClient(endpoint=service_endpoint, index_name=index_name, credential=credential)
117117

118-
results = client.search("search text")
118+
results = client.search("beach access")
119119
for result in results:
120120
print(result)
121121
```
@@ -127,24 +127,16 @@ az login
127127
1. Get a personal identity token:
128128

129129
```azurecli
130-
az account get-access-token --scope https://search.azure.com/.default
130+
az account get-access-token --scope https://search.azure.com/.default --query accessToken --output tsv
131131
```
132132

133-
1. Set variables used for the connection, pasting the full search service endpoint and the token you got in the previous step.
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.
134134

135-
```http
135+
```REST
136136
@baseUrl = PUT-YOUR-SEARCH-SERVICE-URL-HERE
137137
@token = PUT-YOUR-PERSONAL-IDENTITY-TOKEN-HERE
138138
```
139139
140-
<!-- 1. Extract the token from the output:
141-
142-
`TOKEN=$(az account get-access-token --resource https://<your-search-service-name>.search.windows.net --query accessToken --output tsv)`
143-
144-
1. Provide the token in a request header:
145-
146-
`az rest --method get --url "https://<your-search-service-name>.search.windows.net/indexes/<your-index-name>/docs?api-version=2021-04-30-Preview&search=*" --headers "Authorization=Bearer $TOKEN"` -->
147-
148140
1. Specify the authorization bearer token in a REST call:
149141
150142
```REST
@@ -154,7 +146,7 @@ az login
154146
155147
{
156148
"queryType": "simple",
157-
"search": "motel",
149+
"search": "beach access",
158150
"filter": "",
159151
"select": "HotelName,Description,Category,Tags",
160152
"count": true

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

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.author: heidist
99
ms.service: azure-ai-search
1010
ms.topic: quickstart
1111
ms.devlang: rest-api
12-
ms.date: 10/31/2024
12+
ms.date: 11/29/2024
1313
ms.custom:
1414
- mode-api
1515
- ignite-2023
@@ -116,7 +116,7 @@ If you're not familiar with the REST client for Visual Studio Code, this section
116116
117117
1. Open or create a new file named with either a `.rest` or `.http` file extension.
118118
119-
1. Paste in the following example if you're using API keys. Replace the `@baseUrl` and `@apiKey` placeholders with the values you copied earlier.
119+
1. Paste in the following example if you're using API keys. Replace the `@baseUrl` and `@apiKey` placeholders with the values you copied earlier, without quotes.
120120
121121
```http
122122
@baseUrl = PUT-YOUR-SEARCH-SERVICE-ENDPOINT-HERE
@@ -128,7 +128,7 @@ If you're not familiar with the REST client for Visual Studio Code, this section
128128
api-key: {{apiKey}}
129129
```
130130
131-
1. Or, paste in this example if your using roles. Replace the `@baseUrl` and `@token` placeholders with the values you copied earlier.
131+
1. Or, paste in this example if your using roles. Replace the `@baseUrl` and `@token` placeholders with the values you copied earlier, without quotes.
132132
133133
```http
134134
@baseUrl = PUT-YOUR-SEARCH-SERVICE-ENDPOINT-HERE
@@ -144,6 +144,8 @@ If you're not familiar with the REST client for Visual Studio Code, this section
144144
145145
:::image type="content" source="media/search-get-started-rest/rest-client-request-setup.png" lightbox="media/search-get-started-rest/rest-client-request-setup.png" alt-text="Screenshot that shows a REST client configured for a search service request.":::
146146
147+
If you get `WWW-Authenticate: Bearer realm="Azure Cognitive Search" error="invalid_token" error_description="Authentication token failed validation."`, remove the quotes around the token, save the file, and retry your request.
148+
147149
Key points:
148150
149151
- Parameters are specified by using an `@` prefix.

0 commit comments

Comments
 (0)