Microsoft Entra: Retiring Microsoft Entra Connect Sync versions earlier than 2.5.79.0 on September 30, 2026

Introduction As previously announced in MC1160190, we will retire Microsoft Entra Connect Sync versions earlier than 2.5.79.0 on September 30, 2026.This retirement aligns with ongoing security and reliability improvements, including a May 2025 back-end service hardening update that requires customers to run supported versions to maintain synchronization continuity. When this will happen This change will take effect on September 30, 2026. How this affects your organization Our service telemetry indicates your tenant may be using a version of Microsoft Entra Connect Sync that will be affected by this back-end service change. Who is affected Organizations running Microsoft Entra Connect Sync versions earlier than 2.5.79.0. What will happen This is a breaking change: tenants running versions earlier than 2.5.79.0 will no longer be able to run synchronization services after September 30, 2026. After this date, synchronization services on unsupported versions will stop working until your organization upgrades. Versions older than Microsoft Entra Connect V2 remain retired, and in‑place upgrades from DirSync or Azure AD Sync are not supported; these require a swing migration. The Connect Sync installer is only available through the Microsoft Entra admin center. Supported Connect Sync versions and tenants using Microsoft Entra Cloud Sync are not affected. What you can do to prepare Upgrade to maintain synchronization Upgrade to version 2.5.79.0 or later before September 30, 2026. Verify minimum requirements:.NET Framework 4.7.2 TLS 1.2 Select the appropriate upgrade method Auto‑upgrade (where supported). If your environment is eligible and you prefer this option, ensure that auto-upgrade is enabled. Automatic upgrade for express installations In‑place upgrade for single-server environments with fewer than ~100k objects Swing migration (recommended) for older 1.x deployments, servers not updated in 12–18 months, OS upgrades, or any scenario involving DirSync or Azure AD Sync Decommission old servers Fully remove old Connect Sync servers to prevent outdated “rogue” servers from overwriting directory data. Evaluate Microsoft Entra Cloud Sync (optional) If you prefer a cloud-managed synchronization approach, Microsoft Entra Cloud Sync: Uses lightweight provisioning agents with cloud-managed configuration. Supports multi‑forest and disconnected‑forest AD environments. Supports multiple active agents for high availability. Does not change or override your existing authentication method (PHS, PTA, federation). Cloud Sync provides synchronization only, not authentication. Use the supported sync scenarios evaluation tool to determine if Cloud Sync meets your organization’s provisioning needs. Prepare internal teams Notify identity administrators and helpdesk teams about the retirement and required upgrade. Update internal documentation and operational runbooks. Review the Microsoft Entra Connect Sync release version history to confirm the latest supported version. Documentation and resources: Download .NET Framework 4.7.2 | .NET Framework | Microsoft General Availability - Dedicated new 1st party resource application to enable AD to Microsoft Entra ID sync using Microsoft Entra Connect Sync or Cloud Sync | Microsoft Entra | Microsoft Learn Hardening update to Microsoft Entra Connect Sync | Hybrid | Microsoft Entra ID | Microsoft Entra | Microsoft Learn Microsoft Entra Connect: Automatic upgrade | Hybrid | Microsoft Entra ID | Microsoft Entra | Microsoft Learn Microsoft Entra Connect: Upgrade from a previous version to the latest | Hybrid | Microsoft Entra ID | Microsoft Entra | Microsoft Learn Microsoft Entra Connect: Version release history | Hybrid | Microsoft Entra ID | Microsoft Entra | Microsoft Learn TLS 1.2 enforcement for Microsoft Entra Connect | Hybrid | Microsoft Entra ID | Microsoft Entra | Microsoft Learn What is Microsoft Entra Cloud Sync? | Hybrid | Microsoft Entra ID | Microsoft Entra | Microsoft Learn Compliance considerations No compliance considerations identified. Review as appropriate for your organization.