Feedback by UserVoice

Office 365 Security & Compliance

We have partnered with UserVoice, a third-party service and your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.

Welcome to the Security (Protection) & Compliance UserVoice forum. We’re happy you’re here! If you have suggestions or ideas on how to improve Security or Compliance related features in O365, we’d love to hear them!

How it works
◾Check out the ideas others have suggested and vote on your favorites
◾If you have a suggestion that’s not listed yet, submit your own — 25 words or less, please
◾Include one suggestion per post

Thanks for joining our community and helping improve these features in Office 365!

Need Tech Support? Please see the O365 Community for the product or feature you are having issues with, or open a support ticket through your Office 365 administrator portal.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. SMTP Protocol Logs availability

    SMTP Protocol logs are an invaluable tool when troubleshooting message delivery in on-premises Exchange Server.

    I have just had a support case closed because Office 365 support cannot provide SMTP Protocol logs and I'm stuck, not able to determine the cause of a mail flow issue without the logs. The only option for send/receive information on a particular message is advanced message trace, which does not provide details of the message conversation.

    Can you provide a way for admins to request these logs from the Office 365 support team, if not provide a way to access them via Remote PowerShell?…

    225 votes
    Sign in
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Message Trace  ·  Flag idea as inappropriate…  ·  Admin →

    As Exchange Online operates in a multi-tenant configuration, protocol logs include connections from multiple customers. Unlike Message Tracking Logs, these logs are not attributed to a specific tenant at a protocol level, therefore there is no way extract a single tenant’s logs. We provide Message Trace as the best way of tracking the messages that pass through our service.

    For connections from your own servers to our service, you do have the ability to analyse your logs which would mirror our own front door protocol logs. Message Trace would then take over for messages that were accepted by our service.

    For support cases, protocol logs can be searched for as part of tracking down an issue for an instance of an issue, however support cannot provide customers with their protocol logs for them to do their own investigation.

    We understand that admins have much less control of what happens to…

  • Don't see your idea?

Feedback and Knowledge Base