Create API Connection using Consent URL
Prerequisites (Tenant-level)
-
For the Google API,
-
You must be a Google Workspace Super Admin for your domain.
-
The following APIs might be disabled as part of your Tenant's security compliance. Make sure they are enabled before integration:
-
Admin SDK API
-
Enterprise License Manager API
-
-
-
For Microsoft Graph and Power BI API, you should have
-
A Microsoft Entra (Azure AD) tenant.
-
A Global Administrator or Privileged Role Administrator to grant tenant-wide admin consent for application permissions.
-
A pre-configured admin user to configure the Pipelines for fetching app usage reports.
-
In Power BI-specific flows:
-
A Power BI Tenant Admin and the ability to change Tenant settings in the Power BI Admin portal.
-
Following special configurations. For more information, refer https://yarken.atlassian.net/wiki/x/B4A2Kg.
-
Create a Microsoft Entra Security Group (e.g., Power BI).
-
Add an application (e.g., Yarken Power BI) as a member to the Power BI group.
-
Enable the service principals access (read-only) in PBI Tenant Admin portal.
-
-
-
Procedure
Use the procedure below to create the API connections automatically for Microsoft Graph API, Power BI API, Google API, and Google Reseller API.
To create,
-
Navigate to Settings > Pipelines > Connections.
-
Click + NEW CONNECTION.
-
Choose any API connection Type, for example, Microsoft Graph API.
In the Authentication type, the Platform Credentials are auto-selected for Microsoft Graph and Power BI API.
-
Choose one of the options for configuring API:
-
Option 1, CONNECT API — allows you to immediately connect to API using in-app OAuth flow. The CONNECT API button name varies based on connection type you selected, for example, CONNECT MICROSOFT GRAPH API, CONNECT POWER BI API, or CONNECT GOOGLE API.
-
Click CONNECT button.
-
Sign in with the your cloud provider specific credential account and grant the requested permissions.
-
Once accepted, you will be redirected to Yarken, and the required permissions should have been granted.
-
-
Option 2, COPY CONSENT URL — allows you to copy and share the consent URL to authorize via email or another device. This option is ideal for team admins or offline setup.
-
Click COPY CONSENT URL.
-
Paste the URL into a browser on the other device (or send it to the admin who will perform consent).
-
Complete sign-in and grant admin consent.
-
Once accepted, you will be redirected to Yarken, and the required permissions should have been granted.
-
-
-
Verify that the option to create a pipeline and fetch data instantly is checked.
The application creates a connection and its associated pipeline.
Create API Connection manually
Note: The Google API connection cannot be created manually. It must be configured through a consent URL. Manual API connections are supported only for Microsoft Graph and Power BI.
Use the procedure below to create the API connections manually for Microsoft Graph and Power BI API.
Prerequisites
When creating an API connection manually, you must have:
-
Tenant Id, Client Id, and Client Secret
Procedure
To create,
-
Navigate to Settings > Pipelines > Connections.
-
Click + NEW CONNECTION.
-
Choose Microsoft Graph or Power BI API connection Type.
-
In the Authentication Type, select Custom Credentials from the drop-down list.
-
On Create a new connection dialog box, enter the details below:
-
Name: The name of the connection.
-
Tenant Id: The unique identifier of your Azure Active Directory tenant.
-
Tenant Name: The name of your Azure Active Directory tenant.
-
Client Id: The unique identifier for your Azure AD application (App Registration).
-
Client Secret: The secret key used to authenticate your application with the Microsoft Graph API.
-
-
Click TEST CONNECTION to validate credentials.
-
If the test passes, click SAVE.
Create Cloud Storage Connection (manual only)
Use this procedure to create cloud storage connections for Azure Blob Storage, AWS S3, and Google Cloud Storage. After a connection is created, you can use it when configuring a Cloud Storage Pipeline.
Prerequisites
Before you begin, ensure you have the required credentials for your cloud storage provider.
Azure Blob Storage
Yarken supports two authentication methods for Azure Blob Storage:
-
Account Key – Authenticates using the Azure Storage Account access key. This is the traditional method and is suitable when your organization uses storage account keys to access Azure Blob Storage.
-
Service Principal – Authenticates using Microsoft Entra ID application credentials. This method is recommended for organizations that use role-based access control (RBAC) and want to avoid sharing storage account keys. For information, refer Create an Azure Service Principal.
Choose one of the following authentication methods:
Account Key authentication
-
Storage Account Name
-
Storage Account Access Key
-
Container Name
Service Principal authentication
-
Storage Account Name
-
Tenant ID
-
Client ID
-
Client Secret
-
Container Name
AWS S3
-
Access Key
-
Secret Key
-
Bucket Name
-
(Optional) Region
For more information on how to retrieve AWS access keys, refer Retrieve AWS Access and Secret keys.
Google Cloud Storage
-
Access Key
-
Secret Key
-
Bucket Name
Procedure
To create a cloud storage connection:
-
Navigate to Settings > Pipelines > Connections.
-
Click + NEW CONNECTION.
-
Select the required Connection Type (for example, Azure Blob Storage, AWS S3, or Google Cloud Storage).
-
Enter the connection details.
The required fields vary depending on the selected connection type and authentication method.
Azure Blob Storage
Account Key authentication
Select Account Key as the Authentication type, then provide the following information.
|
Field |
Description |
|---|---|
|
Name |
A unique name for the connection. |
|
Account Name |
The Azure Storage Account name. |
|
Access Key |
The Azure Storage Account access key. |
|
Container Name |
The Azure Blob Storage container that stores the files. |
Service Principal authentication
Select Service Principal as the Authentication type, then provide the following information.
|
Field |
Description |
|---|---|
|
Name |
A unique name for the connection. |
|
Account Name |
The Azure Storage Account name. |
|
Tenant ID |
The Microsoft Entra ID tenant associated with the Azure subscription. |
|
Client ID |
The Application (Client) ID of the registered Microsoft Entra application. |
|
Client Secret |
The client secret generated for the Microsoft Entra application. |
|
Container Name |
The Azure Blob Storage container that stores the files. |
Ensure that the Service Principal has the required permissions to access the Azure Storage Account and container. Otherwise, the connection test and subsequent pipeline executions will fail.
AWS S3
|
Field |
Description |
|---|---|
|
Name |
A unique name for the connection. |
|
Access Key |
AWS access key used to authenticate the account. |
|
Secret Key |
AWS secret key associated with the access key. |
|
Bucket Name |
The S3 bucket containing the files. |
|
Region |
AWS region where the bucket is located. Leave blank to allow automatic detection during connection testing. |
Google Cloud Storage
|
Field |
Description |
|---|---|
|
Name |
A unique name for the connection. |
|
Access Key |
Google Cloud Storage access key. |
|
Secret Key |
Google Cloud Storage secret key. |
|
Bucket Name |
Google Cloud Storage bucket containing the files. |
-
Click TEST CONNECTION to verify that the credentials are valid.
-
If the connection test is successful, click SAVE.
The cloud storage connection is created and is available for use when configuring Cloud Storage Pipelines.
Next steps
Related content