So I spoke too soon, the issue came back today. Customer called and said the error is showing up again. I have opened up a ticket with Microsoft to see if they can tell me what's going on. I'll still update the post in case others are having the same issues.