Feedback by UserVoice

Edward Dickson

My feedback

  1. 19 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 » Reports  ·  Flag idea as inappropriate…  ·  Admin →
    Edward Dickson 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 » Reports  ·  Flag idea as inappropriate…  ·  Admin →
    Edward Dickson supported this idea  · 
  3. 165 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Office 365 Security & Compliance » Reports  ·  Flag idea as inappropriate…  ·  Admin →
    Edward Dickson supported this idea  · 
  4. 246 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    21 comments  ·  Office 365 Security & Compliance » Reports  ·  Flag idea as inappropriate…  ·  Admin →

    1. Click into “details”.
    2. Choose “connector report”.
    3. Choose “request report”.
    4. Answer the questions in the wizard, clicking “Next”, “Next”, and “Save”.
    5. Wait for the report to come to the email address specified. It will contain the following fields:
    message_id, direction, sender_address, recipient_address, connector_name, connector_type, tls_version, tls_cipher

    With the Message_Id value, you can combine this with MessageTrace to get the Subject.

    If this does not help, please provide more information as to the scenario and detail that is missing. Thank you for the feedback!

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

    Hi Scott,

    The solution that you have suggested is inadequate for the situation. The connector report has no functionality to filter emails based on TLS version or protocol, prior to the report being exported and has a small limit on the data that you return.

    This means that it isn't possible to export a report of which emails use TLS 1.0 or 1.1 without exporting a list of every single email from that period. If that isn't bad enough, it wouldn't be a single report as there is relatively small limit on the size of the reports.

    I full well agree that TLS 1.0 and TLS 1.1 should be depreciated but Microsoft need to provide their customers with the tools to make this happen without incident!

    Edward

  5. 206 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Office 365 Security & Compliance  ·  Flag idea as inappropriate…  ·  Admin →
    Edward Dickson supported this idea  · 

Feedback and Knowledge Base