David

My feedback

  1. 69 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Public » Settings  ·  Flag idea as inappropriate…  ·  Admin →
    David supported this idea  · 
  2. 91 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Public » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    David supported this idea  · 
  3. 154 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Public » Presence  ·  Flag idea as inappropriate…  ·  Admin →
    David supported this idea  · 
  4. 814 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    44 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    David supported this idea  · 
  5. 733 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    72 comments  ·  Public » Presence  ·  Flag idea as inappropriate…  ·  Admin →
    David supported this idea  · 
  6. 1,026 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    375 comments  ·  Public » Performance  ·  Flag idea as inappropriate…  ·  Admin →

    Feature teams have been finding unique areas of improvement around crashes/hangs/lock ups of the client, and have been making small improvements through both proactive and reactive findings to help around reliability regressions. If you happen to see any unique issues, please let us know and we will continue to share updates as they become available.

    An error occurred while saving the comment
    David commented  · 

    A frequent occurrence (several times per week) is that the whole OS becomes non-responsive (often accompanied with a high-pitched shriek from the speakers) for around 10 seconds during a video call, but then recovers.

    Less often, I get the OS either crashing, or being indefinitely unresponsive and requiring a forced shutdown, when in a video call.

    This is on fully patched Windows 10 on a fairly high spec Dell XPS laptop, and has been a persistent issue over the course of the 14 months or so that I've used Teams.

    David supported this idea  · 
  7. 1,611 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    196 comments  ·  Public » Meetings  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    David commented  · 

    This behaviour is completely mad and makes the "Schedule a meeting" button in the channel pointless and a hazard. You select a specific set of invitees, and then with no warning it invites your entire organization. Even that it posts the meeting text in the channel is unexpected, but I wouldn't mind so much if uninvited people could turn up through the link in the channel if it weren't the case that it was spamming the entire organization by email too.

    It absolutely beggars belief that this even made it out the door as a released product in the first place as broken as this.

    David supported this idea  · 
  8. 1,460 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    299 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    David supported this idea  · 
  9. 187 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    David commented  · 

    The toolbar moves to the left when the Participants or Meeting Chat button is pressed, so "Request control" ends up positioned where the Participants or Meeting Chat buttons previously were. Given that re-clicking on those buttons is a way to close the Participants list or Chat window, it is very easy to click on the "Request control" by accident when, for example, you only open chat briefly to see one new message and then mean to close it again by re-clicking in the same spot.

    David supported this idea  · 
  10. 3,306 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    596 comments  ·  Public » Meetings  ·  Flag idea as inappropriate…  ·  Admin →
    David supported this idea  · 

Feedback and Knowledge Base