reCAPTCHA on Google Cloud は、アカウント防御、SMS 防御、多要素認証、不正防止などのエンタープライズ グレードの機能を提供します。このプラットフォームは、ダッシュボードに Google Cloud を使用し、Cloud Monitoring と Looker を統合して、モニタリング、レポート作成、アラートを強化します。
reCAPTCHA 管理コンソールは引き続きご利用いただけます。アカウントを Google Cloudに移行した後も、reCAPTCHA 管理コンソールから、過去のデータと Classic アカウントに関連する構成にアクセスできます。ただし、キー構成の変更は Google Cloud コンソールで行う必要があります。
[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-09-04 UTC。"],[],[],null,["This document explains the migration of reCAPTCHA Classic to\nreCAPTCHA Enterprise on Google Cloud, including the reasons\nto migrate, the automated process, and the impact on your existing\nreCAPTCHA implementations.\n\nWhy migrate to reCAPTCHA\n\nreCAPTCHA on Google Cloud provides enterprise-grade\nfeatures like account defender, SMS defense, multi-factor authentication, and\nfraud prevention. The platform uses Google Cloud for dashboards and\nintegrates with Cloud Monitoring and Looker for enhanced monitoring,\nreporting, and alerts.\n\nWhether you [migrate your keys yourself](https://www.google.com/recaptcha/admin/migrate)\nor wait for the automated migration, your keys continue to function without\nany code changes.\n\nImpact on existing keys and data\n\nYour existing v2 or v3 site keys continue to work after migration. You don't\nneed to change any code on your website. The key continues to function even if\nyou don't immediately accept the project ownership invitation.\n\nGoogle Cloud-based deployment benefits\n\nMoving to the Google Cloud-based deployment provides the following\nbenefits:\n\n- **Simplified technology**: All reCAPTCHA development is dedicated to this unique offering.\n- **Stronger compliance**: The platform improves adherence to data protection regulations by shifting from data controller to data processor.\n- **Advanced feature exposure**: You gain access to advanced features such as Account Defense and Password Defense, as well as an improved Google Cloud console experience that includes generative AI insights and an enhanced dashboard.\n- **Resolves terms of service issues**: The platform resolves issues where users' transitive enterprise use Terms of Service restrict their data usage.\n\nAutomatic migration process overview\n\nIf you don't migrate your keys yourself, reCAPTCHA automatically migrates them.\nThe automatic migration provisions a Google Cloud project and associates your\nreCAPTCHA keys with that project. Automigration includes the\nfollowing steps:\n\n1. A Google Cloud project is created to hold your existing keys.\n\n2. Your project keys are associated with the Google Cloud project.\n\n3. An email invitation is sent to you to accept ownership of the project. If a\n key has multiple owners, all of them are invited to the same new project.\n\n Project ownership invitations don't expire. Your keys\n continue to function after migration. However, to manage the keys, such as\n to create, delete, or modify them, you must accept the project.\n\n If you have an existing Google Cloud account, you can move the project\n that was created by the automigration process to your existing\n Google Cloud account by creating a new reCAPTCHA\n key in a project of the existing Google Cloud account.\n | **Important:** If the administrator or owner of a Classic reCAPTCHA key is no longer active, the automatic migration still proceeds. If this occurs, you cannot reclaim the migrated project. However, you can create a new site key to associate with a new or existing project that you can access.\n\nMigration timeline\n\nAll reCAPTCHA Classic customers must migrate or will be migrated\nto Google Cloud by the end of 2025. The process involves the following\nphases.\n\n- **Q3 2024**: New Classic keys are no longer allowed.\n- **Q1 2025**: The first notification that informs customers to migrate using the self-migration tool is sent.\n- **Q3 2025** : A follow-up notification is sent to customers that haven't yet migrated from Classic, which links directly to the [migration tool](https://www.google.com/recaptcha/admin/migrate) in the [Google Cloud console](/recaptcha/docs/migrate-recaptcha#migrate-through-cloud-console).\n- **Q4 2025**: Customers are automatically migrated from Classic to the Enterprise version.\n- **Q4 2025**: All Classic keys are rejected, with API access locked for keys without a Google Cloud project.\n\nYou can migrate your Classic accounts at your convenience. Consider your\ncompany's code freeze schedule when planning your migration. The Google team\nautomatically migrates your Classic accounts in October if you don't migrate\nyour account. No immediate code changes are required. SiteVerify requests\ncontinue to function as they did before the migration. Migrate and\n[create an assessment](/recaptcha/docs/using-features) after your account\nmigrates to Google Cloud to use the advanced features.\n\nAccess to the reCAPTCHA Admin console\n\nThe [reCAPTCHA Admin console](https://www.google.com/recaptcha/admin)\nremains available. After you migrate your account to Google Cloud,\nyou can still access your historical data and any configuration related to your\nClassic accounts from the\n[reCAPTCHA Admin console](https://www.google.com/recaptcha/admin).\nHowever, any changes to key configuration must be made through the Google Cloud console.\n| **Important:**\n\nIf you don't accept project ownership after your account is migrated, the\nreCAPTCHA Admin console will redirect you to accept project ownership.\n\nBilling and enforcement\n\nreCAPTCHA Enterprise has a free tier of 10,000 monthly\nassessments. For usage over 10,000 assessments per month, you must enable\n[billing](/recaptcha/docs/billing-information#how-it-works) for your\nGoogle Cloud project.\n\nIf you exceed the free 10,000 monthly assessments after automigration and\ndon't enable billing, reCAPTCHA returns an error for any new\nrequest.\n\n- **`SiteVerify` requests** : After migration, `SiteVerify` requests that exceed\n their quota will `fail open`. This means that they will return `success:true`\n with a score of `0.9`, and the API response will include an error message\n indicating that you exceeded the quota. This behavior is designed to prevent\n valid users from being blocked, similar to the previous Classic\n reCAPTCHA policy. It is a change in API behavior for Enterprise\n keys.\n\n- **`CreateAssessment` requests** : `CreateAssessment` requests\n that exceed their quota `fail closed`. This means that the request will\n return a `Resource Exhausted (429)` HTTP error and no `Assessment` is\n created. To help prevent this, over-quota notifications and emails will\n alert you about a missing billing account.\n\nKey management and monitoring\n\nAfter migration, you onboard to the Google Cloud console for key management. Use the\nGoogle Cloud console to monitor your site's traffic and analyze risk for\nrequests that occur after the migration.\n\nWhat's next\n\n- [Use reCAPTCHA features after migration](/recaptcha/docs/using-features)."]]
