Connections | Yarken Help

Use Connections to securely connect Yarken to supported cloud storage providers, APIs, and external applications. Each connection stores the credentials and configuration Yarken needs to access the source. You can reuse a connection across supported pipelines and automation workflows.

Go to Admin > Pipelines > Connections to work with BASIC and ADVANCED connections.

Creating a connection does not load data by itself. A pipeline or automation must use the connection before data can enter Yarken.

What you can do

Connect Yarken to supported cloud storage providers and APIs.
Reuse approved credentials across supported pipelines and automation workflows.
Use consent-based authorization for supported APIs.
Test connection details before you save them.
Update credentials when keys, secrets, or authorizations change.
Review Advanced Connection authorization status.
Remove connections that are no longer required.

Before you begin

You must have the Admin or Cost Model Manager role to manage Connections and Pipelines.
Collect the required credentials, permissions, and source-system details before you start.
For an Advanced Connection, confirm that Yarken has enabled the required integration for your environment.

Store and rotate credentials according to your organization's security requirements. Test a connection again after you change any credential.

Connection and pipeline responsibilities

Component	What it does
Connection	Defines how Yarken authenticates to and communicates with the source system.
Pipeline	Uses a connection to retrieve, map, schedule, and process data.
Advanced Integration	Uses an authorized Advanced Connection to retrieve and process supported provider data through a Yarken-managed integration.

A BASIC connection can be reused across multiple supported pipelines when the source and access requirements are the same. Advanced Connections are managed within the applicable Advanced Integration.

Choose BASIC or ADVANCED

Method	Use it when	Who configures it
BASIC	You need a native Yarken connection for supported cloud storage or API ingestion.	Your Yarken administrator or Cost Model Manager creates and manages the connection.
ADVANCED	You need a Yarken-managed integration or provider-specific workflow enabled for your environment.	Yarken creates the connection during implementation. Your administrator authorizes and maintains it.

BASIC connections

Select the BASIC tab to create and manage native Yarken connections.

Supported BASIC connection types

Connection type	Category	Setup method	Important behavior
Azure Blob Storage	Cloud storage	Manual	Supports Account Key and Service Principal authentication.
AWS S3	Cloud storage	Manual	Requires access details for the source bucket.
Google Storage	Cloud storage	Manual	Requires access details for the Google Cloud Storage bucket.
Microsoft Graph API	API	Consent flow or manual	The consent flow can create the connection and associated pipeline automatically.
Power BI API	API	Consent flow or manual	Requires Power BI tenant and service principal configuration.
Google API	API	Consent flow	Manual creation is not supported.
Google Reseller API	API	Consent flow	Uses the supported consent process and can create the associated pipeline automatically.

Create a BASIC connection

Use Create BASIC connections for provider-specific prerequisites, authentication requirements, and step-by-step procedures.

Authentication methods

The available authentication method depends on the connection type.

Platform Credentials — Uses the supported consent flow for Microsoft Graph API and Power BI API.
Custom Credentials — Lets you enter Microsoft Entra application credentials manually for Microsoft Graph API and Power BI API.
Account Key or Service Principal — Available for Azure Blob Storage.
Access Key and Secret Key — Used by supported AWS S3 and Google Storage connections.

Microsoft Graph API, Power BI API, Google API, and Google Reseller API support the consent workflow.

CONNECT API — Sign in and grant permissions through the in-app authorization flow.
COPY CONSENT URL — Copy the authorization link and send it to the administrator who will grant consent.

When Auto create pipeline and fetch data instantly. is selected, Yarken creates the connection and its associated pipeline after consent and starts the initial data fetch.

For the complete procedure and provider-specific prerequisites, see Create BASIC connections.

ADVANCED connections

Select the ADVANCED tab to authorize and maintain connections used by Yarken-managed Advanced Integrations.

Yarken creates Advanced Connections during implementation. Your administrator authorizes the connections and maintains their authentication details.

Advanced Connections are available for the Advanced Integrations Yarken has enabled for your environment. See Advanced integrations for the current supported-integration list.

Advanced Connection statuses

Status	Meaning	Required action
Access requested	The connection still requires authorization.	Open the connection and complete the authentication process.
Connected	The connection is authorized and ready for use.	Continue to the applicable Advanced pipeline and validate the integration.

For detailed instructions, see Authorize Advanced Connections.

What happens next

Connection method	Next step
BASIC cloud storage	Create a Data Mapping Template, where required, and configure a cloud storage pipeline or Automate workflow.
BASIC API consent flow	Review the automatically created pipeline when the setup option was selected. Confirm its schedule and run status.
BASIC API manual setup	Create the required API pipeline manually.
ADVANCED	Confirm that every required connection is Connected, then review the applicable Advanced pipeline and use Run or activate it as required.

Connection best practices

Use dedicated service accounts for integrations.
Use short-lived credentials whenever the provider supports them.
Rotate credentials according to your organization's security policy.
Test every connection after a configuration change.
Remove unused connections to reduce maintenance and security risks.
Reuse an approved connection across supported pipelines instead of creating unnecessary duplicates.

Troubleshoot a connection

Issue	What to check
The connection test fails	Verify credentials, account or bucket details, provider permissions, and network access. Test again after correcting the configuration.
Authentication fails after the connection worked previously	Check for expired credentials, rotated secrets, revoked consent, or changed provider permissions.
An Advanced Connection remains Access requested	Complete the required authorization and confirm that the status changes to Connected.
A pipeline or Advanced Integration cannot reach the source	Verify that the required connection is valid and available. Reauthorize or retest the affected connection, then review the applicable pipeline status.
You cannot delete a BASIC connection	Identify any pipelines that reference the connection. Update or remove those pipelines first.
API consent was granted, but data is not available	Confirm that Yarken created the pipeline, review its status and run history, and verify that the required provider permissions were granted.

For more help, see Troubleshoot Pipelines and integrations and Troubleshoot Advanced Integrations.

Related content