Feedback by UserVoice

Anonymous

My feedback

  1. 192 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Office 365 Security & Compliance » eDiscovery  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  2. 12,106 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    452 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
  3. 1,003 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    29 comments  ·  Office 365 Admin » SharePoint Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  4. 112 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Office 365 Security & Compliance » Malware  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  5. 1,064 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    32 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →

    Disabling the welcome mail is possible with an extra parameter in the Set-UnifiedGroup cmdlet in Exchange PowerShell: -UnifiedGroupWelcomeMessageEnabled:$false. See https://docs.microsoft.com/en-us/powershell/module/exchange/users-and-groups/set-unifiedgroup

    Use this as a part of a custom group creation flow if you would like to restrict and/or customize the welcome mail for many groups across your tenant.

    Anonymous supported this idea  · 
  6. 21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  7. 9,712 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1045 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  8. 880 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    27 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  9. 177 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  10. 506 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    53 comments  ·  Office 365 Security & Compliance  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
    An error occurred while saving the comment
    Anonymous commented  · 

    Please prioritize and fix this issue. It is really a big problem when trying to ensure encrypted transmissions. We cannot wait 2 days for TLS enforced connections to fail, when sending to non-TLS supported recipients - it should be instant. The server will not begin supporting TLS just because it tries for 2 days. We use Office Message Encryption when it fails for non-TLS supported recipients, but having to wait several days to be adviced an e-mail cannot be delivered is unacceptable for our usage. Thank you!

  11. 3,549 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    197 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.

    Anonymous supported this idea  · 
  12. 47 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 

Feedback and Knowledge Base