Feedback by UserVoice

Samuel Lockett

My feedback

  1. 762 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    62 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Samuel Lockett supported this idea  · 
  2. 1,866 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    66 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Samuel Lockett supported this idea  · 
  3. 3,244 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    114 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Samuel Lockett supported this idea  · 
  4. 875 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    67 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →

    Following up on the previous update, if a workload (such as Planner) is enabled for Outlook by default, we don’t plan on hiding those groups from the GAL. The only other scenario currently under consideration where we would hide groups by default is “Secret Groups”. “Secret Groups” would be hidden from everywhere unless you are a member. “Secret groups” is on the Microsoft 365 Groups backlog, but there is no delivery date available at this time.

    Samuel Lockett supported this idea  · 
  5. 834 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    51 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Samuel Lockett commented  · 

    Below are the steps I used to set these permissions for read/write group and read only group.

    -=:Setup Read Only Access for O365 Groups:=-
    1. Setup a security group like TestGroupROG
    2. Create regular O365 Group and add members that can read/write
    3. Go into the group's Documents -> Click on the Gear -> Site Permissions -> Advanced Sharepoint Permissions
    Note: You can go straight to the permissions through this link by changing the Group Name: https://domain.sharepoint.com/sites/TestGroup/_layouts/15/user.aspx
    4. Click Grant Permissions -> (You will see Invite people) Type in name of person or group you want to have read only permissions -> Click "More Options"
    Select the permission level [Read] and click Share

    I am sure this would be a breeze with powershell if you need multiple groups.
    New-MsolGroup -DisplayName “Test Security Group”

    Samuel Lockett supported this idea  · 
  6. 349 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    21 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Samuel Lockett supported this idea  · 
  7. 1,426 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    28 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Samuel Lockett supported this idea  · 
  8. 13,788 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    520 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Samuel Lockett supported this idea  · 
  9. 1,820 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    251 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your responses. We appreciate that you’ve taken the time to provide us with feedback to help make our products better.

    We’re actively working on significant improvements to the end user experience with the feature across Outlook clients. This includes improvements to the UX, the classification algorithms, and controls.

    Today, admins have a Power-Shell cmdlet that allows them to control the Clutter feature on a per mailbox level. Details of this can be found here: https://technet.microsoft.com/en-us/library/mt586787%28v=exchg.160%29.aspx?f=255&MSPPError=-2147217396

    Our decision to provide the cmdlet based control for Clutter was based on early feedback we received on the Clutter feature.

    We will continue to improve the admin controls based on the continued feedback. Considering the responses on this forum, it would be helpful to better understand the gaps in the current admin control story. Do you believe the gap here is in not having a tenant level control or not having…

    Samuel Lockett supported this idea  · 
    An error occurred while saving the comment
    Samuel Lockett commented  · 

    Turn off Clutter by default. Cmdlet takes forever for each user when doing in batch. Need tenant and gui option.

Feedback and Knowledge Base