Feedback by UserVoice

Anonymous

My feedback

  1. 85 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Anonymous supported this idea  · 
    Anonymous commented  · 

    We had a similar issue with these reports, however we have a huge user base (thousands of users) and use an automated powershell script to change forwarding addresses. We got hundreds of alerts with the account that was being used to make changes, but since the alerts were missing two critical pieces of information - which object was being changed, and what the old & new email addresses were - we thought the account that was making the changes was the account being affected. We called O365 support, and *their* technician thought the same thing. We spent over a week in technical support because even their technicians thought the user listed was the one being changed, before they finally figured out what was going on. For this alert to be useful it needs to include this extra data and possibly the ability to customize the alert so it only fires when forwarding to a non-tenant email address

  2. 9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Office 365 Security & Compliance » Auditing  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  3. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Office 365 Security & Compliance » Reports  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 

Feedback and Knowledge Base