AD & Integration Status
Open the application's integration settings and select a connector. Configure only the scopes and permissions required, test the connection, preview proposed records, and confirm synchronization where supported.
| Integration | Configuration and current status |
|---|---|
| Microsoft Active Directory | Implemented connector: domain-controller LDAP/LDAPS URL, domain, bind username/password, Base DN, filters, scopes, and mappings. The application host must reach the controller. Use an approved directory account and certificate configuration. |
| Microsoft Entra ID | Configuration fields exist for Graph URL, tenant ID, client ID, secret, and scopes. It is not marked implemented in the current registry, so working synchronization is not available. |
| Microsoft Intune | Configuration entry exists, but its connector is not implemented in the current dispatcher. Operational Intune synchronization is not available. |
| Generic REST API integration | Configuration entry exists; a generic working connector is not established in the dispatcher. This is separate from the implemented endpoint check-in API. |
| Endpoint check-in API | Implemented authenticated POST endpoint described above. 401 means invalid token; 503 means the server token is not configured. |
AD integration synchronizes directory records; it does not itself install endpoint software. Domain deployment is separate from LDAP configuration. Do not imply every internal API accepts the discovery token: other endpoints have their own authentication and role requirements.