Dan Smith

My feedback

  1. 2 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  ·  Bug Reports » Client - Desktop  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Dan Smith commented  · 

    FYI: Microsoft acknowledged the issue today and did confirm that setting teams.exe to run in compatibility mode was the temporary fix. Apparently, this is related to users who have both an MSA and AAD accounts with matching names. (See TM236316):

    Dan Smith shared this idea  · 
  2. 25 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

    15 comments  ·  Public » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Dan Smith commented  · 

    This seems to be a much larger problem than Microsoft is letting on. There are two fixes which seem to work:

    Roll-back your Teams client to v1.3.0.24755 (or earlier)
    Configure Teams.exe to run under "Windows 7 Compatibility Mode"

    ...in either case, you'll also need to delete the users "C:\Users\*\AppData\Local\Microsoft\Teams" and "C:\Users\*\AppData\Roaming\Microsoft\Teams" after you've made the change.

  3. 2,028 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

    621 comments  ·  Public » Presence  ·  Flag idea as inappropriate…  ·  Admin →

    Hi — My apologies for the delay in updating this item. We rolled out a fix a year ago for a specific issue of status changing to away in Teams when you were still active on the device. We thought this had fixed the “incorrect status” issue. From comments below, it sounds like people are still seeing issues.

    If you are still having issues, it would be super helpful if you can capture logs by typing Ctrl + Shift + Alt + 1, and send the file from your downloads folder along with device info and detailed repro steps to teamsml@microsoft.com.

    Thanks all!

    An error occurred while saving the comment
    Dan Smith commented  · 

    It appears that Teams will get stuck in a certain status until the user clicks into Teams to make the application window the active one.

    Also, it appears that the "Out Of Office" status gets stuck in Teams even if the period of time defined in Outlook has expired.

  4. 57 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

    3 comments  ·  Public » Meetings  ·  Flag idea as inappropriate…  ·  Admin →
    Dan Smith supported this idea  · 
  5. 51 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

    5 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Dan Smith supported this idea  · 
  6. 1,060 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

    108 comments  ·  Public » Notifications  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Dan Smith commented  · 

    This is starting to become critical for us!

    We have a strict deletion policy which expunges all Chat messages after 24 hours. Having copies of these same chat messages sent to users' mailboxes is a critical hole in functionality. We must be able to administratively control the various notifications settings for the Teams client.

    Most importantly, we need to disable the "Missed activity emails" notification option as well as any other option which can send a notification via email.

    Dan Smith supported this idea  · 
  7. 34,832 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

    2917 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!

    Dan Smith supported this idea  · 
  8. 1,641 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

    on the backlog  ·  223 comments  ·  Public » People  ·  Flag idea as inappropriate…  ·  Admin →
    Dan Smith supported this idea  · 
  9. 255 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

    30 comments  ·  Public » People  ·  Flag idea as inappropriate…  ·  Admin →
    Dan Smith supported this idea  · 
  10. 444 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

    47 comments  ·  Public » IT Pro  ·  Flag idea as inappropriate…  ·  Admin →
    Dan Smith supported this idea  · 
  11. 640 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

    89 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Dan Smith supported this idea  · 
  12. 20,256 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

    1773 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Dan Smith supported this idea  · 
  13. 3,313 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

    458 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Dan Smith supported this idea  · 
  14. 1,105 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

    under review  ·  103 comments  ·  Public » Presence  ·  Flag idea as inappropriate…  ·  Admin →
    Dan Smith supported this idea  · 
    An error occurred while saving the comment
    Dan Smith commented  · 

    Is there any information on where this feature request currently stands? It's been under review for well over a year now. Thank you!

  15. 1,290 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

    209 comments  ·  Public » Desktop  ·  Flag idea as inappropriate…  ·  Admin →
    Dan Smith supported this idea  · 
    An error occurred while saving the comment
    Dan Smith commented  · 

    We need to have this as a per-computer install just like all other MS Office applications. Applications which are based on a "per-user" installation are not easily administered in an enterprise environment. We are having a great deal of trouble getting this consistently deployed for our users. Please, something needs to be done as soon as possible!

  16. 5,505 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

    583 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Dan Smith commented  · 

    Yes, would love to be able to rename the "General" channel to something like "Announcements".

    Dan Smith supported this idea  · 
  17. 21 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
    Dan Smith commented  · 

    Agreed, Zoom is preferred due to this limitation.

    Dan Smith supported this idea  · 
  18. 9 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

    0 comments  ·  Bug Reports » Privacy/Security  ·  Flag idea as inappropriate…  ·  Admin →
    Dan Smith shared this idea  · 
  19. 17 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  ·  Bug Reports » Chat  ·  Flag idea as inappropriate…  ·  Admin →
    Dan Smith shared this idea  · 
  20. 19,452 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

    2012 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Dan Smith commented  · 

    With regard to Retention Policies:

    We noticed that we can now set a "Deletion" policy for Teams Chats which says to delete any conversation older than 24 hours. We've implemented this policy and we'd like to share a couple of observations...

    1.) It took about two weeks for the "desktop" Teams Clients to start scrubbing their chat histories.

    2.) The "desktop" Teams Client is not consistently adhering to the deletion rule. For example: Mostly all chat history was cleared, but in a few cases parts of several conversations remain visible from activity which took place over 2-10 days ago.

    3.) The "web" Teams Client seems to be clearing chat conversations as we've defined. However, the "Recent" view still shows the last topics for several users (no chat content however). [see attached file]

    An error occurred while saving the comment
    Dan Smith commented  · 

    FYI: I opened a ticket with Microsoft in order to get better visibility on this issue. They forwarded my comments on to whomever is responsible for this, but they recommended that someone with Premier Support submit an official "Design Change Request".

    Dan Smith supported this idea  · 
    An error occurred while saving the comment
    Dan Smith commented  · 

    There is a serious gap in functionality which must be addressed before our tenant can be moved over to Teams from Skype for Business:

    Currently in Skype for Business we have explicitly disabled the archiving of IMs as well as the saving of chat history. We've done this by applying our own customized 'CsClientPolicy'...

    $CsPolicy = Get-CsClientPolicy -Identity 'ClientPolicyNoSaveIMNoArchiving';

    $CsPolicy.EnableIMAutoArchiving == False
    $CsPolicy.EnableServerConversationHistory == False

    Our organization explicitly DOES NOT retain any instant messages and considers them "transitory conversations" which do not need to be archived.

    As Teams currently stands, there is no way to apply a similar policy to our users. This needs to be addressed before our tenant is migrated over to Teams. Once a user exits a private chat and closes the Teams app, no conversation history should persist. We do not consider allowing end-users to delete their own chat histories a viable workaround. This is a critical need for us.

    Please help!

← Previous 1

Feedback and Knowledge Base