Forum Discussion
Solved
Authenticating with an access token Connect-MicrosoftTeams
Has anyone tried authenticating with an access token (using -AadAccessToken or -MsAccessToken)? The old version of New-CsOnlineSession had an -OAuthAccessToken param, which accepted a jwt with the PS ...
- FYI - I raised a ticket, and it should be fixed by mid november.
Issue description:
Cannot properly run Connect-MicrosoftTeams -AccessTokens
Resolution Steps:
Escalated case with our engineering Team
Issue is known bug and currently being fixed
Expecting a fix to go out by NOV mid
PhoneMe007, Can you please explain more briefly about the issue.
- Can anyone in Microsoft please share some information on, when then cmdlet, Grant-CsOnlineVoiceRoutingPolicy, will be available with App Based Authentication using certificate?
Currently its only available in none-interactive scripts using Client Secret !!!! - Similarly lots of items are broken: https://twitter.com/AndresGorzelany/status/1377263616353824774?s=19
- Hi PhoneMe007 could you please check with latest Powershell Teams module. It have the inbuilt sfb connecter features.
- No change teams1535 ☹️
- New-CsOnlineSession has an -OAuthAccessToken param, which accepted a jwt with the Powershell permissions in the scope, which we could obtain silently, and so avoid login to run the Powershell commands. This no longer works for Connect-MicrosoftTeams with any of the voice related cmdlets and functions. We can obtain the token but Powershell returns an error.
- Sridevi-MSFT Have you been able to find a solution?
SajAccess4 I have taken this to Engineering team will update you immediately once I get any inputs from them.
