Intune - Android Enterprise enrollment stuck on install required apps

Ian Emmett 50

We have an issue which we from all our best efforts are struggling to pin point the problem.

We are getting the problem below which is stopping COBO mobiles getting installed...

The application failed to install because there is a configuration issue with your managed Play account or connection within Microsoft Intune. (0xC7D24FC1)

As far as i can see there are no policies we can see that is causing any upset in this program and Google play account is connected and appears to be working fine. We can also find no reference to the error number.

If anyone has come across this then any help would be appreciated.

Sean Howells 5 Reputation points

2023-01-16T10:59:37.18+00:00

Hi

We have been experiencing this issue also.

We have tried different versions of android, different model phones.

It has been an issue since late december, nothing was changed on our config.

Connectors are all showing as fine.

It just hangs on the 2 required apps

I have tried all the above steps you have suggested however I still get no further.

Sorry I originally put this in answers
Dominic Putka 5 Reputation points

2023-01-18T10:07:53.96+00:00

We are having this issue too. Exactly the same.

No Changes in the configuration within the environment.

400 android devices already enrolled and then in December we are getting passed the initial MS sign in page but then the required apps are constantly trying to download and it's stuck.

Sometimes it doesn't even get this far and times out on updating the device, even though the device is on the latest software.
Josef 5 Reputation points

2023-01-18T13:33:06.15+00:00

Hi,

we are having exactly the same issue. Doesn't matter if its a brand-new device out of the box or already used and factory reseted device. This happens everytime we try to enroll an android phone as corporate.

Enrolling the phone and personal and installing a work profile still works.

Did you guys find any solution?
Dominic Putka 5 Reputation points

2023-01-18T14:14:31.96+00:00

How would you enroll it as personal without signing into the Google Store to download the Intune / Authenticator app?
Josef 5 Reputation points

2023-01-18T14:25:26.1333333+00:00

Thats not possible, for personal you need to create/login a Google Account and download the Intune App.

We did this as workaround because the user needed access to teams and outlook on her phone.
PaulFernandes-2598 0 Reputation points

2023-01-20T16:30:44.8066667+00:00

Having exactly the same issue. Have unlinked and re linked the managed google account multiple times.
Alan McCulloch 1 Reputation point

2023-01-27T14:51:53.27+00:00

This fault appeared for us recently. I have had the same device hang and work on separate attempts. I left it last night hanging on the 2 'required apps' and in the morning they had been installed. So it does eventually do it but I can not figure out what the hang point is. I noticed on one boot some 'IronSource' bloatware but this is Samsung apparently. Any help is appreciated.
Dominic Putka 5 Reputation points

2023-02-02T12:09:00.3633333+00:00

I believe this is only happening on our Android 12 (OnePlus) devices. following some research I believe it to be the the IMEI not being exposed to Endpoint to allow the device to Authenticate the two required devices.

Our OnePlus Android 11 devices work first time every time.
Ian Emmett 0 Reputation points

2023-02-02T13:03:36.6033333+00:00

Ok so ive been speaking with MS tech team and they say that due the amount of people that are having this problem (i think started with this post) that they have a team looking in to fix the issue

this is what ive been advised as a quick workaround for the moment.
please try try adding conditional access and put all cloud apps then exclude MS intune
Dominic Putka 5 Reputation points

2023-02-03T16:53:09.73+00:00

I did this yesterday as suggested and I thought I was onto a winner the first phone worked first time.
Since then... No such luck around 12 attempts later.
George Francis 5 Reputation points

2023-02-15T14:09:34.2433333+00:00

I’m working with Motorola G62 with Android 12 and having the issue in those. The Samsungs with Android 11 have no issue. Not yet been able to ascertain if it’s an Android 12 issue only or device related.

Does removing and recreating the managed Google play account not mean you have to then re-enroll all Androids?
Lucas Pilkington 0 Reputation points

2023-02-16T11:49:24.44+00:00

We are having the same issue with all Samsung Devices running Android 13
Jouni 0 Reputation points

2023-03-16T03:43:56.2466667+00:00

This same issue also occurs on fully managed company devices, same OS (V12), on both Nokia and Motorola model Androids, effectively means we cannot use these mobile devices, as we cannot get past the initial enrolment stage.
Simon Griffiths 0 Reputation points

2023-04-11T09:23:11.52+00:00

I had the same issue on our Galaxy A53s. I resolved it by ensuring some Google and Microsoft domains weren't blocked by our DNS filter. Check your DNS logs at the time of enrolment and ensure nothing is being blocked. Hopefully that's of some help to someone.
MJCymru 0 Reputation points

2023-06-21T10:47:38.3066667+00:00

Has anyone found a solution for this?
George Francis 5 Reputation points

2023-06-21T12:38:16.6166667+00:00

I logged it with Microsoft and they said it’s a Google issue. They closed the ticket and unable to give me any reference to track it against. Admittedly last couple of times I tried I didn’t see the issue. This is enrolling over home WiFi network so should not be anything blocking.
MJCymru 0 Reputation points

2023-06-21T13:08:38.63+00:00

Thanks George, we are seeing it regardless of network so even a hotspot apps are spinning when trying to enrol

8 answers

DomSci 1 Reputation point

2023-02-15T12:57:13.46+00:00

Does anybody have a solution for that issue?
Is it maybe also depending on the Android Version?
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Ian Emmett 50 Reputation points

2023-02-15T13:25:00.2833333+00:00

We had to remove Google Play store connection completely, create a new google playstore account and reattach to Intune.
Please sign in to rate this answer.
Grant G 0 Reputation points

2023-09-25T16:56:51.7033333+00:00

Did this mess with the Android devices that you had already deployed with full company profiles?
Sign in to comment
Jessie Söderlund 0 Reputation points

2023-09-21T11:22:26.8666667+00:00
Hi Ian and others experiencing this issue ,

this problems root cause is that you cannot distribute applications via managed google play because google has updated their terms of service and for reason X its not automatically accepted for your managed google account. Therefore you need to accept google managed play stores new terms and conditions.

It is not notified anywhere that you need to do this, there are two ways to resolve this issue.

go to https://play.google.com/work/termsofservice and log in with the managed google play account that is connected to intune and accept the new conditions and terms

connect a whole new managed google play account to intune as the managed google play account (preferably a shared mailbox in ur tenant).

Answer provided by Jessie Söderlund Consultant in Sulava Oy
Please sign in to rate this answer.
Grant G 0 Reputation points

2023-09-25T16:54:44.01+00:00

@Jessie Söderlund How long does it take after you sign in and update the TOS?
Sign in to comment