Create an Azure AI Search solution

All organizations rely on information to make decisions, answer questions, and function efficiently. The problem for most organizations is not a lack of information, but the challenge of finding and extracting the information from the massive set of documents, databases, and other sources in which the information is stored.

For example, suppose Margie’s Travel is a travel agency that specializes in organizing trips to cities around the world. Over time, the company has amassed a huge amount of information in documents such as brochures, as well as reviews of hotels submitted by customers. This data is a valuable source of insights for travel agents and customers as they plan trips, but the sheer volume of data can make it difficult to find relevant information to answer a specific customer question.

To address this challenge, Margie’s Travel can use Azure AI Search to implement a solution in which the documents are indexed and enriched by using AI skills to make them easier to search.

Create Azure resources

The solution you will create for Margie’s Travel requires the following resources in your Azure subscription:

An Azure AI Search resource, which will manage indexing and querying.
An Azure AI Services resource, which provides AI services for skills that your search solution can use to enrich the data in the data source with AI-generated insights.
A Storage account with a blob container in which the documents to be searched are stored.

Important: Your Azure AI Search and Azure AI Services resources must be in the same location!

Create an Azure AI Search resource

In a web browser, open the Azure portal at https://portal.azure.com, and sign in using the Microsoft account associated with your Azure subscription.
Select the ＋Create a resource button, search for search, and create an Azure AI Search resource with the following settings:
- Subscription: Your Azure subscription
- Resource group: Create a new resource group (if you are using a restricted subscription, you may not have permission to create a new resource group - use the one provided)
- Service name: Enter a unique name
- Location: Select a location - note that your Azure AI Search and Azure AI Services resources must be in the same location
- Pricing tier: Basic
Wait for deployment to complete, and then go to the deployed resource.
Review the Overview page on the blade for your Azure AI Search resource in the Azure portal. Here, you can use a visual interface to create, test, manage, and monitor the various components of a search solution; including data sources, indexes, indexers, and skillsets.

Create an Azure AI Services resource

If you don’t already have one in your subscription, you’ll need to provision an Azure AI Services resource. Your search solution will use this to enrich the data in the datastore with AI-generated insights.

Return to the home page of the Azure portal, and then select the ＋Create a resource button, search for Azure AI Services, and create an Azure AI Services multi service account resource with the following settings:
- Subscription: Your Azure subscription
- Resource group: The same resource group as your Azure AI Search resource
- Region: The same location as your Azure AI Search resource
- Name: Enter a unique name
- Pricing tier: Standard S0
Select the required checkboxes and create the resource.
Wait for deployment to complete, and then view the deployment details.

Create a storage account

Return to the home page of the Azure portal, and then select the ＋Create a resource button, search for storage account, and create a Storage account resource with the following settings:
- Subscription: Your Azure subscription
- Resource group: *The same resource group as your Azure AI Search and Azure AI Services resources
- Storage account name: Enter a unique name
- Region: Choose any available region
- Performance: Standard
- Redundancy: Locally-redundant storage (LRS)
- On the Advanced tab, check the box next to Allow enabling anonymous access on individual containers
Wait for deployment to complete, and then go to the deployed resource.
On the Overview page, note the Subscription ID -this identifies the subscription in which the storage account is provisioned.
On the Access keys page, note that two keys have been generated for your storage account. Then select Show keys to view the keys.

Tip: Keep the Storage Account blade open - you will need the subscription ID and one of the keys in the next procedure.

Prepare to develop an app in Visual Studio Code

You’ll develop your search app using Visual Studio Code. The code files for your app have been provided in a GitHub repo.

Tip: If you have already cloned the mslearn-knowledge-mining repo, open it in Visual Studio code. Otherwise, follow these steps to clone it to your development environment.

Start Visual Studio Code.
Open the palette (SHIFT+CTRL+P) and run a Git: Clone command to clone the https://github.com/MicrosoftLearning/mslearn-knowledge-mining repository to a local folder (it doesn’t matter which folder).
When the repository has been cloned, open the folder in Visual Studio Code.
Wait while additional files are installed to support the C# code projects in the repo.

Note: If you are prompted to add required assets to build and debug, select Not Now.

Upload Documents to Azure Storage

Now that you have the required resources, you can upload some documents to your Azure Storage account.

In Visual Studio Code, in the Explorer pane, expand the Labfiles\01-azure-search folder and select UploadDocs.cmd.
Edit the batch file to replace the YOUR_SUBSCRIPTION_ID, YOUR_AZURE_STORAGE_ACCOUNT_NAME, and YOUR_AZURE_STORAGE_KEY placeholders with the appropriate subscription ID, Azure storage account name, and Azure storage account key values for the storage account you created previously.
Save your changes, and then right-click the 01-azure-search folder and open an integrated terminal.
Enter the following command to sign into your Azure subscription by using the Azure CLI.
```
 az login
```
A web browser tab will open and prompt you to sign into Azure. Do so, and then close the browser tab and return to Visual Studio Code.
Enter the following command to run the batch file. This will create a blob container in your storage account and upload the documents in the data folder to it.
```
 .\UploadDocs.cmd
```

Index the documents

Now that you have the documents in place, you can create a search solution by indexing them.

In the Azure portal, browse to your Azure AI Search resource. Then, on its Overview page, select Import data.
On the Connect to your data page, in the Data Source list, select Azure Blob Storage. Then complete the data store details with the following values:
- Data Source: Azure Blob Storage
- Data source name: margies-data
- Data to extract: Content and metadata
- Parsing mode: Default
- Connection string: Select Choose an existing connection. Then select your storage account, and finally select the margies container that was created by the UploadDocs.cmd script.
- Managed identity authentication: None
- Container name: margies
- Blob folder: Leave this blank
- Description: Brochures and reviews in Margie’s Travel web site.
Proceed to the next step (Add cognitive skills).
in the Attach Azure AI Services section, select your Azure AI Services resource.

In the Add enrichments section:

Change the Skillset name to margies-skillset.
Select the option Enable OCR and merge all text into merged_content field.
Ensure that the Source data field is set to merged_content.
Leave the Enrichment granularity level as Source field, which is set the entire contents of the document being indexed; but note that you can change this to extract information at more granular levels, like pages or sentences.

Select the following enriched fields:

Cognitive Skill	Parameter	Field name
Extract location names		locations
Extract key phrases		keyphrases
Detect language		language
Generate tags from images		imageTags
Generate captions from images		imageCaption

Double-check your selections (it can be difficult to change them later). Then proceed to the next step (Customize target index).
Change the Index name to margies-index.
Ensure that the Key is set to metadata_storage_path and leave the Suggester name blank and Search mode at its default.

Make the following changes to the index fields, leaving all other fields with their default settings (IMPORTANT: you may need to scroll to the right to see the entire table):

Field name	Retrievable	Filterable	Sortable	Facetable	Searchable
metadata_storage_size	✔	✔	✔
metadata_storage_last_modified	✔	✔	✔
metadata_storage_name	✔	✔	✔		✔
metadata_author	✔	✔	✔	✔	✔
locations	✔	✔			✔
keyphrases	✔	✔			✔
language	✔	✔			✔

Double-check your selections, paying particular attention to ensure that the correct Retrievable, Filterable, Sortable, Facetable, and Searchable options are selected for each field (it can be difficult to change them later). Then proceed to the next step (Create an indexer).
Change the Indexer name to margies-indexer.
Leave the Schedule set to Once.
Expand the Advanced options, and ensure that the Base-64 encode keys option is selected (generally encoding keys make the index more efficient).
Select Submit to create the data source, skillset, index, and indexer. The indexer is run automatically and runs the indexing pipeline, which:
1. Extracts the document metadata fields and content from the data source
2. Runs the skillset of cognitive skills to generate additional enriched fields
3. Maps the extracted fields to the index.
On the left side, view the Indexers page, which should show the newly created margies-indexer. Wait a few minutes, and click &orarr; Refresh until the Status indicates success.

Search the index

Now that you have an index, you can search it.

At the top of the Overview page for your Azure AI Search resource, select Search explorer.
In Search explorer, in the Query string box, enter * (a single asterisk), and then select Search.

This query retrieves all documents in the index in JSON format. Examine the results and note the fields for each document, which contain document content, metadata, and enriched data extracted by the cognitive skills you selected.
In the View menu, select JSON view and note that the JSON request for the search is shown, like this:
```
 {
   "search": "*"
 }
```
Modify the JSON request to include the count parameter as shown here:
```
 {
   "search": "*",
   "count": true
 }
```
Submit the modified search. This time, the results include a @odata.count field at the top of the results that indicates the number of documents returned by the search.
Try the following query:
```
 {
   "search": "*",
   "count": true,
   "select": "metadata_storage_name,metadata_author,locations"
 }
```
This time the results include only the file name, author, and any locations mentioned in the document content. The file name and author are in the metadata_storage_name and metadata_author fields, which were extracted from the source document. The locations field was generated by a cognitive skill.
Now try the following query string:
```
 {
   "search": "New York",
   "count": true,
   "select": "metadata_storage_name,keyphrases"
 }
```
This search finds documents that mention “New York” in any of the searchable fields, and returns the file name and key phrases in the document.

Let’s try one more query:

 {
   "search": "New York",
   "count": true,
   "select": "metadata_storage_name",
   "filter": "metadata_author eq 'Reviewer'"
 }

This query returns the filename of any documents authored by Reviewer that mention “New York”.

Explore and modify definitions of search components

The components of the search solution are based on JSON definitions, which you can view and edit in the Azure portal.

While you can use the portal to create and modify search solutions, it’s often desirable to define the search objects in JSON and use the Azure AI Service REST interface to create and modify them.

Get the endpoint and key for your Azure AI Search resource

In the Azure portal, return to the Overview page for your Azure AI Search resource; and in the top section of the page, find the Url for your resource (which looks like https://resource_name.search.windows.net) and copy it to the clipboard.
In Visual Studio Code, in the Explorer pane, expand the 01-azure-search folder and its modify-search subfolder, and select modify-search.cmd to open it. You will use this script file to run cURL commands that submit JSON to the Azure AI Service REST interface.
In modify-search.cmd, replace the YOUR_SEARCH_URL placeholder with the URL you copied to the clipboard.
In the Azure portal, in the Settings section, view the Keys page for your Azure AI Search resource, and copy the Primary admin key to the clipboard.
In Visual Studio Code, replace the YOUR_ADMIN_KEY placeholder with the key you copied to the clipboard.
Save the changes to modify-search.cmd (but don’t run it yet!)

Review and modify the skillset

In Visual studio Code, in the modify-search folder, open skillset.json. This shows a JSON definition for margies-skillset.
At the top of the skillset definition, note the cognitiveServices object, which is used to connect your Azure AI Services resource to the skillset.
In the Azure portal, open your Azure AI Services resource (not your Azure AI Search resource!) and, in the Resource Management section, view its Keys and Endpoint page. Then copy KEY 1 to the clipboard.
In Visual Studio Code, in skillset.json, replace the YOUR_COGNITIVE_SERVICES_KEY placeholder with the Azure AI Services key you copied to the clipboard.
Scroll through the JSON file, noting that it includes definitions for the skills you created using the Azure AI Search user interface in the Azure portal. At the bottom of the list of skills, an additional skill has been added with the following definition:
```
 {
     "@odata.type": "#Microsoft.Skills.Text.V3.SentimentSkill",
     "defaultLanguageCode": "en",
     "name": "get-sentiment",
     "description": "New skill to evaluate sentiment",
     "context": "/document",
     "inputs": [
         {
             "name": "text",
             "source": "/document/merged_content"
         },
         {
             "name": "languageCode",
             "source": "/document/language"
         }
     ],
     "outputs": [
         {
             "name": "sentiment",
             "targetName": "sentimentLabel"
         }
     ]
 }
```
The new skill is named get-sentiment, and for each document level in a document, it, will evaluate the text found in the merged_content field of the document being indexed (which includes the source content as well as any text extracted from images in the content). It uses the extracted language of the document (with a default of English), and evaluates a label for the sentiment of the content. Values for the sentiment label can be “positive”, “negative”, “neutral”, or “mixed”. This label is then output as a new field named sentimentLabel.
Save the changes you’ve made to skillset.json.

Review and modify the index

In Visual studio Code, in the modify-search folder, open index.json. This shows a JSON definition for margies-index.
Scroll through the index and view the field definitions. Some fields are based on metadata and content in the source document, and others are the results of skills in the skillset.

At the end of the list of fields that you defined in the Azure portal, note that two additional fields have been added:

 {
     "name": "sentiment",
     "type": "Edm.String",
     "facetable": false,
     "filterable": true,
     "retrievable": true,
     "sortable": true
 },
 {
     "name": "url",
     "type": "Edm.String",
     "facetable": false,
     "filterable": true,
     "retrievable": true,
     "searchable": false,
     "sortable": false
 }

The sentiment field will be used to add the output from the get-sentiment skill that was added the skillset. The url field will be used to add the URL for each indexed document to the index, based on the metadata_storage_path value extracted from the data source. Note that index already includes the metadata_storage_path field, but it’s used as the index key and Base-64 encoded, making it efficient as a key but requiring client applications to decode it if they want to use the actual URL value as a field. Adding a second field for the unencoded value resolves this problem.

Review and modify the indexer

In Visual studio Code, in the modify-search folder, open indexer.json. This shows a JSON definition for margies-indexer, which maps fields extracted from document content and metadata (in the fieldMappings section), and values extracted by skills in the skillset (in the outputFieldMappings section), to fields in the index.
In the fieldMappings list, note the mapping for the metadata_storage_path value to the base-64 encoded key field. This was created when you assigned the metadata_storage_path as the key and selected the option to encode the key in the Azure portal. Additionally, a new mapping explicitly maps the same value to the url field, but without the Base-64 encoding:
```
 {
     "sourceFieldName" : "metadata_storage_path",
     "targetFieldName" : "url"
 }    
```
All of the other metadata and content fields in the source document are implicitly mapped to fields of the same name in the index.
Review the ouputFieldMappings section, which maps outputs from the skills in the skillset to index fields. Most of these reflect the choices you made in the user interface, but the following mapping has been added to map the sentimentLabel value extracted by your sentiment skill to the sentiment field you added to the index:
```
 {
     "sourceFieldName": "/document/sentimentLabel",
     "targetFieldName": "sentiment"
 }
```

Use the REST API to update the search solution

Right-click the modify-search folder and open an integrated terminal.
In the terminal pane for the modify-search folder, enter the following command to run the modify-search.cmd script, which submits the JSON definitions to the REST interface and initiates the indexing.
```
 ./modify-search
```
When the script has finished, return to the Overview page for your Azure AI Search resource in the Azure portal and view the Indexers page. The periodically select Refresh to track the progress of the indexing operation. It may take a minute or so to complete.

There may be some warnings for a few documents that are too large to evaluate sentiment. Often sentiment analysis is performed at the page or sentence level rather than the full document; but in this case scenario, most of the documents - particularly the hotel reviews, are short enough for useful document-level sentiment scores to be evaluated.

Query the modified index

At the top of the blade for your Azure AI Search resource, select Search explorer.
In Search explorer, in the Query string box, submit the following JSON query:
```
 {
   "search": "London",
   "select": "url,sentiment,keyphrases",
   "filter": "metadata_author eq 'Reviewer' and sentiment eq 'positive'"
 }
```
This query retrieves the url, sentiment, and keyphrases for all documents that mention London authored by Reviewer that have a positive sentiment label (in other words, positive reviews that mention London)
Close the Search explorer page to return to the Overview page.

Create a search client application

Now that you have a useful index, you can use it from a client application. You can do this by consuming the REST interface, submitting requests and receiving responses in JSON format over HTTP; or you can use the software development kit (SDK) for your preferred programming language. In this exercise, we’ll use the SDK.

Note: You can choose to use the SDK for either C# or Python. In the steps below, perform the actions appropriate for your preferred language.

Get the endpoint and keys for your search resource

In the Azure portal, on the Overview page for your Azure AI Search resource, note the Url value, which should be similar to https://your_resource_name.search.windows.net. This is the endpoint for your search resource.
On the Keys page, note that there are two admin keys, and a single query key. An admin key is used to create and manage search resources; a query key is used by client applications that only need to perform search queries.

You will need the endpoint and query key for your client application.

Prepare to use the Azure AI Search SDK

In Visual Studio Code, in the Explorer pane, browse to the 01-azure-search folder and expand the C-Sharp or Python folder depending on your language preference.
Right-click the margies-travel folder and open an integrated terminal. Then install the Azure AI Search SDK package by running the appropriate command for your language preference:

C#
```
 dotnet add package Azure.Search.Documents --version 11.6.0
```
Python
```
 pip install azure-search-documents==11.5.1
```
View the contents of the margies-travel folder, and note that it contains a file for configuration settings:
- C#: appsettings.json
- Python: .env
Open the configuration file and update the configuration values it contains to reflect the endpoint and query key for your Azure AI Search resource. Save your changes.

Explore code to search an index

The margies-travel folder contains code files for a web application (a Microsoft C# ASP.NET Razor web application or a Python Flask application), which includes search functionality.

Open the following code file in the web application, depending on your choice of programming language:
- C#:Pages/Index.cshtml.cs
- Python: app.py
Near the top of the code file, find the comment Import search namespaces, and note the namespaces that have been imported to work with the Azure AI Search SDK:
In the search_query function, find the comment Create a search client, and note that the code creates a SearchClient object using the endpoint and query key for your Azure AI Search resource:
In the search_query function, find the comment Submit search query, and review the code to submit a search for the specified text with the following options:
- A search mode that requires all of the individual words in the search text are found.
- The total number of documents found by the search is included in the results.
- The results are filtered to include only documents that match the provided filter expression.
- The results are sorted into the specified sort order.
- Each discrete value of the metadata_author field is returned as a facet that can be used to display pre-defined values for filtering.
- Up to three extracts of the merged_content and imageCaption fields with the search terms highlighted are included in the results.
- The results include only the fields specified.

Explore code to render search results

The web app already includes code to process and render the search results.

Open the following code file in the web application, depending on your choice of programming language:
- C#:Pages/Index.cshtml
- Python: templates/search.html
Examine the code, which renders the page on which the search results are displayed. Observe that:
- The page begins with a search form that the user can use to submit a new search (in the Python version of the application, this form is defined in the base.html template), which is referenced at the beginning of the page.
- A second form is then rendered, enabling the user to refine the search results. The code for this form:
  - Retrieves and displays the count of documents from the search results.
  - Retrieves the facet values for the metadata_author field and displays them as an option list for filtering.
  - Creates a drop-down list of sort options for the results.
- The code then iterates through the search results, rendering each result as follows:
  - Display the metadata_storage_name (file name) field as a link to the address in the url field.
  - Displaying highlights for search terms found in the merged_content and imageCaption fields to help show the search terms in context.
  - Display the metadata_author, metadata_storage_size, metadata_storage_last_modified, and language fields.
  - Display the sentiment label for the document. Can be positive, negative, neutral, or mixed.
  - Display the first five keyphrases (if any).
  - Display the first five locations (if any).
  - Display the first five imageTags (if any).

Run the web app

return to the integrated terminal for the margies-travel folder, and enter the following command to run the program:

C#
```
dotnet run
```
Python
```
flask run
```
In the message that is displayed when the app starts successfully, follow the link to the running web application (http://localhost:5000/ or http://127.0.0.1:5000/) to open the Margies Travel site in a web browser.
In the Margie’s Travel website, enter London hotel into the search box and click Search.
Review the search results. They include the file name (with a hyperlink to the file URL), an extract of the file content with the search terms (London and hotel) emphasized, and other attributes of the file from the index fields.
Observe that the results page includes some user interface elements that enable you to refine the results. These include:
- A filter based on a facet value for the metadata_author field. This demonstrates how you can use facetable fields to return a list of facets - fields with a small set of discrete values that can displayed as potential filter values in the user interface.
- The ability to order the results based on a specified field and sort direction (ascending or descending). The default order is based on relevancy, which is calculated as a search.score() value based on a scoring profile that evaluates the frequency and importance of search terms in the index fields.
Select the Reviewer filter and the Positive to negative sort option, and then select Refine Results.
Observe that the results are filtered to include only reviews, and sorted based on the sentiment label.
In the Search box, enter a new search for quiet hotel in New York and review the results.
Try the following search terms:
- Tower of London (observe that this term is identified as a key phrase in some documents).
- skyscraper (observe that this word doesn’t appear in the actual content of any documents, but is found in the image captions and image tags that were generated for images in some documents).
- Mojave desert (observe that this term is identified as a location in some documents).
Close the browser tab containing the Margie’s Travel web site and return to Visual Studio Code. Then in the Python terminal for the margies-travel folder (where the dotnet or flask application is running), enter Ctrl+C to stop the app.

Clean-up

Now that you’ve completed the exercise, delete all the resources you no longer need. Delete the Azure resources:

In the Azure portal, select Resource groups.
Select the resource group you don’t need, then select Delete resource group.

More information

To learn more about Azure AI Search, see the Azure AI Search documentation.