Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Entra Connect export error 'permission-issue' 8344: 'Insufficient access rights to perform the operation'

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

In Synchronization Service Manager, an on-premises Active Directory connector row with Profile Name Export and Status completed-export-errors can list objects with the error "permission-issue", "Connected data source error code" 8344, and "Connected data source error" "Insufficient access rights to perform the operation." Microsoft's cause is that the connector account, MSOL_<hex-digits> by default, "doesn't have permissions in Active Directory to write back the object's properties that are being synchronized with Microsoft Entra ID."

Find the attribute the export is trying to write, then find out why the connector account cannot write it on that object. Microsoft's pages describe two routes to a missing permission: permissions inheritance is blocked on the container, or the object is a protected account. Granting rights blindly is the wrong first move.

What the error means

Microsoft Entra Connect Sync writes some attributes back to on-premises Active Directory, such as mS-DS-ConsistencyGuid when it is the source anchor, or Exchange hybrid attributes like msDS-ExternalDirectoryObjectID. The error means an export tried to change one of those attributes and Active Directory refused.

Microsoft's permissions page says that for an Express installation an automatically generated account (MSOL_nnnnnnnnnn) is created "with all the necessary permission", and that you do not need the ADSyncConfig module "unless you have blocked permissions inheritance on organizational units or on specific Active Directory objects that you want to synchronize". A custom connector account needs permissions prepared in advance for each feature you enable.

Protected accounts add a second route to the same error. Microsoft's Active Directory documentation describes protected accounts and groups (such as Administrators, Domain Admins, Account Operators and Enterprise Admins) as objects whose permissions "are set and enforced via an automatic process". SDProp runs every 60 minutes by default on the domain controller holding the PDC Emulator, compares permissions on protected objects with the AdminSDHolder object, and resets any that differ. Inheritance is disabled on protected accounts, so a permission you grant at the OU or domain root does not reach them.

Likely causes

Cause What you see How to confirm
Inheritance blocked on an OU or object Errors cluster in one OU or on hand-picked objects Troubleshooting console option 4, then option 2, "Get objects with inheritance disabled", or Get-ADSyncObjectsWithInheritanceDisabled
Synchronised object is a protected account or group member Errors on administrator accounts only Object is in a protected group; permissions reset by SDProp
Feature permissions were never granted (custom connector account) Errors on one attribute for every object Pending Export shows the same attribute each time; the feature's permissions are missing
AdminCount still above zero on a user who left a protected group Permissions not applied to an ordinary-looking user Microsoft lists this as a known issue
SDProp not propagating Error persists after a correct fix Microsoft lists SDProp issues as a known issue
Permissions edited by hand Unexpected errors after manual changes Microsoft warns manual grants "might cause insufficient permissions"

Prove the cause before changing anything

Nothing in this section changes Active Directory.

  1. Identify the connector account. Any of these works: the Microsoft Entra Connect wizard, Configure, View or export current configuration, then the ACCOUNT field under Synchronized Directories; the connector's properties in Synchronization Service Manager (Connect to Active Directory Forest, User name); or PowerShell on the Connect server:

    Get-ADSyncADConnectorAccount
    

    Microsoft also lists Get-ADSyncToolsADconnectorAccount from the ADSyncTools module.

  2. Find the attribute. In Synchronization Service Manager, open Operations, select the connector's Export row with status completed-export-errors, select an object that lists permission-issue, open the Pending Export tab, and sort the Attribute information table by the Changes column. The attribute name there is the permission you need to check.

  3. Identify the feature behind the attribute. Microsoft lists mS-DS-ConsistencyGuid for the source anchor, and the Exchange hybrid writeback attributes such as msDS-ExternalDirectoryObjectID. To list the enabled features, run:

    (Get-ADSyncGlobalSettings).Parameters | select Name, Value | sort Name
    
  4. Check inheritance across the area that holds the failing objects:

    Get-ADSyncObjectsWithInheritanceDisabled -SearchBase '<DistinguishedName>'
    

    By default it looks for OUs only. Add -ObjectClass * to include all object classes, as Microsoft documents.

  5. Read the permissions on one failing object and on one that exports successfully:

    Show-ADSyncADObjectPermissions -ADobjectDN '<DistinguishedName>'
    

    A missing entry for the connector account on the failing object, with the working object having one, points to blocked inheritance or a protected object.

How to read the results: failures across one OU and a disabled-inheritance hit for that OU is the inheritance cause. Failures on administrator accounts alone point to protected accounts. The same attribute failing everywhere points to a missing feature permission.

Fix

Microsoft calls the Entra Connect Troubleshooting console "the recommended and preferred method", and the ADSyncConfig module "also a recommended method". Manual grants through Active Directory Users and Computers or dsacls carry Microsoft's warning that they "might cause insufficient permissions that can lead to unexpected results."

Who can run it. The account running the tool must be able to grant permissions in Active Directory on all domains in the forest, which Microsoft says in practice means Enterprise Administrator rights from the forest root.

Cause: feature permissions missing, or inheritance blocked on an OU. Use the console: open the Microsoft Entra Connect wizard, Configure, Additional tasks, Troubleshoot, Launch, enter 4 (Configure AD DS Connector Account Permissions), choose the permission set that matches the feature (for Exchange hybrid, option 4), choose Existing Connector Account, name the connector, then give the DistinguishedName of the affected OU instead of pressing Enter. Pressing Enter applies the permissions at the root of every domain in the forest, which is broader than needed.

The PowerShell equivalent, with the syntax Microsoft documents:

Set-ADSyncExchangeHybridPermissions -ADConnectorAccountDN '<ConnectorAccountDN>' -ADobjectDN '<OU-DN>'

Other cmdlets follow the same pattern, for example Set-ADSyncMsDsConsistencyGuidPermissions and Set-ADSyncBasicReadPermissions. Microsoft says that with -ADobjectDN, "the cmdlet sets permissions on this object only and not on the domain root or AdminSDHolder container."

Risk: these commands change access control lists in Active Directory. Before running them, record the current permissions with Show-ADSyncADObjectPermissions. There is no one-step undo documented by Microsoft; back out by removing the added entries from the object's security settings, using your recorded copy.

Cause: protected accounts. Microsoft's advice is not to widen AdminSDHolder to suit synchronisation: "Don't synchronize your on-premises AD administrator accounts to Microsoft Entra ID." The cleaner fix is to stop synchronising those accounts. The console asks whether to update the AdminSDHolder container, and Microsoft says to answer Yes "only if you're synchronizing Protected Accounts in Active Directory to Microsoft Entra ID", otherwise No. The ADSyncConfig switch -IncludeAdminSdHolders modifies the AdminSDHolder container, and Microsoft states that "This isn't recommended."

Disruptive step: changing AdminSDHolder changes the template permissions for every protected account and group in the domain, applied by SDProp within about 60 minutes. Back out by removing the entry you added from AdminSDHolder and letting SDProp run again.

Cause: AdminCount or SDProp trouble. Microsoft's known-issues table says neither is fixed by the listed solutions. Escalate these to your Active Directory administrators; they involve the directory itself, not Entra Connect.

Example (illustrative): ad01 serves CONTOSO and Entra Connect runs on aadc01. An export shows 240 objects, and 28 fail with 8344. All 28 are in OU=Finance,DC=contoso,DC=com, and the other 212 (240 - 28) export without error. Pending Export lists msDS-ExternalDirectoryObjectID on each failing object. Get-ADSyncObjectsWithInheritanceDisabled -SearchBase 'DC=contoso,DC=com' lists the Finance OU. The administrator records permissions with Show-ADSyncADObjectPermissions -ADobjectDN 'OU=Finance,DC=contoso,DC=com', then runs the Exchange hybrid permission command with -ADobjectDN set to that OU and the next sync clears the errors.

Confirm the fix

  • Run the next export (or wait for the sync cycle) and open Operations. The Export row should show success, with no permission-issue entries.
  • Re-run Show-ADSyncADObjectPermissions on a formerly failing object and confirm an entry for the connector account.
  • Confirm the attribute value now matches between the connector space and Active Directory.
  • Check that no administrator accounts have been added to the synchronised scope by accident.

What to watch afterwards

  • Record every OU where you block inheritance. Re-run Get-ADSyncObjectsWithInheritanceDisabled after each Active Directory delegation change.
  • Keep a list of which accounts sit in protected groups and keep them out of the synchronised scope, as Microsoft advises.
  • After enabling a new Entra Connect feature, run the matching permission cmdlet first. Microsoft says to prepare permissions in advance.
  • Watch export results after each upgrade of Entra Connect.

Risks and limits

These commands have not been run or lab-tested. The 8344 troubleshooting page is dated 2026-04-23, and the permissions page is dated 2025-04-09; menu wording in your version of the wizard may differ.

Microsoft's page describes a dsacls command that grants read and write on all properties of all descendant objects at the domain root. That is a wide grant, and it is not reproduced here. An error can persist after a correct fix if SDProp or AdminCount is the cause, which these pages list as unresolved by the standard solutions.

Sources