Feedback by UserVoice

Anonymous

My feedback

  1. 62 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  2. 42 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Office 365 Security & Compliance » Auditing  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    Yeah Teams IM message appears in Content Search but not via Message Trace which is no good when your trying to track the IP address of a guest user that sent a message within a Teams meeting with inappropriate content.

    If anyone knows how, please let me know. :)

    Anonymous supported this idea  · 
  3. 1,020 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    34 comments  ·  Delve » People Experiences  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    You can create a Conditional Access Policy and select the group of users, who you don't want using Delve to find information. The app to block is Office Delve. It's not hiding specific users from appearing in Delve but restricting users who should be able to use Delve. Also stops the need to disable Delve org-wide. :)

  4. 62 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anonymous supported this idea  · 
  5. 3,651 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    199 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  · 
  6. 77 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Were you able to old text without UI assistance? We also need to bold text for compliance reasons but am finding it difficult to do so at present.
    Thanks!

Feedback and Knowledge Base