Exchange Online to introduce External Recipient Rate Limit

IanMcDonald Thank you for your response and the provided explanation. I appreciate being informed about upcoming changes; however, without actionable steps, such notifications can feel counterproductive.

Suggestion for Improvement: It may be beneficial to release notices only when the corresponding pre-req tools/reports are ready. Alternatively, if early warnings are necessary, clearly communicate a grace period post-report availability before enforcement begins. This approach would alleviate concerns regarding the perceived narrow window between report issuance and policy enforcement.

One more thing: Product managers for M365 need TO FOCUS ON TECH DEBT... we are going on far too long with the same on-prem roots foundations that are not suited to multi-tenancy or cloud based access of data (poor API access). I see it everywhere from Azure portal to Exchange. The fact you can't simply turn out this report promptly suggests to me that the backend is such a hot mess that your agility to work with the platform is practically in paralysis. What hot new features do I want in the road map? FIX THE FOUNDATION to enable true innovation to sit on top of it. It's not sexy but it's a debt you will ether pay by coding or pay by not being able to make a simple email report. I am sure you have dev's that would love nothing better to attack that foundation, set aside 30% of your development for this purpose. It will pay off big later on.