[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2024-06-26。"],[[["\u003cp\u003eThis document outlines how to remove corporate email addresses from consumer accounts, referred to as "evicting," to mitigate social engineering risks.\u003c/p\u003e\n"],["\u003cp\u003eEviction involves creating and then deleting a conflicting managed account in Cloud Identity or Google Workspace, forcing the consumer account owner to rename their account.\u003c/p\u003e\n"],["\u003cp\u003eThe process of evicting accounts requires a pre-existing Cloud Identity or Google Workspace account, with the corporate email address domain verified within it.\u003c/p\u003e\n"],["\u003cp\u003eBest practices for evicting accounts include ensuring the user can no longer receive emails on the corporate email address and proactively provisioning user accounts to prevent new consumer accounts.\u003c/p\u003e\n"],["\u003cp\u003eAfter eviction, the consumer account owner can convert to a Gmail account, use a different email address, or use a temporary \u003ccode\u003egtempaccount.com\u003c/code\u003e address, all while keeping their data and settings.\u003c/p\u003e\n"]]],[],null,["# Evict consumer accounts\n\nIf you haven't been using\n[Cloud Identity](/identity)\nor\n[Google Workspace](https://gsuite.google.com/),\nit's possible that your organization's employees have been using consumer\naccounts to access Google services. Some of these consumer accounts might use a\ncorporate email address such as `alice@example.com` as a primary or alternate\nemail address.\n\nThis document describes how you can *evict* , or get rid of, these types of\nconsumer accounts by removing the corporate email address from them. Although\nthe consumer accounts will still exist, removing the corporate email address\nhelps you mitigate a social engineering risk---as long as a consumer account has a\nseemingly trustworthy email address like `alice@example.com`, the owner of the\naccount might be able to convince current employees or business partners to\ngrant them access to resources they shouldn't be allowed to access.\n\nAlternatively, by\n[migrating consumer accounts](/architecture/identity/migrating-consumer-accounts),\nyou can keep these accounts and turn them into\n[managed accounts](/architecture/identity/overview-google-authentication#managed_user_account).\nBut there might be some accounts that you don't want to migrate, such as the\nfollowing:\n\n- Consumer accounts that are used by former employees.\n- Consumer accounts that are used by employees that are not supposed to access Google services.\n- Consumer accounts for which you cannot recognize the owner.\n\nBefore you begin\n----------------\n\nTo evict offending consumer accounts, you must satisfy the following\nprerequisites:\n\n- You have [identified a suitable onboarding plan](/architecture/identity/assessing-onboarding-plans) and have completed all prerequisites for consolidating your existing user accounts.\n- You have created a [Cloud Identity or Google Workspace account](/architecture/identity/overview-google-authentication#cloud_identity_or_g_suite_account).\n\nThe primary or alternate email address of the consumer account must correspond\nto one of the domains that you have added to your Cloud Identity or\nGoogle Workspace account. Both primary and secondary domains qualify, but\nalias domains are not supported.\n\nProcess\n-------\n\nEvicting unwanted consumer accounts works similarly to\n[migrating consumer accounts](/architecture/identity/migrating-consumer-accounts),\nbut it is based on deliberately creating a conflicting account. The following\ndiagram illustrates the process. Boxes on the **Administrator** side denote\nactions a Cloud Identity or Google Workspace administrator takes;\nrectangular boxes on the **User account owner** side denote actions only the\nowner of a consumer account can perform.\n\n#### Find unmanaged user accounts\n\nYou can use the\n[transfer tool for unmanaged users](https://admin.google.com/ac/unmanaged)\nto find consumer accounts that use a primary email address that matches one of\nthe verified domains of your Cloud Identity or Google Workspace\naccount.\n\n#### Create a conflicting account\n\nWhen you have identified a consumer account that you want to evict, do the\nfollowing:\n\n1. Create a user account in Cloud Identity or\n Google Workspace that has the same corporate email address as the\n account you want to evict.\n\n If the consumer account uses the corporate email address as the primary\n email address, the Admin Console warns you about an impending conflict.\n Because you are intentionally creating the conflicting account, select\n **Create new user**.\n\n Because you don't want the managed user account to ever be used, assign a\n random password.\n2. Delete the user account that you just created.\n\nBy creating a conflicting account and immediately deleting it, you force the\nowner to rename that user account. But you avoid that owner being shown a ballot\nscreen that prompts them to choose between the managed and consumer account.\n\n#### Rename the user account\n\nFor the owner of the evicted user account, the next time they sign in, they see\nthe following message:\n\nAs the screenshot suggests, they have three options for proceeding:\n\n- Convert the user account into a Gmail account.\n- Associate a different email address with the account.\n- Postpone the rename. This causes the user account to use a temporary `gtempaccount.com` email address in the meantime.\n\nAll configuration and data that was created by using this consumer account is\nunaffected by the rename.\n\nBest practices\n--------------\n\nWe recommend the following best practices when you evict unwanted consumer\naccounts:\n\n- Ensure that affected users can no longer receive email on their (former) corporate email address. Otherwise, a user might be able to undo the rename and switch the primary email address back to the corporate email address.\n- Prevent other users from signing up for new consumer accounts by [proactively provisioning user accounts to Cloud Identity or Google Workspace](/architecture/identity/best-practices-for-federating).\n\nWhat's next\n-----------\n\n- Review how you can [assess existing user accounts](/architecture/identity/assessing-existing-user-accounts).\n- Learn how to [remove a corporate email address from a Gmail account](/architecture/identity/sanitizing-gmail-accounts)."]]