Observing 169 Address Calling to Exchange ECP

I am observing a 169 address within the domain reaching out to the public IP address of our exchange servers and attempting to access random files in the ECP directory. I don't know how a 169 address could possibly reach a public IP address unless their is some kind of obfuscation going on that I am not aware of.

More curious to me is that the 169 addresses are not based on any kind of order like you would normally …

address cybersecurity exchange