accessToken not generated after adding Scope

[bhandaribhumin]

let kScopes: [String] = ["user.read","Calendars.Read","Calendars.ReadWrite"]

App Permission:

Error Log:

Could not acquire token silently: Error Domain=MSALErrorDomain Code=-50003 "(null)" UserInfo={MSALDeclinedScopesKey=(
  "Calendars.Read",
  "Calendars.ReadWrite"
), MSALGrantedScopesKey=(
    "User.Read",
    email
), MSALErrorDescriptionKey=Server returned less scopes than requested

TID=101906 MSAL 1.1.3 iOS 14.0 [2020-08-21 12:21:19 - ] Server returned less scopes than requested, granted scopes: {(
    "User.Read",
    profile,
    openid,
    email
)}
TID=101906 MSAL 1.1.3 iOS 14.0 [2020-08-21 12:21:19 - ] Removing reserved scopes from granted scopes: {(
    openid,
    profile,
    "offline_access"
)}
TID=101906 MSAL 1.1.3 iOS 14.0 [2020-08-21 12:21:19 -] Final granted scopes: {(
    "User.Read",
    profile,
    openid,
    email
)}
TID=101906 MSAL 1.1.3 iOS 14.0 [2020-08-21 12:21:19 -] [MSAL] Silent flow finished. Result (null), error: -51415 error domain: MSIDOAuthErrorDomain
TID=101906 MSAL 1.1.3 iOS 14.0 [2020-08-21 12:21:19 - ] [MSAL] acquireTokenSilent returning with error: (MSALErrorDomain, -50003) Masked(not-null)

[kaisong1990]

@bhandaribhumin Thanks for providing the information. Based on the info from the error log, there is no Calendars.Read and Calendars.ReadWrite in the final granted scopes.

Could you try to reproduce the issue and provide correlation id for further investigation?

[bhandaribhumin]

Yes I was using the same client ID, I confirmed. Also see above image for app permissions I already given to this app.

[bhandaribhumin]

@kaisong1990 awaiting please help me on this.

[bhandaribhumin]

@kaisong1990 is below policy is blocking me for call Graph API.

[jasoncoolmax]

Did your issue go away once you uncheck the above box?

[bhandaribhumin]

@jasoncoolmax This is recommended from Microsoft for our organization.

[aherciya]

@bhandaribhumin Are you still seeing this issue?

[bhandaribhumin]

@aherciya thanks for asking but our org. admin is still looking for remove this policy from azure. Awaiting acknowledge from admin :)

[mipetriu]

Closing this issue due to lack of response. Feel free to reopen when the policy can be removed.