MS publishes Azure IP ranges[1] so it should be trivial to check if the attack originates from those or something else. MS also has abuse contact exactly for t

MS publishes Azure IP ranges[1] so it should be trivial to check if the attack originates from those or something else. MS also has abuse contact exactly for this purpose[2]. I have no experience what their response is there, but probably worth a shot anyways. [1] https://www.microsoft.com/en-us/download/details.aspx?id=56519 https://www.microsoft.com/en-us/download/details.aspx?id=565... [2] https://msrc.microsoft.com/report/abuse https://msrc.microsoft.com/report/abuse