We've had reports of several users, whose host is using third party auth, receiving the following error message after failing to connect: "Connections to this remote machine are temporarily blocked because someone was trying to connect to it with invalid PIN.  Please try again later"

The problem with this message is that is not accurate and confuses the end user as they never entered a PIN during the connection process.

We should update this message to mention third party auth.  It may be difficult to provide specific links for troubleshooting, perhaps we can use a policy registry key for enterprise admins to provide a specific troubleshooting link.