EMM에서 시작한 흐름과 관리 Google Play iframe을 모두 사용하여 업그레이드가 진행될 수 있으므로 Pub/Sub 알림을 사용하면 EMM에서 두 가지 방법을 모두 모니터링하고 다음과 같은 작업을 실행할 수 있습니다.
UI에서 연락처 정보를 업데이트하고, 기존 Gmail 계정을 삭제한 후 업그레이드된 기업의 새 administrator[].email로 업데이트합니다.
업그레이드가 완료되면 IT 관리자에게 업그레이드하라는 메시지를 삭제합니다.
동일한 Pub/Sub 알림이 EMM에서 시작한 업그레이드와 iframe에서 시작한 업그레이드에 모두 사용됩니다.
2. 업그레이드 방법
EMM에서 시작된 업그레이드 흐름
EMM은 EMM에서 시작한 흐름을 구현하는 것이 좋습니다. 이 흐름을 사용하여 업그레이드를 시작하는 IT 관리자 (일반적으로 EMM 콘솔에서)는 iframe에서 시작된 흐름과 유사한 업그레이드 환경을 제공하는 URL로 리디렉션되지만 기존 Gmail 계정에 로그인하라는 메시지는 표시되지 않습니다. 이렇게 하면 업그레이드 프로세스가 단축되고 간소화되며, 원래 기업을 바인딩하는 데 사용된 Gmail 계정에 액세스할 수 없는 고객에게도 업그레이드 옵션이 제공됩니다.
업그레이드 URL을 생성한 후 IT 관리자가 업그레이드 프로세스를 시작하는 데 사용할 URL을 삽입하는 버튼 (또는 유사한 UI 요소)을 구현합니다. 이 버튼 또는 유사한 요소는 업그레이드할 수 있는 기업에만 표시해야 합니다.
IT 관리자에게 업그레이드 절차를 설명하고 고객에게 업그레이드를 권장하는 안내를 제공하는 것이 좋습니다. 업그레이드에 관한 고객용 정보는 이 고객센터 도움말을 참고하거나 직접 링크하세요.
Play EMM API Python 예시:
# Enterprise IDENTERPRISE_ID="LC01056q4j"response=msa_service.enterprises().get(enterpriseId=ENTERPRISE_ID).execute()enterprise_type=response['enterpriseType']# Generates an enterprise upgrade URL if the enterprise is a managed Google Play Accounts enterpriseif(enterprise_type!="managedGooglePlayAccountsEnterprise"):response=esa_service.enterprises().generateEnterpriseUpgradeUrl(enterpriseId=ENTERPRISE_ID).execute()print(response['url'])
IT 관리자에게는 관리 Google Play 기업의 iframe 상단에 관리 Google 도메인으로 업그레이드할 수 있다는 배너가 표시됩니다. IT 관리자는 업그레이드를 시작하거나 배너를 닫아 알림을 지연시킬 수 있습니다. 닫으면 30일 후에 배너가 다시 표시됩니다.
IT 관리자가 업그레이드를 시작하면 기존 기업용 관리 Google Play 계정 소유자 계정(일반적으로 원래 기업을 바인딩하는 데 사용된 Gmail 주소)으로 로그인하라는 메시지가 표시됩니다. 이 단계에서는 관리자가 이 기업용 관리 Google Play 결합의 업그레이드를 시작할 권한이 있는지 확인합니다.
로그인이 완료되면 관리자에게 직장 이메일을 입력하라는 메시지가 표시됩니다. 이미 충분한 권한을 가진 관리 Google 도메인의 관리자인 경우 해당 계정을 사용하여 업그레이드 단계를 완료할 수 있습니다.
해당 회사 이름에 대해 아직 도메인 인증 관리 Google 도메인이 없는 경우 IT 관리자에게 도메인 생성을 안내합니다.
로그인에 성공하거나 관리 Google 도메인 관리자 계정을 만드는 단계를 완료하면 IT 관리자에게 관리 Google 도메인으로 업그레이드할 의도를 확인하는 메시지가 표시됩니다. 이 단계를 완료하면 성공 화면이 표시되고 관리자는 고객센터 도움말을 방문하거나 Google 관리 콘솔에 로그인할 수 있습니다.
3. 업그레이드 완료 후
기업 업그레이드에 관한 Pub/Sub 알림을 수신하면 원하는 경우 enterprises.get를 호출하여 결합 유형이 managedGoogleDomain인지 확인할 수 있습니다. 기업 ID는 업그레이드 전과 동일하게 유지됩니다.
업그레이드 후 EMM은 사용자에게 이 엔터프라이즈를 업그레이드하도록 권장하는 메시지를 콘솔에서 삭제해야 합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["필요한 정보가 없음","missingTheInformationINeed","thumb-down"],["너무 복잡함/단계 수가 너무 많음","tooComplicatedTooManySteps","thumb-down"],["오래됨","outOfDate","thumb-down"],["번역 문제","translationIssue","thumb-down"],["샘플/코드 문제","samplesCodeIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-07-26(UTC)"],[],[],null,["# Upgrade an enterprise\n\nAn [Enterprise](/android/work/play/emm-api/v1/enterprises) resource binds an organization to your EMM. Multiple\nenterprise bindings can be associated with a single organization to facilitate\ntest and QA EMM environments, or separate regional EMM implementations.\n\nBindings can be of two different types:\n\n- A managed Google Play Accounts enterprise, which is created by an IT admin using a Gmail account.\n- A managed Google domain enterprise, which is created by an IT admin using their work email (as part of the new recommended [signup flow](/android/work/play/emm-api/create-enterprise#managed_google_domain_sign-up)).\n\nBinding enterprises to a managed Google domain is now the default for Play EMM\nAPI and is strongly encouraged.\n\nThe benefits of using a managed Google domain for an IT admin include:\n\n- Better security and manageability for the IT admin credentials when logging in using a work address versus a Gmail account.\n- Multiple EMM instances can be bound and managed from the same managed Google domain.\n- Multiple Google products and services can be managed with the same IT admin login.\n- Account recovery is simpler for both admin and user accounts on a managed Google domain.\n\nFor users, having enterprises bound to a managed Google domain provides\nseveral advantages, including:\n\n- Simplifies user login by allowing users to login with their work email on Android devices.\n- Allows additional services including SSO, Google Workspace and Gemini on managed devices.\n- Enables cross device experiences including Chrome Sync, sharing files across devices, transferring meetings between devices and more.\n\nThis guide describes how to upgrade a managed Google Play Accounts enterprise\n(created with a Gmail account) to a managed Google domain enterprise.\n\nTypes of upgrades\n-----------------\n\nThere are two mechanisms with which to upgrade a managed Google Play Accounts\nenterprise.\n\n- EMM-initiated: EMMs use APIs to query the binding type, and provide a way for an IT admin to start the upgrade for eligible bindings using a button or a similar UX element directly from their console.\n- Managed Google Play iframe-initiated: organization IT admins can start the upgrade process from the [managed Google Play iframe](/android/work/play/emm-api/managed-play-iframe).\n\nGuidance for EMMs\n-----------------\n\nThe following steps are highly recommended for EMMs, in order to recognize when\nan upgrade happens, support EMM-initiated and iframe-initiated upgrades, and\npresent the updated enterprise information to the IT admin.\n\n### 1. Set up Pub/Sub notifications\n\nIt is highly recommended to sign up for Pub/Sub notifications to receive an\nalert when an enterprise is upgraded. Subscribe to\n[`EnterpriseUpgradeEvent`](/android/work/play/emm-api/v1/enterprises/pullNotificationSet#notification.enterpriseUpgradeEvent) with the enterprise ID of every bound organization\nenterprise to watch for upgrade events. Look for [`upgradeStateSucceeded`](/android/work/play/emm-api/v1/enterprises/pullNotificationSet#notification.enterpriseUpgradeEvent.upgradeState)\nto indicate a successful upgrade.\n\nSince upgrades can happen using both the EMM-initiated flow and [the managed\nGoogle Play iframe](/android/work/play/emm-api/managed-play-iframe), Pub/Sub notifications allow EMMs to monitor both methods\nand take actions that could include:\n\n- Updating contact info in their UI, removing the old Gmail account and updating to the new [administrator\\[\\].email](/android/work/play/emm-api/v1/enterprises#administrator.email) for the upgraded enterprise.\n- Removing messaging that prompts IT admins to upgrade, once the upgrade is complete.\n\nThe same Pub/Sub notification is used for EMM-initiated upgrades as well as\niframe-initiated upgrades.\n\n### 2. Upgrade methods\n\n#### EMM-initiated upgrade flow\n\nEMMs are strongly encouraged to implement the EMM-initiated flow. IT admins that\ninitiate an upgrade using this flow (typically from an EMM console) will be\nredirected to a URL that provides a similar upgrade experience to the\niframe-initiated flow, however the IT admin will **not** be prompted to login to\ntheir existing Gmail account. This shortens and simplifies the upgrade process\nand also provides an upgrade option for customers that don't have access to the\nGmail account originally used to bind the enterprise.\n\n- The first step in the upgrade process is to determine the enterprise type, and whether that enterprise is eligible for upgrade. To determine the enterprise type, call [`enterprises.get`](/android/work/play/emm-api/v1/enterprises/get), and receive `\"enterpriseType\":\n String`. Enterprises of type [`managedGooglePlayAccountsEnterprise`](/android/work/play/emm-api/v1/enterprises#enterpriseType) are eligible for upgrade. Enterprises of type [`managedGoogleDomain`](/android/work/play/emm-api/v1/enterprises#enterpriseType) have either been upgraded, or were created using a work email and thus are not eligible for upgrade.\n- For eligible enterprises generate an enterprise upgrade URL using [`enterprises.generateEnterpriseUpgradeURL`](/android/work/play/emm-api/v1/enterprises/generateEnterpriseUpgradeUrl).\n- After generating the upgrade URL, implement a button (or similar UI element) that embeds the URL which IT admins will use to initiate the upgrade process. This button or similar element should only be shown for enterprises that are eligible for upgrade.\n- It is recommended to provide guidance to the IT admin, explaining the upgrade process and encouraging customers to upgrade. Refer to (or link directly to) this [help center article](https://support.google.com/googleplay/work/answer/7040932) for customer facing information on upgrades.\n\n| **Note:** Take care to only present the upgrade button (or similar UI element) to IT admin roles that are authorized to initiate the upgrade. Since the IT admin is not prompted for the enterprise owner's Gmail credentials, any admin presented with the upgrade URL will be able to execute the upgrade.\n\n**Play EMM API Python example:** \n\n```python\n# Enterprise ID\nENTERPRISE_ID = \"LC01056q4j\"\n\nresponse =\nmsa_service.enterprises().get(enterpriseId=ENTERPRISE_ID).execute()\nenterprise_type = response['enterpriseType']\n\n# Generates an enterprise upgrade URL if the enterprise is a managed Google Play Accounts enterprise\nif (enterprise_type != \"managedGooglePlayAccountsEnterprise\"):\n response = esa_service.enterprises().generateEnterpriseUpgradeUrl(\n enterpriseId=ENTERPRISE_ID\n ).execute()\n print(response['url'])\n```\n\n#### Iframe-initiated upgrade flow\n\nEMMs should be familiar with the flow that IT admins will encounter when\ninitiating an upgrade from the [managed Google Play iframe](/android/work/play/emm-api/managed-play-iframe):\n\n- IT admins will encounter a banner on the top of the iframe for managed Google\n Play enterprises notifying them that they are eligible to upgrade to a managed\n Google domain. The IT admin has the opportunity to initiate the upgrade, or\n close the banner to delay the notification. If closed, the banner will reappear\n after 30 days.\n\n- If an IT admin elects to begin the upgrade they will be prompted to sign in\n with their existing\n [managed Google Play Accounts enterprise owner account](https://support.google.com/googleplay/work/answer/7040932)\n (typically the Gmail address used to originally bind the enterprise). This step\n confirms the admin has rights to initiate the upgrade for this managed Google\n Play enterprise binding.\n\n- Upon successful login, the admin will be prompted to provide their work\n email. If they are already an admin of a managed Google domain with sufficient\n privileges, they will be able to use that account to finish the upgrade steps.\n If there isn't already a domain verified managed Google Domain for that company\n name, the IT admin will be guided to create one.\n\n| **Note:** The managed Google domain created by this step will be an email-verified team. Later the IT admin will want to [verify the domain](https://cloud.google.com/identity/docs/verify-domain) using DNS in order to unlock the full capabilities of the managed Google domain.\n\n- Upon successful login, or completion of the steps to create a managed Google domain admin account, the IT admin will be prompted to confirm their intent to upgrade to a managed Google domain. Completion of this step will result in a success screen and the admin can visit a [help center article](https://support.google.com/work/android/answer/16147675) or log into the Google [admin console](https://admin.google.com).\n\n### 3. After successful upgrade\n\nUpon receiving a Pub/Sub notification of an enterprise upgrade, you can\noptionally call [`enterprises.get`](/android/work/play/emm-api/v1/enterprises/get) to confirm the binding type to be\n`managedGoogleDomain`. The enterprise ID remains the same as it was prior to the\nupgrade.\n\nAfter upgrade, EMMs should remove any messaging shown in their console\nencouraging users to upgrade this enterprise.\n\nThe Gmail address of the IT admin ([`administrator[].email`](/android/work/play/emm-api/v1/enterprises#administrator.email)) will be\nreplaced by a new work email address of the IT admin.\n\nThe [`enterprise`](/android/work/play/emm-api/v1/enterprises) field [`name`](/android/work/play/emm-api/v1/enterprises#name) will also be changed upon upgrade to\nreflect the name of the managed Google domain.\n| **Note:** Any contact info (e.g. Gmail address) for the previously associated binding is deleted upon successful upgrade. If the organization wishes to update contact information, it must be done in the [admin console](https://admin.google.com) of the now associated managed Google domain."]]
