Enable API keys access control for AI search service in the code about azure-search-openai-demo

[pamelafox]

Thanks for the clarification. I'll see if we can find a contact at Copilot studio about enabling RBAC based access there. But we might also add an env variable to allow key access as well.
CC @mattgotteiner

[kyle-bosley]

I experienced a similar issue. To resolve this navigate to the "Search Service" that was created in Azure. This should be in the same resource group as the other stuff that this sample created. Once you find the search service, expand the "settings" on the left side and there will be a section called "keys". Click this and you will have the option to change the API Access control.

[pamelafox]

Could you help us understand:

1. What are the use cases for needing keys? Is it so you can use the same search service with other code, or because you're modifying this repo's code to use keys?
2. Do you actually need to disable RBAC entirely (which wouldn't be compatible with this repo's code), or you just need to also have key access?

[kyle-bosley]

1. My specific use case was deploying to CoPilot studio. In order to do this, I needed to enable API keys. So I guess it would be using the same search service with other code.
2. You do not need to disable RBAC entirely. I should have been more specific but there is an option to use both RBAC and API keys.