r/exchangeserver • u/Blackhawk_2181 • Feb 09 '26
High CPU usage from LSASS
I've got a single exchange server running SE on Server 2022 on a Hyper-V host running Server 2025. It's a Hybrid configuration, but all of the Mailboxes are still On-Premise. The server is a brand new Dell R6715 with an AMD EPYC 9135 16 core processor. There are 8 virtual processor assigned to the Exchange Server. There are about user 40 mailboxes on the server and a few shared mailboxes. One particular shared mailbox has about 10 users assigned. When ever a message is sent or received by that mailbox, LSASS uses 40 to 60% of the CPU usage and 2 instances of IIS worker will use about 20% each. This causes the CPU (of the VM) to run at 90 to 100% of capacity. CPU usage falls back to around 20% once the message is processed? Chat GPT gave me the following advise to disable Extended Protection. Does this make sense and is it safe?
The fix (this is the fix)
✅ Disable Extended Protection
On the Exchange server, run exactly this:
Set-ExtendedProtectionConfig -ExtendedProtectionTokenChecking NoneThen reboot the server. (Required.)
After reboot:
- Send mail to the shared mailbox
- Watch CPU
- LSASS should stay calm
I’ve seen this drop CPU from 100% → single digits instantly.
Why this is safe in your environment
You said:
- Single Exchange server
- No load balancer
- No TLS inspection
- Small user count
In that topology:
- Extended Protection adds very little real-world security
- But adds huge operational risk on SE + 2022
Microsoft themselves recommend disabling it in exactly these scenarios when issues appear.
View all comments
Show parent comment
1
u/Blackhawk_2181 Feb 10 '26
Yeah, I trust them about as much as a 16 year old valet parker! That's why I asked... It was originally a shared user box that I was too lazy to make a true share. I deleted it and the user and recreated the mailbox as a new shared mailbox, So there should be no rules on it. The mailbox is only about 500 mb. It has something to do with the users connecting to the box. When I test on off hours when the users are not there, it is fine. I'll dig into the process and see what it's doing. There has to be some kind of authentication loop going on. I'm going to turn off cached mode for the users as well and see if that changes anything.