Hello Arif Usman,
Welcome to the Microsoft Q&A and thank you for posting your questions here.
I understand that you would like to use azure automation to create user\groups in on-premise AD with runbook.
Regarding your scenarios and questions:
If I have a domain-joined VM in Azure (joined to on-prem AD via VPN or ExpressRoute), can this VM function as an Azure Arc-enabled hybrid worker?
Yes, and here’s how: https://learn.microsoft.com/en-us/azure/automation/automation-hybrid-runbook-worker
Is using a hybrid runbook worker the most efficient and secure way to manage on-prem AD objects from Azure?
Yes, especially the extension-based HRW.
Check this link: https://practical365.com/how-to-manage-on-premises-infrastructure-using-azure-automation-hybrid-worker/ it helps you in hybrid runbook worker the most efficient and secure method.
Are there alternative architectures or best practices recommended for this use case?
I will recommend these Architectures:
- Azure Automation Account
- Extension-based Hybrid Runbook Worker on Azure VM
- Azure Key Vault for storing AD service account credentials
- Azure Monitor / Log Analytics for logging and alerting
For best practices:
- Use PowerShell runbooks with ActiveDirectory module.
- Secure credentials using Managed Identity or Key Vault.
- Monitor execution via Azure Monitor and Log Analytics Workspace as stated in the link above.
Finally, avoid the followings:
- Agent-based HRW (retired).
- Exposing AD via public APIs.
I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.
Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.