FAQ
Answers to the questions AOH Sync administrators ask most often.
General
What does AOH Sync do?
AOH Sync shows you where HR and your directories disagree: accounts that match no person in HR, and service accounts with no owner. When you're ready, it can also keep Active Directory and Microsoft Entra ID (formerly Azure Active Directory) in step with HR as people join, change roles, and leave.
What HR systems does AOH Sync support?
AOH Sync connects to HR systems through a Connector: through the HR system's API, a database connection, a CSV file (uploaded or over SFTP), or an LDAP directory. Any HR system that can provide its people through one of these can be connected. See Step 6 — Connect a Source System. Contact support for a specific compatibility question.
What is the target identity system?
AOH Sync writes user accounts and their attributes to Active Directory and Microsoft Entra ID through Microsoft's API-driven provisioning. For hybrid users, it writes to Active Directory, and Microsoft Entra Connect Sync or Cloud Sync carries the change to Entra ID. It also manages group memberships in Entra ID.
Does AOH Sync replace Entra ID or Microsoft Entra Connect?
No. AOH Sync is not an identity provider and does not replace Microsoft Entra Connect. It works alongside Connect Sync or Cloud Sync: for hybrid users, AOH Sync writes to Active Directory, and your sync tool carries the change to Entra ID. Your existing Entra ID policies, MFA settings, and conditional access rules remain in effect.
Authentication & access
How do I log in to AOH Sync?
AOH Sync uses your organization's Entra ID for authentication — there are no separate AOH Sync credentials. Go to your AOH Sync URL and click Sign in with Microsoft. Complete any MFA prompt your organization requires.
I see "Access Denied" when I try to log in. What should I do?
This usually means one of three things: you have not been granted an AOH Sync role, you are signing in with a personal Microsoft account instead of your work account, or your session has expired. Ask your AOH Sync Administrator to check your access under Administration → Access Management. See Access Management for details on roles.
Why can I not see a particular feature?
AOH Sync uses role-based access control. The features visible to you depend on the role your Administrator has assigned. Roles are described in Roles & Permissions.
Sync behavior
How often does AOH Sync sync data?
Sync frequency is configured per Connector. Most organizations run an incremental Sync on a schedule (commonly every 15–60 minutes) and a full Sync nightly. You can also trigger a Sync manually at any time. See Connector Schedule for configuration details.
What triggers a sync?
A Sync runs when the schedule fires or when you click Run Now in the Connector view. Schedules are configured in Connectors → your Connector → Schedule.
Why was a user skipped during sync?
AOH Sync skips a record when required fields are missing (email address, first name, last name, or employee ID), when the record matches an exclusion rule, or when no changes are detected since the last Sync. The Sync log in Connectors → your Connector → Sync History shows the reason for each skipped record.
Can I edit user data directly in AOH Sync?
No. Changes belong in the system you treat as the source of truth: usually HR, sometimes IT. When sources disagree, the source priority you set decides which value wins (see The Identity Dataplane). AOH Sync carries the change to Active Directory or Entra ID on the next Sync.
What data does AOH Sync read from my HR system?
AOH Sync uses the identity attributes you map: typically names, work email, employee ID, department, job title, manager reference, location, and employment dates. It can read whatever its HR credential or file can reach, so give it a credential or export limited to identity fields, without salary, compensation, or personal addresses. The exact fields synced depend on your Connector's Field Mapping configuration.
Groups & memberships
How are users assigned to Entra ID groups?
Group membership rules are defined in your Connector's Field Mappings configuration. Rules match HR attributes (such as department or job title) to Entra ID groups. When an employee's attributes change, AOH Sync updates their group memberships on the next Sync.
A user is not in the right group. What should I check?
First confirm the employee's attributes in your HR system are correct. Then check whether the relevant group rule in AOH Sync matches those attributes. Most group discrepancies trace back to an HR record that does not yet match the rule criteria, or to a Sync that has not run since the HR change.
Can I manually add a user to a group that AOH Sync manages?
Manual changes to Entra ID groups managed by AOH Sync will be overwritten on the next Sync. If you need a user in a group for a reason not captured in HR, ask your Administrator to create a rule that covers the case, or exclude that group from AOH Sync management.
Data & security
Where is my data stored?
AOH Sync is deployed as a single-tenant virtual machine in your own Azure subscription. Identity data flows through your instance and is written to Entra ID; it is not stored in any shared or third-party system. See Where Your Data Lives for full details.
Is data encrypted?
Yes. All data in transit uses TLS. Credentials and secrets are stored in AOH Sync's built-in Vault, which is part of your deployment and runs entirely within your Azure subscription. See Encryption.
What permissions does AOH Sync hold in Entra ID?
AOH Sync uses two credentials that you create and control: an App Registration for admin sign-in, and a provisioning credential. Microsoft Entra Permissions Requested lists both: the sign-in permissions and the provisioning permissions.
Who can see my data?
Access to AOH Sync is controlled entirely by your Administrator through role assignments. All actions are recorded in the Audit Log. See Audit & Status Logs.
Errors & failures
What happens when a sync fails?
Failed records are isolated — they do not block the rest of the Sync. Each failure is logged with a reason code. AOH Sync retries failed records on the next scheduled Sync. You can see failures on the Dashboard and drill into details in the Connector's Sync History.
What do common error messages mean?
See Troubleshooting for a list of common symptoms and how to resolve them.
Related
Last updated