Update 7/14/2025: Updated the FAQ.
As with all cloud services, Exchange Online imposes service limits to prevent misuse of Exchange Online resources and ensure availability for all users. For examp...
Updated Jul 14, 2025
Version 18.0
Blog Post
The idea I love it, go secure, less spam yeey. The timing and implementation I hate. One of the things I loved about Exchange team that if they do change something they give us time to prepare. In the worst case I got less than a week and I consider myself lucky, because in the morning, I was scrolling social media, and I following Tony Redmond who was writing about this article. I only read Microsoft news once monthly mostly through Nick Ross, because who's got to time, to always catch up and follow all the updates Microsoft is giving out. The normal time I get this information would be that our clients are blocked and can’t send mails.
Out company is an MSP, and also providing other IT related services to customers. We have multiple transport logistics companies, whose job is to organize transporting goods. The company is relatively small (<30 people), but they need to send large volume emails to arrange and do work. Now I was rushing to check the report, yet the option name was not the same (Tenant Outbound External Recipients count, yeey go renaming team...) but the main problem, is the report is just not loading. It is just an empty white page. I will check the page later, but all things considered, (with do respect) this is not what we used from Exchange Team.
KevinShaughnessy
Microsoft
Microsoftbrogyi I hear you and I'll take the blame for the short notice. Our protocol is typically months in advance to give folks time to prepare, etc. and I've always aligned with that in previous releases. Alas, a confluence of factors conspired against that this time. Apologies.
You don't have to wait for the report to be fully deployed/enabled later this week. Use the PowerShell cmdlet referenced in the FAQ: Get-LimitsEnforcementStatus. Check Threshold (your quota) and ObservedValue (your current volume).
Well this give you a moments nr. but that changes all the time, and it depenmds a lot on what kind off business you run in your tenant, and by the way this by far not the first time MS is introducing "new features" without giving the admins the tools to stay in control or even manage it.
An apology to one user in a comment is not sufficient. Update your blog post with an official statement from Microsoft.
I am getting an error message when running Get-LimitsEnforcementStatus and no report is available.
Can someone MS acknowledge the concerns that this enforced change is making, and put something into place to address it.
The Exchange cmdlet Get-LimitsEnforcementStatus is not known in our tenant. So there is neither the report nor the cmdlet. What now?
- KevinShaughnessy
SevenOfNine BoBeB sorry for the delay - didn't see this one until now. Are you still not seeing or hitting errors with the cmdlet? The report should have lit up in your tenants earlier today. PM me your tenantID or primary domain if you're still not seeing both of them or hitting any errors.
The cmdlet is still missing. The report shows up under reports, but if I open it, the page is completely empty, even the header is missing. I compared it to another tenant, where it is working.
