Feedback by UserVoice

O365 Compliance and Protection Feedback

← Customer Feedback for Microsoft Office 365

My feedback

  1. New function proporsal : Coping eDiscovery result to Discovery mailbox operation from S/C center.

    144 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    12 comments  ·  Office 365 Security & Compliance » eDiscovery  ·  Flag idea as inappropriate…  ·  Admin →
    O365 Compliance and Protection Feedback commented  · 

    We are porting this feature to the Security & Compliance Center. This functionality will be available before the Exchange Admin Center In-Place eDiscovery and Hold functionality is disabled. Documentation will be available here: https://aka.ms/ediscovery.

  2. Allow use of TLS 1.1 and higher

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Office 365 Security & Compliance » Advanced Security Management  ·  Flag idea as inappropriate…  ·  Admin →
    O365 Compliance and Protection Feedback commented  · 

    We have requested updates from the Skype team, but you'll want to send that team feedback through their feedback & support channels. Skype does not monitor this forum.

  3. Change Exchange Online recipient limit

    1,305 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    100 comments  ·  Office 365 Security & Compliance » Spam & Phishing  ·  Flag idea as inappropriate…  ·  Admin →
    thinking about it  ·  O365 Compliance and Protection Feedback responded

    Thank you for the feedback. Most of the comments here reflect a desire to be able to LOWER the recipient limit for a specific user. This is something we will consider as priorities allow. If you’re voting or commenting — we would be curious if this is driven more by account compromises or just user behavior (e.g., don’t have permissions to send to the DL, so the user just expands the DL)?

    For issues with compromised accounts, we want you to be aware that we take this issue seriously and have been working on that problem from many angles. That said, we believe that limiting the number of recipients per email will not stop or even slow the bad guys significantly. Instead, we encourage you to visit https://securescore.office.com/ and implement best practices to protect your organization.

    For any comments regarding other issues with limits or throttling (e.g., increasing a limit),…

    O365 Compliance and Protection Feedback commented  · 

    Correct, DLs count as single recipients. There are certainly separate limits and throttles for DLs, but that seems to be out of scope here.

    O365 Compliance and Protection Feedback commented  · 

    @ScottMoore - the 500 recipient limit only applies to hosted mailboxes. It does not apply to applications unless they also happen to authenticate and use a mailbox.

Feedback and Knowledge Base

(thinking…)

Related Sites