Skip to content

Commit e4d103d

Browse files
committed
Remove duplicate info and point at Gmail connector doc
1 parent 9309bf9 commit e4d103d

File tree

1 file changed

+7
-11
lines changed

1 file changed

+7
-11
lines changed

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

Lines changed: 7 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -29,15 +29,15 @@ If you have logic apps that use the Gmail connector, you'll receive an email abo
2929

3030
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:
3131

32-
* Logic Apps built-in triggers and actions: Control, Data Operations, Date Time, Liquid, Request, Schedule, Variables, and XML
32+
* Logic Apps built-in triggers and actions: Batch, Control, Data Operations, Date Time, Flat File, Liquid, Request, Schedule, Variables, and XML
3333

3434
* Google services: Gmail, Google Calendar, Google Contacts, Google Drive, Google Sheets, and Google Tasks
3535

3636
* Approved Microsoft services: Dynamics 365, Excel Online, Microsoft Teams, Office 365, OneDrive, and SharePoint Online
3737

3838
* Connectors for customer-managed data sources: FTP, HTTP, RSS, SFTP, SMTP, and SQL Server
3939

40-
For detailed and the most recent information, see the [Gmail connector's technical reference documentation](https://docs.microsoft.com/connectors/gmail/).
40+
For the most recent information, see the [Gmail connector's technical reference documentation](https://docs.microsoft.com/connectors/gmail/).
4141

4242
<a name="update-affected-workflows"></a>
4343

@@ -49,19 +49,15 @@ If you have to use the Gmail connector with a Gmail consumer account and Google
4949

5050
1. In your Gmail connector, use the client ID and client secret values from your Google client app.
5151

52-
### Create Google client app
53-
54-
1. To create this app, use the [Google API Console wizard](https://console.developers.google.com/start/api?id=gmail&credential=client_key) and follow the instructions. For detailed steps, review the instructions in the [Gmail connector's technical reference documentation](https://docs.microsoft.com/connectors/gmail/).
52+
For more information, see the [Gmail connector's technical reference documentation](https://docs.microsoft.com/connectors/gmail/#authentication-and-bring-your-own-application).
5553

56-
1. Provide these values when required:
54+
### Create Google client app
5755

58-
* Gmail scope: `https://mail.google.com`
59-
* Authorized domain: `azure-apim.net`
60-
* Redirect URI: `https://global.consent.azure-apim.net/consent`
56+
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](https://docs.microsoft.com/connectors/gmail/#authentication-and-bring-your-own-application).
6157

62-
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.
58+
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.
6359

64-
![Client ID and client secret for your Google client app](./media/connectors-google-data-security-privacy-policy/google-api-console.png)
60+
![Client ID and client secret for your Google client app](./media/connectors-google-data-security-privacy-policy/google-api-console.png)
6561

6662
### Use client app settings in logic app
6763

0 commit comments

Comments
 (0)