Entra Connect 2.6.3.0 Full Import AAD Connector returns "completed-no-objects" - tenant never shows as installed

The behavior described (AAD connector Full Import completing with completed-no-objects and 0 imported objects, while the AD connector imports successfully) matches a connector/engine-side “no data” condition, not a generic connectivity failure. From the available context, the only supported, actionable checks are on the sync engine and connector configuration; backend tenant investigation requires Microsoft Support.

Use the following checks and steps that are documented for “object not syncing” and connector issues:

1. Verify Operations tab status and details
   In Synchronization Service Manager:
   • Open the Operations tab and locate the AAD connector Full Import run.
   • Confirm the status string (for example, completed-no-objects) and check whether any Synchronization Errors or warnings are listed for that run.
   • If there are errors, select the error links to see the object and error details and address those first.
2. Check connector space for AAD connector
   Still in Synchronization Service Manager:
   • Select Connectors, choose the Microsoft Entra (Azure AD) connector, and select Search Connector Space.
   • Use Scope = Pending Import with Add checked to see if any objects are staged but not associated with on-prem objects.
   • If the search returns no objects at all for the AAD connector, this confirms that the import is truly bringing in zero objects.
3. Confirm object and attribute filtering is not excluding everything
   For scenarios where all objects or attributes of a type are missing:
   • Use PowerShell to verify optional app/attribute filtering:

          (Get-ADSyncGlobalSettings).Parameters | where Name -eq 'Microsoft.OptionalFeature.FilterAAD' | select Name, Value
     

   • If Microsoft Entra app and attribute filtering is enabled, review the configuration per Microsoft Entra app and attribute filtering to ensure it is not filtering out all relevant object types or attributes.
4. Confirm AAD connector object types include device (for known import issues)
   There is a documented issue where missing object types (for example, device) on the Microsoft Entra connector cause import problems:
   • In the Sync console (Forefront Identity Manager / Synchronization Service Manager), open the Microsoft Entra connector Properties.
   • Under Connector Design → Select Object Types, verify that device is selected along with user, group, and contact.
   • If device is not selected, select it, click OK three times, and rerun a Full Import.
5. Check for connector configuration corruption after ABA (application-based authentication) changes
   For environments on 2.5.x and later using application-based authentication, opening and saving the Microsoft Entra connector in the legacy UI can clear critical ABA parameters (ApplicationManagedBy, CertificateManagedBy, CertificateId), which can break proper connector behavior:
   • Avoid using Synchronization Service Manager UI to edit the Microsoft Entra connector when ABA is enabled.
   • If this was done, repair the connector parameters using PowerShell on the Entra Connect server:

          [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
          Install-Module ADSyncTools   # or Update-Module ADSyncTools if already installed
          Import-Module ADSyncTools
          Repair-ADSyncToolsEntraAppParameters
     

   • After repair, rerun the Microsoft Entra Connect configuration wizard and then rerun a Full Import on the AAD connector.
6. Run a full sync cycle after any filtering or connector changes
   When domain/OU filtering or connector object/attribute settings are changed, a full import is required for changes to take effect:
   • Run:

          Start-ADSyncSyncCycle -PolicyType Initial
     

   • Then verify the AAD connector Full Import run again in the Operations tab.
7. If all checks succeed but AAD still imports 0 objects
   The provided documentation does not include further tenant-backend diagnostics. If:
   • Operations show completed-no-objects with no errors,
   • Connector space for AAD remains empty, and
   • Filtering, object types (including device), and ABA parameters are all verified and correct,
   then the remaining step is to open a support case with Microsoft, referencing the trace evidence (DirectorySynchronizationEnabled=True, DirectorySynchronizationStatus=Enabled, empty lastDirectorySyncTime, and ImportV2 chunk size 0) so engineering can inspect the tenant-side state.

References:

• Troubleshoot an object that is not synchronizing with Microsoft Entra ID
• Connector space object properties
• Troubleshoot Microsoft Entra Connect Sync application-based authentication
• Microsoft Entra Management Agent hangs during Full Import or Delta Import with error: System.Collections.Generic.KeyNotFoundException
• End-to-end troubleshooting of Microsoft Entra Connect objects and attributes