Remedy.
React!
Actively deactivate the inactive Active Directory and activate the inactive active Active Directory retroactively.
Crossfingers and reboot.
Alas, poor Redmond has acknowledged the Azure Active Directory is "having issues" alongside the disappearance of its Office 365 service in the UK and Europe. Microsoft's Office 365 service went down earlier this morning, and Microsoft has now copped to an issue affecting Azure Active Directory. Azure's status page reveals: …
Azure goes down a lot less than in-house Directory services I've seen in the past with much much shorter times to recovery. The downside is that you don't get the sense that anybody is working on the problem though constantly calling the IT team for a status update tends to get things fixed much slower.
1) That's what DND functions on telephones are for.
2) That's what junior techs are for (literally: Stand there, touch nothing, tell people to go away).
3) In-house stuff is under your control. You can spin up "something" quite quickly, even if it's just rolling back to a snapshot or similar. Azure, you are at their mercy.
I'm assuming (not really looked into it as my place won't touch cloud things) that you can have in-house AD talking to Azure AD and vice-versa, like any other directory, no? If not, I don't understand why you'd touch it. But Azure going down in that case could still cause problems with remote-workers and other services, I imagine.
Redundancy, people. Cloud is fine. But what's your backup? If you can't answer that satisfactorily, you have to think if you're doing your job properly. We still don't live in an age where people can't put diggers through fibre lines.
They had a small issue with mail sent from their servers having the sent from address as user@on.Microsoft.realdomain.com
I think it was related to active directory sync with azure but seemed to sort itself out.
We don't use the cloud so the only complaints I had were from my users getting NDR's for non existent address's
Don't confuse Active Directory with Azure Active Directory, which have nothing in common apart from the similar names.
For example, Azure AD has only very recently gained the ability to function as a Windows domain controller: this feature is now in "technical preview".
http://blogs.technet.com/b/ad/archive/2015/10/14/azure-ad-domain-services-is-now-in-public-preview-use-azure-ad-as-a-cloud-based-domain-controller.aspx
Meanwhile in Redmond the Christmas party is in full swing, all the executives dressed as Santa, the PA's dressed in cute costumes and even the servs dressed as elves, allowed out of the dark dungeons are allowed to partake in a little bit of mulled wine.
Oh wait, the real fun is about to start - somebody just took out a violin.
Such fun
My application servers are running on Amazon, my database in Azure, my directory services on Microsoft, my Network is outsourced, System Integrators from Asia are developing my apps and I use service providers to deliver the in house services. All my users are using Windows365, (except for the ones on Google and its Drive), using mobiles supported by three different comms companies.
- my JIT suppliers have executed a similarly brilliant IT strategy
- - their JIT suppliers have executed a similarly brilliant IT strategy
- - - their JIT suppliers have executed a similarly brilliant IT strategy
- - - - recurring
And you wonder why we do not sleep at night!!!! <swallow some more sleeping pills with energy drinks>
Talking to each other, and it hasn't been down for even a day?
Calm down. Save the drastic measures for when they're needed.
I still keep the spear and loin cloth from my Y2K Preparation kit in the office.
Ready to go feral and hunt my co-workers for food at a moment's notice.