Skip to content

Commit e4e1ea5

Browse files
committed
updated README
1 parent a150bbb commit e4e1ea5

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

README.MD

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -94,10 +94,14 @@ The easiest way to deploy the full-stack application is to fork the repository a
9494
Make sure you give the user thay you are using to connect to the database the permission to run the needed stored procedures:
9595

9696
```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+
GRANT REFERENCES ON DATABASE SCOPED CREDENTIAL::[<openai_url>] TO [sql-aisearch];
98100
```
99101

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.
101105

102106
## Sample Data
103107

0 commit comments

Comments
 (0)