[BUG] MSAL2Teams provider custom scope

[vogtn]

Describe the bug Placeholder issue to help for issue with permissions, custom api usage

Screenshots If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. edge, chrome, safari]
• Framework [e.g. react, vue, none]
• Context [e.g. Microsoft Teams, SharePoint, Office Add-ins, Web]
• Version [e.g. 0.1]
• Provider [e.g. Msal2Provider] (bonus if you share the provider config)

Additional context Add any other context about the problem here.

[ghost]

Hello vogtn, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌

[ARsquare]

Bug Not able to get the access token for scope with permission to custom service API.

Environment OS: macOS, windows Browser: chrome, edge Framework: react Context: Microsoft Teams Provider: MSAL2Teams provider

Sample permission: api://bc8d95c2-812e-4b1a-affc-c329d23f5809/access_as_user

I can see the permission in the consent screen (the 1st permission), but the access token that I get is not containing this permission in it's scope.

[vogtn]

More context: https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-on-behalf-of-flow#:~:text=and%20combined%20consent-,The%20middle%20tier%20application,-adds%20the%20client

Trying to enable this scenario

[gavinbarron]

Closed as this provider is deprecated