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: articles/ai-services/openai/how-to/use-web-app.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ You can customize the app's front-end and back-end logic. The app provides sever
37
37
38
38
When you're customizing the app, we recommend:
39
39
40
-
- Resetting the chat session (clear chat) if any settings changes are made. Notify your application end-users that their chat history will be lost.
40
+
- Resetting the chat session (clear chat) if any settings changes are made. Notify your application end-users that their chat history will be lost.
41
41
42
42
- Clearly communicating how each setting that you implement affects the user experience.
43
43
@@ -82,7 +82,7 @@ After you turn on chat history, your users can show and hide it in the upper-rig
82
82
83
83
## Deleting your Cosmos DB instance
84
84
85
-
Deleting your web app doesn't delete your Cosmos DB instance automatically. To delete your Cosmos DB instance along with all stored chats, you need to go to the associated resource in the [Azure portal](https://portal.azure.com) and delete it. If you delete the Cosmos DB resource but keep the chat history option selected on subsequent updates from the Azure OpenAI Studio, your users are noified of a connection error but can continue to use the web app without access to the chat history.
85
+
Deleting your web app doesn't delete your Cosmos DB instance automatically. To delete your Cosmos DB instance along with all stored chats, you need to go to the associated resource in the [Azure portal](https://portal.azure.com) and delete it. If you delete the Cosmos DB resource but keep the chat history option selected on subsequent updates from the Azure OpenAI Studio, your users are notified of a connection error. However, they can continue to use the web app without access to the chat history.
86
86
87
87
## Enabling Microsoft Entra ID authentication between services
88
88
@@ -125,7 +125,7 @@ In the webapp application settings, navigate to "Environment Variables" and make
125
125
126
126
If using an embedding model deployed to the same resource as your model used for inference, there are no other settings changes required.
127
127
128
-
However, if you're using an embedding model deployed to a different resource, make the following additional changes to your app's environment variables:
128
+
However, if you're using an embedding model deployed to a different resource, make the following extra changes to your app's environment variables:
129
129
* Set `AZURE_OPENAI_EMBEDDING_ENDPOINT` variable to the full API path of the embedding API for the resource you're using for embeddings, for example, `https://<your embedding AOAI resource name>.openai.azure.com/openai/deployments/<your embedding deployment name>/embeddings`
130
130
* Delete the `AZURE_OPENAI_EMBEDDING_KEY` variable to use Microsoft Entra ID authentication.
0 commit comments