I\'ve been hunting for this error that occurs intermittently on an AJAX call to an Azure ASP.NET Website, and today I\'ve finally caught it in our logs. I was suspecting a lock
It sounds like the problem is in the connection from the client to the Internet. If you are making the Ajax call in client-side JavaScript, it doesn't matter (at least as far as performance goes) whether the web app and database are in the same region. A very slow connection will call a timeout.
Since this is intermittent, I recommend catching this error in JavaScript and allowing prompting the client to retry the save.