Forum Discussion
Getting random error 403 Failed to decrypt conversation id on Teams from this morning
The issue has been described on this post by another user : https://stackoverflow.com/questions/77185620/getting-error-403-failed-to-decrypt-conversation-id-microsoft-teams-azure-bot.
So sum up, we have a working code which has not changed since yesterday and we get random 403 when try to send messages to users with the error "Failed to decrypt conversation id".
We check the official Microsoft Status Page and nothing appears.
Thank you for your help
9 Replies
- how we can fix this can anyone guide me please
- It seems that it has been working for the last 20 min.
- This issue seems to be occurring intermittently. We could not repro this issue, we are still checking, and we will inform the engineering team since this issue has been reported by multiple users. Few people said its working for them. Meanwhile we wanted to confirm that users are unlocked for now.
Yup, same here... interestingly enough with the same codebase and different app id (aka our stage environment) its working all the time...
- Exactly the same. We have a flaky production environment, but it works well in staging... I would have preferred the other way around.
- Hmmm, is your production application deployed to the app store? Because thats basically the only difference in our case...
