-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Configuring search extension before deployment #368
Comments
Make sure you are logged in with the user account that is set as the "admin" for your instance then you should see the publish option to allow everyone to see it :). |
Thanks, that worked like a charm! |
Sorry for necroing, but how did you specifically do this? 😊 |
@AbasBicep what part specifically are you stuck at? |
@bwitzig-zen Did not understand the "logged in with the user account that is set as the admin for your instance" Could you please explain where specifically I need to be admin? I am using my global admin to access this in my test tenant, and would LOVE to be able to publish BING with the correct API key to everyone :P |
For running locally, this will be entered in the env.local (check the env.example file for more info) For hosting in Azure, check the app service (web app) in azure. There will be an Environment Variable |
@bwitzig-zen Wow this worked wonders. I am just curious; how did you find this out? I did not have that env variable in my deployment, but after adding it, it worked like a charm. |
Hi!
I would like to configure the bing search extension globally on my deployment of azurechat.
Is that possible? I couldn't find any information on it in the docs.
Thanks,
The text was updated successfully, but these errors were encountered: