If the load balancer already does some connection tracking, it can just keep serving existing connections and only drop new ones. If connection tracking is not available, the IP blocklist would be a suitable option.
IP blocking is generally not what you want though.
Okay, they get different IPs during the day, fine. But it's still kind of randomized. Stepping through IP ranges will reduce load and give access to more people.
I really don't get the issue you are seeing with this.
IIRC Microsoft posted a comment around 10pm where they discussed rate-limiting external connections, and many reactions on last week's HN thread were like "wait, you so didn't even drop load before now?" So internal load may have been a contributing factor, but it's by no means certain given that they didn't stop serving clients.
(It might be better not to use CIDR ranges, but use the lower bits instead if possible. For example starting to unblock all IPs that end with .80 until .90, to get more random geographical distribution)
Which leads to my suspicion it was internal load that brought the system down. Communication between the servers (like delivering queued up messages from one O365 account to another), and not external access from users and apps.