Matthew Yauch
My feedback
-
72 votesMatthew Yauch
supported this idea
·
-
4 votes
An error occurred while saving the comment Matthew Yauch
supported this idea
·
-
17,514 votes
Thank you for your votes and comments on this feature. The team is in the process of finalizing designs for deleting private chat threads. I will update as we have more progress to share.
Matthew Yauch
supported this idea
·
-
32,073 votes
The engineering team is continuing to work on adding support for multiple accounts on desktop clients. We will first launch support for 1 work/school account and 1 personal account so users can enjoy Teams for work and personal side-by-side. Windows and MacOS. Support for multiple work accounts is still being worked on and will come at a later date.
You can track status via the roadmap here: https://www.microsoft.com/microsoft-365/roadmap?searchterms=68845.
Thanks!
Matthew Yauch
supported this idea
·
I'm having the same issue, though it was slightly earlier. My last known working date was 9/26. The next week on 10/2 my script was attempting to send notifications and they did not work. I have enterprise accounts both for work and for home, and this was occurring on my NOC team in my work tenant.
I tried deleting the webhook and creating a new one on the original Team. This did not work, and gave the exact same results as the original webhook. The API call gives a success result, even though no message is ever posted.
I tested using my personal tenant and had no issues setting up a webhook and receiving messages.
I then tested using my work tenant with a different Team than the original webhook, and that also works.
The issue appears to be tied to the original Team itself.
Edit: Doh! I was having trouble getting to connectors at all this morning (gave 503 server unavailable).
This finally went away, and I just tested a webhook again on my original Team and it works now. Wonder what that was...
Edit2: Aaaaand it's broken again.