Using classic Outlook for Windows in business environments
Dear @Rainer,
Welcome to Microsoft Q&A Forum!
Thank you very much for taking the time to share your detailed observations regarding the built‑in Report button in Outlook. I completely understand how confusing and frustrating this experience can be, especially when the actual behavior may not seem to fully align with the available documentation. I truly appreciate your patience while reviewing these points.
Below, I would like to address each of your concerns individually and clarify the current, supported behavior based on what I researched.
1.Reporting an email as Junk does not add the sender to Blocked Senders:
When a user reports an email as Junk using the Outlook Report button, the primary purpose of this action is to provide feedback to Microsoft’s filtering systems and help improve spam detection across the service. The message is moved to the Junk Email folder as expected. However, this action does not automatically add the sender to the user’s Blocked Senders list.
This behavior is expected. Reporting messages is intended for service‑level threat intelligence, while personal sender blocking is managed separately through:
- The Blocked Senders list
- Exchange mail flow rules or Outlook mailbox rules
- Anti‑spam policies at the tenant level
References:
- Manage mail flow rules in Exchange Online
- Manage email messages by using rules in Outlook
- Configure anti-spam policies for cloud mailboxes
2.Reporting an email as Phishing does not clearly document sender blocking:
When an email is reported as Phishing, Outlook typically moves the message to Deleted Items, and the report is sent to Microsoft for security analysis.
Microsoft does not publicly document whether the sender is automatically blocked after a phishing report. This is intentional, as phishing reports feed into Microsoft Defender threat intelligence, where actions such as blocking are handled centrally and dynamically, rather than through visible user‑level rules.
As a result:
- Reporting phishing should not be relied on as a guaranteed “block sender” action.
- Long‑term blocking should be enforced using security policies or mail flow rules.
Reference: User reported settings
3.Admin limitations after reviewing reported messages:
After a message is reported and reviewed by an administrator, the available actions are intentionally limited:
- The original email cannot be restored to the user’s Inbox
- The message cannot be permanently deleted from the reporting pipeline
This is expected behavior and is part of Microsoft’s security model. Once reported, messages become part of an investigation and telemetry process, and administrators are provided review visibility rather than full remediation control.
If a message was incorrectly classified, the recommended approach is to:
- Adjust anti‑spam or anti‑phishing policies
- Release or allow similar messages going forward
4.Organization logo not appearing in report notification emails:
You also mentioned that the option “Replace the Microsoft logo with my organization’s logo across all reporting experiences” is enabled, yet the Microsoft logo still appears in notification emails.
While this branding setting does apply to many Microsoft 365 portals and interfaces, not all email notification templates may currently support custom branding. Some security‑related notification emails are still Microsoft‑controlled and may not reflect tenant branding, even when the logo is configured correctly elsewhere.
This may be considered as expected behavior and not related to a misconfiguration on your side.
Reference: Customize the Microsoft 365 theme for your organization
Therefore, in my perspective view, your findings are valid, and many of the behaviors you described are expected but not yet fully documented. For gaps such as branding consistency or clearer sender‑blocking behavior, Microsoft actively encourages customer feedback. You may consider:
- Submitting feedback via the Microsoft Feedback Portal
- Opening a support case through the Microsoft 365 Admin Center for more information of current behavior.
Please know that I completely understand how these behaviors can impact administrative workflows, and I appreciate you bringing such detailed observations forward. However, this is a peer‑to‑peer support forum. Microsoft Q&A moderators like myself, as well as other community members, share guidance based on personal experience and publicly available information. Due to security and privacy protocols, we do not have access to your internal environment and are unable to help you further. Our role is to help guide the discussion and connect you with relevant and helpful resources. I hope for your patience and understanding in this situation.
Besides that, sharing your experience to Microsoft Feedback portal helps Microsoft prioritize feature improvements in this scenario. Once you submit your feedback there, other users and I can locate your post and vote for it, which increases your visibility and priority to the product team. And I appreciate you raising this issue. Your action can help others in our community who face the same concern.
I hope this clarification helps align expectations and provides you some insights in this concern. Wish you a pleasant day!
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.