In large organizations, digital business cards rarely fail because of the card itself, but because of the rollout: anyone who wants to bring an app or a wallet pass to hundreds of managed company devices can hardly avoid Mobile Device Management (MDM), typically Microsoft Intune in combination with Entra ID (Azure AD). This is exactly where the market has to be assessed honestly: rolling out an app that sits in the App Store or Play Store is handled by the customer's own MDM (Microsoft Intune, Jamf) for any store app whatsoever.
The pure distribution is therefore a property of the operating system and the MDM platform, not a feature of the card provider. The actual, app-side differentiator is Managed App Configuration: whether the app accepts preconfigured settings (such as tenant or SSO) via MDM and thus starts without manual setup.
Precisely this app-side MDM and AppConfig support is publicly undocumented across the entire field and, by our strict standard, stands at "?" for all providers. In this comparison, we show how Intune, Entra ID, SSO, SCIM and Managed App Configuration differ from one another, why the pure distribution is generically possible for any store app, and what IT and data protection officers in the DACH region should pay attention to.
The order (oneVcard, Spreadly, Lemontaps) follows our weighted methodology of enterprise capabilities, GDPR compliance and overall rating; oneVcard is best positioned for an Intune scenario through its documented Microsoft Entra ID/Azure integration (SSO and user provisioning), but the concrete MDM device rollout is publicly undocumented here as well and must be confirmed with the provider before signing a contract.