The Outlook connector integration is broken for all users of this connector. The connector’s Azure client secret has expired (AADSTS7000222) for Replit’s own Azure App ID: 0c40bdec-fc27-40e5-bb69-1b3425534e90. No user-side reconnection can fix this — it requires Replit to rotate their client secret in the Azure portal. This affects connector config ccfg_outlook_01K4BBCKRJKP82N3PYQPZQ6DAK.
Help please!
Looks like the same thing is happening to me, outlook got disconnected, all looks happy on outlook side but just failed as per image is this a to your problem brentnhunter13
Yes, that is exactly the same problem I’m having. When I go into the Integrations screen, there is no option to remove the Outlook connector, only to reconnect. And when I click “Reconnect”, that is the error I constantly get.
Help please!
I can confirm the same issue on my side.
Outlook connector shows “InvalidAuthenticationToken / AADSTS7000222”.
Permissions are granted in Microsoft, but the connector remains in error state.
This is blocking production email sending in my app.
Please confirm when the Azure client secret has been rotated.
Same here for me, I have a ticket open with Replit Support but have had no update for 24 hrs, this is impacting my scheduling app, really need this fixed ASAP.
I reported the issue and waiting for the engineers from Replit to find a solution. I have no premium subscription so I guess I’ll have to wait 
Second day no updates must be some major problem. Surprised so little people reporting a problem if it is a general problem with the Outlook connector.
Thank you, all.
The more people who report this issue, the better. Maybe it’s only affecting users on a certain instance. And the more people who participate in this conversation, the better. I will report any progress information as I get it but hopefully Replit will respond soon. I also need this to be fixed ASAP, as it is impacting my live production application.
Suddenly, it works for me now! I hope it works for everyone else now too.
Replit, thanks for resolving this issue!
I got a confirmation via email it workes for me too.
Yep, all working.
Got a note back from Support to confirm it was now working.
