Feedback by UserVoice

Beck

My feedback

  1. 66 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Beck supported this idea  · 
  2. 157 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Office 365 Security & Compliance  ·  Flag idea as inappropriate…  ·  Admin →
    Beck supported this idea  · 
  3. 281 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Office 365 Admin » SharePoint Admin  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Beck commented  · 

    @Justin Horne - THANK YOU!! Your script worked flawlessly and saved me from having to explain to directors/executives why they were going to receive emails that they joined the group.

  4. 48 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
  5. 108 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Office 365 Security & Compliance » Auditing  ·  Flag idea as inappropriate…  ·  Admin →
  6. 1,993 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    80 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Beck commented  · 

    We have been on Office 365 for over 4 years now and someone stumbled across this problem today and it caused a delayed reply to a customer inquiry. The maddening part is that if you grant users full access either via admin portal or powershell, you still get the same behavior - visible in OWA but not Outlook client. I'd vote this but I'm out of votes.

  7. 2,605 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    318 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
  8. 2,839 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    236 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
  9. 39 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment An error occurred while saving the comment
    Beck commented  · 

    This idea is the same but has more votes - go vote for it so MS hears that we need this! There was an admin comment from Microsoft that the feature work is planned but has not started as of July 15 2019

    An error occurred while saving the comment
    Beck commented  · 

    Please add this feature Microsoft!

    Beck shared this idea  · 
  10. 10,753 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1115 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Beck commented  · 

    Please add this feature natively! We had to write a powershell script and assign a license to a generic user.

  11. 237 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Beck commented  · 

    Please help Microsoft! This is still an issue a year and a half later. I still have to use a Windows 7 machine because of this and there's less than one year before Windows 7 is EOL.

    Beck shared this idea  · 
  12. 4,242 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    180 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
  13. 1,631 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    42 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →

    We’ve recently shipped the ability to change the SharePoint Site URL associated with a Microsoft 365 Group (formerly Office 365 Group). https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=56205. This can be done via the SharePoint Admin Center. The site URL can be changed on a per-site basis, but currently we don’t have plans to allow admins to change the global default from “/sites” to something different.

    An error occurred while saving the comment
    Beck commented  · 

    What would be great would be if the SPO URL for sites created by Office 365 groups had /groups in the path instead of /sites. That would be another way to avoid this conflict. I was asked to create a /sites/marketing SPO site however I was getting an access denied message as a global admin. Turns out there was an Office 365 group created 2 months ago called Marketing and since sites created automatically for groups use the /sites URL they in essence squatted on the URL 1st. My global admin account did not have access to the group, hence the access denied message when trying to create the new site collection with the sites/marketing URL. *facepalm*

    Beck supported this idea  · 
  14. 3,682 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    200 comments  ·  Office 365 Security & Compliance  ·  Flag idea as inappropriate…  ·  Admin →

    Azure Active Directory Conditional Access has functionality for “Countries/Regions” – see https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/location-condition

    That said, the most effective protection you can have against password spray attacks is to enable MFA and disable basic authentication. If you cannot do this for your entire organization, then blocking user access to legacy protocols like POP, EWS, IMAP and SMTP is another step you can take. Exchange Online Client Access Rules can help you to further customize (https://docs.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/client-access-rules/client-access-rules). For additional recommendations, please see Office 365 Secure Score.

    That said, please know that we are listening to feedback and working on solutions to help make Office 365 users more secure. Thank you for the feedback.

    An error occurred while saving the comment
    Beck commented  · 

    THIS SHOULD BE STANDARD!!! WE SHOULDN'T HAVE TO PAY EXTRA FOR AZURE AD PREMIUM TO DO THIS!!

    impossible travel 2nd sign in Nigeria - OF COURSE ITS IMPOSSIBLE BECAUSE WE HAVE NO ONE THAT TRAVELS THERE!!!

  15. 2,322 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    79 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Beck supported this idea  · 
  16. 94 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Beck shared this idea  · 
  17. 224 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    32 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Beck supported this idea  · 
  18. 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…

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

    Please give us the option to disable it for our entire organization. If that cannot be allowed, please give us a way to prevent it on new users, perhaps by adding a parameter to the New-MsolUser cmdlet. Something like -ClutterEnabled that we could set to $false and when the mailbox is created, clutter would be disabled.

Feedback and Knowledge Base