6 votesneed-feedback · 4 comments · Azure Active Directory » Domain Services · Flag idea as inappropriate… · Admin →
An error occurred while saving the commentHarry Powell commented
Hey Mike, thanks for replying. In my company we had a requirement where we manage infrastructure for two companies - essentially a top level company and its subsidiary; that did not have any network connectivity no shared user space but wanted to collaborate and share certain applications between the businesses. Initially we decided to go down the O365 route (both companies identities syncing to a single tenant) in order to allow for address book collaboration etc.
However there was actual apps, hosted in an Azure subscription that we wanted both sets of users to use, and didnt really want to deploy the IAAS machines to build a domain and wanted to utilise the Azure AD footprint we already had, merely uplifting that to AADS, creating non-transitive forest trusts between our on-prem domain (at this time we still had direction from the business to not have any network connections between the environments).
I think AADS could have been a great tool to use, would have allowed us to consume more SAAS services in Azure, and is still something i think would be a great aide to businesses looking to take some of the management out of AD/Forest management, that want to use Azure to host a shared/bridging platform for their user bases like we did.
Please let me know if you would like to have a call or a further discussion about this with me.
Working with the ARM PM team to review this request.
Thanks for your suggestion! The feature is currently in our backlog, but has to be prioritized with other ones. So we don’t have an ETA at this point of time. Please don’t hesitate to vote for it if you want to see it’s done sooner.
We plan to add the auto-start to the regular Compute blade at some point. However, if you create the VMs in a Lab, the auto-start is already available.
Also, we do de-allocate.
Thanks for the input!