100% this. We had the same issue at our company for several years - we put up with it for a while but eventually raised it with microsoft. To be fair, it take

100% this. We had the same issue at our company for several years - we put up with it for a while but eventually raised it with microsoft. To be fair, it take a fair bit of back-and-forth with microsoft to track the problem down, but turns out about 5 or 10 years back when the company was only a few people, one of the directors had played around with setting up a microsoft domain, didn't use it, stopped playing with it and then forgot about it. Didn't cause any issues until years down the track when suddenly we started getting errors like the above. Once we established that MS worked with us to remove the domain from their systems, the errors went away, and I considered they were very helpful given the very small amount of money we spend on their services.