In modern Entra ID–based environments, device groups replace the role traditionally played by Organizational Units (OUs) in on-premises Active Directory. These groups are used not only to structure devices logically, but also to plan and drive operational workflows, including patching, remediation, and other forms of automation.
Action1 has long supported this approach through its Groups feature, allowing customers to target devices dynamically based on endpoint attributes. However, until recently, leveraging Entra ID group structure inside Action1 required a workaround: Entra ID–joined devices had to be manually placed into the appropriate Action1 groups in order to mirror the Entra structure.
The new Entra ID Groups → Action1 Connector changes that.
Entra ID Groups Action1 Connector
What the Connector Does
The Entra ID Groups → Action1 Connector is a lightweight integration that:
· Reads devices and their group membership from Microsoft Entra ID
· Matches Entra ID devices to Action1 endpoints by device name
· Writes Entra-related data into Action1 custom attributes
· Enables dynamic grouping and automation inside Action1 based on Entra ID group membership
Once Entra ID group membership is written into Action1 custom attributes, it can be reused across the platform, just like any other endpoint attribute.
Typical Use Case
A common scenario looks like this:
· Devices are organized into groups in Entra ID (for example: Marketing, Engineering, Production Servers)
· The connector writes Entra ID group membership into Action1 custom attributes
· Action1 dynamic groups automatically include the correct endpoints
· Patch deployment, remediation, and policies stay aligned with the Entra ID group structure
The result: consistent targeting without manual updates or duplicated logic.
Built for Enterprise and MSP Scenarios
The connector supports flexible configuration models designed for real-world environments:
· One Entra tenant → multiple Action1 organizations
· Multiple Entra tenants → multiple Action1 organizations
Each Entra tenant acts as a data source, while one or more Action1 organizations act as targets. To avoid ambiguity, each Action1 organization can be associated with only one Entra tenant.
Custom attribute mapping can be shared across organizations or defined individually per organization or scope. This allows teams to adapt the integration to their naming conventions and automation strategy.
Entra ID Groups Action1 Connector
Why This Matters
By bringing Entra ID device group data into Action1, customers can:
· Drive automation from identity instead of static inventories
· Keep endpoint targeting aligned with Intune and Entra ID structures
· Reduce manual effort and configuration drift
For organizations that rely on Entra ID as their identity backbone, this connector makes Action1 a natural extension of their cloud-first ecosystem.
