Azure Data Factory (ADF) Google Drive Connector

In this article you will learn how to integrate Google Drive data to Azure Data Factory (ADF) without coding in just a few clicks (live / bi-directional connection to Google Drive). Read / write Google Drive data inside your app; perform many Google Drive operations without coding, just using easy to use high performance API Connector for Google Drive.

Using Google Drive Connector you will be able to connect, read, and write data from within Azure Data Factory (ADF). Follow the steps below to see how we would accomplish that.

Download  Help File  Buy 

Create ODBC Data Source (DSN) based on ZappySys API Driver

To get data from GoogleDrive using Azure Data Factory (ADF) we first need to create a DSN (Data Source) which will access data from GoogleDrive. We will later be able to read data using Azure Data Factory (ADF). Perform these steps:

  1. Install ZappySys ODBC PowerPack.

  2. Open ODBC Data Sources (x64):
    Open ODBC Data Source

  3. Create a System Data Source (System DSN) based on ZappySys API Driver

    ZappySys API Driver
    Create new System DSN for ZappySys API Driver
    You should create a System DSN (instead of a User DSN) if the client application is launched under a Windows System Account, e.g. as a Windows Service. If the client application is 32-bit (x86) running with a System DSN, use ODBC Data Sources (32-bit) instead of the 64-bit version. Furthermore, a User DSN may be created instead, but then you will not be able to use the connection from Windows Services (or any application running under a Windows System Account).
  4. When the Configuration window appears give your data source a name if you haven't done that already, then select "Google Drive" from the list of Popular Connectors. If "Google Drive" is not present in the list, then click "Search Online" and download it. Then set the path to the location where you downloaded it. Finally, click Continue >> to proceed with configuring the DSN:

    GoogleDriveDSN
    Google Drive
    ODBC DSN Template Selection

  5. Now it's time to configure the Connection Manager. Select Authentication Type, e.g. Token Authentication. Then select API Base URL (in most cases, the default one is the right one). More info is available in the Authentication section.

    Steps to get Google Drive Credentials

    To make this work you will have to create an OAuth application. To register an App, perform the following steps (Detailed steps found in the help link at the end):

    1. Go to Google API Console
    2. From the Project Dropdown (usually found at the top bar) click Select Project
    3. On Project Propup click CREATE PROJECT
    4. Once project is created you can click Select Project to switch the context (You can click on Notification link or Choose from Top Dropdown)
    5. Click ENABLE APIS AND SERVICES
    6. Now we need to enable Google Drive API.
    7. Search Google Drive API. Select and click ENABLE
    8. Go to back to main screen of Google API Console
    9. Click OAuth Concent Screen Tab. Enter necessary details and Save.
    10. Click Credentials Tab
    11. Click CREATE CREDENTIALS (some where in topbar) and select OAuth Client ID option.
    12. When prompted Select Application Type as Desktop App and click Create to receive your ClientID and Secret. You can use this information now to configure Connection with UseCustomApp=true.

    Fill in all required parameters and set optional parameters if needed:

    GoogleDriveDSN
    Google Drive
    User Account [OAuth]
    https://www.googleapis.com/
    Required Parameters
    UseCustomApp Fill in the parameter...
    Optional Parameters
    ClientId Fill in the parameter...
    ClientSecret Fill in the parameter...
    Scope Fill in the parameter...
    RetryMode Fill in the parameter...
    RetryStatusCodeList Fill in the parameter...
    RetryCountMax Fill in the parameter...
    RetryMultiplyWaitTime Fill in the parameter...
    ODBC DSN Oauth Connection Configuration
    Steps to get Google Drive Credentials
    Use these steps to authenticate as service account rather than Google / GSuite User. Learn more about service account here

    Basically to call Google API as Service account we need to perform following steps listed in 3 sections (Detailed steps found in the help link at the end)

    Create Project

    First thing is create a Project so we can call Google API. Skip this section if you already have Project (Go to next section)
    1. Go to Google API Console
    2. From the Project Dropdown (usually found at the top bar) click Select Project
    3. On Project Propup click CREATE PROJECT
    4. Once project is created you can click Select Project to switch the context (You can click on Notification link or Choose from Top Dropdown)
    5. Click ENABLE APIS AND SERVICES
    6. Now we need to Enable two APIs one by one (Drive API).
    7. Search Drive. Select and click ENABLE

    Create Service Account

    Once Project is created and APIs are enabled we can now create a service account under that project. Service account has its ID which looks like some email ID (not to confuse with Google /Gmail email ID)
    1. Go to Create Service Account
    2. From the Project Dropdown (usually found at the top bar) click Select Project
    3. Enter Service account name and Service account description
    4. For Role, do not select anything for now and Click Continue and then click Done. Next we will create Key.

    Create Key

    Once service account is created we need to create key file (i.e. credentials).
    1. In the Cloud Console, click the email address for the service account that you created.
    2. Click Keys.
    3. Click Add key, then click Create new key.
    4. Click Create and select P12 format. A P12 key file is downloaded to your computer. We will use this file in our API connection.
    5. Click Close.
    6. Now you may use downloaded *.p12 key file as secret file and Service Account Email as Client ID (e.g. some-service-account-name@your-project-id.iam.gserviceaccount.com ).

    Add Permission

    Now last thing is give read/write permission to Service Account. Basically you can create or open Google Sheet and add the Service Account as an editor to it as below.
    1. Copy the email address of your service account we created in previous step (its usually like this some-service-account-name@your-project-id.iam.gserviceaccount.com).
    2. Create or select an existing Google Docs File.
    3. Navigate to Google Docs File for which you like to give read/write access to Service Account.
    4. Click on the Share button in the top right, and add the email address of the service account as an editor. Here is how to share file(s) with specific people. Juse share with Service Account (use Service Account Email found on previous section)

    Fill in all required parameters and set optional parameters if needed:

    GoogleDriveDSN
    Google Drive
    Service Account (Using Private Key File) [OAuth]
    https://www.googleapis.com/
    Required Parameters
    Service Account Email Fill in the parameter...
    Service Account Private Key Path (i.e. *.p12) Fill in the parameter...
    Optional Parameters
    Scope Fill in the parameter...
    RetryMode Fill in the parameter...
    RetryStatusCodeList Fill in the parameter...
    RetryCountMax Fill in the parameter...
    RetryMultiplyWaitTime Fill in the parameter...
    ODBC DSN Oauth Connection Configuration

  6. Once the data source has been configured, you can preview data. Select the Preview tab and use settings similar to the following to preview data:
    ODBC ZappySys Data Source Preview

  7. Click OK to finish creating the data source.

Read data in Azure Data Factory (ADF) from ODBC datasource (Google Drive)

  1. To start press New button:

    Create new Self-Hosted integration runtime
  2. Select "Azure, Self-Hosted" option:

    Create new Self-Hosted integration runtime
  3. Select "Self-Hosted" option:

    Create new Self-Hosted integration runtime
  4. Set a name, we will use "OnPremisesRuntime":

    Set a name for IR
  5. Download and install Microsoft Integration Runtime.

  6. Launch Integration Runtime and copy/paste Authentication Key from Integration Runtime configuration in Azure Portal:

    Copy/paste Authentication Key
  7. After finishing registering the Integration Runtime node, you should see a similar view:

    Check Integration Runtime node status
  8. Go back to Azure Portal and finish adding new Integration Runtime. You should see it was successfully added:

    Integration Runtime status
  9. Go to Linked services section and create a new Linked service based on ODBC:

    Add new Linked service
  10. Select "ODBC" service:

    Add new ODBC service
  11. Configure new ODBC service. Use the same DSN name we used in the previous step and copy it to Connection string box:

    GoogleDriveDSN
    DSN=GoogleDriveDSN
    Configure new ODBC service
  12. For created ODBC service create ODBC-based dataset:

    Add new ODBC dataset
  13. Go to your pipeline and add Copy data connector into the flow. In Source section use OdbcDataset we created as a source dataset:

    Set source in Copy data
  14. Then go to Sink section and select a destination/sink dataset. In this example we use precreated AzureBlobStorageDataset which saves data into an Azure Blob:

    Set sink in Copy data
  15. Finally, run the pipeline and see data being transferred from OdbcDataset to your destination dataset:

    Run the flow

Create Custom Store Procedure in ZappySys Driver

You can create procedures to encapsulate custom logic and then only pass handful parameters rather than long SQL to execute your API call.

Steps to create Custom Store Procedure in ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here

  1. Go to Custom Objects Tab and Click on Add button and Select Add Procedure:
    ZappySys Driver - Add Store Procedure

  2. Enter the desired Procedure name and click on OK:
    ZappySys Driver - Add Store Procedure Name

  3. Select the created Store Procedure and write the your desired store procedure and Save it and it will create the custom store procedure in the ZappySys Driver:
    Here is an example stored procedure for ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here

    CREATE PROCEDURE [usp_get_orders]
        @fromdate = '<<yyyy-MM-dd,FUN_TODAY>>'
     AS
        SELECT * FROM Orders where OrderDate >= '<@fromdate>';
    

    ZappySys Driver - Create Custom Store Procedure

  4. That's it now go to Preview Tab and Execute your Store Procedure using Exec Command. In this example it will extract the orders from the date 1996-01-01:

    Exec usp_get_orders '1996-01-01';

    ZappySys Driver - Execute Custom Store Procedure

  5. Let's generate the SQL Server Query Code to make the API call using store procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
    As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.

    SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC usp_get_orders @fromdate=''1996-07-30''')

    ZappySys Driver - Generate SQL Server Query

  6. Now go to SQL served and execute that query and it will make the API call using store procedure and provide you the response.
    ZappySys Driver - Generate SQL Server Query

Create Custom Virtual Table in ZappySys Driver

ZappySys API Drivers support flexible Query language so you can override Default Properties you configured on Data Source such as URL, Body. This way you don't have to create multiple Data Sources if you like to read data from multiple EndPoints. However not every application support supplying custom SQL to driver so you can only select Table from list returned from driver.

If you're dealing with Microsoft Access and need to import data from an SQL query, it's important to note that Access doesn't allow direct import of SQL queries. Instead, you can create custom objects (Virtual Tables) to handle the import process.

Many applications like MS Access, Informatica Designer wont give you option to specify custom SQL when you import Objects. In such case Virtual Table is very useful. You can create many Virtual Tables on the same Data Source (e.g. If you have 50 URLs with slight variations you can create virtual tables with just URL as Parameter setting.

  1. Go to Custom Objects Tab and Click on Add button and Select Add Table:
    ZappySys Driver - Add Table

  2. Enter the desired Table name and click on OK:
    ZappySys Driver - Add Table Name

  3. And it will open the New Query Window Click on Cancel to close that window and go to Custom Objects Tab.

  4. Select the created table, Select Text Type AS SQL and write the your desired SQL Query and Save it and it will create the custom table in the ZappySys Driver:
    Here is an example SQL query for ZappySys Driver. You can insert Placeholders also. Read more about placeholders here

    SELECT
      "ShipCountry",
      "OrderID",
      "CustomerID",
      "EmployeeID",
      "OrderDate",
      "RequiredDate",
      "ShippedDate",
      "ShipVia",
      "Freight",
      "ShipName",
      "ShipAddress",
      "ShipCity",
      "ShipRegion",
      "ShipPostalCode"
    FROM "Orders"
    Where "ShipCountry"='USA'

    ZappySys Driver - Create Custom Table

  5. That's it now go to Preview Tab and Execute your custom virtual table query. In this example it will extract the orders for the USA Shipping Country only:

    SELECT * FROM "vt__usa_orders_only"

    ZappySys Driver - Execute Custom Virtual Table Query

  6. Let's generate the SQL Server Query Code to make the API call using store procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
    As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.

    SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC [usp_get_orders] ''1996-01-01''')

    ZappySys Driver - Generate SQL Server Query

  7. Now go to SQL served and execute that query and it will make the API call using store procedure and provide you the response.
    ZappySys Driver - Generate SQL Server Query

Conclusion

In this article we discussed how to connect to Google Drive in Azure Data Factory (ADF) and integrate data without any coding. Click here to Download Google Drive Connector for Azure Data Factory (ADF) and try yourself see how easy it is. If you still have any question(s) then ask here or simply click on live chat icon below and ask our expert (see bottom-right corner of this page).

Download Google Drive Connector for Azure Data Factory (ADF) Documentation 

Actions supported by Google Drive Connector

Google Drive Connector support following actions for REST API integration. If some actions are not listed below then you can easily edit Connector file and enhance out of the box functionality.
 Get drive info
Gets drive information    [Read more...]
 Search items
Lists items (i.e. files / folders) with search criteria    [Read more...]
 List folders
Lists folders    [Read more...]
Parameter Description
PageSize
Search Criteria
 List files
Lists files    [Read more...]
Parameter Description
PageSize
Search Criteria Data filter (e.g. somecolumn -eq &#39;somevalue&#39; ) , User can select multiple filter criteria using &#39;AND&#39;,&#39;OR&#39; operator , Note*:- please refer the link for more filter criteria : https://zappysys.com/links?url=https://developers.google.com/drive/api/guides/search-files
Option Value
none
Allow only shared files and folders sharedWithMe=true
Skip trashed files trashed=false
Skip Folders mimeType!=&#39;application/vnd.google-apps.folder&#39;
Skip App Script mimeType!=&#39;application/vnd.google-apps.script&#39;
Search for file name name=&#39;enter the filename here&#39;
Search for full text fullText contains &#39;enter the fullText here&#39;
Search for spreadsheet mimeType = &#39;application/vnd.google-apps.spreadsheet&#39;
Search for multiple files type mimeType contains &#39;application/vnd.google-apps.spreadsheet&#39; OR mimeType contains &#39;application/vnd.google-apps.document&#39; OR mimeType contains &#39;application/vnd.google-apps.presentation&#39; OR mimeType contains &#39;application/vnd.google-apps.drawing&#39;
 List deleted files
Lists files    [Read more...]
Parameter Description
PageSize
Search Criteria
 Get file info
Gets information of a file    [Read more...]
Parameter Description
Id Id of a file you want to see information for
 Download a file
Downloads a file    [Read more...]
Parameter Description
File Id Id of a file you want to download
 Export a file
Export a document editor files such document, Spreadsheets, Drawings, Presentations, Apps Scripts to common file formats as defined in this link https://developers.google.com/drive/api/guides/ref-export-formats    [Read more...]
Parameter Description
File Id Id of a file you want to export and file must be editor type (e.g. document, Spreadsheets, Drawings, Presentations, Apps Scripts)
Export As (Mime Type) The MIME type of the format requested for this export.
Option Value
None
Export to PDF application/pdf
Export to HTML text/html
Export to HTML (zipped) application/zip
Export to Plain text text/plain
Export to Rich text application/rtf
Export to Open Office doc application/vnd.oasis.opendocument.text
Export to MS Word document application/vnd.openxmlformats-officedocument.wordprocessingml.document
Export to EPUB application/epub+zip
Export to MS Excel application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
Export to Open Office sheet application/x-vnd.oasis.opendocument.spreadsheet
Export to (sheet only) text/tab-separated-values
Export to JPEG image/jpeg
Export to PNG image/png
Export to SVG image/svg+xml
Export to MS PowerPoint application/vnd.openxmlformats-officedocument.presentationml.presentation
Export to Open Office presentation application/vnd.oasis.opendocument.presentation
Export to JSON application/vnd.google-apps.script+json
fields fields
 Upload a file
Uploads a file    [Read more...]
Parameter Description
FileName A filename the file will have in Google Drive
DiskFilePath Specify a disk file path
ParentFolderId Id of a parent folder you want to upload the file in. Use value &#39;root&#39; to place the file in the topmost level.
KeepRevisionForever Defines whether uploaded file has revisions
AddParents A comma-separated list of parent IDs to add
OcrLanguage A language hint for OCR processing during image import (ISO 639-1 code).
UseContentAsIndexableText Whether to use the uploaded content as indexable text.
 Create a folder
Creates a folder    [Read more...]
Parameter Description
Name A folder name the folder will have in Google Drive
ParentFolderId Id of a parent folder you want to create the folder in. Use value &#39;root&#39; to create the folder in the topmost level.
 Delete an item
Deletes an item    [Read more...]
 Duplicate a file
Duplicates a file    [Read more...]
Parameter Description
Id Id of a file you want to duplicate
 Update a file
Update file    [Read more...]
Parameter Description
Id Id of a file you want to update
DiskFilePath A disk file path you want to update file contents with
KeepRevisionForever Defines whether uploaded file has revisions
AddParents A comma-separated list of parent IDs to add
OcrLanguage A language hint for OCR processing during image import (ISO 639-1 code).
UseContentAsIndexableText Whether to use the uploaded content as indexable text.
 Update metadata in a file
Updates meta-data in a file    [Read more...]
Parameter Description
Id Id of a file you want to update meta-data to
KeepRevisionForever Defines whether uploaded file has revisions
Option Value
True True
False False
AddParents A comma-separated list of parent IDs to add
OcrLanguage A language hint for OCR processing during image import (ISO 639-1 code).
UseContentAsIndexableText Whether to use the uploaded content as indexable text.
 Empty trash
Empties trash    [Read more...]
 Delete all items
Deletes all items from the drive    [Read more...]
 Generic Request
This is generic endpoint. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL.    [Read more...]
Parameter Description
Url API URL goes here. You can enter full URL or Partial URL relative to Base URL. If it is full URL then domain name must be part of ServiceURL or part of TrustedDomains
Body Request Body content goes here
IsMultiPart Check this option if you want to upload file(s) (i.e. POST RAW file data) or send data using Multi-Part encoding method (i.e. Content-Type: multipart/form-data). Multi-Part request allows you to mix key/value and upload files in same request. On the other hand raw upload allows only single file upload (without any key/value) ==== Raw Upload (Content-Type: application/octet-stream) ===== To upload single file in raw mode check this option and specify full file path starting with @ sign in the Body (e.g. @c:\data\myfile.zip ) ==== Form-Data / Multipart Upload (Content-Type: multipart/form-data) ===== To treat your Request data as multi part fields you must specify key/value pairs separated by new lines into RequestData field (i.e. Body). Each key value pair is entered on new-line and key/value are separated using equal sign (=). Preceding and trailing spaces are ignored also blank lines are ignored. If field value has some any special character(s) then use escape sequence (e.g. For NewLine: \r\n, For Tab: \t, For at (@): \@). When value of any field starts with at sign (@) its automatically treated as File you want to upload. By default file content type is determined based on extension however you can supply content type manually for any field using this way [ YourFileFieldName.Content-Type=some-content-type ]. By default File Upload Field always includes Content-Type in the request (non file fields do not have content-type by default unless you supply manually). For some reason if you dont want to use Content-Type header in your request then supply blank Content-Type to exclude this header altogather [e.g. SomeFieldName.Content-Type= ]. In below example we have supplied Content-Type for file2 and SomeField1, all other fields are using default content-type. See below Example of uploading multiple files along with additional fields. If some API requires you to pass Content-Type: multipart/form-data rather than multipart/form-data then manually set Request Header =&gt; Content-Type: multipart/mixed (it must starts with multipart/ else will be ignored). file1=@c:\data\Myfile1.txt file2=@c:\data\Myfile2.json file2.Content-Type=application/json SomeField1=aaaaaaa SomeField1.Content-Type=text/plain SomeField2=12345 SomeFieldWithNewLineAndTab=This is line1\r\nThis is line2\r\nThis is \ttab \ttab \ttab SomeFieldStartingWithAtSign=\@MyTwitterHandle
Filter Enter filter to extract array from response. Example: $.rows[*] --OR-- $.customers[*].orders[*]. Check your response document and find out hierarchy you like to extract
Headers Headers for Request. To enter multiple headers use double pipe or new line after each {header-name}:{value} pair

Google Drive Connector Examples for Azure Data Factory (ADF) Connection

This page offers a collection of SQL examples designed for seamless integration with the ZappySys API ODBC Driver under ODBC Data Source (36/64) or ZappySys Data Gateway, enhancing your ability to connect and interact with Prebuilt Connectors effectively.

Get drive information    [Read more...]

Gets drive information

SELECT *
  FROM Drive

Dowload a file    [Read more...]

Downloads a file

SELECT * FROM download_file
  WITH(Id='1PpE2eSi5faAnMwiSolwr34zA5MwOdR3D'	
      ,ResponseDataFile='C:\MyFiles\myfile.ext'
  )
  --You can get file Id by selecting from 'list_files' endpoint

Get file list    [Read more...]

Downloads a file

SELECT * FROM Files

Update a file    [Read more...]

Updates a file

UPDATE Files
  WITH (Id='1EVzXFVBQIh3LcJvfcLhI1UWhW3qUxFkM'
  ,DiskFilePath='C:\MyFiles\myfile.ext')
  --You can get file Id by selecting from 'list_files' endpoint

Delete a file    [Read more...]

Deletes a file

DELETE FROM Files
  WITH (Id='1gcu0hV34OTfgvcu9CFhr7Go4b35j5Mop')
  --You can get file Id by selecting from 'list_files' endpoint

Upload a file    [Read more...]

Uploads a file

INSERT INTO Files
  WITH (FileName='My filename'
      ,DiskFilePath='C:\MyFolder\Mymyfile.ext'
      ,ParentFolderId='root')
  --You can get ParentFolderId by selecting from 'list_folders' endpoint or just use 'root'

Delete a folder    [Read more...]

Deletes a folder

DELETE FROM Folders
  WITH (Id='1yDO11prsLH9DUrBTCadV6GGMJrITjF9I')
  --You can get folder Id by selecting from 'list_folders' endpoint

Create a folder    [Read more...]

Creates a folder

INSERT INTO Folders
  WITH (Name='My folder name'
      ,ParentFolderId='root')
  --You can get ParentFolderId by selecting from 'list_folders' endpoint or just use 'root'

Get file information    [Read more...]

Gets file information

SELECT * FROM FileInfo
  WITH (Id='1EVzXFVBQIh3LcJvfcLhI1UWhW3qUxFkM')
  --You can get file Id by selecting from 'list_files' endpoint

Get items list    [Read more...]

Gets items list

SELECT * FROM ItemsList

Get items list using query    [Read more...]

Gets items list using query

SELECT Id, Kind, Name, MimeType
  FROM list_items
  WITH (Query = 'name contains ''.txt''')

Get files list    [Read more...]

Gets files list

SELECT * FROM FilesList

Get folders list    [Read more...]

Gets folders list

SELECT * FROM FoldersList

Select from trash    [Read more...]

Shows deleted items in Trash

SELECT * FROM Trash

Empty trash bin    [Read more...]

Empties trash bin

DELETE FROM Trash

Export File    [Read more...]

Export a Google files to know other format

SELECT "Status" FROM export_file
				WITH(
					  Id='1j0HFOP4gsoE-Zbf2xN3IsPSj8wgwNtIfyyvM1_BWkW4'
					, ExportAs='application/pdf'
				))
			 --You can export files from 'export_file' endpoint

Other App Integration scenarios for Google Drive

Other Connectors for Azure Data Factory (ADF)


Download Google Drive Connector for Azure Data Factory (ADF) Documentation 

  • How to connect Google Drive in Azure Data Factory (ADF)?

  • How to get Google Drive data in Azure Data Factory (ADF)?

  • How to read Google Drive data in Azure Data Factory (ADF)?

  • How to load Google Drive data in Azure Data Factory (ADF)?

  • How to import Google Drive data in Azure Data Factory (ADF)?

  • How to pull Google Drive data in Azure Data Factory (ADF)?

  • How to push data to Google Drive in Azure Data Factory (ADF)?

  • How to write data to Google Drive in Azure Data Factory (ADF)?

  • How to POST data to Google Drive in Azure Data Factory (ADF)?

  • Call Google Drive API in Azure Data Factory (ADF)

  • Consume Google Drive API in Azure Data Factory (ADF)

  • Google Drive Azure Data Factory (ADF) Automate

  • Google Drive Azure Data Factory (ADF) Integration

  • Integration Google Drive in Azure Data Factory (ADF)

  • Consume real-time Google Drive data in Azure Data Factory (ADF)

  • Consume realtime Google Drive API data in Azure Data Factory (ADF)

  • Google Drive ODBC Driver | ODBC Driver for Google Drive | ODBC Google Drive Driver | SSIS Google Drive Source | SSIS Google Drive Destination

  • Connect Google Drive in Azure Data Factory (ADF)

  • Load Google Drive in Azure Data Factory (ADF)

  • Load Google Drive data in Azure Data Factory (ADF)

  • Read Google Drive data in Azure Data Factory (ADF)

  • Google Drive API Call in Azure Data Factory (ADF)