Skip to content
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

Support MSI access to cognitive services QnAMaker and LUIS #1136

Closed
scheyal opened this issue Mar 2, 2021 · 0 comments
Closed

Support MSI access to cognitive services QnAMaker and LUIS #1136

scheyal opened this issue Mar 2, 2021 · 0 comments
Labels
needs-triage The issue has just been created and it has not been reviewed by the team.

Comments

@scheyal
Copy link
Contributor

scheyal commented Mar 2, 2021

BF CLI will have to light up access of QnAMaker and LUIS services using Managed Service Identity.
We know the services support MSI.

We need to put the ground work to investigate

  • Do they support access via the interfaces we use (REST API)?
  • Do we have sufficient info to access the right resources via the CLI
  • Can we allow side by side migration and slowly deprecate use of keys.

References:

The BF CLI (as a client) needs to support AAD Auth. Refer to Sign in with the Azure CLI | Microsoft Docs for how Azure CLI has done that. In that case, the AAD security principal is the one created for the CLI user. That user needs to be in Cognitive Services role(s) for RBAC (ex. “Cognitive Services User”) to work.

https://docs.microsoft.com/en-us/azure/cognitive-services/authentication?tabs=powershell#authenticate-with-azure-active-directory has a sample for registered AAD app (i.e. service principal). User principal (of the CLI user) works the same way.

The Microsoft Authentication Library (MSAL) Supports Node.JS. Refer to https://docs.microsoft.com/en-us/azure/active-directory/develop/reference-v2-libraries.

QnA maker supports MSI already as documented here: Authentication - Azure Cognitive Services | Microsoft Docs

@scheyal scheyal added the needs-triage The issue has just been created and it has not been reviewed by the team. label Mar 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage The issue has just been created and it has not been reviewed by the team.
Projects
None yet
Development

No branches or pull requests

2 participants