Feedback by UserVoice

Scott MacKnight

My feedback

  1. 412 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 →
    An error occurred while saving the comment
    Scott MacKnight commented  · 

    Agreed! It's ridiculous that we have no way to protect ourselves from these problems -- whether caused by the user, IT, some script, or a third-party tool. I had half of my Contacts corrupted for reasons unknown and was told that:
    1. there's no backup/restore option
    2. there's not going to be one in the near future
    3. there's no way to determine what caused this
    4. there's no tool that can be run to protect against this in the future

    I don't see why there isn't either a backup tool that we can run or at the very least, a database-level log that monitors changes to our OST files that can identify where these changes originate and ideally, notifies us of atypical behaviors such as the one I encountered.

    Scott MacKnight supported this idea  · 
  2. 3,245 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    115 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Scott MacKnight commented  · 

    Better still would be a setting like Litigation Hold that we can enable on a per user basis that would allow us to maintain a snapshot/backup of a mailbox at regular intervals -- OR some other way to backup a mailbox so we can protect Calendar, Contact and Task items from accidental deletion or sync corruption.

    Scott MacKnight supported this idea  · 

Feedback and Knowledge Base