SOLVED

Authenticating with an access token Connect-MicrosoftTeams

%3CLINGO-SUB%20id%3D%22lingo-sub-2233794%22%20slang%3D%22en-US%22%3EAuthenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2233794%22%20slang%3D%22en-US%22%3EHas%20anyone%20tried%20authenticating%20with%20an%20access%20token%20(using%20-AadAccessToken%20or%20-MsAccessToken)%3F%20The%20old%20version%20of%20New-CsOnlineSession%20had%20an%20-OAuthAccessToken%20param%2C%20which%20accepted%20a%20jwt%20with%20the%20PS%20permissions%20in%20the%20scope%2C%20which%20one%20could%20obtain%20silently%2C%20and%20so%20avoid%20login.%3CBR%20%2F%3E%3CBR%20%2F%3ENew-CsOnlineSession%20has%20been%20dropped%20and%20the%20SfB%20Connector%20is%20end%20of%20life%20in%20July%20and%20Connect-MicrosoftTeams%20does%20appear%20to%20support%20token%20for%20the%20telephony%20functions.%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2233794%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECalling%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2254020%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2254020%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1007716%22%20target%3D%22_blank%22%3E%40PhoneMe007%3C%2FA%3E%2C%20Can%20you%20please%20explain%20more%20briefly%20about%20the%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2256987%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2256987%22%20slang%3D%22en-US%22%3ENew-CsOnlineSession%20has%20an%20-OAuthAccessToken%20param%2C%20which%20accepted%20a%20jwt%20with%20the%20Powershell%20permissions%20in%20the%20scope%2C%20which%20we%20could%20obtain%20silently%2C%20and%20so%20avoid%20login%20to%20run%20the%20Powershell%20commands.%20This%20no%20longer%20works%20for%20Connect-MicrosoftTeams%20with%20any%20of%20the%20voice%20related%20cmdlets%20and%20functions.%20We%20can%20obtain%20the%20token%20but%20Powershell%20returns%20an%20error.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2256997%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2256997%22%20slang%3D%22en-US%22%3ESimilarly%20lots%20of%20items%20are%20broken%3A%20%3CA%20href%3D%22https%3A%2F%2Ftwitter.com%2FAndresGorzelany%2Fstatus%2F1377263616353824774%3Fs%3D19%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftwitter.com%2FAndresGorzelany%2Fstatus%2F1377263616353824774%3Fs%3D19%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273692%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273692%22%20slang%3D%22en-US%22%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1007716%22%20target%3D%22_blank%22%3E%40PhoneMe007%3C%2FA%3E%20could%20you%20please%20check%20with%20latest%20Powershell%20Teams%20module.%20It%20have%20the%20inbuilt%20sfb%20connecter%20features.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276292%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276292%22%20slang%3D%22en-US%22%3ENo%20change%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F635527%22%20target%3D%22_blank%22%3E%40teams1535%3C%2FA%3E%20%3Afrowning_face%3A%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2289757%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2289757%22%20slang%3D%22en-US%22%3EUpdate%3A%20Microsoft%20has%20released%20a%20preview%20version%20(2.1.0)%20of%20the%20Teams%20PowerShell%20module%20which%20works%20properly%20with%20modern%20authentication.%20It%E2%80%99s%20likely%20that%20this%20version%20will%20be%20pushed%20through%20to%20general%20availability%20quite%20quickly.%20%3CBR%20%2F%3EPlease%20go%20through%20this%20link%20for%20more%20information.%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Foffice365itpros.com%2F2021%2F03%2F10%2Fmicrosoft-updates-teams-powershell-module-2-0%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Foffice365itpros.com%2F2021%2F03%2F10%2Fmicrosoft-updates-teams-powershell-module-2-0%2F%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2293498%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2293498%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F635527%22%20target%3D%22_blank%22%3E%40teams1535%3C%2FA%3E%26nbsp%3BUnfortunately%20this%20method%20still%20doesn't%20work%20with%20any%20of%20the%20voice%20related%20cmdlets%2Ffunctions%20-%26nbsp%3BGet-CsOnlineSession%20for%20example%20is%20not%20a%20recognised%20cmdlets%20when%20you%20try%20running%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPS%20C%3A%5CWINDOWS%5Csystem32%26gt%3B%20Set-CsOnlinePSTNUsage%20-Identity%20Global%20-Usage%20%40%7Badd%3D%22UnrestrictedPstnUsage%22%7D%3C%2FP%3E%3CP%3EGet-CsOnlineSession%20%3A%20Run%20Connect-MicrosoftTeams%20before%20running%20cmdlets.%3C%2FP%3E%3CP%3EAt%20C%3A%5CProgram%20Files%5CWindowsPowerShell%5CModules%5CMicrosoftTeams%5C2.2.0%5Cnet472%5CSfBORemotePowershellModule.psm1%3A57%20char%3A22%3C%2FP%3E%3CP%3E%2B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%24remoteSession%20%3D%20%26amp%3B%20(Get-CsOnlineSessionCommand)%3C%2FP%3E%3CP%3E%2B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%2B%20CategoryInfo%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20NotSpecified%3A%20(%3A)%20%5BGet-CsOnlineSession%5D%2C%20UnauthorizedAccessException%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%2B%20FullyQualifiedErrorId%20%3A%20UnauthorizedAccessException%2CMicrosoft.Teams.ConfigApi.Cmdlets.GetCsOnlineSession%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EInvoke-Command%20%3A%20Cannot%20validate%20argument%20on%20parameter%20'Session'.%20The%20argument%20is%20null%20or%20empty.%20Provide%20an%20argument%3C%2FP%3E%3CP%3Ethat%20is%20not%20null%20or%20empty%2C%20and%20then%20try%20the%20command%20again.%3C%2FP%3E%3CP%3EAt%20C%3A%5CProgram%20Files%5CWindowsPowerShell%5CModules%5CMicrosoftTeams%5C2.2.0%5Cnet472%5CSfBORemotePowershellModule.psm1%3A47766%20char%3A38%3C%2FP%3E%3CP%3E%2B%20...%26nbsp%3B%26nbsp%3B%26nbsp%3B%20-Session%20(Get-PSImplicitRemotingSession%20-CommandName%20'Set-CsOnline%20...%3C%2FP%3E%3CP%3E%2B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%2B%20CategoryInfo%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20InvalidData%3A%20(%3A)%20%5BInvoke-Command%5D%2C%20ParentContainsErrorRecordException%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%2B%20FullyQualifiedErrorId%20%3A%20ParameterArgumentValidationError%2CMicrosoft.PowerShell.Commands.InvokeCommandCommand%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2309951%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2309951%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1007716%22%20target%3D%22_blank%22%3E%40PhoneMe007%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F635527%22%20target%3D%22_blank%22%3E%40teams1535%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20either%20of%20you%20been%20able%20to%20resolve%20this%20issue%20as%20I'm%20experiencing%20the%20same%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2313459%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2313459%22%20slang%3D%22en-US%22%3ENope%2C%20and%20even%20in%202.3.0%20released%20yesterday%20it's%20no%20better...%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2315780%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2315780%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F998754%22%20target%3D%22_blank%22%3E%40Sridevi-MSFT%3C%2FA%3E%20Have%20you%20been%20able%20to%20find%20a%20solution%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2320101%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2320101%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1041635%22%20target%3D%22_blank%22%3E%40SajAccess4%3C%2FA%3E%26nbsp%3BI%20have%20taken%20this%20to%20Engineering%20team%20will%20update%20you%20immediately%20once%20I%20get%20any%20inputs%20from%20them.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2323623%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2323623%22%20slang%3D%22en-US%22%3EThanks%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F998754%22%20target%3D%22_blank%22%3E%40Sridevi-MSFT%3C%2FA%3E%2C%20appreciate%20your%20help%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2345844%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2345844%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20facing%20the%20same%20issue%20on%20connecting%20to%20the%20Teams%20module%20using%20an%20access%20token.%20Although%20the%20command%20doesnt%20throw%20and%20error%2C%20running%20Skype%20commands%20gives%20me%20this%20for%20the%20command%20%22Get-CsTeamsCallingPolicy%22%3C%2FP%3E%3CP%3EError%3A%3CBR%20%2F%3EGet-CsOnlineSession%20%3A%20Run%20Connect-MicrosoftTeams%20before%20running%20cmdlets.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2345847%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2345847%22%20slang%3D%22en-US%22%3EI%20am%20facing%20the%20same%20issue%20on%20connecting%20to%20the%20Teams%20module%20using%20an%20access%20token.%20Although%20the%20command%20doesnt%20throw%20and%20error%2C%20running%20Skype%20commands%20gives%20me%20this%20for%20the%20command%20%22Get-CsTeamsCallingPolicy%22%3CBR%20%2F%3E%3CBR%20%2F%3EError%3A%3CBR%20%2F%3EGet-CsOnlineSession%20%3A%20Run%20Connect-MicrosoftTeams%20before%20running%20cmdlets.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2354827%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2354827%22%20slang%3D%22en-US%22%3EI%20have%20experienced%20the%20same%20thing%20with%20Get-CsOnlineUser.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2365019%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2365019%22%20slang%3D%22en-US%22%3Ewhat%20is%20the%20use%20of%20releasing%20this%20powershell%20if%20it%20doesn't%20work%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2367427%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2367427%22%20slang%3D%22en-US%22%3EI%20am%20also%20finding%20that%20when%20connecting%20with%20access%20tokens%20the%20Get-CSOnlinePSTNGateway%20and%20anything%20that%20used%20to%20be%20connected%20via%20the%20new-csonlinesession%20no%20longer%20functions.%3CBR%20%2F%3EIf%20you%20log%20in%20with%20Connect-MicrosoftTeams%20interactively%20then%20it%20will%20work%2C%20but%20this%20is%20undesirable%20for%20our%20automation%20requirements.%3CBR%20%2F%3EModule%20version%202.3.1%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2367883%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2367883%22%20slang%3D%22en-US%22%3E%3CDIV%3E%3CFONT%20face%3D%22inherit%22%3EWe%20have%20implemented%20a%20fix%20which%20will%20be%20available%20when%20the%203.0.0%20version%20is%20released.%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2368105%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2368105%22%20slang%3D%22en-US%22%3EWhat%20is%20the%20likely%20date%20for%20its%20release%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2368121%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2368121%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1051121%22%20target%3D%22_blank%22%3E%40priyachads%3C%2FA%3E%26nbsp%3B-%20Currently%20we%20don't%20have%20any%20ETA%20to%20share.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2368536%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2368536%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F998754%22%20target%3D%22_blank%22%3E%40Sridevi-MSFT%3C%2FA%3E%26nbsp%3B%20So%20what%20do%20you%20suggest%20until%20the%20AccessToken%20method%20works%3F%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20currently%20unable%20to%20manage%20the%20Teams%2FSFB%20using%20any%20auth%20method%20we%20have%20available%20(except%20for%20direct%2C%20user-present%20auth%20which%20doesn't%20work%20in%20an%20automated%20environment).%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20is%20the%20currently-supported%20method%20for%20using%20(e.g.)%20%22Get-CsOnlineUser%22%20(or%20what%20is%20the%20equivalent%20cmdlet%20that%20should%20work%20with%20the%20available%20Connect-MicrosoftTeams%20authentication%20methods)%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2369003%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2369003%22%20slang%3D%22en-US%22%3EThanks%20Sridevi!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2372817%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2372817%22%20slang%3D%22en-US%22%3EI%20am%20also%20getting%20the%20same%20issue.%20Skype%20for%20Business%20Online%20Powershell%20connections%20are%20blocked%2C%20and%20the%20Teams%20Powershell%20module%20which%20replaces%20them%20does%20not%20work.%20Are%20there%20any%20workarounds%20or%20do%20we%20have%20to%20wait%20and%20hope%20that%20version%203.0.0%20fixes%20the%20issue%3F%3CBR%20%2F%3EWould%20it%20be%20possible%20to%20unblock%20the%20Skype%20for%20Business%20Online%20Powershell%20connections%20until%20this%20issue%20is%20resolved%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2375159%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2375159%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20same%20issue%20as%20the%20others%20there.%20I%20can't%20do%20what%20i%20have%20to%20do%20for%20Teams%20Voice.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2377029%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2377029%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F998754%22%20target%3D%22_blank%22%3E%40Sridevi-MSFT%3C%2FA%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20please%20suggest%20an%20alternative%20method%20if%20new%20%22Connect-MicrosoftTeams%22%20does%20not%20work%20using%20-AadAccessToken%20for%20executing%20Get-CsTenant%20or%20SFB%20commands%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20blocked%20and%20not%20sure%20when%20the%20fix%20of%203.0.x%20will%20come%20%3F%20Please%20help.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2377031%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2377031%22%20slang%3D%22en-US%22%3EMicrosoft%20retired%20SFB%20but%20did%20not%20support%20the%20-AadAccessToken.%20Is%20there%20any%20other%20way%20for%20now%20to%20deal%20with%20this%20situation%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2377285%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2377285%22%20slang%3D%22en-US%22%3EMy%20understanding%20is%20that%20we'll%20need%20to%20wait%20for%203.x%20to%20see%20if%20this%20resolves%20the%20situation.%20From%20the%20released%20notes%20it%20sounds%20reasonably%20positive.%20Interesting%20that%20the%20release%20notes%20came%20ahead%20of%20delivery%2C%20when%20ordinarily%20they%20lag%20a%20few%20weeks%20behind.%20So%20perhaps%20this%20was%20reactive%20instead%20of%20proactive%2C%20based%20on%20the%20chatter....%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2377288%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2377288%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F998754%22%20target%3D%22_blank%22%3E%40Sridevi-MSFT%3C%2FA%3E%20do%20you%20have%20a%20ballpark%20figure%20on%20a%20release%20date%20for%203.0%3F%20May%2C%20Q2%2C%20Q3...%20This%20will%20assist%20with%20expectation%20management.%20Are%20you%20also%20saying%20this%20will%20be%20a%20definitive%20fix%20in%203.0%2C%20like%20for%20like%20in%20terms%20of%20token%20authentication%3F%20Thanks%20very%20much%20as%20always.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2381171%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2381171%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1007716%22%20target%3D%22_blank%22%3E%40PhoneMe007%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20pretty%20sure%20that%20this%20is%20the%20same%20problem%20that%20I%20am%20having.%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20what%20I%20am%20doing.%3C%2FP%3E%3CP%3EFor%20my%20test%20added%20a%20new%20user%20to%20my%20tenant%20with%20the%20global%20admin%20role%20and%20is%20configured%20it%20to%20use%20MFA.%20This%20is%20the%20only%20user%20that%20in%20the%20tenant%20that%20is%20configured%20this%20way.%3CBR%20%2F%3EIn%20AzureAD%20I%20then%20added%20a%20new%20App%20Registration%20which%20was%20allocated%20the%20Application%20(client)%20ID%20of%20%2271045f16-xxxx-xxxx-xxxx-xxxx%22.%3CBR%20%2F%3ETo%20this%20App%20Registration%20I%20added%20a%20new%20secret%20that%20was%20assigned%20the%20Secret%20ID%20%22314e6c61-xxxx-xxxx-xxxx-xxxxxxxxxxxxx%22%20and%20the%20value%20%22YDjZy--xx~xxxxxxxxxxxxxxx.xx.xxxxx%22.%3CBR%20%2F%3EI%20also%20added%20Policy.Read.All%20API%20Permission.%3C%2FP%3E%3CP%3EI%20then%20ran%20the%20following%20script%20which%20acquires%20the%20access_token%20that%20is%20used%20in%20the%20Connect-MicrosoftTeams%20command.%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-powershell%22%3E%3CCODE%3E%24clientId%20%3D%20%2271045f16-xxxx-xxxx-xxxx-xxxx%22%20%20%0A%24clientSecret%20%3D%20%22YDjZy--xx~xxxxxxxxxxxxxxx.xx.xxxxx%22%20%20%0A%24tenantName%20%3D%20%22mydomain.onmicrosoft.com%22%20%20%0A%24resource%20%3D%20%22https%3A%2F%2Fgraph.microsoft.com%2F%22%20%20%0A%24tokenBody%20%3D%20%40%7B%20%20%0A%20%20%20Grant_Type%20%20%20%20%3D%20%22client_credentials%22%20%20%0A%20%20%20Scope%20%20%20%20%20%20%20%20%20%3D%20%22https%3A%2F%2Fgraph.microsoft.com%2F.default%22%20%20%0A%20%20%20Client_Id%20%20%20%20%20%3D%20%24clientId%20%20%0A%20%20%20Client_Secret%20%3D%20%24clientSecret%20%20%0A%7D%20%20%20%0A%24tokenResponse%20%3D%20Invoke-RestMethod%20-Uri%20%22https%3A%2F%2Flogin.microsoftonline.com%2F%24tenantName%2Foauth2%2Fv2.0%2Ftoken%22%20-Method%20POST%20-Body%20%24tokenBody%20%20%0AImport-Module%20MicrosoftTeams%0AConnect-MicrosoftTeams%20-AadAccessToken%20%24tokenResponse.access_token%20-AccountId%20mfaadmin%40mydomain.net%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3EWhatever%20command%20I%20try%20to%20run%20fails%20with%20the%20following%20error%3A%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-powershell%22%3E%3CCODE%3EGet-CsCloudMeetingPolicy%0A%20%20%20Get-CsOnlineSession%20%3A%20Run%20Connect-MicrosoftTeams%20before%20running%20cmdlets.%0A%20%20%20At%20C%3A%5CProgram%20Files%5CWindowsPowerShell%5CModules%5CMicrosoftTeams%5C2.3.1%5Cnet472%5CSfBORemotePowershellModule.psm1%3A63%20char%3A22%0A%20%20%20%2B%20%20%20%20%20%24remoteSession%20%3D%20%26amp%3B%20(Get-CsOnlineSessionCommand)%0A%20%20%20%2B%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%0A%20%20%20%2B%20CategoryInfo%20%20%20%20%20%20%20%20%20%20%3A%20NotSpecified%3A%20(%3A)%20%5BGet-CsOnlineSession%5D%2C%20UnauthorizedAccessException%0A%20%20%20%2B%20FullyQualifiedErrorId%20%3A%20UnauthorizedAccessException%2CMicrosoft.Teams.ConfigApi.Cmdlets.GetCsOnlineSession%0A%20%60%60Invoke-Command%20%3A%20Cannot%20validate%20argument%20on%20parameter%20'Session'.%20The%20argument%20is%20null%20or%20empty.%20Provide%20an%20argument%0A%20%20%20that%20is%20not%20null%20or%20empty%2C%20and%20then%20try%20the%20command%20again.%0A%20%20At%20C%3A%5CProgram%20Files%5CWindowsPowerShell%5CModules%5CMicrosoftTeams%5C2.3.1%5Cnet472%5CSfBORemotePowershellModule.psm1%3A2975%20char%3A38%0A%20%2B%20...%20%20%20%20-Session%20(Get-PSImplicitRemotingSession%20-CommandName%20'Get-CsCloudM%20...%0A%20%2B%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%0A%20%2B%20CategoryInfo%20%20%20%20%20%20%20%20%20%20%3A%20InvalidData%3A%20(%3A)%20%5BInvoke-Command%5D%2C%20ParentContainsErrorRecordException%0A%20%2B%20FullyQualifiedErrorId%20%3A%20ParameterArgumentValidationError%2CMicrosoft.PowerShell.Commands.InvokeCommandCommand%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3EWhen%20I%20run%20the%20Connect-MicrosoftTeams%20command%20with%20the%20standard%20credentials%20parameters%2C%20I%20am%20able%20to%20call%20all%20the%20powershell%20commands%20(that%20I%20tested%20with).%3CBR%20%2F%3EIs%20this%20the%20same%20issue%2C%20or%20should%20I%20open%20a%20separate%20thread%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2381371%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2381371%22%20slang%3D%22en-US%22%3EThat%20is%20certainly%20the%20issue%20we%20are%20facing.%20Connect-MicrosoftTeams%20has%20never%20worked%20with%20this%20sort%20of%20authentication%2C%20though%20it%20is%20supposed%20to%20work%20and%20the%20eventual%203.0%20version%20might%20possibly%20fix%20it%2C%20finally.%3CBR%20%2F%3E%3CBR%20%2F%3EUp%20until%20now%20we%20have%20been%20doing%20something%20trickier%20using%20New-PsSession%20and%20Import-PsSession%20which%20was%20working%20(and%20seemed%20to%20provide%20the%20missing%20%22Session%22%20that%20your%20error%20is%20complaining%20about).%20Sadly%2C%20this%20approach%20has%20evidently%20been%20deprecated%20and%20now%20only%20works%20intermittently%20or%20with%20specific%20tenants%20(or%20maybe%20specific%20back-end%20lync%20servers).%20Microsoft%20has%20clearly%20removed%20a%20working%20feature%20before%20they%20have%20a%20working%20replacement.%3CBR%20%2F%3E%3CBR%20%2F%3EInterestingly%2C%20when%20it%20works%2C%20we%20get%20the%20following%20warning%20message%20instead%20of%20an%20error%3A%3CBR%20%2F%3E%3CBR%20%2F%3EWARNING%3A%20Your%20tenant%20has%20been%20granted%20exception%20to%20use%20Skype%20For%20Business%20Online%20connector%20till%20June%2015%202021.%20Your%20organization%20must%20replace%20the%20Skype%20for%20Business%20Online%20PowerShell%20connector%20module%20with%20the%20Teams%20PowerShell%20Module%20prior%20to%20that%20date.%20Please%20visit%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fsfbocon2tpm%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fsfbocon2tpm%3C%2FA%3E%20for%20supported%20options.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2383353%22%20slang%3D%22de-DE%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2383353%22%20slang%3D%22de-DE%22%3E%3CP%3EWe%20are%20facing%20the%20same%20issues%20here.%20Somehow%20the%20S4B%20OnlineConnector%20got%20removed%20without%20providing%20a%20working%20alternative%20solution%20to%20change%20policies%20scriptbased.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2385726%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2385726%22%20slang%3D%22en-US%22%3EAppears%20to%20be%20the%20same%20and%20potentially%20fixed%20with%203.0%20release%2C%20which%20we%20hope%20will%20appear%20this%20week...%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2387239%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2387239%22%20slang%3D%22en-US%22%3E%3CP%3ENote%20that%20there%20is%20a%202.3.2%20preview%20(available%20on%20the%20%3CA%20href%3D%22https%3A%2F%2Fwww.powershellgallery.com%2Fpackages%2FMicrosoftTeams%2F2.3.1%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E2.3.1%20download%20page%3C%2FA%3E)%20with%20no%20release%20notes%20or%20other%20info%20about%20content.%26nbsp%3B%20However%2C%20we've%20already%20tested%20and%20it%20breaks%20in%20a%20different%20way%20under%20this%20use%20case.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20actually%20have%20created%20a%20workaround%20for%20this%20AccessToken%20auth%20issue%20with%202.3.1%2C%20which%20involved%20decompiling%20some%20DLLs%20to%20figure%20out%20the%20bug%20in%20that%20Microsoft%20code.%26nbsp%3B%20%26nbsp%3BWe%20may%20be%20able%20to%20post%20that%20approach%20after%20some%20additional%20review.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2388834%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2388834%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1041768%22%20target%3D%22_blank%22%3E%40et01267%3C%2FA%3E%20that%20is%20really%20great!%20I'm%20keen%20to%20try%20this%20out.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2389566%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2389566%22%20slang%3D%22en-US%22%3EThanks%2C%20would%20be%20really%20interested%20to%20view%20your%20findings.%3CBR%20%2F%3E%3CBR%20%2F%3EThey%20have%20now%20added%20release%20notes%20for%20for%202.3.2%20preview%20release.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2390596%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2390596%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20got%20the%202.3.2%20preview%20installed%20and%20I%20am%20now%20getting%20this%20error%3A%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-powershell%22%3E%3CCODE%3EPS%20C%3A%5CUsers%5CAdministrator%26gt%3B%20Connect-MicrosoftTeams%20-AccessTokens%20%40(%24graph_token%2C%20%24teams_token)%20-AccountId%20XXXX%40XXXX%0AConnect-MicrosoftTeams%20%3A%20Invalid%20audiences%2048ac35b8-9aa8-4d74-927d-1f4a14a0b239%20found%20in%20the%20provided%20tokens%0AAt%20line%3A1%20char%3A1%0A%2B%20Connect-MicrosoftTeams%20-AccessTokens%20%40(%24graph_token%2C%20%24teams_token)%20-A%20...%0A%2B%20~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%0A%20%20%20%20%2B%20CategoryInfo%20%20%20%20%20%20%20%20%20%20%3A%20AuthenticationError%3A%20(%3A)%20%5BConnect-MicrosoftTeams%5D%2C%20ArgumentException%0A%20%20%20%20%2B%20FullyQualifiedErrorId%20%3A%20Connect-MicrosoftTeams%2CMicrosoft.TeamsCmdlets.Powershell.Connect.ConnectMicrosoftTeams%0A%0AConnect-MicrosoftTeams%20%3A%20Invalid%20audiences%2048ac35b8-9aa8-4d74-927d-1f4a14a0b239%20found%20in%20the%20provided%20tokens%0AAt%20line%3A1%20char%3A1%0A%2B%20Connect-MicrosoftTeams%20-AccessTokens%20%40(%24graph_token%2C%20%24teams_token)%20-A%20...%0A%2B%20~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%0A%20%20%20%20%2B%20CategoryInfo%20%20%20%20%20%20%20%20%20%20%3A%20NotSpecified%3A%20(%3A)%20%5BConnect-MicrosoftTeams%5D%2C%20ArgumentException%0A%20%20%20%20%2B%20FullyQualifiedErrorId%20%3A%20System.ArgumentException%2CMicrosoft.TeamsCmdlets.Powershell.Connect.ConnectMicrosoftTeams%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20used%20%22%3CA%20href%3D%22https%3A%2F%2Fgraph.microsoft.com%2F.default%26quot%3B%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgraph.microsoft.com%2F.default%22%3C%2FA%3E%26nbsp%3Bas%20the%20scope%20for%20the%20graph%20access%20token%2C%20what%20should%20l%20use%20as%20the%20scope%20for%20the%20teams%20access%20token%2C%20any%20ideas%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2390756%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2390756%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1046905%22%20target%3D%22_blank%22%3E%40guyfrancis%3C%2FA%3E%3C%2FP%3E%3CP%3EIf%20I%20supply%20the%20tokens%20without%20securing%20them%2C%20I%20get%20an%20error%20about%20invalid%20audience%20too%2C%20which%20we%20have%20seen%20in%20the%20past%20when%20trying%20to%20use%20wrong%20tokens%20(e.g.%20using%20a%20graph%20token%20for%20sfb%20calls)%3C%2FP%3E%3CP%3EThe%20error%20message%20is%20interesting%20though.%20When%20I%20supply%20a%20graph%20token%20and%20a%20sfb%20token%2C%20it%20says%3A%3CBR%20%2F%3EInvalid%20audiences%20xxxxxxxx-9aa8-4d74-927d-1f4a14a0b239%20found%20in%20the%20provided%20tokens%3C%2FP%3E%3CP%3E(It%20seems%20you%20have%20to%20supply%20a%20minimum%20of%202%20tokens%2C%20or%20else%20you%20get%20a%20different%20error%20asking%20to%20supply%20a%20graph%20%2B%20a%20teams%20token)%3C%2FP%3E%3CP%3EAnyway%2C%20when%20I%20supply%20a%20graph%20token%20%2B%20a%20random%20Azure%20AD%20token%20(intentionally%20incorrect)%2C%20it%20gives%20the%20same%20error%20as%20above.%20When%20I%20supply%20a%20sfb%20token%20with%20a%20Azure%20AD%20token%2C%20it%20says%3A%3C%2FP%3E%3CP%3EInvalid%20audiences%20%3CA%20href%3D%22https%3A%2F%2Fgraph.microsoft.com%2Cxxxxxxxx-9aa8-4d74-927d-1f4a14a0b239%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgraph.microsoft.com%2Cxxxxxxxx-9aa8-4d74-927d-1f4a14a0b239%3C%2FA%3E%20found%20in%3CBR%20%2F%3Ethe%20provided%20tokens%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2393413%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2393413%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1007716%22%20target%3D%22_blank%22%3E%40PhoneMe007%3C%2FA%3E%26nbsp%3BI'm%20seeing%20this%20same%20behavior.%20%26nbsp%3BMy%20understanding%20is%20that%20the%20newest%20version%20was%20deprecating%20the%20AAD%20tokens%2C%20but%20it%20appears%20to%20still%20require%20them.%20%26nbsp%3BBut%20then%20when%20they%20are%20provided%20it%20complains%20that%20the%20audience%20is%20incorrect.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2394909%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2394909%22%20slang%3D%22en-US%22%3EI've%20got%20it%20work%20using%20%2248ac35b8-9aa8-4d74-927d-1f4a14a0b239%2F.default%22%20as%20the%20scope%20for%20the%20Teams%20access%20token.%20It%20is%20not%20fully%20tested%20yet%2C%20but%20I'm%20getting%20past%20the%20error%20with%20Connect-MicrosoftTeams.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2394932%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2394932%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1046905%22%20target%3D%22_blank%22%3E%40guyfrancis%3C%2FA%3E%20Connect-MicrosoftTeams%20also%20works%20for%20me%2C%20however%20after%20that%20has%20succeeded%20all%20cmdlets%20that%20I%20try%20to%20run%20return%20the%20original%20error.%3CBR%20%2F%3EGet-CsOnlineSession%20%3A%20Run%20Connect-MicrosoftTeams%20before%20running%20cmdlets....%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2396785%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2396785%22%20slang%3D%22en-US%22%3EThank%20you!%20This%20is%20the%20furthest%20I%20have%20gotten%20so%20far%2C%20however%20even%20now%20that%20I%20have%20both%20tokens%20and%20can%20successfully%20connect%20and%20run%20eg.%20Get-Team%2C%20the%20voice%20cmdlets%20like%20Get-CsOnlineUser%20still%20give%20a%20permissions%20error%20%22Connecting%20to%20remote%20server%20api.interfaces.records.teams.microsoft.com%20failed%20with%20the%20following%20error%20message%20%3A%20Access%20is%20denied.%22.%20Any%20idea%20which%20permissions%20should%20be%20granted%20for%20this%20to%20work%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2570303%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2570303%22%20slang%3D%22en-US%22%3EHas%20there%20been%20any%20update%20on%20when%20this%20fix%20will%20be%20released%3F%20In%203.0.0%20version%20or%20sooner%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2580183%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2580183%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20trying%20to%20setup%20something%20similar%20in%20Softerra%20Adaxes%2C%20but%20I'm%20not%20getting%20very%20far%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-powershell%22%3E%3CCODE%3E%24clientId%20%3D%20%22%22%20%20%0A%24clientSecret%20%3D%20%22%22%20%20%0A%24tenantName%20%3D%20%22tenant.onmicrosoft.com%22%0A%24tenantNameshort%20%3D%20%22%22%0A%24tenantIdCode%20%3D%20%22%22%0A%20%20%0A%24graphResource%20%3D%20%22https%3A%2F%2Fgraph.microsoft.com%2F%22%20%20%0A%24graphtokenBody%20%3D%20%40%7B%20%20%0A%20%20%20Grant_Type%20%20%20%20%3D%20%22client_credentials%22%20%20%0A%20%20%20Scope%20%20%20%20%20%20%20%20%20%3D%20%22https%3A%2F%2Fgraph.microsoft.com%2F.default%22%20%20%0A%20%20%20Client_Id%20%20%20%20%20%3D%20%24clientId%20%20%0A%20%20%20Client_Secret%20%3D%20%24clientSecret%20%20%0A%7D%20%20%20%0A%24graphTokenResponse%20%3D%20Invoke-RestMethod%20-Uri%20%22https%3A%2F%2Flogin.microsoftonline.com%2F%24tenantName%2Foauth2%2Fv2.0%2Ftoken%22%20-Method%20POST%20-Body%20%24graphtokenBody%0A%0A%0A%24teamsResource%20%3D%20%22https%3A%2F%2Fapi.interfaces.records.teams.microsoft.com%22%20%20%0A%24teamstokenBody%20%3D%20%40%7B%20%20%0A%20%20%20Grant_Type%20%20%20%20%3D%20%22client_credentials%22%20%20%0A%20%20%20Scope%20%20%20%20%20%20%20%20%20%3D%20%2248ac35b8-9aa8-4d74-927d-1f4a14a0b239%2F.default%22%20%20%0A%20%20%20Client_Id%20%20%20%20%20%3D%20%24clientId%20%20%0A%20%20%20Client_Secret%20%3D%20%24clientSecret%0A%20%20%0A%7D%20%20%20%0A%24TeamsTokenResponse%20%3D%20Invoke-RestMethod%20-Uri%20%22https%3A%2F%2Flogin.microsoftonline.com%2F%24tenantName%2Foauth2%2Fv2.0%2Ftoken%22%20-Method%20POST%20-Body%20%24teamstokenBody%0A%0AConnect-MicrosoftTeams%20-TenantId%20%24tenantId%20-AccessTokens%20%40(%24graphTokenResponse.access_token%2C%24TeamsTokenResponse.access_token)%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20get%20this%20error%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-csharp%22%3E%3CCODE%3EConnect-MicrosoftTeams%20%3A%20Not%20supported%20tenant%20type.%0AAt%20C%3A%5Cscripts%5Cconnect-teams.ps1%3A27%20char%3A1%0A%2B%20Connect-MicrosoftTeams%20-TenantId%20%24tenantId%20-AccessTokens%20%40(%24graphToke%20...%0A%2B%20~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%0A%20%20%20%20%2B%20CategoryInfo%20%20%20%20%20%20%20%20%20%20%3A%20AuthenticationError%3A%20(%3A)%20%5BConnect-MicrosoftTeams%5D%2C%20ArgumentException%0A%20%20%20%20%2B%20FullyQualifiedErrorId%20%3A%20Connect-MicrosoftTeams%2CMicrosoft.TeamsCmdlets.Powershell.Connect.ConnectMicrosoftTeams%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20I%20try%20something%20along%20the%20lines%20of%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-powershell%22%3E%3CCODE%3EConnect-MicrosoftTeams%20-TenantId%20%24tenantId%20-ClientId%20%24clientId%20-Certificatethumbprint%20%24certificateThumbprint%26nbsp%3B%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3BI%20get%20the%20following%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EConnecting%20to%20remote%20server%20api.interfaces.records.teams.microsoft.com%20failed%20with%20the%20following%20error%20message%20%3A%20The%20WinRM%20client%20cannot%20process%20the%20request....%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2655484%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2655484%22%20slang%3D%22en-US%22%3EAny%20Updates%20on%20this%20Topic%3F%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fteams%2Fconnect-microsoftteams%3Fview%3Dteams-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fteams%2Fconnect-microsoftteams%3Fview%3Dteams-ps%3C%2FA%3E%3CBR%20%2F%3E%24graphtoken%20%3D%20%23Get%20MSGraph%20Token%20for%20following%20for%20resource%20%22%3CA%20href%3D%22https%3A%2F%2Fgraph.microsoft.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgraph.microsoft.com%3C%2FA%3E%22%20and%20scopes%20%22AppCatalog.ReadWrite.All%22%2C%20%22Group.ReadWrite.All%22%2C%20%22User.Read.All%22%3B%3CBR%20%2F%3E%24teamstoken%20%3D%20%23Get%20Teams%20resource%20token%20for%20resource%20id%20%2248ac35b8-9aa8-4d74-927d-1f4a14a0b239%22%20and%20scope%20%22user_impersonation%22%3B%3CBR%20%2F%3E%3CBR%20%2F%3EConnect-MicrosoftTeams%20-AccessTokens%20%40(%24graphtoken%2C%20%24teamstoken)%20-AccountId%20%24adminaccount%3CBR%20%2F%3E%3CBR%20%2F%3EAccount%20Environment%20Tenant%20TenantId%3CBR%20%2F%3E-------%20-----------%20------------------------------------%20------------------------------------%3CBR%20%2F%3Euser%40contoso.com%20AzureCloud%20xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx%20xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx%3CBR%20%2F%3E%3CBR%20%2F%3ESpecifies%20a%20access%20tokens%20for%20%22MSGraph%22%20and%20%22Skype%20and%20Teams%20Tenant%20Admin%20API%22%20resources.%20This%20new%20parameter%20is%20added%20in%20version%202.3.2-preview.%3CBR%20%2F%3E%3CBR%20%2F%3EFollowing%20steps%20must%20be%20performed%20by%20Tenant%20Admin%20in%20the%20Azure%20portal%20when%20using%20your%20own%20application.%3CBR%20%2F%3E%3CBR%20%2F%3ESteps%20to%20configure%20the%20AAD%20application.%3CBR%20%2F%3E%3CBR%20%2F%3EGo%20to%20Azure%20portal%20and%20go%20to%20App%20Registrations.%3CBR%20%2F%3ECreate%20or%20select%20the%20existing%20application.%3CBR%20%2F%3EAdd%20the%20following%20permission%20to%20this%20Application.%3CBR%20%2F%3EClick%20API%20permissions.%3CBR%20%2F%3EClick%20Add%20a%20permission.%3CBR%20%2F%3EClick%20on%20the%20Microsoft%20MS%20Graph%2C%20and%20then%20select%20Delegated%20Permission.%3CBR%20%2F%3EAdd%20the%20following%20permissions%3A%20%22AppCatalog.ReadWrite.All%22%2C%20%22Group.ReadWrite.All%22%2C%20%22User.Read.All%22%3B%3CBR%20%2F%3ENext%2C%20we%20need%20to%20add%20%22Skype%20and%20Teams%20Tenant%20Admin%20API%22%20resource%20permission.%20Click%20Add%20a%20permission.%3CBR%20%2F%3ENavigate%20to%20%22APIs%20my%20organization%20uses%22%3CBR%20%2F%3ESearch%20for%20%22Skype%20and%20Teams%20Tenant%20Admin%20API%22.%3CBR%20%2F%3EAdd%20all%20the%20listed%20permissions.%3CBR%20%2F%3EGrant%20admin%20consent%20to%20both%20MS%20Graph%20and%20%22Skype%20and%20Teams%20Tenant%20Admin%20API%22%20name.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2677173%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2677173%22%20slang%3D%22en-US%22%3EThey%20seems%20to%20have%20gone%20backwards%20with%20release%202.5.0.%20I%20used%20to%20be%20able%20to%20use%3CBR%20%2F%3E%3CBR%20%2F%3EConnect-MicrosoftTeams%20-AccessTokens%20%40(%24graphtoken%2C%20%24teamstoken)%20-Verbose%20-AccountId%20%22user%40domain.com%22%3CBR%20%2F%3E%3CBR%20%2F%3Eto%20at%20least%20access%20the%20new%20cmdlets%2C%20but%20now%20I%20get%3CBR%20%2F%3E%3CBR%20%2F%3EParameter%20set%20cannot%20be%20resolved%20using%20the%20specified%20named%20parameters.%20One%20or%20more%20parameters%20issued%20cannot%20be%20used%20together%20or%20an%20insufficient%20number%20of%20parameters%20were%20provided.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2686622%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2686622%22%20slang%3D%22en-US%22%3ERemoving%20the%20-AccountId%20%22user%40domain.com%22%20parameter%20should%20allow%20you%20to%20login.%20Seems%20this%20detail%20is%20derived%20via%20the%20tokens%20now%20in%202.5.0%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2686628%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2686628%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F998754%22%20target%3D%22_blank%22%3E%40Sridevi-MSFT%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20is%20the%20timeline%20for%203.0.0%20to%20be%20released%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2688192%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2688192%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1138045%22%20target%3D%22_blank%22%3E%40MattLadewig%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUsing%20Teams%202.5.0%3C%2FP%3E%3CP%3EDoes%20not%20work%20here.%26nbsp%3B%20I've%20created%20a%20GitHub%20Issue%20to%20clarify%20the%20Permissions%20needed%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Foffice-docs-powershell%2Fissues%2F8194%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Foffice-docs-powershell%2Fissues%2F8194%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Teams_AccessTokens_01.jpg%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F306021i8E30F3BECEFFB200%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Teams_AccessTokens_01.jpg%22%20alt%3D%22Teams_AccessTokens_01.jpg%22%20%2F%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Teams_AccessTokens_02.jpg%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F306020i557DFF0FE74F926E%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Teams_AccessTokens_02.jpg%22%20alt%3D%22Teams_AccessTokens_02.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3EAndres%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2688735%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2688735%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1138045%22%20target%3D%22_blank%22%3E%40MattLadewig%3C%2FA%3EWhen%20I%20do%20this%20I%20now%20get%20%22Object%20reference%20not%20set%20to%20an%20instance%20of%20an%20object.%22%20on%20the%20Connect-MicrosoftTeams%20line.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2693854%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2693854%22%20slang%3D%22en-US%22%3EDo%20we%20have%20an%20update%20on%20when%20Teams%20module%203.0.0%20will%20release%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2804287%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2804287%22%20slang%3D%22en-US%22%3EHas%20anyone%20successfully%20got%20this%20working%20yet%3F%3CBR%20%2F%3E%3CBR%20%2F%3EThere%20was%20a%20new%20version%20released%20today%20for%20MicrosoftTeams%2C%20but%20I%20still%20unsuccessful.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20provided%20the%20App%20the%20relevant%20permissions%20as%20outlined%20in%20the%20documentation.%3CBR%20%2F%3E%3CBR%20%2F%3EConnect-MicrosoftTeams%20-AccessTokens%20%40(%24tokenResponse%2C%20%24teams_tokenResponse)%20-AccountId%20%24UPN%3CBR%20%2F%3E%3CBR%20%2F%3EConnect-MicrosoftTeams%20%3A%20Parameter%20set%20cannot%20be%20resolved%20using%20the%20specified%20named%20parameters.%3CBR%20%2F%3EAt%20line%3A1%20char%3A1%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2804369%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2804369%22%20slang%3D%22en-US%22%3EI%20got%20this%20working%20by%20rolling%20back%20to%20an%20older%20preview%20version.%3CBR%20%2F%3E%3CBR%20%2F%3EInstall-Module%20-Name%20MicrosoftTeams%20-RequiredVersion%20%222.3.2-preview%22%20-AllowPrerelease%20-force%3CBR%20%2F%3EImport-Module%20MicrosoftTeams%20-RequiredVersion%202.3.2%3CBR%20%2F%3E%3CBR%20%2F%3E%24ApplicationId%20%3D%20'xx'%3CBR%20%2F%3E%24ApplicationSecret%20%3D%20'xx'%3CBR%20%2F%3E%24TenantID%20%3D%20'xx'%3CBR%20%2F%3E%24UPN%20%3D%20%22admin%40xx%22%3CBR%20%2F%3E%3CBR%20%2F%3E%24ReqTokenBody%20%3D%20%40%7B%3CBR%20%2F%3EGrant_Type%20%3D%20%22client_credentials%22%3CBR%20%2F%3Eclient_Id%20%3D%20%24ApplicationId%3CBR%20%2F%3EClient_Secret%20%3D%20%24ApplicationSecret%3CBR%20%2F%3EScope%20%3D%20%22%3CA%20href%3D%22https%3A%2F%2Fgraph.microsoft.com%2F.default%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgraph.microsoft.com%2F.default%3C%2FA%3E%22%3CBR%20%2F%3E%7D%3CBR%20%2F%3E%3CBR%20%2F%3E%24graph_TokenResponse%20%3D%20Invoke-RestMethod%20-Uri%20%22%3CA%20href%3D%22https%3A%2F%2Flogin.microsoftonline.com%2F%24TenantID%2Foauth2%2Fv2.0%2Ftoken%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Flogin.microsoftonline.com%2F%24TenantID%2Foauth2%2Fv2.0%2Ftoken%3C%2FA%3E%22%20-Method%20POST%20-Body%20%24ReqTokenBody%3CBR%20%2F%3E%3CBR%20%2F%3E%24teams_ReqTokenBody%20%3D%20%40%7B%3CBR%20%2F%3EGrant_Type%20%3D%20%22client_credentials%22%3CBR%20%2F%3Eclient_Id%20%3D%20%24ApplicationId%3CBR%20%2F%3EClient_Secret%20%3D%20%24ApplicationSecret%3CBR%20%2F%3EScope%20%3D%20%2248ac35b8-9aa8-4d74-927d-1f4a14a0b239%2F.default%22%3CBR%20%2F%3E%7D%3CBR%20%2F%3E%3CBR%20%2F%3E%24teams_TokenResponse%20%3D%20Invoke-RestMethod%20-Uri%20%22%3CA%20href%3D%22https%3A%2F%2Flogin.microsoftonline.com%2F%24TenantID%2Foauth2%2Fv2.0%2Ftoken%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Flogin.microsoftonline.com%2F%24TenantID%2Foauth2%2Fv2.0%2Ftoken%3C%2FA%3E%22%20-Method%20POST%20-Body%20%24teams_ReqTokenBody%3CBR%20%2F%3E%3CBR%20%2F%3EConnect-MicrosoftTeams%20-AccessTokens%20%40(%24graph_tokenResponse.access_token%2C%24teams_tokenResponse.access_token)%20-AccountId%20%24UPN%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2851155%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2851155%22%20slang%3D%22en-US%22%3EFYI%20-%20I%20raised%20a%20ticket%2C%20and%20it%20should%20be%20fixed%20by%20mid%20november.%3CBR%20%2F%3E%3CBR%20%2F%3EIssue%20description%3A%3CBR%20%2F%3ECannot%20properly%20run%20Connect-MicrosoftTeams%20-AccessTokens%3CBR%20%2F%3E%3CBR%20%2F%3EResolution%20Steps%3A%3CBR%20%2F%3EEscalated%20case%20with%20our%20engineering%20Team%3CBR%20%2F%3EIssue%20is%20known%20bug%20and%20currently%20being%20fixed%3CBR%20%2F%3EExpecting%20a%20fix%20to%20go%20out%20by%20NOV%20mid%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2887943%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2887943%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F960255%22%20target%3D%22_blank%22%3E%40NMLVS%3C%2FA%3E%20good%20to%20hear%20that%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2926600%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2926600%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20were%20successfully%20using%20Microsoft%20Teams%20powershell%20using%20Access%20Tokens.%20But%20today%20we%20are%20faced%20with%20strange%20issue%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20getting%20error%20during%20authentication%3A%20Connect-MicrosoftTeams%3C%2FP%3E%3CP%3E%3CFONT%20color%3D%22%23FF0000%22%3E%3CSTRONG%3EThe%20provided%20tokens%20must%20have%20less%20than%20180%20seconds%20difference%20in%20the%20time%20range%20of%20expiration.%20System.Management.Automation.RemoteException%3A%20The%20provided%20tokens%20must%20have%20less%20than%20180%20seconds%20difference%20in%20the%20time%20range%20of%20expiration.%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20checked%20the%20access%20tokens%20expiry%2C%20they%20do%20differ%20by%20more%20then%20180%20seconds.%20We%20are%20using%20Refresh%20tokens%20to%20generate%20Access%20tokens.%20This%20is%20done%20automatically%20using%20.NET%20code%2C%20both%20access%20tokens%20are%20fetched%20within%20few%20milliseconds%2C%20yet%20the%20expiry%20differs.%20And%20when%20we%20use%20these%20tokens%20we%20get%20above%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20experienced%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMuhammad%20Usman%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2947209%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2947209%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1206908%22%20target%3D%22_blank%22%3E%40usman83%3C%2FA%3E%26nbsp%3B%3CSPAN%3EMuhammad%2C%20we%20stating%20to%20have%20this%20same%20error%20just%20today%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22The%20provided%20tokens%20must%20have%20less%20than%20180%20seconds%20difference%20in%20the%20time%20range%20of%20expiration.%22%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CBR%20%2F%3EI've%20compared%20these%202%20tokens%20expiration%20time%20and%20there%20are%20almost%207%20minutes%20of%20difference%20between%20them.%20We%20ask%20Microsoft%20to%20generate%20the%20tokens%20one%20right%20after%20the%20other.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EIf%20you%20get%20a%20solution%2C%20please%20share%20it%20here.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2952992%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2952992%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F724919%22%20target%3D%22_blank%22%3E%40hernan-invosys%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20having%20the%20same%20issue%2C%20this%20was%20working%20for%20till%2010%2F11%2F2021%20and%20it%20has%20suddenly%20stopped%20working%20today.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2963967%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2963967%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F998754%22%20target%3D%22_blank%22%3E%40Sridevi-MSFT%3C%2FA%3E%26nbsp%3BAny%20update%20on%20the%20error%20with%20180%20seconds%20difference%20in%20token%20expiration%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2964926%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2964926%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20Using%20Teams%20PowerShell%20Module%202.6.1%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20i%20am%20Still%20not%20able%20to%20Connect%20with%20the%20Access%20Tokens.%3C%2FP%3E%3CP%3EAny%20Updates%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2964993%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2964993%22%20slang%3D%22en-US%22%3E%3CP%3EHow%20are%20you%20guys%20able%20to%20work%20with%20that%20access%20token%3F%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1041635%22%20target%3D%22_blank%22%3E%40SajAccess4%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1215762%22%20target%3D%22_blank%22%3E%40petetheman%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F724919%22%20target%3D%22_blank%22%3E%40hernan-invosys%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1206908%22%20target%3D%22_blank%22%3E%40usman83%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2956419%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2956419%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F998754%22%20target%3D%22_blank%22%3E%40Sridevi-MSFT%3C%2FA%3E%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI've%20also%20started%20experiencing%20this%20issue%20today.%20Was%20working%20fine%20before%2C%20but%20now%20I%20get%20the%20error%3A%20%22%20The%20provided%20tokens%20must%20have%20less%20than%20180%20seconds%20difference%20in%20the%20time%20range%20of%20expiration.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUsing%20Teams%20PowerShell%20Module%26nbsp%3B2.3.2%20with%20a%20graph%20token%20and%20a%20Teams%20token%20that%20are%20created%20at%20the%20same%20time%2C%20but%20the%20expiration%20time%20can%20be%20as%20great%20as%2020min.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2967798%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2967798%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F642475%22%20target%3D%22_blank%22%3E%40Thomsch%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F998754%22%20target%3D%22_blank%22%3E%40Sridevi-MSFT%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20still%20unable%20to%20get%20it%20work.%20I'm%20still%20receiving%20an%20error%20%22Connect-MicrosoftTeams%20%3A%20The%20provided%20tokens%20must%20have%20less%20than%20180%20seconds%20difference%20in%20the%20time%20range%20of%20expiration.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20not%20been%20able%20to%20figure%20out%20how%20to%20configure%20the%20expiration%20of%20the%20tokens%20as%20we%20generate%20the%20tokens%20at%20the%20same%20time%20and%20the%20difference%20in%20expiration%20is%20approx.%20800%20seconds.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2967856%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2967856%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F960255%22%20target%3D%22_blank%22%3E%40NMLVS%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20update%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2968848%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2968848%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F642475%22%20target%3D%22_blank%22%3E%40Thomsch%3C%2FA%3E%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F998754%22%20target%3D%22_blank%22%3E%40Sridevi-MSFT%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EI%20do%20the%20following%20two%20requests%20to%20get%20the%20tokens%20the%20payload%20is%20below%3CBR%20%2F%3E%3CBR%20%2F%3EGraph%20Token%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Flogin.microsoftonline.com%2Fcommon%2Foauth2%2Fv2.0%2Ftoken%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Flogin.microsoftonline.com%2Fcommon%2Foauth2%2Fv2.0%2Ftoken%3C%2FA%3E%3CBR%20%2F%3Eclient_id%3Dredacted%3CBR%20%2F%3E%26amp%3Bscope%3DDirectory.AccessAsUser.All%3CBR%20%2F%3E%26amp%3Bcode%3Dredacted%3CBR%20%2F%3E%26amp%3Bredirect_uri%3Dredacted%3CBR%20%2F%3E%26amp%3Bgrant_type%3Dauthorization_code%3CBR%20%2F%3E%26amp%3Bclient_secret%3Dredacted%3CBR%20%2F%3E%3CBR%20%2F%3ETeams%20Token%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Flogin.microsoftonline.com%2Fcommon%2Foauth2%2Ftoken%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Flogin.microsoftonline.com%2Fcommon%2Foauth2%2Ftoken%3C%2FA%3E%3CBR%20%2F%3Eresource%3D48ac35b8-9aa8-4d74-927d-1f4a14a0b239%3CBR%20%2F%3E%26amp%3Bclient_id%3Dredacted%3CBR%20%2F%3E%26amp%3Brefresh_token%3Dredacted%3CBR%20%2F%3E%26amp%3Bredirect_uri%3Dredacted%3CBR%20%2F%3E%26amp%3Bgrant_type%3Drefresh_token%3CBR%20%2F%3E%26amp%3Bclient_secret%3Dredacted%3CBR%20%2F%3E%3CBR%20%2F%3EBut%20the%20token%20expiry%20time%20of%20the%20two%20tokens%20are%20always%20more%20than%20180%20seconds.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EGraph%20JWT%26nbsp%3B%3C%2FP%3E%3CP%3E%22aud%22%3A%20%2200000003-0000-0000-c000-000000000000%22%2C%3CBR%20%2F%3E%22iss%22%3A%20%22%3CA%20href%3D%22https%3A%2F%2Fsts.windows.net%2Fredacted%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fsts.windows.net%2Fredacted%2F%3C%2FA%3E%22%2C%3CBR%20%2F%3E%22iat%22%3A%201637048601%2C%3CBR%20%2F%3E%22nbf%22%3A%201637048601%2C%3CBR%20%2F%3E%22exp%22%3A%201637054055%2C%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ETeams%20JWT%26nbsp%3B%3C%2FP%3E%3CP%3E%22aud%22%3A%20%2248ac35b8-9aa8-4d74-927d-1f4a14a0b239%22%2C%3CBR%20%2F%3E%22iss%22%3A%20%22%3CA%20href%3D%22https%3A%2F%2Fsts.windows.net%2Fredacted%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fsts.windows.net%2Fredacted%2F%3C%2FA%3E%22%2C%3CBR%20%2F%3E%22iat%22%3A%201637048627%2C%3CBR%20%2F%3E%22nbf%22%3A%201637048627%2C%3CBR%20%2F%3E%22exp%22%3A%201637053010%2C%3CBR%20%2F%3E%3CBR%20%2F%3ETime%20difference%20%3D%26nbsp%3B1045%20seconds%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20this%20will%20result%20in%20the%20error%20that%20the%20expiry%20time%20difference%20is%20greater%20than%20180%20seconds.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20something%20wrong%20with%20the%20way%20I%20am%20requesting%20a%20token%2C%20or%20is%20there%20a%20change%20in%20the%20token%20issuing%20logic%20that%20is%20not%20compatible%20with%20the%20Teams%20Connector%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20regards%3C%2FP%3E%3CP%3EPeter%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2972997%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2972997%22%20slang%3D%22en-US%22%3ESame%20problem%20here%20since%20a%20couple%20of%20days%20now...%3CBR%20%2F%3E%3CBR%20%2F%3EBoth%20Graph%20and%20Teams%20access%20tokens%20started%20obtaining%20random%20expiry%20values%20instead%20of%20previously%20static%203599%20seconds.%3CBR%20%2F%3E%3CBR%20%2F%3EAs%20a%20quick%20fix%2C%20can%20Microsoft%20at%20least%20disable%20the%20tokens%20expiry%20difference%20verification%20to%20restore%20access%3F%3CBR%20%2F%3E%3CBR%20%2F%3EThanks.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2975673%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2975673%22%20slang%3D%22en-US%22%3E%3CP%3ETried%20with%20ClientSecret.%20Same%20Result.%3C%2FP%3E%3CP%3E%24TenantId%20%3D%20%22tenantname.onmicrosoft.com%22%3CBR%20%2F%3E%24AppID%20%3D%20%22546f064a-baa2-4eb9-8b68-70c79b91942b%22%20%23TeamsPS%3CBR%20%2F%3E%24ClientSecret%20%3D%20ConvertTo-SecureString%20%22MyClientSecret%22%20-AsPlainText%20-Force%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%23GraphAccessToken%3CBR%20%2F%3E%24Scope%20%3D%20%22%3CA%20href%3D%22https%3A%2F%2Fgraph.microsoft.com%2F.default%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgraph.microsoft.com%2F.default%3C%2FA%3E%22%3CBR%20%2F%3E%24Token%20%3D%20Get-MsalToken%20-clientID%20%24AppID%20-ClientSecret%20%24ClientSecret%20-tenantID%20%24tenantID%20-Scope%20%24Scope%3CBR%20%2F%3E%24GraphAccessToken%20%3D%20%24Token.AccessToken%3CBR%20%2F%3E%24GraphAccessToken%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%23TeamsAccessToken%3CBR%20%2F%3E%24Scope%20%3D%20%2248ac35b8-9aa8-4d74-927d-1f4a14a0b239%2F.default%22%3CBR%20%2F%3E%24Token%20%3D%20Get-MsalToken%20-clientID%20%24AppID%20-ClientSecret%20%24ClientSecret%20-tenantID%20%24tenantID%20-Scope%20%24Scope%3CBR%20%2F%3E%24TeamsAccessToken%20%3D%20%24Token.AccessToken%3CBR%20%2F%3E%24TeamsAccessToken%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%23Connect%3CBR%20%2F%3E%24AccessTokens%20%3D%20%40(%24GraphAccessToken%2C%24TeamsAccessToken)%3CBR%20%2F%3EConnect-MicrosoftTeams%20-AccessTokens%20%24AccessTokens%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Teams_CBA_04.jpg%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F327641iCA6DA0D5C70D1A57%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Teams_CBA_04.jpg%22%20alt%3D%22Teams_CBA_04.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3ERegards%3CBR%20%2F%3EAndres%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2976243%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2976243%22%20slang%3D%22en-US%22%3EI%20see%202.6.2-prerelease%20was%20added%20a%20couple%20of%20days%20ago%2C%20however%20it%20seems%20pretty%20broken.%20Was%20this%20version%20supposed%20to%20resolve%20this%20issue%20(expiry%20time%20mismatch)%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2976933%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2976933%22%20slang%3D%22en-US%22%3EI%20don't%20see%20how%20one%20or%20another%20version%20of%20Teams%20PowerShell%20client%20app%20can%20make%20a%20difference%20here.%3CBR%20%2F%3EAccess%20tokens%20are%20handed%20out%20by%20the%20Microsoft%20Identity%20Platform.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2978024%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2978024%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1221733%22%20target%3D%22_blank%22%3E%40BJMUK%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20tried%20different%20versions%20and%20this%20error%20is%20still%20generated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2980282%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2980282%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1220844%22%20target%3D%22_blank%22%3E%40serge2021%3C%2FA%3E%26nbsp%3BI%20was%20hoping%20they%20may%20have%20removed%20the%20requirement%2C%20or%20increased%20the%20allowed%20difference.%20Looking%20at%20the%20other%20replies%2C%20that's%20not%20the%20case%20though.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2980716%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2980716%22%20slang%3D%22en-US%22%3EAs%20of%20this%20morning%20-%20the%20problem%20persists.%3CBR%20%2F%3E%3CBR%20%2F%3EAnybody%20here%20logged%20an%20official%20support%20case%20with%20Microsoft%3F%20Otherwise%2C%20I%20feel%20like%20we%20can%20keep%20talking%20here%20for%20days%2Fweeks%20in%20a%20row%20without%20being%20heard.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2980994%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2980994%22%20slang%3D%22en-US%22%3Ewhat%20region%20are%20you%20in%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1220844%22%20target%3D%22_blank%22%3E%40serge2021%3C%2FA%3E%3F%20am%20wondering%20if%20this%20is%20a%20regional%20issue%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2981738%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2981738%22%20slang%3D%22en-US%22%3ENorth%20America%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2982943%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2982943%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1215762%22%20target%3D%22_blank%22%3E%40petetheman%3C%2FA%3E%26nbsp%3BMy%20region%20is%20Australia%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2985360%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2985360%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1041635%22%20target%3D%22_blank%22%3E%40SajAccess4%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EA%20few%20things%20to%20note%3A%3C%2FP%3E%3CUL%3E%3CLI%3EWe%20have%20a%20case%20open%20with%20Microsoft.%26nbsp%3B%20They%20have%20acknowledged%20the%20problem%20with%20the%20token%20expiry%20variability%20and%20have%20engaged%20the%20Product%20Group.%26nbsp%3B%20No%20actual%20progress%20that%20I%20know%20of.%3C%2FLI%3E%3CLI%3EThis%20seems%20to%20affect%20North%20America%20and%20AUS%20(at%20least)%2C%20that%20started%20rolling%20out%20around%20Nov%2010%2C%20though%20it%20might%20have%20been%20simultaneous.%26nbsp%3B%20However%2C%20more%20and%20more%20of%20our%20customers%20have%20been%20seeing%20the%20problem%20over%20the%20past%20week.%3C%2FLI%3E%3CLI%3EThe%20issue%20is%20that%20on%20or%20about%20Nov%2010%20there%20was%20evidently%20some%20change%20to%20the%20expiry%20time%20of%26nbsp%3B%20tokens.%26nbsp%3B%20The%20data%20is%20a%20little%20too%20sparse%20to%20be%20sure.%26nbsp%3B%20%26nbsp%3B%3CUL%3E%3CLI%3Eessentially%2C%20it%20seems%20like%20there%20was%20a%20random%20amount%20of%20time%20added%20to%20each%20token's%20expiry.%26nbsp%3B%20Prior%20to%20Nov%2010%2C%20these%20tokens%20all%20expired%20after%20precisely%203900%20seconds%3B%20subsequently%2C%20this%20was%20longer%20(never%20shorter)%20by%20some%20random%20amount%20up%20to%201500%20secs.%3C%2FLI%3E%3CLI%3EThe%20180%20sec%20check%20on%20the%20difference%20in%20exp%20times%20for%20the%20two%20tokens%20was%20probably%20always%20there%2C%20but%20up%20until%20Nov%2010%20that%20difference%20was%20always%20approx%200.%3C%2FLI%3E%3CLI%3Esee%20the%20graph%20at%20the%20end%20for%20an%20illustration%20of%20how%20this%20suddenly%20manifested%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3CLI%3EWe%20have%20implemented%20a%20hack%20workaround%3A%20We%20keep%20getting%20tokens%20until%20we%20have%20two%20with%20expiry%20within%20180%20sec.%26nbsp%3B%20This%20often%20takes%20a%20lot%20of%20tries%20to%20get%20%22lucky%22.%3C%2FLI%3E%3C%2FUL%3E%3CP%3EHere's%20a%20graph%20for%20one%20of%20our%20customers%2C%20where%20the%20problem%20starts%20around%20Nov%2016.%26nbsp%3B%20You%20can%20see%20how%20the%20token%20duration%20for%20both%20Teams%20and%20Graph%20tokens%20(which%20we%20obtain%20simultaneously)%20initially%20(and%20for%20a%20long%20time%20before%20the%20data%20presented%20here)%20have%20a%20duration%20of%203900%20sec%20and%20the%20difference%20in%20expiry%20time%20(the%20blue%20line)%20is%20always%20~%20zero%20and%20between%20the%20180%20(red%20dot)%20boundary.%26nbsp%3B%20Then%20everything%20goes%20nuts%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Screen%20Shot%202021-11-18%20at%209.57.01%20AM.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F328195iE49CA26B28D3AFDD%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Screen%20Shot%202021-11-18%20at%209.57.01%20AM.png%22%20alt%3D%22Screen%20Shot%202021-11-18%20at%209.57.01%20AM.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2987188%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2987188%22%20slang%3D%22en-US%22%3E%3CP%3EOur%20hack%20workaround%20still%20seems%20to%20be%20working.%26nbsp%3B%20It%20requires%20an%20average%20of%20over%205%20token%20requests%20to%20get%20an%20acceptable%20expiry%20time%20difference%20less%20than%20180.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20has%20provided%20an%20explanation%20on%20our%20case%2C%20which%20is%20pretty%20much%20what%20we%20expected%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22lia-indent-padding-left-30px%22%3E%3CEM%3EOur%20internal%20mentioned%20that%20they%20recently%20got%20some%20similar%20cases%20with%20this%20error.%20Our%20team%20has%20already%20isolated%20the%20root%20cause%20of%20the%20issue%20which%20is%20increase%20in%20Access%20token%20refresh%20time%20from%201h%20token%20can%20now%20be%20anywhere%20between%2065m%20-95minutes.%20Below%20there%20is%20the%20complete%20explanation%20of%20the%20root%20cause.%3C%2FEM%3E%3C%2FP%3E%3CP%20class%3D%22lia-indent-padding-left-30px%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22lia-indent-padding-left-30px%22%3E%3CEM%3EThis%20is%20due%20to%20a%20recently%20enabled%20ESTS%20Jittering%20feature%20to%20add%20a%20random%20minutes%20(0-30%20minutes)%20to%20the%20default%201H%20token%2C%20i.e%2C%20the%20default%201h%20token%20can%20now%20be%20anywhere%20between%2065m%20-95minutes%20(%205%20more%20minutes%20for%20clock%20skew).%20The%20change%20of%20ESTS%20is%20to%20reduce%20the%20spike%20in%20token%20requests%20at%20peak%20hour%20and%20thus%20reduce%20ESTS%20peak%20hour%20cost.%20Apps%20with%20a%20logic%20to%20compare%20two%20tokens'%20expiration%20time%20have%20to%20change%20their%20codes%20accordingly%2C%20as%20ESTS%20has%20never%20committed%20to%20make%20two%20successive%20tokens%20with%20a%20fixed%20time%20difference.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20other%20words%2C%20one%20part%20of%20Microsoft%20(ESTS)%20made%20this%20change%20to%20reduce%20the%20number%20of%20tokens%20they%20have%20to%20provide%2C%20and%20smooth%20out%20their%20load.%26nbsp%3B%20%26nbsp%3BAnd%20they%20are%20telling%20the%20other%20part%20of%20Microsoft%20(Teams%20or%20Azure)%20that%20%22your%20code%20is%20broken%20for%20making%20any%20assumption%20about%20these%20token%20expiry%20times.%22%26nbsp%3B%20%26nbsp%3BWhat%20teamwork!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENo%20word%20yet%20on%20when%20the%20Teams%2FAzure%2Fwhoever%20people%20will%20make%20the%205-minute%20code%20change%20to%20remove%20the%20180%20sec%20check.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2997246%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2997246%22%20slang%3D%22en-US%22%3E%3CP%3EMore%20news%20from%20Microsoft%20regarding%20the%20token%20expiry%20fiasco%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22lia-indent-padding-left-30px%22%3E%3CEM%3E%3CSPAN%20class%3D%22%22%3EAs%20per%20the%20latest%20update%20and%20after%20analyzing%20all%20the%20internal%20cases%20with%20our%20product%20group%20for%20the%20same%20issue%2C%20we%20can%20confirm%20that%20it%20is%20a%20bug%20and%20I%20also%20crossverified%20with%20the%20engineering%20team.%3C%2FSPAN%3E%3C%2FEM%3E%3C%2FP%3E%3CP%20class%3D%22lia-indent-padding-left-30px%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22lia-indent-padding-left-30px%22%3E%3CEM%3E%3CSPAN%20class%3D%22%22%3EHowever%2C%20the%20ETA%20for%20implementing%20the%20change%20is%20January%202022%20as%20we%20don%E2%80%99t%20have%20any%20preview%20releases%20for%20this%20year.%3C%2FSPAN%3E%3C%2FEM%3E%3C%2FP%3E%3CP%20class%3D%22lia-indent-padding-left-30px%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22%22%3EThey%20also%20recommended%20using%20-Credential%20argument%20instead%20of%20-AccessTokens%2C%20which%20is%20completely%20pointless%20for%20our%20asynchronous%2C%20server-based%20PowerShell%20tooling.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22%22%3ESo%20I%20would%20recommend%20implementing%20some%20sort%20of%20hack%2C%20as%20we%20have%2C%20unless%20you%20can%20wait%20until%20next%20year%20(maybe).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3008008%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticating%20with%20an%20access%20token%20Connect-MicrosoftTeams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3008008%22%20slang%3D%22en-US%22%3EThanks%20mate.%20Actually%20that%20helps%20a%20lot.%3C%2FLINGO-BODY%3E
Occasional Contributor
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 permissions in the scope, which one could obtain silently, and so avoid login.

New-CsOnlineSession has been dropped and the SfB Connector is end of life in July and Connect-MicrosoftTeams does appear to support token for the telephony functions.
77 Replies

@PhoneMe007, Can you please explain more briefly about the issue.

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.
Hi @PhoneMe007 could you please check with latest Powershell Teams module. It have the inbuilt sfb connecter features.
No change @teams1535 :frowning_face:
Update: Microsoft has released a preview version (2.1.0) of the Teams PowerShell module which works properly with modern authentication. It’s likely that this version will be pushed through to general availability quite quickly.
Please go through this link for more information.
https://office365itpros.com/2021/03/10/microsoft-updates-teams-powershell-module-2-0/

@teams1535 Unfortunately this method still doesn't work with any of the voice related cmdlets/functions - Get-CsOnlineSession for example is not a recognised cmdlets when you try running it.

 

PS C:\WINDOWS\system32> Set-CsOnlinePSTNUsage -Identity Global -Usage @{add="UnrestrictedPstnUsage"}

Get-CsOnlineSession : Run Connect-MicrosoftTeams before running cmdlets.

At C:\Program Files\WindowsPowerShell\Modules\MicrosoftTeams\2.2.0\net472\SfBORemotePowershellModule.psm1:57 char:22

+     $remoteSession = & (Get-CsOnlineSessionCommand)

+                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Get-CsOnlineSession], UnauthorizedAccessException

    + FullyQualifiedErrorId : UnauthorizedAccessException,Microsoft.Teams.ConfigApi.Cmdlets.GetCsOnlineSession

 

Invoke-Command : Cannot validate argument on parameter 'Session'. The argument is null or empty. Provide an argument

that is not null or empty, and then try the command again.

At C:\Program Files\WindowsPowerShell\Modules\MicrosoftTeams\2.2.0\net472\SfBORemotePowershellModule.psm1:47766 char:38

+ ...    -Session (Get-PSImplicitRemotingSession -CommandName 'Set-CsOnline ...

+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : InvalidData: (:) [Invoke-Command], ParentContainsErrorRecordException

    + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.InvokeCommandCommand

@PhoneMe007 @teams1535

 

Have either of you been able to resolve this issue as I'm experiencing the same?

Nope, and even in 2.3.0 released yesterday it's no better...
@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.

Thanks @Sridevi-MSFT, appreciate your help
I am facing the same issue on connecting to the Teams module using an access token. Although the command doesnt throw and error, running Skype commands gives me this for the command "Get-CsTeamsCallingPolicy"

Error:
Get-CsOnlineSession : Run Connect-MicrosoftTeams before running cmdlets.
I have experienced the same thing with Get-CsOnlineUser.
what is the use of releasing this powershell if it doesn't work
I am also finding that when connecting with access tokens the Get-CSOnlinePSTNGateway and anything that used to be connected via the new-csonlinesession no longer functions.
If you log in with Connect-MicrosoftTeams interactively then it will work, but this is undesirable for our automation requirements.
Module version 2.3.1
We have implemented a fix which will be available when the 3.0.0 version is released.
What is the likely date for its release?

@priyachads - Currently we don't have any ETA to share.

www.000webhost.com