-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Epic] - Use an existing AD #475
Comments
Hi there - what is the ETA on integrating AzureHPC into existing AD/AAD? We have requirements to do this to meet strict security policies and have a tool by BeyondTrust (PowerBroker/ADBridge) to handle that integration. Can we 1) deploy that, and 2) disable the AD installation in the build script? |
@lhg2 we don't have an ETA yet and this work hasn't started. We are driven by customer requirements and demand, so if you have one we will be glad to work with you on this. |
Thank you. At the very least, we would need to use an AD integration tool (PowerBroker/ADBridge) to perform a domainjoin to our on-prem AD environment. We would need to bypass the current AD build requirement (don't need SSSD, etc.) and use our tooling for proper Enterprise integration and centralized user management. Is this achievable? |
probably yes, but never tested. You would have to replace in the scripts all the domain join stuff with yours. Also we do have specific groups used to grant users privileges for sudo access for example. Can we connect offline ? Please send me an email to xpillons@microsoft.com |
@xpillons - Yep! Thanks much. |
Instead of deploying a Sandbox ADDS dedicated to an azhop environment, provide the capability to connect to an existing Domain Controller.
The text was updated successfully, but these errors were encountered: