Tried with ClientSecret. Same Result.
$TenantId = "tenantname.onmicrosoft.com"
$AppID = "546f064a-baa2-4eb9-8b68-70c79b91942b" #TeamsPS
$ClientSecret = ConvertTo-SecureString "MyClientSecret" -AsPlainText -Force
#GraphAccessToken
$Scope = "https://graph.microsoft.com/.default"
$Token = Get-MsalToken -clientID $AppID -ClientSecret $ClientSecret -tenantID $tenantID -Scope $Scope
$GraphAccessToken = $Token.AccessToken
$GraphAccessToken
#TeamsAccessToken
$Scope = "48ac35b8-9aa8-4d74-927d-1f4a14a0b239/.default"
$Token = Get-MsalToken -clientID $AppID -ClientSecret $ClientSecret -tenantID $tenantID -Scope $Scope
$TeamsAccessToken = $Token.AccessToken
$TeamsAccessToken
#Connect
$AccessTokens = @($GraphAccessToken,$TeamsAccessToken)
Connect-MicrosoftTeams -AccessTokens $AccessTokens
Regards
Andres
Hi,
A few things to note:
- We have a case open with Microsoft. They have acknowledged the problem with the token expiry variability and have engaged the Product Group. No actual progress that I know of.
- This seems to affect North America and AUS (at least), that started rolling out around Nov 10, though it might have been simultaneous. However, more and more of our customers have been seeing the problem over the past week.
- The issue is that on or about Nov 10 there was evidently some change to the expiry time of tokens. The data is a little too sparse to be sure.
- essentially, it seems like there was a random amount of time added to each token's expiry. Prior to Nov 10, these tokens all expired after precisely 3900 seconds; subsequently, this was longer (never shorter) by some random amount up to 1500 secs.
- The 180 sec check on the difference in exp times for the two tokens was probably always there, but up until Nov 10 that difference was always approx 0.
- see the graph at the end for an illustration of how this suddenly manifested
- We have implemented a hack workaround: We keep getting tokens until we have two with expiry within 180 sec. This often takes a lot of tries to get "lucky".
Here's a graph for one of our customers, where the problem starts around Nov 16. You can see how the token duration for both Teams and Graph tokens (which we obtain simultaneously) initially (and for a long time before the data presented here) have a duration of 3900 sec and the difference in expiry time (the blue line) is always ~ zero and between the 180 (red dot) boundary. Then everything goes nuts:
