Forum Discussion

PhoneMe007's avatar
PhoneMe007
Brass Contributor
Mar 24, 2021
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 ...
Administrator
Calling
microsoft teams
  • NMLVS's avatar
    NMLVS
    Oct 15, 2021
    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
NMLVS's avatar
NMLVS
Brass Contributor
Oct 15, 2021
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
  • BJMUK's avatar
    BJMUK
    Copper Contributor
    Nov 17, 2021
    I see 2.6.2-prerelease was added a couple of days ago, however it seems pretty broken. Was this version supposed to resolve this issue (expiry time mismatch)?
    • SajAccess4's avatar
      SajAccess4
      Copper Contributor
      Nov 17, 2021

      BJMUK 

       

      I have tried different versions and this error is still generated.

    • serge2021's avatar
      serge2021
      Copper Contributor
      Nov 17, 2021
      I don't see how one or another version of Teams PowerShell client app can make a difference here.
      Access tokens are handed out by the Microsoft Identity Platform.
      • BJMUK's avatar
        BJMUK
        Copper Contributor
        Nov 18, 2021

        serge2021 I was hoping they may have removed the requirement, or increased the allowed difference. Looking at the other replies, that's not the case though.

  • SajAccess4's avatar
    SajAccess4
    Copper Contributor
    Nov 16, 2021

    NMLVS 

     

    Any update?

    • usman83's avatar
      usman83
      Copper Contributor
      Nov 04, 2021

      Hi,

       

      We were successfully using Microsoft Teams powershell using Access Tokens. But today we are faced with strange issue:

       

      We are getting error during authentication: Connect-MicrosoftTeams

      The provided tokens must have less than 180 seconds difference in the time range of expiration. System.Management.Automation.RemoteException: The provided tokens must have less than 180 seconds difference in the time range of expiration.

       

      We have checked the access tokens expiry, they do differ by more then 180 seconds. We are using Refresh tokens to generate Access tokens. This is done automatically using .NET code, both access tokens are fetched within few milliseconds, yet the expiry differs. And when we use these tokens we get above error.

       

      Has anyone experienced this?

       

      Regards,

       

      Muhammad Usman

       

      • serge2021's avatar
        serge2021
        Copper Contributor
        Nov 17, 2021
        Same problem here since a couple of days now...

        Both Graph and Teams access tokens started obtaining random expiry values instead of previously static 3599 seconds.

        As a quick fix, can Microsoft at least disable the tokens expiry difference verification to restore access?

        Thanks.

Resources