Findings report
SampleEntra 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. | Finding | Severity | Recommendation |
|---|---|---|---|
| EC-01 | Entra Connect 2.1.20.0, retired by Microsoft; mandatory upgrade to 2.6.84.0 or later by 7 April 2027 | Critical | New server with the current version, swing migration through staging |
| EC-02 | Server shares the operating system with the file service; 8 local admins | Critical | Dedicated Tier 0 server, two named admins |
| EC-03 | No staging server, no rehearsed failover | High | Second server in staging mode, switch-over rehearsed |
| EC-04 | No alert on sync errors or stalls | High | Connect Health with alerts to the IT mailbox and a Teams channel |
| EC-05 | TLS 1.0 and 1.1 active on the server | High | Enforce TLS 1.2, with the upgrade |
| EC-07 | Accidental deletion threshold at the default 500, with 184 users | Medium | Set 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.



