You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Unleash the Power of Azure Open AI
1
+
# Unleash the Power of Azure OpenAI
2
2
3
3
1.[Introduction](#introduction)
4
4
1.[Solution Overview](/docs/1-introduction.md)
@@ -14,11 +14,11 @@
14
14
15
15
# Introduction
16
16
17
-
_Azure Chat Solution Accelerator powered by Azure Open AI Service_
17
+
_Azure Chat Solution Accelerator powered by Azure OpenAI Service_
18
18
19
19

20
20
21
-
_Azure Chat Solution Accelerator powered by Azure Open AI Service_ is a solution accelerator that allows organisations to deploy a private chat tenant in their Azure Subscription, with a familiar user experience and the added capabilities of chatting over your data and files.
21
+
_Azure Chat Solution Accelerator powered by Azure OpenAI Service_ is a solution accelerator that allows organisations to deploy a private chat tenant in their Azure Subscription, with a familiar user experience and the added capabilities of chatting over your data and files.
Copy file name to clipboardExpand all lines: docs/8-extensions.md
+3
Original file line number
Diff line number
Diff line change
@@ -47,6 +47,9 @@ As an example you can create an extension that calls Bing Search API to search f
47
47
48
48
In the example below only the `query` is required as Bing does not require a body parameter.
49
49
50
+
> [!NOTE]
51
+
> As header values specified for an extension often contain secrets (e.g. API keys) Azure Chat stores those values securely in Azure Key Vault. If you are deploying the solution to Azure using azd or the bicep templates the required Key Vault role assignment is automatically created. If you are running the solution locally you will need to manually add the "Key Vault Secrets Officer" role to identy that is running the solution (wh8ch will typically be the user logged into the Azure CLI)
Copy file name to clipboardExpand all lines: docs/migration.md
+9-5
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,19 @@
1
-
# Migration
1
+
# Migration 2.1
2
+
3
+
The new changes merges GPT-4 and GPT-4 Vision models into a single GPT-4o model. This allows multi-modal inputs and generates text as an output. The new model is available within the following [regions](https://learn.microsoft.com/en-us/azure/ai-services/openai/concepts/models#gpt-4-and-gpt-4-turbo-preview-model-availability).
4
+
5
+
# Migration 2.0
2
6
3
7
The following changes and services are required to migrate from the old version to the new version.
4
8
5
9
Refer the `.env.example` file for the latest environment variable changes.
6
10
7
11
If you previously had Azure Chat running and have pulled the v2 version you will need at minimum to make the following changes:
8
12
9
-
* Change the "OPENAI_API_KEY" environment setting to "AZURE_OPENAI_API_KEY"
10
-
* Add an additional container to your Cosmos DB database called "config" with a partition key of "/userId"
11
-
* Add the "AZURE_KEY_VAULT_NAME" environment setting with the name of your Azure Key Vault
12
-
* Add the "New Azure Services" settings below if you wish to use these features
13
+
- Change the "OPENAI_API_KEY" environment setting to "AZURE_OPENAI_API_KEY"
14
+
- Add an additional container to your Cosmos DB database called "config" with a partition key of "/userId"
15
+
- Add the "AZURE_KEY_VAULT_NAME" environment setting with the name of your Azure Key Vault
16
+
- Add the "New Azure Services" settings below if you wish to use these features
0 commit comments