Merge pull request #305455 from TimShererWithAquent/us474076-04

Freshness Edit: Data security and privacy policies for Google connectors in Azure Logic Apps

Author: v-regandowner

articles/connectors/connectors-google-data-security-privacy-policy.md

@@ -1,70 +1,74 @@
 ---
-title: Data security and privacy policies for Google connectors
+title: Data Security and Privacy Policies for Google Connectors
 description: Learn about the impact that Google security and privacy policies have on Google connectors, such as Gmail, in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: concept-article
-ms.date: 05/04/2025
 ms.custom: sfi-image-nochange
+ms.date: 09/12/2025
+#Customer intent: As an integration developer who works with Google connector in Azure Logic Apps, I need to know how Google's policies affect workflows that use Google services, such as Gmail.
 ---
 
 # Data security and privacy policies for Google connectors in Azure Logic Apps
 
-Starting **May 1, 2020**, changes due to Google's [data security and privacy policies](https://www.blog.google/technology/safety-security/project-strobe/) might affect your logic app workflows that use the Google connectors, such as the [Gmail connector](/connectors/gmail/). For example, if your workflows use the Gmail connector with a Gmail consumer account (email address that ends with @gmail.com or @googlemail.com), your workflows can use only specific [Google-approved triggers, actions, and connectors](#approved-connectors). However, if your workflows use the Gmail connector with a G-Suite business account (email address with a custom domain), your workflows aren't affected and have no restrictions on using the Gmail connector.
+[!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
 
-> [!NOTE]
-> Currently, the Gmail connector works only with the **Logic App (Consumption)** resource type, not the **Logic App (Standard)** resource type.
+Starting **May 1, 2020**, changes due to Google's [data security and privacy policies](https://www.blog.google/technology/safety-security/project-strobe/) might affect logic app workflows that use the Google connectors, such as the [Gmail connector](/connectors/gmail/).
+
+If your workflows use the Gmail connector with a Gmail consumer account, which is an email address that ends with `@gmail.com` or `@googlemail.com`, your workflows can use only specific [Google-approved connector operations](#approved-connectors). If your workflows use the Gmail connector with a G-Suite business account, which is an email address with a custom domain, your workflows aren't affected and have no restrictions on using the Gmail connector.
 
 ## Affected workflows
 
-If you have logic app workflows that use the Gmail connector, you'll receive an email about potentially affected logic apps. However, starting **June 15, 2020**, any non-compliant workflows will be disabled. You can take either of these actions:
+Since **June 15, 2020**, any noncompliant workflows have been disabled. You can take either of the following actions:
 
-* Update the affected logic apps by [following the steps in this topic](#update-affected-workflows). You need to create a Google client app, which provides a client ID and client secret that you use for authentication in your Gmail trigger or action.
+- Update the affected logic apps as described later in this article. You must create a Google client app, which provides a client ID and client secret to use for authentication with Google triggers or actions.
 
-* Update the affected logic apps so that they use only the [Google-approved connectors](#approved-connectors) before you re-enable the disabled logic apps.
+- Update the affected logic apps so that they use only the Google-approved connectors described in the next section. You can then reenable the disabled logic apps.
 
 <a name="approved-connectors"></a>
 
 ## Google-approved connectors
 
-Under this policy, when you use a Gmail consumer account, you can use the Gmail connector with only specific Google-approved services, which are subject to change. Our engineering teams continue working with Google to add more services to this list. For now, here are the Google-approved triggers, actions, and connectors that you can use in the same logic app workflow with the Gmail connector when you use a Gmail consumer account:
+Under this policy, when you use a Gmail consumer account, you can use the Gmail connector with only specific Google-approved services, which are subject to change.
+
+The following list specifies the Google-approved connectors and operations that you can use in the same logic app workflow with the Gmail connector when you use a Gmail consumer account:
 
-* Azure Logic Apps built-in triggers and actions: Batch, Control, Data Operations, Date Time, Flat File, Liquid, Request, Schedule, Variables, and XML
+- Azure Logic Apps built-in triggers and actions: Batch, Control, Data Operations, Date Time, Flat File, Liquid, Request, Schedule, Variables, and XML
 
-  Built-in triggers and actions that aren't approved by Google, such as HTTP, Azure Functions, Azure Logic Apps, and others, make a logic app non-compliant with the Gmail connector because the app can send or receive data from anywhere.
+  Built-in triggers and actions that Google doesn't approve make a logic app noncompliant with the Gmail connector because the app can send or receive data from anywhere. These triggers and actions include HTTP, Azure Functions, and Azure Logic Apps.
 
-* Google services: Gmail, Google Calendar, Google Contacts, Google Drive, Google Sheets, and Google Tasks
+- Google services: Gmail, Google Calendar, Google Contacts, Google Drive, Google Sheets, and Google Tasks
 
-* Approved Microsoft services: Dynamics 365, Excel Online, Microsoft Teams, Microsoft 365, OneDrive, and SharePoint Online
+- Approved Microsoft services: Dynamics 365, Excel Online, Microsoft Teams, Microsoft 365, OneDrive, and SharePoint Online
 
-* Connectors for customer-managed data sources: FTP, RSS, SFTP, SMTP, and SQL Server
+- Connectors for customer-managed data sources: FTP, RSS, SFTP, SMTP, and SQL Server
 
-## Non-compliant examples
+## Noncompliant examples
 
-Here are some examples that use the Gmail connector with built-in triggers and actions or managed connectors that aren't approved by Google:
+Here are some examples that use the Gmail connector with built-in triggers and actions or managed connectors that Google doesn't approve:
 
-* This logic app workflow uses the Gmail connector with the HTTP built-in trigger:
+- This logic app workflow uses the Gmail connector with the HTTP built-in trigger:
 
-  ![Non-compliant logic app - Example 1](./media/connectors-google-data-security-privacy-policy/not-compliant-logic-app-1.png)
+  :::image type="content" source="./media/connectors-google-data-security-privacy-policy/noncompliant-gmail-connector.png" alt-text="Screenshot shows a noncompliant workflow that uses a Google email action.":::
 
   The workflow also uses the Google Calendar connector, which is approved.
 
-* This workflow uses the Gmail connector with the Azure Blob Storage connector:
+- This workflow uses the Gmail connector with the Azure Blob Storage connector:
 
-  ![Non-compliant logic app - Example 2](./media/connectors-google-data-security-privacy-policy/not-compliant-logic-app-2.png)
+  :::image type="content" source="./media/connectors-google-data-security-privacy-policy/noncompliant-blob-storage.png" alt-text="Screenshot shows a noncompliant workflow that uses a Google action with a create blob action.":::
 
-* This workflow uses the Gmail connector with the X connector:
+- This workflow uses the Gmail connector with the X connector:
 
-  ![Non-compliant logic app - Example 3](./media/connectors-google-data-security-privacy-policy/not-compliant-logic-app-3.png)
+  :::image type="content" source="./media/connectors-google-data-security-privacy-policy/noncompliant-create-tweet.png" alt-text="Screenshot shows a noncompliant workflow that uses an X action.":::
 
 For the most recent information, see the [Gmail connector's technical reference documentation](/connectors/gmail/).
 
 <a name="update-affected-workflows"></a>
 
 ## Steps for affected workflows
 
-If you have to use the Gmail connector with a Gmail consumer account and Google non-approved connectors in a logic app, you can create your own Google app for personal or internal use in your enterprise. For this scenario, here are the high-level steps that you need to take:
+If you have to use the Gmail connector with a Gmail consumer account and Google nonapproved connectors in a logic app workflow, you can create your own Google app for personal or internal use in your enterprise. For this scenario, follow these high-level steps:
 
 1. Create a Google client app by using the [Google API Console](https://console.developers.google.com).
 
@@ -74,44 +78,49 @@ For more information, see the [Gmail connector's technical reference documentati
 
 ### Create Google client app
 
-To set up a project for your client app, use the [Google API Console wizard](https://console.developers.google.com/start/api?id=gmail&credential=client_key) and follow the instructions. Or, for detailed steps, review the instructions in the [Gmail connector's technical reference documentation](/connectors/gmail/#authentication-and-bring-your-own-application).
+To set up a project for your client app, use the [Google API Console wizard](https://console.developers.google.com/start/api?id=gmail&credential=client_key) and follow the instructions. Or, see the [Gmail connector's technical reference documentation](/connectors/gmail/#authentication-and-bring-your-own-application).
 
-When you're done, your screen looks like this example except you'll have your own **Client ID** and **Client secret** values, which you later use in your logic app.
+When you're done, your screen looks like this example except that you have your own **Client ID** and **Client secret** values, which you later use in your workflow.
 
-![Client ID and client secret for your Google client app](./media/connectors-google-data-security-privacy-policy/google-api-console.png)
+:::image type="content" source="./media/connectors-google-data-security-privacy-policy/google-api-console.png" alt-text="Screenshot shows the Google API's partner site with client ID and client secret for your Google client app.":::
 
-### Use client app settings in logic app
+### Configure client app settings in logic app workflow
 
 To use the client ID and client secret from your Google client app in your Gmail trigger or action, follow these steps:
 
-1. In the [Azure portal](https://portal.azure.com), open your logic app in the Logic App Designer.
+1. In the [Azure portal](https://portal.azure.com), open your logic app resource.
+
+1. Open your workflow in the designer.
+
+   If you're adding a new Gmail trigger or action and creating an entirely new connection, skip ahead to providing the connection information.
+
+1. In the Gmail trigger or action, select **Change connection** or select **Connections** in the toolbar, and then select **Reassign**.
 
-1. If you're adding a new Gmail trigger or action and creating an entirely new connection, continue to the next step. Otherwise, in the Gmail trigger or action, select **Change connection** > **Add new**, for example:
+1. In **Change connection**, select **Add new**:
 
-   ![Select "Change connection" > "Add new"](./media/connectors-google-data-security-privacy-policy/change-gmail-connection.png)
+   :::image type="content" source="./media/connectors-google-data-security-privacy-policy/change-gmail-connection.png" alt-text="Screenshot shows the Change connection page where you can add a new connection.":::
 
-1. Provide your connection information, for example:
+1. Enter a name for the connection and then provide your connection information: 
 
-   ![Provide connection information](./media/connectors-google-data-security-privacy-policy/authentication-type-bring-your-own.png)
+   :::image type="content" source="./media/connectors-google-data-security-privacy-policy/authentication-type-bring-your-own.png" alt-text="Screenshot shows the Create connection page.":::
 
    | Property | Value | Description |
    |----------|-------|-------------|
-   | **Authentication Type** | **Bring your own application** | Specifies that you'll use your own client app for authentication. |
+   | **Authentication Type** | **Bring your own application** | Specifies that you use your own client app for authentication. |
    | **Client ID** | <*client-ID*> | The client ID from your Google client app |
    | **Client Secret** | <*client-secret*> | The client secret from your Google client app |
-   ||||
 
 1. When you're done, select **Sign in**.
 
-   A page appears that shows the client app that you created. If you're using a Gmail consumer account, you might get a page that show your client app isn't verified by Google and prompts you to first allow access to your Google account.
+   A page appears that shows the client app that you created. If you're using a Gmail consumer account, you might get a page that shows that Google can't verify your client app. Google prompts you to first allow access to your Google account.
 
-   ![Prompt for access to your Google account](./media/connectors-google-data-security-privacy-policy/allow-access-authorized-domain.png)
+   :::image type="content" source="./media/connectors-google-data-security-privacy-policy/allow-access-authorized-domain.png" alt-text="Screenshot shows the prompt for access to your Google account.":::
 
 1. If necessary, select **Allow**.
 
    You can now use the Gmail connector without restrictions in your logic app.
 
-## Next steps
+## Related content
 
-* Learn more about the [Gmail connector](/connectors/gmail/)
+- Learn more about the [Gmail connector](/connectors/gmail/)