[[["易于理解","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)：2025-08-21。"],[[["\u003cp\u003eApigee subscription users with the \u003cem\u003eApigee Integrations\u003c/em\u003e add-on are now redirected to Application Integration at no extra cost, with existing integrations automatically synchronized.\u003c/p\u003e\n"],["\u003cp\u003eApplication Integration utilizes new predefined IAM roles, meaning existing user accounts will be granted equivalent permissions, and custom IAM roles may need to be updated.\u003c/p\u003e\n"],["\u003cp\u003eA new default service account is created for Application Integration operations, such as running integrations and invoking Cloud Functions, and this service account has its own specific email address format.\u003c/p\u003e\n"],["\u003cp\u003eWhile most Apigee Integration APIs have equivalents in Application Integration, the resource paths in REST APIs have changed, although existing paths will still work.\u003c/p\u003e\n"],["\u003cp\u003eThe sender email address for the Send Email and Approval tasks is now \u003ccode\u003enoreply-application-integration@google.com\u003c/code\u003e, and approval requests will link to Application Integration.\u003c/p\u003e\n"]]],[],null,["# Use Application Integration\n\nThis page provides information intended for existing Apigee customers who want to use Application Integration with the same Google Cloud project.\n\nOverview\n--------\n\n\nAll Apigee subscription users who had enabled the *Apigee Integrations* add-on, will now be redirected to Application Integration at no additional cost.\nApplication Integration is set up for you, and all your existing integrations in Apigee were automatically synchronized and available to use. This means that you can continue to use your existing Google Cloud project for Application Integration without any additional configurations.\n\n\nTo know more about Application Integration, see [Application Integration overview](/application-integration/docs/overview).\n| **Note:** Existing integrations configured in the `US multi-region(us)` location are not available in Application Integration.\n\nFrom the Apigee portal, you will be redirected to Application Integration:\n\n\n| **Tip:** We recommend using the Application Integration [API reference](/application-integration/docs/apis) and [IAM permissions](/application-integration/docs/predefined-iam-roles-permissions) once you start using Application Integration.\n\nWhat has changed?\n-----------------\n\n\nThe following table provides a summary of the expected differences or changes in your Google Cloud project:\n\n### IAM permission changes\n\n\nAll existing user accounts or principals are granted with equivalent [Predefined Application Integration](/application-integration/docs/predefined-iam-roles-permissions) IAM permissions.\n\n\nApplication Integration IAM permissions have the following format:\n\n### Format\n\n```\nintegrations.integrationRESOURCE.ACTION\n```\n\n### Example\n\n```\nintegrations.integrationVersions.get\n```\n\n#### Custom IAM role limitations\n\nThe following limitations apply if you have defined [custom IAM roles](/iam/docs/roles-overview#custom) in your Google Cloud project:\n\n- Apigee proxies using a service account with custom IAM roles containing Apigee Integration permissions might fail. We recommend that you update your custom IAM roles with the Application Integration [IAM permissions](/application-integration/docs/predefined-iam-roles-permissions).\n\nFor information about IAM roles and permissions, see [Access control overview](/application-integration/docs/access-control).\n\n### Service account changes\n\n\nA new default service account with the [Application Integration Service Agent](/iam/docs/understanding-roles#integrations.serviceAgent) `(roles/integrations.serviceAgent)` IAM role is created in your Google Cloud project.\n\nThe new Application Integration default service account is used for the following integration operations:\n\n- To run an integration.\n- To invoke a Cloud Function using the [Cloud Function task](/application-integration/docs/configure-cloud-function-task).\n- To call an Integration Connector using the [Connectors task](/application-integration/docs/configure-connectors-task).\n- To create service account tokens for [Service account type](/application-integration/docs/configure-authentication-profiles#service-account) authentication profiles.\n- To encrypt and decrypt Cloud KMS keys for authentication profiles.\n\nApplication Integration default service account has the following email address:\n\n### Format\n\n```\n service-PROJECT_NUMBER@gcp-sa-integrations.iam.gserviceaccount.com\n```\n\n### Example\n\n```\n service-46733320069@gcp-sa-integrations.iam.gserviceaccount.com\n```\n\nFor information about service accounts, see [Access control overview](/application-integration/docs/access-control#sa).\n| **Notes:** Apigee will continue to use the existing default Apigee service account---`service-`\u003cvar translate=\"no\"\u003ePROJECT_NUMBER\u003c/var\u003e`@gcp-sa-apigee.iam.gserviceaccount.com`---for other Apigee resources and operations.\n\n### REST API changes\n\n\nIn general, most of the Apigee Integration APIs have their respective Application Integration API equivalents.\n\n\nThe following table describes the key change in the REST APIs of Application Integration when compared to Application Integration:\n\n| **Note:**Your existing resource paths will continue to work in Application Integration.\n\nFor information about Application Integration APIs, see [Application Integration REST API](/application-integration/docs/apis).\n\n### Integration task changes\n\nThe [Send Email](/application-integration/docs/configure-send-email-task) task and the [Approval](/application-integration/docs/configure-approval-task) task will use `noreply-application-integration@google.com` to send email notifications. In addition, all the approval request emails sent using the [Approval task](/application-integration/docs/configure-approval-task) will link to Application Integration."]]
