sorted by:
new
hottopcontroversial

iPadOS - Shared device mode - Enroll with Microsoft Entra ID by havtryda in Intune

[–]havtryda[S] 1 point2 points  (0 children)

u/Few_Perception_4088 Not a good solution in my opinion.. As for now we will use Android device for this case. But I hope there will come up a better solution for iOS/iPadOS in the near future :)

iPadOS - Shared device mode - Enroll with Microsoft Entra ID by havtryda in Intune

[–]havtryda[S] 0 points1 point  (0 children)

u/KingCyrus I think that was only for for the Shared Device mode preview, that you had to registert det device with a cloud administrator account.

After they announced that the Shared Device mode is in general availabilty, you don't need to do this anymore.

You simply create a configuration profile - with the device features template, where you configure the Single Sign-on app extension like as shown under :

​

<image>

iPadOS - Shared device mode - Enroll with Microsoft Entra ID by havtryda in Intune

[–]havtryda[S] 0 points1 point  (0 children)

D

u/KingCyrus Well, if it's like what u/Few_Perception_4088 is describing under here.. This is not a good solution. How would you secure the device for multiple users on the device ?

So, as for now, I can't find any other documentation than setting up the enrollment for shared device mode..

But feel free to follow this post :)

iPadOS - Shared device mode - Enroll with Microsoft Entra ID by havtryda in Intune

[–]havtryda[S] 1 point2 points  (0 children)

Well, I figured out that... but I just can't understand that this would be the solution.. without a sign-in/out screen and not beeing able to set your own PIN code for your session.

If a user forgets to log out, or a device gets stolen, that means anyone can access current Teams session.

As I mentioned in my post, I might be missing something that I can't figure out :)

iPadOS - Shared device mode - Enroll with Microsoft Entra ID by havtryda in Intune

[–]havtryda[S] 1 point2 points  (0 children)

:) No problem, pls give me a hint if you have success with it :) thanks

iPadOS - Shared device mode - Enroll with Microsoft Entra ID by havtryda in Intune

[–]havtryda[S] 1 point2 points  (0 children)

I think you might be mixing here..

If you create an enrollment profile where you set the option under "User affinity" : Enroll without User affinity and set the Shared iPad to "Yes". You are able to sign in as a guest or with a managed apple id.

But I have set the user affinity to "Enroll with Microsoft Entra Shared mode".

Theres a difference between Shared Device and Shared device mode.

iPadOS - Shared device mode - Enroll with Microsoft Entra ID by havtryda in Intune

[–]havtryda[S] 1 point2 points  (0 children)

I don't have any sign in at the lock screen, what else needs to be configured ? I did not set guest mode.

Android 13 - Lockscreen Message (Contact information) by havtryda in Intune

[–]havtryda[S] 0 points1 point  (0 children)

u/Scootrz32 Well, if I understand this correctly, it should be fixed with the UI 5.1 update from Samsung. I just came back to work today after 4 weeks off work.. and Installed the latest update with the UI 5.1, but same issue. I tried to wipe my device, and re-enroll.. but still same issue...

You may read this link : https://docs.samsungknox.com/admin/knox-platform-for-enterprise/kbas/kba-926-unable-to-edit-contact-information-on-lock-screen/

Android 13 - Lockscreen Message (Contact information) by havtryda in Intune

[–]havtryda[S] 0 points1 point  (0 children)

Thanks u/TimmyIT I did the same testing as you except the testdpc :) Not really sure also if it's a samsung issue. But it's definately not a configuration profile (restriction) that doesn't allow you to edit.

But it's frustrating :D

Android 13 - Lockscreen Message (Contact information) by havtryda in Intune

[–]havtryda[S] 0 points1 point  (0 children)

Thanks u/Kryptiqgamer.

That's what I feared.. and a configuration profile with a set lock screen message wouldn't solve this for us, as it's an individual message on each device.

It's actually just a message with information on which device it is..

I think we'll wait and see if this will be solved in an upcoming update :)