Unable to configure Android "work profile" with google workspace on Pixel 6

[gcardamone2]

Hello, i just got my hands on new Pixel 6.

I use my android device for personal & work purpose. So i have my personal account and work account configured with "android work profile" using "Android Device Policy".

I used it on Pixel 4, Pixel 5, and it works very well. Also, we have some company policy, so i can't have the OTP code generator installed on my android profile.

As i usually do when i have to set my work account, i go to
"Settings > Password & Account > Add Account".

After finish the setup, on Pixel 6 doesn't ask for configure work account.

So, i opened the "Android Device Policy" App on my Pixel 6 device, and it prompt me to insert a QR (or code), and to obtain it from IT department.

So i contacted the SysAdmin of Google Workspace, and explained all the throuble i had. So he connected on the GCP platform, but there is no section where to obtain those codes.

I gave him also the link of the console where android policy store those codes (https://enterprise.google.com/u/0/android/experience/overview). But also here there is no option to generate the codes (he was logged as sysadmin user, and only thing he can see on the page was "profile already enrolled").

So, there is another way to enroll account using workspace credentials?

Please help me. Thanks everyone

[NickC]

I'm experiencing the same issue. We have an unmanaged device policy and shouldn't have to setup a managed policy in workspace to resolve this. What do we have to do for the prompt to work and allow a work profile setup?

[Jan-Carlos]

Hello @gcardamone2 and @NickC 

If when you try to configure the device for the first time it pronts App Device Policy app instead of Android Device Policy app, it's because your device don't have support to the Android Device Policy app.

The problem is, the App Device Policy app is deprecated and cannot be used anymore.

If you try to install the Android device policy manually, it will not work, it will ask fo a QR CODE or ID number, but there's not a way yo generate this codes on admin console.

So your device isn't available to MDM in advanced mode. but still can be used in basic mode, just ask you IT admin to put you in an OU with basic mode and it will work normally.

Here it is some documentation about this: 

https://workspaceupdates.googleblog.com/2020/10/google-apps-device-policy-upgrade-android.html.html

Yeah, it just sucks that this happens, but i hope it helps you guys to undestand the problem.

Regards, 

Jan Carlos

[Ambroise_Unly]

Hello, this helps understand the issue, but not solve it.

I just bought an Android 12 device (OnePlus 7 Pro). I get the same QR Code screen with no idea how to do that, I am also the Workspace Admin of the company, so I should be able to follow through any configuration setup myself, but I don't know what to do. As you pointed out, it seems it's not possible to define anything on admin.google.com.

> So your device isn't available to MDM in advanced mode. but still can be used in basic mode, just ask you IT admin to put you in an OU with basic mode and it will work normally.

I don't understand that part, I have a single OU in our company, and it is already in Basic mode. When you say that "it will work normally", did you mean that we can't set up a work profile, but we can still add the Google account as a normal account? Because that I could do, but it's not what I want. The reason I'm looking for a Work profile setup is because I want to install apps 2 times with different accounts linked (Slack, LastPass, etc.)

I also tried to look for "Android Device Policy app" but no luck there either.

Is this issue fixed with Android 13? I might just need to buy a new device.

[Ambroise_Unly]

I opened a SE question at https://android.stackexchange.com/questions/252451/how-to-add-work-profile-on-android-12-oneplus-7-p... maybe it'll yield a solution eventually.

[chrisRG]

Many thanks!

Finally arrived at this post after 2 days of pulling my hair out!!! 🙂

Question is: is the device actually not compatible or the model just not whitelisted?

What would make a standard android version not compatible?

Just curious... have a newer (budget) samsung phone with issues. Tested a 5 year old samsung and worked fine...