-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Azure AI search extension Unauthorized #475
Comments
Or am i mistaken, can i "only" reach the Search service made by the Default deployment with Azure but instead different indexes that i make within that Search Service? because what i'm trying to do is to connect to my "other" resource that has a Search service and it's index. am i missing a Environment Variable in the Azure Chat Web App? |
You can connect different indexes via extensions.
headers: If you are interested, here is an example gpt function definition. The function will get 5 results from the search index and retrieve only the content column from the index. Hope I got your problem and this helps - if not, feel free to describe further, I have worked quite a lot with adding a search service to query via the chatbot. |
Thank you thank you thank you, Yes it works now with creating it as a "New Extension" gets me wondering whats the options regarding the because i would like to use the Citations format in the Azure AI search service option on AzureChat |
Hello!
so i have added ApiKey from Search Service
SearchName from Search Service
IndexName from Search Service
i can speak to the search service through other Blazor project and call the ApiKey, searchName, IndexName
but with AzureChat i always end up with "There was an error calling the api: Unauthorized"
Status 200 for Fetching.
any other things i have missed? have followed Documentation step by step and looked through other issues here but with no success.
my Search index
getting my Web App service from Web App and using the Default domain: "ExampleWebAppName
API endpoint POST https://ExampleWebAppName.azurewebsites.net/api/document
The text was updated successfully, but these errors were encountered: