Everything you need to assess SharedConX before talking to anyone: supported versions, server specs, required permissions, data handling, and failure behaviour.
Exchange: Exchange Online / Microsoft 365 · Exchange Server 2019 / SE, on-premises · Hybrid deployments
Outlook: Outlook for Windows 2016 / 2019 / 365 · New Outlook: yes · Outlook on the web: yes · Outlook for Mac: no
Directory: Active Directory 2019 / 2022 / 2025 · Entra ID: yes
| Requirement | Value |
|---|---|
| Operating system | Windows Server 2019 or later |
| CPU / RAM / Disk | 2 Cores / 8 GB / 1 GB |
| PowerShell | Version 5.1 |
| Database | no extra Database needed |
A dedicated server isn’t required — the Manager can run alongside existing services.
Deployed via MSI. Installation is silent and requires no user interaction.
Security teams ask about this before anything else, so here it is up front.
| Scope | Permission | Purpose |
|---|---|---|
| Exchange | Recipient Management role | Reading and setting mailbox permissions |
| Active Directory | Read on group objects | Detecting membership changes |
| Local server | Log on as a service | Running the Core service |
SharedConX does not require Domain Admin.
SharedConX stores its configuration in the Windows Registry on the Manager server. There is no separate database, and no customer data — mailbox contents, user data, permission records — is stored outside your environment.
No data leaves your network. SharedConX connects only to your own infrastructure: your Active Directory and your Exchange environment. For Exchange Online and hybrid deployments, this includes your own Microsoft 365 tenant — the same connection your administrators use. There is no vendor cloud, no telemetry, and no external service involved in operation. Licence validation works offline.
Every permission change is logged continuously, giving you a complete, uninterrupted audit trail from the moment of deployment. Logs are stored on the Manager server and retained without automatic deletion — retention is under your control.
| Phase | Typical duration |
|---|---|
| Environment analysis | 30 min |
| Manager installation | 30 min |
| Client rollout | 30 min |
| Permission cleanup | Depends on environment |
| Go-live | Depends on customer |
Production mail flow is unaffected throughout.
If the SharedConX Manager service stops, nothing changes. Existing permissions stay in place, mapped mailboxes stay mapped, and users keep working — Outlook has no runtime dependency on the Manager.
The Manager is only involved when configuration changes. While the service is down, those changes simply aren’t processed yet. Once the service is running again, it picks up the current group state and applies whatever is pending.
There is no scenario in which a Manager outage removes access or unmounts mailboxes.