Did your AWA Hybrid application suddenly stop working over the week-end?!
The Problem
First reported by fellow MVP George Hepworth, it would seem that Microsoft, in their very finite wisdom, decided to change some, or all of their AWAs server(s) over the course of the week-end without notifying a single user. As a result, the connection string and credential you’ve always used, today, are invalid and your database is dead in the water.
George reported that the External Connections setting was also disabled.
A few threads on the matter
Below are a few threads that have surfaced regarding the problem.
The Solution
You will need to log into your Office365 account, re-enable the External Connections, get the new server name and credentials and update each of your database in consequence.
I just found that George published a post on the subject, so feel free to check out his post: Sometimes You Just Have to Scratch Your Head….
The Bigger Problem!
With this incident, Microsoft has single handedly shown us what the entire issue is with the cloud! When someone else manages things, you have no say or control over anything and you must always play a disaster and recovery role. Fun times for a great many this morning, and many more issues like this one to come, I suspect!