We've just had this occur, but only noticed it 8 days after it occured when our guys mentioned tickets were quiet - expired 31 Jan!!
Question is, what could've caused it? I'm not aware of changes on Azure, nor for the OSTicket specific accounts. Azure's App Reg tokens were still good till late 2024.
Not only that, this was not alerted on either 'email diagnostic' tests or the DEBUG level logs within OST. Surely one of those should've come up with the oauth failure and not make out it's happy when it's clearly failing/being denied?
Is this going to be a re-occuring issue or did MS do something that could've affected things?
Also, the main reason i post: why is OST Oauth2 > config > Token showing a 90 minute lifetime, when our App Reg Token is 2years? The two seem to be unrelated, but since the OST side Token was the one that that expired... whats the reason/way to be alerted on this in the future?