デバイス上のユーザー アカウントのアップグレードでは、managed Google Play アカウントから managed Google アカウントへの移行が行われます。このプロセスでは、ユーザーの ID がデバイス中心の非個人用アカウントから、企業の Google ID に関連付けられたアカウントに移行します。この企業 ID へのリンクは、すべての Google サービスでユーザー エクスペリエンスを改善し、統合を深めるための基盤となります。
概要
このアップグレードの主な目的は、Google 管理コンソールによるユーザー管理の改善、セキュリティの強化、Gemini などの Google サービスや AI 機能へのアクセスなど、強化された機能をユーザーに提供することです。
ユーザー アカウントをアップグレードする主なメリットは次のとおりです。
すべての Google サービスで使用可能: managed Google Play アカウントとは異なり、この新しい ID は Google ドライブ、ドキュメント、Meet などのすべての Google サービスでシームレスに使用できます。また、IT 管理者が許可している場合はデバイスのバックアップも利用できます。
シームレスなユーザー エクスペリエンス: シングル サインオン（SSO）の統合により、ユーザーは企業環境と Gmail などのすべての Google サービスに自動的にログインできます。
ID の直接制御: 組織は、手動、自動、同期ベースの方法で ID ライフサイクルを直接制御できます。
AccountSetupListener を使用して ADDED_ACCOUNT 状態を受け取り、EMM バックエンドがデバイスを新しい管理対象 Google アカウントに正常に関連付けたら、新しいユーザーにポリシーが適用されていることを確認します。スムーズな移行のため、Devices.update API を使用してアップグレードを開始する前に、対象ユーザーのデバイス ポリシーを適用することをおすすめします。Devices.update を呼び出すために必要な管理対象 Google アカウントのユーザー ID は、Users.list を呼び出すことで取得できます。
管理対象の Google アカウントが設定されたナレッジ ワーカーのデバイスについては、デバイスが企業のポリシーに準拠したら、Devices.setState() を呼び出すことを忘れないでください。これは、デバイスを有効にして、ユーザーに Google サービスへの完全なアクセス権を付与するために必要です。
[[["わかりやすい","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-08-25 UTC。"],[],[],null,["# Upgrade user accounts\n\nUpgrading a user account on a device involves a migration from a\n**managed Google Play Account** to a **managed Google Account**. This process\nshifts the user's identity from a device-centric, non-personal\naccount to one that is tied to their corporate Google identity. This link to a\ncorporate identity is the foundation for an improved and more integrated user\nexperience across all Google services.\n\nOverview\n--------\n\nThe primary goal of this upgrade is to provide customers with enhanced features,\nsuch as improved user management through the Google Admin console, stronger\nsecurity, and access to Google services and AI capabilities like Gemini.\n\n### Key benefits of upgrading user accounts:\n\n- **Works with all Google services:** Unlike managed Google Play Accounts,\n this new identity works seamlessly with all Google services, including Google\n Drive, Docs, and Meet. It also supports device backup when enabled by the IT\n admin.\n\n- **Seamless user experience:** Through single sign-on (SSO) integration, users\n are automatically signed in to their corporate environment and all their Google\n services, such as Gmail.\n\n- **Direct identity control:** The organization can directly control the\n identity lifecycle through manual, automated, or sync-based methods.\n\n- **Familiar user identifier:** For better visibility, the new account uses the\n same email address that the user already knows and uses.\n\nAccount upgrade\n---------------\n\nTo upgrade a device previously enrolled with a **managed Google Play Account**\nto a **managed Google Account**, you can adopt a setup similar to the\nstandard device enrollment flow, but with key differences in token creation\nand post-setup actions.\n\n### 1. Create an enrollment token for account upgrade\n\nThis step involves creating an enrollment token specifically configured for\naccount migration. The token will force Google authentication to link the\ndevice to a managed Google Account.\n\n- Call the `EnrollmentTokens.create()` method of the Play EMM API.\n- Set `enrollmentTokenType` to `USER_DEVICE`.\n- Within the `googleAuthenticationOptions` object:\n- Set `authenticationRequirement` to `REQUIRED`. This makes a Google account mandatory for enrollment.\n- Set `requiredAccountEmail` to the email address of the target managed Google Account. This guides the on-device flow to either prompt the user for this specific account or, if it already exists on the device, perform the upgrade silently without further user authentication.\n\n### 2. Initiate account setup and handle authentication on the device\n\nOnce the enrollment token is available (e.g., pushed by your EMM solution\nor provided using a user interface), you can use the same\n[`AccountSetupClient.startAccountSetup()`](/android/management/reference/amapi/com/google/android/managementapi/setupactions/AccountSetupClient#startAccountSetup(android.content.Context,%20java.lang.String))\nintegration from standard device enrollment to add or associate the account.\n\n- If the managed Google Account specified in `requiredAccountEmail` already exists on the device, the user won't be prompted to authenticate, and the upgrade will proceed silently.\n- If the account does not exist, the user will be forced to sign in with the required email. Because `authenticationRequirement` is set to `REQUIRED` in the token, the option to skip Google authentication won't be available.\n\n### 3. Finalize management and remove the old account\n\nAfter the `ADDED_ACCOUNT` state is received using your `AccountSetupListener`\nand your EMM backend has successfully associated the device with the new managed\nGoogle Account, verify your policies are applied to the new user. We recommend\napplying the target user's device policies *before* initiating the upgrade using\nthe [`Devices.update`](/android/work/play/emm-api/v1/devices/update) API for a\nsmooth transition. You can retrieve the User ID of the managed Google Account,\nwhich is needed in order to call\n[`Devices.update`](/android/work/play/emm-api/v1/devices/update), by calling\n[`Users.list`](/android/work/play/emm-api/v1/users/list).\n\nRemoving the old account from the device is a required step.\nThe DPC Support Library provides `dpcSupport.removeAllAndroidForWorkAccounts()`\nfor this purpose.\n\n### 4. Enable Google services\n\nFor knowledge worker devices with a managed Google Account, remember to\ncall [`Devices.setState()`](/android/work/play/emm-api/v1/devices/setState)\nonce the device is compliant with your enterprise policies. This is necessary to\nactivate the device and grant the user full access to Google services.\n\nSpecial use case\n----------------\n\nThe account upgrade process is also beneficial in the following special\nuse case:\n\n*** ** * ** ***\n\n### Kitting and third-party enrollment services\n\nThe account upgrade flow simplifies **kitting** and **third-party\nenrollment services** by the following process:\n\n1. **Initial process:** A device is enrolled as a userless\n device. This automatically adds a managed Google Play Account and\n applies a set of default policies.\n\n2. **Policy update:** The EMM applies a new policy to the device. This policy\n requires a user login before the device can be used. The device is then\n delivered to the end user.\n\n3. **User upgrade:** When the end user powers on the device, they are\n prompted to sign in. This action triggers the account upgrade flow,\n where their managed Google Account replaces the managed Google Play\n Account.\n\n4. **Final cleanup:** The EMM removes the old managed Google\n Play Account from the device."]]
