Span AADDS domain across multi regions
Span the same AADDS domain to multi regions - currently only possible with vnet pairing and VPN gateways. Would also add redundancy to the domain if say a region were to go down or the AADDS service were to stop within a region.
Engineering has begun work on this.
Ryan Adler commented
I am actually quite surprised that this was not included in the original design. I hope there will be some news soon!
Chris Butler commented
Where can customers self-service view status on this particular feature (multi region ADDS)?
Mike Stephens commented
Remains in development. No ETA that we can share at this time. We'll update this once we get closer to release.
Senior Program Manager
IAM Core | Domain Services
Chris Gray commented
Any ETA for this release?
Scott Heath commented
I see this was set to planned, is there an ETA?
chris hudson commented
We need redundancy if we have a regional failure. We had one today and it wiped out our entire global estate.
Either allow us to add Domain Controllers or better still, allow us to put multiple managed pairs in different regions.
As it stands we're gong to have to remove it and go back to good old IaaS VM's with traditional AD which is a backward step IMO.
S. McKenzie commented
Connectivity across regions is now possible with Global VNet Peering.
However, this does not fix the redundancy problem. If the region hosting the AADDS service goes down the service will be unavailable from all regions.
Shahid Iqbal commented
Beyond redundancy I work with clients who run SaaS solutions deployed to IaaS across regions for different customers and being able to "domain join" their VMs to their AAD would be fantastic. Currently the option of running VPN gateways back to a VNET to enable this isn't an option