CiraSync On-Prem v15.0.1 introduces CardDAV support, and for IT teams managing mobile fleets, it removes a real source of friction. Here is what the feature does, how the deployment works, and where to get the full setup guide.
TL:DR: CiraSync On-Prem v15.0.1 adds native CardDAV support, letting IT teams push Global Address List contacts to managed iOS and Android devices without the Outlook app or brittle Exchange ActiveSync workarounds. It works through any major MDM platform, including Microsoft Intune, VMware Workspace ONE, MobileIron, SOTI, Jamf, and Mosyle. Deployment covers infrastructure setup, IIS configuration, CSOP configuration, and MDM profile validation. Organizations with large mobile fleets, hybrid Exchange environments, or compliance-driven contact management needs benefit most. The full setup guide covers all ten steps.
What CardDAV Support Means for Mobile Contact Delivery
Before CardDAV, delivering corporate contacts to managed mobile devices typically meant relying on the Outlook mobile app or working around limitations in Exchange ActiveSync. Both approaches carry overhead. Outlook requires its own app management and user adoption. Exchange ActiveSync configurations can be brittle, especially in hybrid environments.
CardDAV is a standards-based, HTTP-native protocol built directly into Apple iOS. It does not require a third-party app on iPhone or iPad. For Android, CiraSync provides the CardDAV Direct companion app through Google Play, since Android does not include a complete native CardDAV stack.
With CSOP v15.0.1, organizations can push contacts from the Global Address List directly to managed devices through any major MDM platform, including Microsoft Intune, VMware Workspace ONE, MobileIron, SOTI, Jamf, and Mosyle.
How the Deployment Works
The setup involves ten steps, from upgrading CSOP to validating contact delivery on test devices. At a high level, the process covers four areas.
Infrastructure configuration. A dedicated public DNS hostname points to the CSOP server. A publicly trusted TLS certificate covers that hostname. Port 443 is open inbound and outbound on perimeter firewalls and Windows Firewall.
IIS configuration. A separate IIS website runs the CardDAV endpoint. Two IIS modules, Microsoft Application Request Routing and URL Rewrite, enable the site to function as a reverse proxy in front of the CSOP internal services. A Winsock port reconfiguration in the CSOP Setup Wizard aligns internal service ports with the new routing setup.
CSOP configuration. A new CardDAV collection is created in the CSOP admin portal and assigned as the CardDAV target collection under Sync Options. Mobile Direct is enabled against that collection, and CSOP generates ready-to-deploy configuration profiles for iOS and Android.
MDM deployment and validation. The iOS XML profile and Android managed configuration are pushed through your MDM to the target device groups. Validation covers profile installation status in the MDM console, contact visibility in the native Contacts app, and caller ID resolution across phone, messaging, and CRM apps.
Who Benefits
CardDAV support is most immediately useful for organizations that:
- Manage large iOS and Android fleets through an MDM platform
- Need to deliver Global Address List contacts to mobile devices without requiring Outlook
- Are running hybrid Exchange or are in the process of migrating to Microsoft 365
- Have compliance or governance requirements that call for centralized, auditable contact management without reliance on third-party mobile apps
Get the Full Setup Guide
The complete step-by-step guide covers all ten deployment steps, IIS module installation and configuration, Winsock port mapping, MDM profile deployment for both iOS and Android, and a troubleshooting quick reference table for common issues.
Download the CiraSync On-Prem CardDAV Setup Guide to get started.
For questions or escalations, contact help@cirasync.com.
