Matthew Yauch

My feedback

  1. 72 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    17 comments  ·  Public » Desktop  ·  Flag idea as inappropriate…  ·  Admin →
    Matthew Yauch supported this idea  · 
  2. 4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Bug Reports » Activity  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Matthew Yauch commented  · 

    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.

    Matthew Yauch supported this idea  · 
  3. 17,514 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1855 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    Matthew Yauch supported this idea  · 
  4. 32,073 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2683 comments  ·  Public » Account Access (Sign-In)  ·  Flag idea as inappropriate…  ·  Admin →

    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  · 

Feedback and Knowledge Base