It appears that a Microsoft setting created an issue with the change of date to the new year.
A signed int variable maxes out at 2147483647. When the date rolled over to 202201010001, the issue arose.
Click Here for Microsoft's suggested solution.
More about this issue:
Alt workaround (disable the malware protection built into Exchange):