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
+4-4Lines changed: 4 additions & 4 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 users change any settings. Notify the 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 turned on in the studio, your users aren'tified 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 noified of a connection error but 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
@@ -95,7 +95,7 @@ You can enable managed identity for the Azure OpenAI resource and the Azure App
95
95
96
96

97
97
98
-
Note: If you are using an embedding model deployed to the same resource used for inference, you only need to enable managed identity on one Azure OpenAI resource. If using an embedding model deployed to a different resource from the one used for inference, you also need to enable managed identity on the Azure OpenAI resource used to deploy your embedding model.
98
+
Note: If you're using an embedding model deployed to the same resource used for inference, you only need to enable managed identity on one Azure OpenAI resource. If using an embedding model deployed to a different resource from the one used for inference, you also need to enable managed identity on the Azure OpenAI resource used to deploy your embedding model.
99
99
100
100
### Enable role-based access control (RBAC) on your Azure Search resource (optional)
101
101
@@ -105,7 +105,7 @@ To enable your Azure OpenAI resource to access your Azure Search resource, you n
105
105
106
106
### Assign RBAC roles to enable intra-service communication
107
107
108
-
The following table summarizes the RBAC role assignments needed for the Azure OpenAI resource used for inference, the Azure OpenAI resource used for embeddings (if using a separate resource for this purpose), Azure Search resource (if using), and the Azure App Service.
108
+
The following table summarizes the RBAC role assignments needed for all Azure resources associated with your application.
0 commit comments