microsoft-365-docs
microsoft-365-docs copied to clipboard
MicrosoftDocs
Edge/Perimeter Blocking appears to be missing
Before messages reach connection filtering, the message is scanned at the perimeter. Messages blocked at the perimeter have historically been trackable using the "Get-PerimeterMessageTrace" command. This command has been depricated with no alternative being made available.
Case #:19578907
- A method for tracking down delivery failures from the recipient side (o365) without asking the sender for these details. Historically we could use Get-PerimeterMessageTrace which is no longer available
- A process for allowing those messages through either by opening a ticket and having Microsoft address the issue from their side, or having steps to follow that work.
and Case #:22133544
User voice request requesting enhancement in this area https://office365.uservoice.com/forums/289138-office-365-security-compliance/suggestions/41483617-message-trace-doesn-t-find-email-blocked-due-to-bl
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: a8878304-7f4b-15c3-d2b6-8a5583930199
- Version Independent ID: 329f3b45-a087-6743-0664-e74dd9e0fc46
- Content: Exchange Online Protection (EOP) overview - Office 365
- Content Source: microsoft-365/security/office-365-security/exchange-online-protection-overview.md
- Service: o365-seccomp
- GitHub Login: @chrisda
- Microsoft Alias: chrisda
@jonwbstr, are you a Microsoft employee? If so, can we continue this discussion over email? Thanks.
For reference, the correct term for filtering at the perimeter is "Domain Based Edge Blocking" or DBEB
I haven't seen any changes to the behavior or to the article yet so hopefully not :)
@jonwbstr Thank you for reporting this feedback here. This list is focused on content issues and I want to make sure your immediate product issue does not get lost in this list. It is a feature request and escalate to the appropriate product team. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.
Hello,
Are those issues something I can follow?
I'm actively interested in the resolution of those issues. Closing a ticket where the resolution is 'i opened separate issue that you can't track' puts me in a slightly awkward position.
Thoughts?
On Fri, Apr 9, 2021, 12:32 PM Yogesh Kumar @.***> wrote:
@chrisda https://github.com/chrisda Can this be resolved? Thanks
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/microsoft-365-docs/issues/3212#issuecomment-816804213, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADXTPAHUTXJ7UCAQHN2FQD3TH4T27ANCNFSM4SWJ76BQ .
Hi all, I noticed the uservoice entry is no longer valid, is there a new location for this feedback or does it need to be recreated somewhere?
@yogkumgit I don't see any updates to the article addressing this issue, what was the reason for closure?
Morning, I am not sure how notifications on closed issues works so mentioning you both.
- Did perimeter blocking get removed or changed?
- Are failures due to perimeter blocking surfaced through message tracking or by another means?
@chrisda, @yogkumgit If the answer to the above questions is "no" where is the current behavior documented if not this article. Thanks!
For clarity, I understand there are open feature requests and bugs concerning the current behavior. In the meantime, my aim is for this article to accurately reflect how message filtering is currently handled.
The goal is to also help admins and MSFT support agents avoid escalations when troubleshooting undelivered and untrackable messages, because of gaps in the documentation.