Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Some of the functionality described in this release plan has not been released. Delivery timelines may change and projected functionality may not be released (see Microsoft policy). Learn more: What's new and planned
| Enabled for | Public preview | Early access | General availability |
|---|---|---|---|
| Admins, makers, marketers, or analysts, automatically | 
Feb 24, 2025 |
- | Jul 2025 |
Business value
Microsoft Entra hybrid join with custom virtual networks (VNETs) and hosted machine groups lets your hosted machine group bots enroll in both your on-premises Active Directory (AD) and Microsoft Entra ID. Use this feature when automation requires authentication with an AD account or when you need to manage devices with Group Policy (GPO).
Feature details
This feature supports joining hosted machine group bots to both on-premises Active Directory (AD) and Microsoft Entra ID when you use custom virtual networks (VNETs).
- You configure a custom virtual network (VNET) by using Azure Virtual Network. The custom VNET needs access to the domain controller.
- When you use a custom VNET, you can access on-premises resources while running your automation.
- You configure Microsoft Entra hybrid join as part of the Power Automate network connection setup.
- With Microsoft Entra hybrid join, your hosted machine group bots enroll in both your on-premises Active Directory (AD) and Microsoft Entra ID.
Geographic areas
Visit the Explore Feature Geography report for Microsoft Azure areas where this feature is planned or available.
Language availability
Visit the Explore Feature Language report for information on this feature's availability.
Additional resources
Additional requirements for Microsoft Entra hybrid joined hosted machines groups (preview) (docs)