@fabricecw Not really, because a session in your application isn’t intrinsically linked to an OAuth then issued by a third party. Just like logging out of your application wouldn’t automatically revoke a token on Microsoft’s servers. Microsoft gave you a token; it was then in your hands to do what you wanted with it.
If a user revokes their token, then that just stops requests being made with that token. It doesn’t end a session in your application. I don’t know what “OIDC Front-Channel Logout” is, but if Microsoft does offer a webhook to be notified of any expiring/revoked tokens, then your application will need to set up a listener for that. You can then look up the user associated with the token that was expired/revoked, and end their sessions that way.
Otherwise, you would only know if a token has been revoked/expired if you tried to make an API request with that token and got a 401 response.