Skip to content

Commit 0348803

Browse files
authored
Fix duplicate entries in llm.md
Removed duplicate entries for Azure-specific considerations in the documentation.
1 parent 6a3eeeb commit 0348803

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

content/llm.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -79,10 +79,10 @@ In this YAML file, you'll want to provide the details of your Azure AI Foundry m
7979
api_key_name: azure
8080
```
8181
Some important Azure-specific considerations:
82-
- `model_id` is essentially the 'friendly name' for the model within the LLM tool. I chose a `aoai/` prefix, so I could differenciate between Azure models, and OpenAI API models.
83-
- `model_name` is the Azure deployment name - which _could_ be different from the model name (although it makes sense to keep it the same where possible).
84-
- `api_base` needs to include the `openai/v1/` suffix, because the LLM tool isn't able to accept the `api_version` from the legacy API. If you're not sure where to find the <foundry resource>, check in the [Azure AI Foundry project overview:](https://ai.azure.com/foundryProject/overview)
85-
- `api_key_name` is the name of the key you stored in step 2 (I used `azure`, but you can use whatever you like, as long as they match)
82+
* `model_id` is essentially the 'friendly name' for the model within the LLM tool. I chose a `aoai/` prefix, so I could differenciate between Azure models, and OpenAI API models.
83+
* `model_name` is the Azure deployment name - which _could_ be different from the model name (although it makes sense to keep it the same where possible).
84+
* `api_base` needs to include the `openai/v1/` suffix, because the LLM tool isn't able to accept the `api_version` from the legacy API. If you're not sure where to find the <foundry resource>, check in the [Azure AI Foundry project overview:](https://ai.azure.com/foundryProject/overview)
85+
* `api_key_name` is the name of the key you stored in step 2 (I used `azure`, but you can use whatever you like, as long as they match)
8686

8787
Don't forget to save the YAML file, once you've added all the above details.
8888

0 commit comments

Comments
 (0)