-
|
Following the authentication tutorial, the image in doc talks about adding certain set of scopes for sample workload to run. I want to know, what is the need of "User.read" scope from Graph APIs. I have not provided permission to this scope from security purpose and only enabled my Azure App to be authorized on required scopes like "Lakehouse.Read.All". Am I missing something under the hood and is this user scope a must, to have our workload running? What's the use of this scope from workload perspective?
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
This scope is added automatically when creating the application, may I ask what's the security concern here?. |
Beta Was this translation helpful? Give feedback.
This scope is added automatically when creating the application, may I ask what's the security concern here?.
Our consent flow requires at least 1 dependency on graph and it's recommended to keep it.
You can replace it with any other graph scope including openID Connect scopes, for example "openId".