Forum Discussion
Work profile on S25 Ultra
Just bought a Galaxy S25 Ultra a few weeks ago and unfortunately I'm not able to create a work profile with MS Intune. I've tried all workarounds that I found on Reddit and Samsung community (https://us.community.samsung.com/t5/Galaxy-S25/New-S25-Ultra-Unable-to-setup-work-profile-using-company-portal/td-p/3126410/page/29).
I think that this can be related to some Android Enterprise support because I could not find any reference of the models when searching for it.
Does anyone else are having issues when trying to create a work profile on S25 series?
- Alex_MucLevel 2.3: Gingerbread15 days ago
MichelOut of curiosity: Does Microsoft have KB articles for Intune that provide information about the new OS major release and its dependencies on features and compatibility?
I'm used to articles like this from Omnissa. They describe a few new OS features, from which version onwards business apps are fully compatible and whether there are any known bugs with the OS version. Also in relation to major OEMs such as Samsung.
- MichelLevel 2.3: Gingerbread15 days ago
Not that specific that I'm aware of. Microsoft uses this Learn portal for some of it:
https://learn.microsoft.com/en-us/intune/intune-service/fundamentals/whats-new
But information is scattered across multiple websites from Microsoft. The tech communicatie blogs also point out certain highlights. I think those best fit what you showed from omnissa:
https://techcommunity.microsoft.com/category/microsoftintune/blog/microsoftintuneblog
- MichelLevel 2.3: Gingerbread16 days ago
There was a Microsoft issue which has been resolved this morning (CET)
Users may be unable to complete Mobile Device Management (MDM) enrollment on some Android 15 devices
ID: IT1045821
Issue type: Incident
Status
Service Restored
Impacted services
Microsoft Intune
Details
Title: Users may be unable to complete Mobile Device Management (MDM) enrollment on some Android 15 devices
User impact: Users may have been unable to complete MDM enrollment on some Android 15 devices.
More info: Users may have been blocked by the user experience (UX) when they tried to complete MDM enrollment on Corporate Owned Samsung S25 and A56 devices running Android 15 for Android Enterprise (AE) user based Corporate Owned Business Only (COBO) and Corporate Owned Profile Enrollment (COPE) enrollment scenarios.
Final status: We've confirmed that our fix has fully deployed, and we've verified through service telemetry that this has remediated the issue.
Scope of impact: This issue impacted users who were attempting to complete MDM enrollment on Corporate Owned Samsung S25 and A56 devices running Android 15 for AE user based COBO and COPE enrollment scenarios.
Start time: Monday, February 24, 2025, at 3:51 PM UTC
End time: Wednesday, April 2, 2025, at 10:26 PM UTC
Root cause: A recent Android 15 update introduced changes to the UI, which caused the UX to be blocked in certain scenarios and resulted in impact.
Next steps:
- We're reviewing our Android 15 update processes so we can better identify similar UI issues during our testing and development process and avoid comparable impact in the future.
This is the final update for the event. - Alex_MucLevel 2.3: Gingerbread16 days ago
Is the problem still there for you?
I tested yesterday with a S25 (SM-S931B) and could not find any problems with the Work Profile Enrollment. I tested it with the security patch level from February and March.We use Omnissa WorkspaceONE. However, since the admin apps differ (CustomDPC vs Android Device Policy), there may also be different behavior.
Omnissa had noticed a problem, especially with Custom DPC Enrollment, if the version of Google Play Services (com.google.android.gms) is less than 24.29.00. - LizzieGoogle Community Manager2 months ago
Hey gustavossilvas,
Nice to meet you.
I believe there is a fix for this, but I would recommend speaking with Samsung directly about how to do this specifically for your version.
I hope you get work profile showing on it really soon (and you will be back to using just one phone rather than two) - please keep us posted, if you can.
As a side note, it's cool to hear you have the new S25 ultra, I hope you are enjoying using it (aside from not having work profile at the moment).
- Alex_MucLevel 2.3: Gingerbread2 months ago
You could use the TestDPC to test if creating a work profile generally works on the S25 Ultra. If there are also problems with the TestDPC, the problem does not necessarily have to be with Intune. In the post you shared, some people actually tried this and also had problems with the TestDPC.
The S25 series is not yet listed as ‘Android Enterprise Recommended’, but I wouldn't worry about that. The certification will probably still take some time. And even when Samsung did release devices without ‘Android Enterprise Recommended’ in the past, the devices worked perfectly with Android Enterprise.
I probably will be able to test it with a Galaxy S25 in a week. I really hope that we don't find any major bugs. 😅 However, I am a little sceptical after the many Android 15 delays and news like this. Since Android 16 is already planned for release in Q2/2025, I find the many postponements due to OneUI7 very unfortunate on Samsung's side.
- gustavossilvasLevel 1.5: Cupcake2 months ago
I've installed TestDPC and got the same errors. I think that all we have to do is just wait for some magical updates. If you have any other suggestions, I'll be happy to know.
In the meantime, I'll keep using two phones... 😅
- Alex_MucLevel 2.3: Gingerbread2 months ago
Particularly for such problems, you can use the Knox Admin Portal as a company to create tickets for Samsung. (And ideally, bug reports and the reproduction steps are supplied directly 😁)
But I would bet that someone has already done this and Samsung is working on the problem. 😃
- jasonbaytonLevel 4.0: Ice Cream Sandwich2 months ago
This appears to be an ongoing issue between Intune and Google currently. I don't have links to support tickets or the like to hand, but it has been raised in my other communities more than once.
Related Content
- 2 years ago
- 2 years ago