Security & Compliance

    Entra Connect checked, hardened and kept current.

    To keep Entra Connect syncing Active Directory and Microsoft 365 securely, we check server, accounts and synchronisation, harden them, keep the version current and report sync errors, as a one-off or monthly.

    For IT teams whose accounts sync from the on-premises Active Directory into Microsoft 365 through Entra Connect.

    • Microsoft Entra Connect
    • Entra Cloud Sync
    • Entra Connect Health
    • Password hash synchronisation
    • Windows Server 2025
    • Defender for Identity
    In front of the Landwasser Viaduct, with a red train crossing, two people on a bench check the sync from server to cloud on a laptop, a bag with the CNEXT logo beside them
    01

    The server everyone forgot

    The Entra Connect server has run for five years on a Windows Server 2016 next to the file server, with the version from the year of installation and a service account whose password sits in an Excel list. On the day of the analysis the report says: version out of support, server belongs in Tier 0 and sits among the ordinary servers, TLS 1.0 active, no alert on sync errors, no staging server. The plan of measures: a new Tier 0 server on Windows Server 2025, Entra Connect in the current version with automatic upgrade, accounts as group managed service accounts, a staging server for failover, Connect Health with alerts to your IT. Three weeks later the new server synchronises, the old one is switched off, and the first monthly report shows zero errors.

    02

    Check, harden, update, monitor

    Entra Connect holds rights on both sides: it reads your whole directory and writes to Entra ID. Whoever takes over the server takes over both. So we treat it like a domain controller: its own tier, a hardened operating system, a current version, monitored synchronisation. Where Microsoft Entra Cloud Sync meets your requirements, we assess the move to the lighter agent.

    • Server and accountsOperating system, patch level, Tier 0 assignment, local admins, the AD connector account with the rights it actually needs and the Entra account for synchronisation.Result: a server that runs Entra Connect only, with admin rights only for the people who need them.
    • Version and upgradeComparison with Microsoft's version history, upgrade through a staging server, automatic upgrade enabled where it fits, TLS 1.2 enforced.Result: a supported version, and the next version change runs as planned.
    • Synchronisation rulesWhich organisational units and attributes are synchronised, custom rules, filters for service and admin accounts that never belong in the cloud, password hash synchronisation and accidental deletion prevention.Result: Entra ID receives what belongs there, and a deletion run with a thousand accounts stops before the damage.
    • Sign-in methodPassword hash synchronisation, pass-through authentication or federation; retiring ADFS where it only serves Microsoft 365 any more; seamless single sign-on with a rotated computer account.Result: a sign-in path your IT can explain, and one federation service fewer.
    • MonitoringMicrosoft Entra Connect Health with alerts for sync errors and outages, Defender for Identity on the server, export errors in the monthly report.Result: a stalled sync service catches your eye before a new colleague stands there without an account on day one.
    • Patching as a serviceEvery month we check version, certificates, service accounts and errors, install updates for Windows and Entra Connect in the maintenance window and test staging and rollback.Result: one log per month with every change, its date and the re-test.
    03

    What we need before the first step

    Access to the Entra Connect server and to the Entra admin center with the Hybrid Identity Administrator and Global Reader roles for the analysis, a maintenance window and one person in your IT who sets up the staging server with us and approves changes. Plus the answers to three questions: which accounts may go to the cloud, how your people sign in today, and who receives the alert when synchronisation stops.

    04

    What you hold at the end

    A findings report on server, accounts, version, rules and sign-in path with a severity per finding, a plan of measures with owners and deadlines and, after implementation, a hardened server in the current version with staging server, alerts and documented rules. As a monthly service: updates in the maintenance window, checks of certificates, accounts and errors, a monthly report with patch log and a contact at CNEXT for changes to the directory.

    What you receive from us

    The documents we work with.

    The findings report shows where the server stands, the plan of measures moves it into Tier 0 and onto the current version, and the monthly report records with its patch log what changed each month.

    Findings report

    Sample

    Entra Connect findings report

    Customer
    Muster AG, Bern (fictional)
    Server
    SRV-AADC01, Windows Server 2016, Entra Connect 2.1.20.0
    Analysed on
    15 October 2026
    Sign-in method
    Password hash synchronisation, seamless SSO
    • 2critical findings
    • 4high findings
    • 5medium findings
    • 0staging servers

    Summary

    Synchronisation runs without errors, but on a version Microsoft has not supported since 2024, on a server shared with the file service where eight people hold local admin rights. There is no staging server and no alert when the service stops. The sign-in method is the right choice and stays.

    No.FindingSeverityRecommendation
    EC-01Entra Connect 2.1.20.0, retired by Microsoft; mandatory upgrade to 2.6.84.0 or later by 7 April 2027CriticalNew server with the current version, swing migration through staging
    EC-02Server shares the operating system with the file service; 8 local adminsCriticalDedicated Tier 0 server, two named admins
    EC-03No staging server, no rehearsed failoverHighSecond server in staging mode, switch-over rehearsed
    EC-04No alert on sync errors or stallsHighConnect Health with alerts to the IT mailbox and a Teams channel
    EC-05TLS 1.0 and 1.1 active on the serverHighEnforce TLS 1.2, with the upgrade
    EC-07Accidental deletion threshold at the default 500, with 184 usersMediumSet to 40 objects

    Synchronisation rules

    • The OUs Users, Groups and Devices are synchronised; the OU Service Accounts is filtered. Three admin accounts sit outside it and are synchronised: EC-08, medium.
    • No custom rules. Cloud Sync would be an option for Muster AG; the decision is taken with the plan of measures.

    Next steps

    Review on 22 October 2026 with the decision Entra Connect or Cloud Sync; then the plan of measures.

    Samples with invented details for a fictional Muster AG.

    Sound familiar? Tell us where you stand today.

    Contact

    What's new.

    As of: 30 October 2026

    • As of 30 October 2026

      Entra Connect Sync 2.6.92.0 is current; an upgrade is mandatory by 7 April 2027.

      Every 2.x version retires twelve months after a newer one is released; versions before 2.5.190.0 are already out of support, and 1.x no longer synchronises. By 7 April 2027 every installation must run version 2.6.84.0 or later with application-based authentication, or synchronisation stops working.

      Source: Microsoft Learn: Entra Connect version release history
    • As of 21 October 2026

      Entra Cloud Sync is Microsoft's future of synchronisation.

      The lightweight provisioning agent needs only outbound connections and updates itself; Microsoft develops new features primarily for Cloud Sync. Not supported are pass-through authentication, custom synchronisation rules and cross-forest references; the limit is 150,000 objects per domain.

      Source: Microsoft Learn: Entra Connect Sync or Cloud Sync, decision guide
    • As of 10 September 2026

      Connect Health needs Entra ID P1 and Entra Connect 2.5.79.0 or later.

      Connect Health shows alerts, synchronisation errors, performance data and usage for Connect Sync, AD FS and AD DS in the Entra admin center. The feature requires Entra ID P1 licences; the first agent needs one, every further agent 25 more.

      Source: Microsoft Learn: What is Microsoft Entra Connect and Connect Health

    One-off or monthly.

    Analysis and hardening as a project, or the server stays in our care, with updates, checks and a report every month.

    • One-off

      Analysis and hardening as a project

      Findings report, plan of measures, a new or hardened server with staging, current version, alerts and documented rules. Handover to your IT with a guide for the next upgrade.

      Analysis and hardening as a project
    • Monthly

      Entra Connect as a managed service

      Updates for Windows and Entra Connect in the maintenance window, checks of certificates, accounts and errors, re-tests, a monthly report with patch log and a contact at CNEXT. Cancellable after the agreed notice period.

      Entra Connect as a managed service

    Before we touch the server.

    Does sign-in fail while you replace the server?

    No. With password hash synchronisation your people sign in directly to Entra ID; synchronisation can stand still for hours without anyone noticing. The new server first runs in staging mode, we compare its exports with the old one, and only then does the role switch. With ADFS federation we plan the move to password hash synchronisation with you beforehand.

    Entra Connect or Entra Cloud Sync?

    Cloud Sync is the lighter agent and needs no server of its own. It covers most scenarios, but not all: device writeback, certain attribute rules and Exchange hybrid setups still need Entra Connect. Which variant fits you is in the findings report with reasons; Microsoft keeps the differences in a comparison table that we check against your environment.

    Why does the server belong in Tier 0?

    Because the account Entra Connect reads with has access to the whole directory, and the account it writes with changes Entra ID. Whoever has local admin on the server can take over both accounts. So the server follows the same rules as domain controllers: its own admins, no other services, no sign-in with everyday accounts.

    How often does Entra Connect need an update?

    Microsoft publishes new versions several times a year and retires old ones after a period. In the monthly service we check at every appointment whether a new version is available and install it in the maintenance window through the staging server. Which versions Microsoft still supports is listed in the version history the monthly report points to.

    What happens if someone deletes an organisational unit by mistake?

    Accidental deletion prevention stops the export run as soon as more objects would be deleted than the configured threshold allows, and Connect Health reports the stop. Your IT checks what happened, restores the objects and releases the run. We set the threshold with you to match your size.

    Agree on a useful next step

    Tell us about your current workflow, the systems involved and the result you need. In our first conversation, we identify what else we need to know to plan a useful next step.