Michael Davis

My feedback

  1. 6,933 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

    329 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    Michael Davis supported this idea  · 
    An error occurred while saving the comment
    Michael Davis commented  · 

    Agree 100% with what Joe comments below on Feb 17, 2021.

    At my office, this is one of the primary complaints about chat / posts. There is no way people will replace e-mail with chat, until old messages can be sorted into topics the way old e-mail can. Labelling messages or using hashtags would solve that problem.

  2. 6 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

    1 comment  ·  Public » Developer Platform  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Michael Davis commented  · 

    This is one of the most requested features at my office regarding posts/ chat messages. If Teams is to replace e-mail here, people need to be able to sort and find old messages. Tagging messages is what would enable that.

    Michael Davis supported this idea  · 
  3. 271 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

    43 comments  ·  Public » Shifts  ·  Flag idea as inappropriate…  ·  Admin →
    Michael Davis supported this idea  · 
  4. 545 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

    82 comments  ·  Public » IT Pro  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Michael Davis commented  · 

    1) Agree with everything said here.

    Organizations change and have turn over. I know that seems to be a surprise to the MS Teams developers, but it's true. That's why Microsoft usually gives us groups (distribution, security, O365) to assign rights in just about every other context. The suggested solution for Teams (using PowerShell) is fine for ad-hoc bulk changes but fails completely to provide a way to maintain user permissions over time.

    We MUST be able to assign policies to the groups that we are already using for everything else.

    Tip: Let us assign policies by Azure AD groups (dynamic included)
    ---------

    2) About the GUI for managing user policies:

    (Microsoft Teams admin center > Users)

    We can see: User name, Phone number and Location. However, we can only filter users (to assign bulk changes) by username and phone number, not location. Who on the planet needs to assign rights in bulk by filtered User name (ex. everyone with the name "John")????

    We should be able to filter by Azure AD user account properties like Job Title, Department, Office and Manager. THEN we'd have a decent way to find relevant groups of people to assign rights to.... if you -- for some weird reason -- can't let us assign by groups.

    Michael Davis supported this idea  · 
  5. 3 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

    1 comment  ·  Public » IP Phones  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Michael Davis commented  · 

    I have commented elsewhere that it should be -- at least -- possible to assign policies based on security group or O365 group (dynamic or otherwise). That's the way most organisations handle system rights. This should be basic.

  6. 23 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 » Settings  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Michael Davis commented  · 

    I agree with bob. Moreover the suggested powershell soluition is not dynamic; policies are only applied to a group, when the script is run. Our organization has turnover -- oddly enough -- and so Teams policies need to follow those changes continually without a bunch of additional manual labor.

    Using security groups or O365 groups for rights should be the obvious way to implement policies.

    Michael Davis supported this idea  · 

Feedback and Knowledge Base