Using classic Outlook for Windows in business environments
It is not the IP address assigned on your end (source IP). It is the destination IP returned by DNS when your client looks up "outlook.com" or whatever you've specified for server (there are many aliases that all point to the same place). They load balance amongst many, many servers and only certain ones seem to have the issue.
My guess is if you are dormant for a while the connection goes away (or maybe a blip on your internet, weak wifi signal, etc) then when it re-establishes it hits a different IP at MS. Bouncing your network connection will get you a new random server (that hopefully doesn't have the issue).