Event banner
Event details
102 Comments
- Like Thomas Roosens, I don't have the report also. according to MS article, the first information was sent to all costumers, and later, when servers will be trigger, we'll receive another information on Message Center. When it will happen? The report being available will mark the start of the server analysis and after that we could pause the trigger?
- The report is coming soon...in a few weeks. We had targeted May 23, but we may need to push that out a few weeks.
- So, in fact, when the throttling phase will begin? is there a clear calendar for it?
- I don't see the report in my Exchange Admin Center. When will this become available?
JKenersoMSFTMicrosoft
The report will be available by the end of June - and will be phased in by Exchange Server version over time- For the first wave of customers, it is expected in the next few weeks.
- What will be the method of notification for Exchange Admins?
- In addition to the new report in the EAC, there's also the SMTP In logs, message tracking logs, and get-queue/message.
- JKenersoMSFTThe primary approach will be a new report - “Connecting Server Mail Flow Report” in the Exchange admin center in Exchange Online.
- So, this is not so much of a "notification". It is actually something that an admin will have to know that they need to be going to look for?
- What are the criteria for unpatched Exchange servers? Are they unpatched vulnerabilities (e.g. Extended Protection not enabled) or just missing security updates?
- For Exchange 2013 and earlier, its simply based on the version (and the fact that these versions are unsupported). For Exchange 2016/2019, we will work with engineering to determine the minimum compliant build, which will in part be based on the severity of any patched vulnerabilities.
- Where will documentation about these criteria be posted? How will we know when this documentation is available? Any service we can subscribe to in order to received updates on available info?
- What is the time frame of first notification for Exchange 2013?
- Exchange 2013 customers are expected to receive notification later this year.
Later this year can be tomorrow :). Is later Q4? Assuming the Exchange 2013 servers have all the latestest CUs and SUs possible.
- what is the time frame for enforcing the new update policy on Exchange 2019?
- Exchange 2016 and Exchange 2019 won't be in scope until early next year.
- Would this be based on the CU or the monthly security updates?
- Does this mean that our Exch2010 hybrid environment will stop working (not be able to send mail to EOL)? We are in a situation where we cannot raise our AD domain functional level to AD2012R2 since we are still running AD2003 servers to facilitate our outdated broadcast environment (National Broadcaster). The projected rollout completion date of the new broadcasting software is only April 2024.
- As Scott as said, upgrading/patching should be a first priority when possible. I'm sure you know it already. However, if you pass your mail thru a supported gateway (or non-Microsoft gateway) first before reaching Office 365, mail should still flow properly. You might look at something like mimecast, barracuda, or similar to do some second-level security/hygiene/dlp stuff before passing to office 365. this could give you more time to complete a migration or upgrade. @scott...not trying to circumvent, but some orgs are complicated and can't move quickly. Priasoft is 20+ years of migration stuff...so i'm familiar.
- Excellent thank you Eric! This might just buy us the time we need. Broadcasting is our core business and mail is critical to this. Will engage our ISP tomorrow to discuss.
- Eventually, yes; we will block email from Exchange 2010 servers that use an inbound connector type of OnPremises. We would strongly recommend you accelerate your plans to move off these outdated and unsupported platforms.
- Thank you Scott. What timeframe are we talking about when you say "eventually"?
Is there any ETA for being able to view the Status Reports for recalled messages - when the sender is a Shared Mailbox?
Same question - when sending as a Delegate?
Per this post 'https://techcommunity.microsoft.com/t5/exchange-team-blog/cloud-based-message-recall-in-exchange-online/ba-p/3744714' the Message Recall function technically WORKS in these scenarios, but the Status Report can't be viewed.- Hi Sara, the message recall feature is not the subject of this AMA. But if you send me your questions about it at schnoll@microsoft.com, I'll do my best to find an answer for you.
Will the reporting/logging information collected be accessible via powershell, in the context of the Transport blocking unpatched exchange?
- Some of it, yes. The details on the reports won't be accessible via PowerShell, but other data points, such as SMTP In logs, Message Tracking logs, and cmdlets like Get-Queue and Get-Message can be used to get details about any throttling or blocking activity.
- I'm thinking about MSPs and monitoring and auto-responses. Would there be a way to setup a chron job to check for the blocking in order to setup a custom notification system to self or customers? Does that make sense?
Welcome to the Exchange Ask Microsoft Anything (AMA)! This text-based live hour event gives you the opportunity to ask questions and provide feedback to the product team. Post each question in the "Comment on this event…" box above.
- Hi folks! Welcome to our AMA. I'm Scott Schnoll, the product marketing manager for Exchange Online and Exchange Server. Very happy to answer your questions today regarding our blog post at https://techcommunity.microsoft.com/t5/exchange-team-blog/throttling-and-blocking-email-from-persistently-vulnerable/bc-p/3817538#M36305.
