Schoggi Can't say for sure until you use it. It does seem the company does not enforce certain OS'es (Play Integrity API) - as you already succeeded with LineageOS - so that's a good sign.

    aerosola That's what I did but even so with the portal not fully initialized the apps that are normally available will not proceed, behave like you are on your main profile.

      r3g_5z I read on one of the dev's replies (unfortunately did a quick search and couldn't find it - if I came across of that reply again will post it here) that supporting enterprise software was not a priority hence why what I wrote.

        r3g_5z GrapheneOS developers have never said this, please do not make assumptions.

        Here Daniel mention:

        This isn't planned since we don't see the work profile feature as having much of a place in GrapheneOS over the long term. It's not meant for how people are using it. We're focused on user profiles.

        In other words we are not very keen to put time and effort on work profiles / enterprise software that are for remote management since our focus is on user profiles. In my view GrapheneOS is all about enterprise user since it's my perception the majority using it are nerds... not the common user.

            burningfeelings From your quote:

            It's not meant for how people are using it.

            What that means is that people will often user the work profile with apps like Insular or Shelter to try and isolate their apps to a different profile. For that use case, user profiles are indeed the way to go.

            The way you are supposed to use work profiles is for enterprise etc. I don't believe that GrapheneOS intends to neglect the proper usage of work profiles.

                matchboxbananasynergy I don't believe that GrapheneOS intends to neglect the proper usage of work profiles.

                Hope you are right. Its the only thing I'm missing for a full switch.

                  3 months later

                  Hi guys

                  Just checking if this has moved on at all.

                  I'm in the same boat. My employer expects a certified OS via play integrity when trying to create the work profile via the intune app (I'm assuming this based on the detail above as I get the same experience, I just can't seem to get past the creation of a work profile from my main profile.)

                  Is it looking for a privileged set of Google apps to allow it to meet these specifications? Or does it look / check for other parameters?

                  It's the only thing missing for me to make a full switch. Absolutely loved the OS but I do really need my work apps to work

                  Don't want a 2nd device. It's mainly really for teams and outlook

                  Thanks! ☺️

                  • de0u replied to this.

                    graphenegrotto If your employer requires an OS certified by Google and Google hasn't certified GrapheneOS then that is an impasse, and not one that is likely to "move".

                    Your employer could choose to add GrapheneOS to their list of certified OS signers.

                    But fundamentally if they require a phone running the stock Google or Samsung OS you will likely need a phone running the stock Google or Samsung OS.

                    • de0u replied to this.

                        Thanks. I actually may have found who can look at this to add graphene as a certified OS. I'll give it a whirl and let you know how I get on. Thanks.

                        • de0u replied to this.

                          graphenegrotto You might want to collect some favorable press mentions of GrapheneOS to share with your security decision-maker. Also, the fact that there is now a foundation might help.

                          Good luck (from all of us, I suspect) and let us know how it goes! Each win in this space will make others easier.

                              I guess I am lucky in this regard, in that the mere presence of the Intune app is sufficient for me to be able to use the Outlook app with my corporate email. It does require Intune to be installed, but not logged in. It did a check upon first login to Outlook and the device passed all the checks. Intune and Outlook are now resting in a secondary user profile.

                              de0u just a further query

                              If I did build this myself using the build guide. Would / Should the verifiedBootKey still match one of the official GrapheneOS verified boot keys, for the selfsigned case?

                              • de0u replied to this.

                                  graphenegrotto If I did build this myself using the build guide. Would / Should the verifiedBootKey still match one of the official GrapheneOS verified boot keys, for the selfsigned case?

                                  To quote the GrapheneOS build guide:

                                  The signing process for release builds is done after completing builds and replaces the dm-verity trees, apk signatures, etc. and can only be reproduced with access to the same private keys

                                  The guide suggests that if you don't generate your own signing keys then the build process will use the public Android test key (I haven't looked). Perhaps your security admin could temporarily enable the public test key as a root for verified boot? Or you could generate your own, which would need to be trusted by your admin.

                                  Please note that I am super not an expert! You may be better off on the Matrix channel. I'd suggest you begin with the goal, something like, "I am trying to convince my employer's security admin to configure MS InTune to trust official GrapheneOS builds, but I'm not confident I know the exact steps to request...".

                                  Also note that if you do sign your own build then you must disable the automatic update client, because the official OTA images it fetches won't match your signing key, so you will uselessly load the update server.

                                  Good luck, and keep us posted!

                                    a month later

                                    So I spoke to my lead who looks after MDM / device enrolment, in short, this wont be supported, we are very large organisation, im just one person trying to get my work apps going / playing nicely with Intune and GrapheneOS :)

                                    The response was, that this lies with the OS creators / maintainers to make this work with GMS.
                                    The aim of Graphene is security, the aim of MDM is external control, and both are exclusive.

                                    Our MDM solution is Microsofts Intune. Documentation / guidance on 'byod personally owned devices with a work profile':- is below (it needs GMS)

                                    https://learn.microsoft.com/en-us/mem/intune/fundamentals/deployment-guide-enrollment-android#byod-android-enterprise-personally-owned-devices-with-a-work-profile

                                    Guidance is not to use AOSP in this scenario:-

                                    https://learn.microsoft.com/en-us/mem/intune/fundamentals/deployment-guide-enrollment-android#android-open-source-project

                                    This is the same case as with Mobileiron being discussed here:-

                                    https://discuss.grapheneos.org/d/4346-grapheneos-and-mobileiron/5

                                    I gave it a shot, so if the devs read this, I hope there is a way of getting this to work with GrapheneOS's play services at some point in the future, it really would be the most complete OS and experience for me to get thids working together, but, if its genuinly exclusive and neither will budge, then its back to me as to what I choose :)

                                    Thanks again

                                    • de0u replied to this.

                                      graphenegrotto Thanks for reporting back, and thanks for the links! Too bad it didn't work out.

                                        4 months later

                                        aerosola THANK YOU for these instructions! This worked for me in my GrapheneOS Pixel 6 with my organization's O365!

                                          aerosola

                                          Worked great on latest GrapheneOS and MS Apps as of 9/14/2033.

                                          I will miss the calendar widget but will look to find a DavX workaround.

                                            2 months later

                                            Hi all
                                            I finally manage to switch to GrapheneOS on a pixel 6a - all works fine. Except now for corporate purposes I need to install MS Intune.
                                            I was able to download, install and run it, however, after initiating work profile creation, intunes just does not respond.
                                            When exiting the app actually disappears from home screen and I need to open it via app list. I can see a workprofile loaded but does not appear to really be activated, so I remove it again and re-tried the process.
                                            On the admin portal of intune, the device does not appear so it seems that the installation/activation of work profile did not complete.
                                            I have tried all the andvises given on this forum:

                                            1. Shelter
                                            2. Download via Playstore or Aurora
                                            3. Download APK Intune for Android directly as suggested by Microsoft
                                            4. Checked that comliance requirements are all set (anyway I dont actually get to the step where intunes checks for non-compliance)
                                            5. tried all the little adjustments to system, like spawning disbled, native code debugging etc.

                                            Does anyone have another thought on this? I really want to avoid having to kill my GrapheneOS experiment (note: dont want an additonal/new device, I want to make GrapheneOS work with Intune as intended if possible). It seems that others have made Intune work on their GrapheneOS, but I am not sure how.

                                            Thank you sooo much for any help

                                              4 months later