En
Identity
Planned Q3Entra ID
User management, group membership, license assignment, sign-in logs, and conditional access policy review.
20 toolsOAuth2Graph API
Identity
Entra ID connector detail.
Entra ID is planned for the MSPlex Q3 launch wave covering identity management, licenses, sign-in logs, and access policy review. Use this page to understand the connector posture, the operational surface it is meant to support, and how it should be evaluated inside a broader MSPlex rollout.
Connector snapshot
The detail page should make fit and readiness legible.
Core capabilities
- User and group management
- License assignment
- Sign-in log visibility
- Conditional access policy review
Operational posture
Judge the connector by workflow depth, not logo count.
Operational surface
Entra ID is treated as a identity surface inside MSPlex, so workflows are framed around how operators actually use it rather than around generic API access.
Auth and boundary
This connector is planned around OAuth2 with the tenant boundary enforced by the exchange layer instead of by ad hoc scripts or agent-local credentials.
Execution model
The current connector posture is graph api, with capabilities oriented around production workflows instead of one-off demo calls.
Evaluation rules
Use connector detail pages to keep rollout conversations realistic.
01
Confirm the workflow fit
Use the connector review to map Entra ID to the exact MSP workflows you want AI to support first, not just to the product name itself.
02
Review current versus planned state
Entra ID is currently labeled Planned Q3. Keep that distinction explicit when discussing rollout timing or readiness.
03
Pair detail with exchange posture
The connector only makes sense as part of the wider MSPlex gateway model, where auth, routing, and tenant proof stay governed together.
Review next
Keep connector detail connected to the rest of the system.
Use with
Related connectors
Need this connector mapped to your rollout plan?
Bring the workflows you need first, the systems they touch, and how close those workflows need to be to the current connector build.