Microsoft's backend team was able to replicate the same issue on their side. It's likely a code error. We're waiting to hear from them if they'll patch it. I'm just surprised we're the only ones who identified this issue. NDI Tools probably won't be used much in MS Teams.