Do Samsung Android Enterprise devices need Samsung accounts for app access?Solved

Yes @oliver_p , Microsoft Entra ID with Android Enterprise is a standard setup for managed Samsung devices.

For daily corporate use, end users generally do not need Samsung accounts on fully managed Android Enterprise devices. In this setup:

1. Apps are deployed through Managed Google Play from Hexnode UEM. Android Enterprise uses managed enterprise accounts in the background, so users do not need to add personal Google accounts or Samsung accounts just to receive apps.
2. Users sign in directly to work apps such as Outlook, Teams, or other corporate apps using their Microsoft Entra ID credentials.
3. Hexnode UEM handles app deployment, restrictions, and device management through Android Enterprise.

A Samsung account is usually required only in specific cases, such as:

• IT admins using Samsung Knox Mobile Enrollment for zero-touch provisioning.
• End users who need Samsung-native services such as Galaxy Store, Samsung Pass, or other Samsung account-dependent apps.

If your workers only use corporate apps, Microsoft Entra ID should be enough. If they need Samsung-native services, you can allow Samsung account sign-in on the devices and have users create or sign in with a company email address, depending on your organization’s account policy.

Regards,
Isabel Lora
Hexnode UEM

That helps. The access message seems to appear mostly when they try to open Samsung-specific stuff, not regular work apps. So if they need Galaxy Store or Samsung Pass, we should allow Samsung accounts?

Correct. If the issue is limited to Samsung-native services, those services may require a Samsung account regardless of Microsoft Entra ID.

In that case, review the Android restriction policy applied through Hexnode UEM. If account addition or Samsung account sign-in is restricted, users may see access issues when opening Samsung apps that depend on a Samsung account.

The practical approach is:

1. Keep Microsoft Entra ID as the main identity provider for corporate app authentication.
2. Continue deploying apps through Managed Google Play from Hexnode UEM.
3. Allow Samsung account sign-in only if Samsung-native services are required.
4. Use company email addresses for Samsung accounts if your organization wants the accounts to remain work-related.

This does not mean every managed Samsung device must have a Samsung account. It is only needed when the workflow depends on Samsung-specific services.

Regards,
Isabel Lora
Hexnode UEM