Deploy contacts to iPhones in Hexnode when .vcf import is not availableSolved

Participant
Discussion
5 days ago Jul 17, 2026

I’m trying to deploy a contacts file to iPhones through Hexnode. The import contacts option looks like it only supports Android devices, and I don’t see the same .vcf import workflow for iOS. Is there a way to push contacts to iPhones from Hexnode, or does iOS need a different setup?

Replies (3)

Marked SolutionPending Review
Hexnode Expert
5 days ago Jul 17, 2026
Marked SolutionPending Review

Hello ,

For iOS devices, Hexnode UEM does not support direct .vcf contact file import in the same way as Android.

The recommended method is to deploy contacts using a CardDAV configuration through an iOS policy. CardDAV lets iPhones sync contacts from a compatible contacts server, such as a hosted provider or an internal organizational contacts server.

You can configure this from an iOS policy by adding the CardDAV account details, including the server address, account information, and other required settings. Once the policy is associated with the device, the CardDAV account is pushed to the iPhone and contacts are synced from that server.

Contacts deployed this way are managed. If the policy is removed or the device is disenrolled, the managed CardDAV account and its contacts are removed from the device as well.

Regards,
Simon Scott
Hexnode UEM

Marked SolutionPending Review
Participant
5 days ago Jul 17, 2026
Marked SolutionPending Review

Oh, okay but where do I get the IP address or FQDN for the CardDAV server? Is that something Hexnode provides?

Marked SolutionPending Review
Hexnode Expert
4 days ago Jul 17, 2026
Marked SolutionPending Review

Hexnode UEM does not host the CardDAV server or generate the server FQDN.

The CardDAV server address must come from the service or system that hosts your contacts. For example, it may be provided by your contacts provider, cloud directory/contact service, or your organization’s internal server administrator.

Once you have the CardDAV server details, you can add them to the iOS policy and deploy it to the required devices.

Save