Feedback by UserVoice

Simon

My feedback

  1. 3,242 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    505 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    We see two patterns in this feedback thread and are addressing them now. The first pattern is that users want AutoSave OFF. The second pattern is that the Template scenarios are problematic with AutoSave.

    To address turning AutoSave OFF, we have implemented these capabilities:

    1. To avoid accidental edits by others, the owner of a file can set it to Always Open Read-Only. This can be done by setting the file to open in Read-Only Recommended (File > Info > Protect Document/ Workbook/ Presentation > Always Open in Read-Only) or by Sharing the file without allowing others to edit (File > Share > People with the link can edit > Uncheck the “Allow Editing” box).

    2. Users can turn AutoSave OFF for a file. While a document is open, clicking the AutoSave toggle turns AutoSave OFF for the current document for that user. The next time the same…

    An error occurred while saving the comment
    Simon commented  · 

    Docs should automatically open in read-only mode to protect against unintentional and, more importantly, unknown edits, i.e. where the user had no idea they changed something. When the user tries to make a edit, a prompt appears confirming they're making edits, then autosave turns on.

    There's automatic versioning with autosaves, so I don't see an issue with it being turned on if the user is wanting to make edits.

  2. 669 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Simon supported this idea  · 
  3. 134 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Simon supported this idea  · 
    An error occurred while saving the comment
    Simon commented  · 

    This really is a terrible rule, unless we can customize it. I don't mind if users forward their emails to their colleague or manager.

    However, if they (or a malicious user) is forwarding it to an external recipient, that's when an alert should be generated. Right now, it's only for all forwards, or none at all.

  4. 423 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Simon supported this idea  · 
  5. 43 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
    Simon commented  · 

    This seems like a pretty big flaw in the audit log.

    Simon supported this idea  · 
  6. 16 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Simon commented  · 

    I second this. At 85% confidence, obvious test data still creates false positives.

    Simon supported this idea  · 
  7. 533 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    35 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Simon supported this idea  · 
  8. 384 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    31 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Simon supported this idea  · 
  9. 170 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Simon commented  · 

    The default NDR is only helpful if there is a legitimate issue sending an email to us. It's pointless if we're rejecting their email purposefully, e.g. when they send to a noreply email address.

    We don't want senders to know that "a custom mail flow rule created by an admin has blocked your message." We don't want to give them steps on "how to fix it" either.

    Simon supported this idea  · 
  10. 1,125 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    33 comments  ·  Office 365 Admin » Apps and App Launcher  ·  Flag idea as inappropriate…  ·  Admin →
    Simon supported this idea  · 
  11. 4,815 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    285 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →
    Simon supported this idea  · 

Feedback and Knowledge Base