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
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,10 +94,14 @@ The easiest way to deploy the full-stack application is to fork the repository a
94
94
Make sure you give the user thay you are using to connect to the database the permission to run the needed stored procedures:
95
95
96
96
```sql
97
-
GRANT EXECUTE ON SCHEMA::[web] TO [your user]
97
+
GRANT EXECUTE ON SCHEMA::[web] TO [<your user>]
98
+
GRANT EXECUTE ANY EXTERNAL ENDPOINT TO [<your user>];
99
+
GRANTREFERENCESON DATABASE SCOPED CREDENTIAL::[<openai_url>] TO [sql-aisearch];
98
100
```
99
101
100
-
and that's it! You can now access the full-stack application deployed in Azure Static Web Apps.
102
+
replace `<your user>` with the user you are using to connect to the database and `<openai_url>` with the name of the database scoped credential you are using to connect to Azure OpenAI, which is the same as the value you used for the `OPENAI_URL` variable in the `.env` file.
103
+
104
+
That's it! You can now access the full-stack application deployed in Azure Static Web Apps.
0 commit comments