Yavda — Client Onboarding

How will Power BI be managed for this client?

This determines whether the client needs to bring their own Microsoft Azure account, or whether Yavda handles everything on their behalf.

🏢

Yavda manages Power BI

The client does not need a Microsoft Azure account. Yavda's service principal embeds reports on their behalf. Ideal for Google Workspace, startups, and non-Microsoft shops.

Recommended for most clients

🔑

Client owns Power BI

The client has their own Microsoft Azure tenant and Power BI workspace. They provide their Azure Tenant ID and Yavda embeds reports using their service principal.

Requires Microsoft Azure tenant

Have a config file? Upload it to pre-fill the form.

📄

Drop a config file here or click to browse

Supports .json · .txt key=value · .env

✅ File loaded — fields pre-filled

Show expected file format

key=value (.txt / .env)

slug=client1
organizationName=Yavda
domain=yavda.com
primaryColor=#2356C8
secondaryColor=#1a3f99
# For CUSTOMER_OWNED only:
azureTenantId=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

JSON (.json)

{
  "slug": "client1",
  "organizationName": "Yavda",
  "domain": "yavda.com",
  "powerBiOwnershipMode": "VENDOR_OWNED",
  "branding": { "primaryColor": "#2356C8", "secondaryColor": "#1a3f99" }
}

Portal ready to launch

Your client's internal portal ID

Internal Tenant ID (Cosmos DB partition key)

—

Permanent ID for this client across all Yavda systems, derived from their email domain.

Add to config/clients.json

Build & publish command (run from repo root)

🌐 Domain & DNS

Portal URL —

DNS propagates in 1–5 minutes. The portal goes live after npm run publish:client.

Your client's internal portal ID

Add to config/clients.json

Build & publish command (run from repo root)

🌐 Domain & DNS

Infrastructure provisioning detail

Download config

Next steps