Skip to main content
O
okmick
Level 1.6: Donut
February 25, 2025
Question

Why is the Google Play organization ID different depending on where you look?

  • February 25, 2025
  • 5 replies
  • 3 views

If you didn't see my other post Private app package name already in use I've asked one of our software vendors to make one of their private apps available to my organization. To prepare for that, I went to gather our organization ID and noticed that it's different depending on where I look.

 

From the Managed Google Play Console:

https://play.google.com/work/adminsettings

From the Managed Google Play iframe in Microsoft Intune:

I know it doesn't mean much with the IDs blacked out but just wanted to show you where exactly I was looking. In the first instance, I'm logged into the same Google account I used to connect Intune with Google Play.

 

Any ideas why the organization IDs would be different? I am wondering which ID to give them.

 

Thanks.

5 replies

Moombas
Moombas
Level 4.4: KitKat
February 25, 2025

On our end the ID's are the same (ensure using the same account) but we also doesn't use Intune but i guess that shouldn't make a difference.

J
jasonbayton
Level: 4.1: Jelly bean
February 25, 2025

Would you bet a steak dinner on you showing the same Google account in both pictures?

 

Because I'm hungry 😋

    O
    okmickAuthor
    Level 1.6: Donut
    February 25, 2025

    Lol ya'll are cracking me up! Did everyone in this thread not read this part of my post?

    I'm logged into the same Google account I used to connect Intune with Google Play.

    I think you owe me a steak dinner sir. I won't post my account details but I will gladly DM you.

    J
    jasonbayton
    Level: 4.1: Jelly bean
    February 25, 2025

    Proof was in the pudding. Follow up .. 

     

    Is it possible the account was initially Gmail (with an existing email address) and later adopted into workspace? 

     

    If that absolutely never ever could have happened, we should involve the authorities :D 

    R
    reyaquino
    Level 1.5: Cupcake
    February 25, 2025

    Hey @okmick maybe this screenshot will help you. Which ID should you give them to add your Organization ID to their Google Play Console (MGP).

     

      O
      okmickAuthor
      Level 1.6: Donut
      February 25, 2025

      Sorry that doesn't help. No new information here. But it is nice to see the Google Play Console that the vendor would see. Thanks!

      Alex_Muc
      Alex_Muc
      Level 3.0: Honeycomb
      February 25, 2025

      I also suspect, like @jasonbayton, that different Google accounts are being used for the comparison.

       

      Have a look in the Intune settings to see which Google account is used for the Managed Google Play / EMM registration. The OrganizationID from the iFrame belongs to this account. This should be the relevant organizationID for the software vendor.

       

       

      O
      okmickAuthor
      Level 1.6: Donut
      February 25, 2025

      I'm logged into the same account like I noted in my original post.

      Alex_Muc
      Alex_Muc
      Level 3.0: Honeycomb
      February 25, 2025

      @okmickthere are good reasons why we are asking explicitly.
      So far, EMM registration, email and OrganizationID were a 1:1:1 relationship. It was simply impossible to have two EMM registrations or OrganizationIDs with one e-mail address. Therefore, there is no harm in double-checking this, even if you may see it differently.

       

      Hence two further questions:
      When did you do the EMM registration?
      Do you have a Managed Google domain?

       

      Because the only other thing that comes to mind is the topic:
      [Product Update] Configure and bind multiple Android Enterprise Mobility Management providers | Android Enterprise Customer Community - 910

       

      O
      okmickAuthor
      Level 1.6: Donut
      February 25, 2025

      Okay fair enough.

       

      The registration date is 8/29/2024.

      I do not have a managed Google domain.

      Terms & ConditionsCookie settingsAccessibility statement