A cloud-based identity and access management service for securing user authentication and resource access
Error 0x80070643 during installation of the Microsoft Entra Provisioning Agent usually indicates that the MSI could not complete because the Windows service account for the agent could not be created or started, or because a previous/partial installation is blocking setup.
Based on the documented agent issues, focus on these areas:
- Verify prerequisites
- Ensure all prerequisites for Microsoft Entra Connect cloud sync are met on the Windows 10 machine, including TLS 1.2 and required components. The provisioning agent setup assumes these are in place.
- Check for previous/partial agent installations
- Open Services.msc and look for:
- Microsoft Entra Provisioning Agent
- Microsoft Entra Connect Agent Updater
- If they exist but are not running or are stuck in Starting, this can cause MSI failures. In that case:
- Uninstall any existing Microsoft Entra Provisioning Agent from Apps & Features.
- Confirm the services are removed.
- Reboot and then rerun the installer.
- Open Services.msc and look for:
- Group Policy / “log on as a service” rights
- The installer creates a local service account
NT SERVICE\AADConnectProvisioningAgentand grants it Log on as a service. If local or domain Group Policy prevents this, the service cannot start and the MSI fails. - On the machine:
- Run secpol.msc → Local Policies → User Rights Assignment → Log on as a service.
- Ensure the entry
NT SERVICE\ALL SERVICESis present. If it is missing, add it and apply policy.
- If the policy is controlled by a domain GPO, adjust the GPO so that
NT SERVICE\ALL SERVICES(or at least the agent service account) is allowed.
- The installer creates a local service account
- Manually set the service logon account (if the service is created but fails to start)
- If the MSI gets far enough to create the service but it fails to start:
- Open Services.msc.
- Open Microsoft Entra Provisioning Agent → Log On tab.
- Change This account to a domain administrator account.
- Apply and start the service, then rerun the installer if it rolled back.
- If the MSI gets far enough to create the service but it fails to start:
- Domain controller / policy considerations
- If this Windows 10 machine is a domain controller or has DC-like policies applied, the same restrictions that affect DC installations can apply (for example, policies blocking local service accounts). In such cases, either:
- Relax the policy to allow the service account as above, or
- Install the provisioning agent on a non‑DC server that meets the prerequisites.
- If this Windows 10 machine is a domain controller or has DC-like policies applied, the same restrictions that affect DC installations can apply (for example, policies blocking local service accounts). In such cases, either:
- Review the detailed MSI log
- In addition to the bootstrapper log you already have, review the MSI log for
Microsoft.SCIM.Provisioning.Setup.msifor entries about:- Failure to grant Log on as a service
- Failure to start
AADConnectProvisioningAgent
- These messages typically confirm that policy or service‑startup issues are the root cause.
- In addition to the bootstrapper log you already have, review the MSI log for
After ensuring prerequisites are met, removing any stale installation, and confirming NT SERVICE\\ALL SERVICES has Log on as a service rights (or assigning a domain admin account to the service), rerun the provisioning agent installer; in the documented cases, the wizard then completes successfully.
References:
- Microsoft Entra Hybrid Sync Agent Installation Issues - No privileges to install MSI
- Microsoft Entra Hybrid Sync Agent Installation Issues - Cannot start service AADConnectProvisioningAgent
- Microsoft Entra Hybrid Sync Agent Installation Issues
- Configure Workday for automatic user provisioning with Microsoft Entra ID
- Cloud sync troubleshooting
- Install the Microsoft Entra provisioning Agent by using a CLI and PowerShell