Skip to content

Commit c7231b6

Browse files
committed
making style fixes minor change
1 parent 894ae6c commit c7231b6

File tree

2 files changed

+9
-9
lines changed

2 files changed

+9
-9
lines changed

articles/ai-services/agents/includes/bicep-setup.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -34,9 +34,9 @@ The following section shows you how to set up the required resources for getting
3434

3535
#### Basic agent setup: use an existing AI Services resource
3636

37-
Replace the parameter value for `aiServiceAccountResourceId` with the full arm resource id of the AI Services account you want to use.
37+
Replace the parameter value for `aiServiceAccountResourceId` with the full arm resource ID of the AI Services account you want to use.
3838

39-
1. To get the AI Services account resource id, sign in to the Azure CLI and select the subscription with your AI Services account:
39+
1. To get the AI Services account resource ID, sign in to the Azure CLI and select the subscription with your AI Services account:
4040

4141
```az login```
4242
2. Replace `<your-resource-group>` with the resource group containing your resource and `your-ai-service-resource-name` with the name of your AI Service resource, and run:
@@ -50,15 +50,15 @@ Replace the parameter value for `aiServiceAccountResourceId` with the full arm r
5050

5151
#### Standard agent setup: use an existing AI Services, storage, and/or Azure AI Search resource
5252

53-
Use an existing AI Search, storage accont, and/or Azure AI Search resource by providing the full arm resource id in the standard agent template file.
53+
Use an existing AI Search, storage account, and/or Azure AI Search resource by providing the full arm resource ID in the standard agent template file.
5454

5555
Use an existing AI Services resource:
56-
1. See steps in basic agent setup to get the AI Services account resource id.
56+
1. Follow the steps in basic agent setup to get the AI Services account resource ID.
5757
2. In the standard agent template file, set the parameter:
5858
- aiServiceAccountResourceId:/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.CognitiveServices/accounts/{serviceName}
5959

6060
Use an existing storage account:
61-
1. To get your storage account resource id, sign in to the Azure CLI and select the subscription with your storage account:
61+
1. To get your storage account resource ID, sign in to the Azure CLI and select the subscription with your storage account:
6262

6363
```az login```
6464
2. Then run the command:
@@ -70,7 +70,7 @@ Use an existing storage account:
7070
- aiStorageAccountResourceId:/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Storage/storageAccounts/{storageAccountName}
7171

7272
Use an existing Azure AI Search resource:
73-
1. To get your Azure AI Search resource id, sign into Azure CLI and select the subscription with your search resource:
73+
1. To get your Azure AI Search resource ID, sign into Azure CLI and select the subscription with your search resource:
7474

7575
```az login```
7676
2. Then run the command:
@@ -82,7 +82,7 @@ Use an existing Azure AI Search resource:
8282
## Basic agent setup resource architecture
8383
:::image type="content" source="../media/quickstart/basic-agent-setup-resources.png" alt-text="An architecture diagram for basic agent setup." lightbox="../media/quickstart/basic-agent-setup-resources.png":::
8484

85-
Resources for the AI hub, AI project, and AI Services are created for you. A storage account is created because it is a required resource for hubs, but this is not used by agents. The AI Services account is connected to your project/hub and a gpt-4o-mini model is deployed in the eastus region. A Microsoft-managed key vault, storage account, and search resource is used by default.
85+
Resources for the AI hub, AI project, and AI Services are created for you. A storage account is created because it's a required resource for hubs, but this storage account is not used by agents. The AI Services account is connected to your project/hub and a gpt-4o-mini model is deployed in the eastus region. A Microsoft-managed key vault, storage account, and search resource is used by default.
8686

8787
## Standard agent setup resource architecture
8888
:::image type="content" source="../media/quickstart/standard-agent-setup-resources.png" alt-text="An architecture diagram for standard agent setup." lightbox="../media/quickstart/standard-agent-setup-resources.png":::

articles/ai-services/agents/includes/file-search/deep-dive.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,14 +48,14 @@ batch = project_client.agents.create_vector_store_file_batch_and_poll(
4848
Files can be removed from a vector store by either:
4949

5050
* Deleting the vector store file object or,
51-
* By deleting the underlying file object, which removes the file it from all vector_store and code_interpreter configurations across all agents and threads in your organization
51+
* Deleting the underlying file object, which removes the file it from all vector_store and code_interpreter configurations across all agents and threads in your organization
5252

5353
The maximum file size is 512 MB. Each file should contain no more than 5,000,000 tokens per file (computed automatically when you attach a file).
5454

5555

5656
## Remove vector store
5757

58-
You can can remove a vector store from the file search tool.
58+
You can remove a vector store from the file search tool.
5959

6060
```python
6161
file_search_tool.remove_vector_store(vector_store.id)

0 commit comments

Comments
 (0)