Table of Contents
Azure Onboarding & Account Connection (New UI)
Azure Onboarding & Account Connection (New UI)
What’s changed with Azure onboarding?
Azure onboarding is now built directly into the Labra platform. You can connect your Azure and Partner Center settings in-app, without following the legacy onboarding guide.
Why do I need to connect my Azure / Partner Center account?
Connecting your account allows Labra to securely access Partner Center APIs to:
- Manage listings
- Create and manage Private Offers
- View revenue and payout data
Who can complete the Azure connection?
A Microsoft Partner Center Global Admin or Azure AD Admin must complete the setup to ensure the correct permissions are granted.
If you don’t have admin access, you’ll need to work with your organization’s admin to complete this step.
What information do I need to connect Azure in Labra?
You’ll be prompted to enter:
- Tenant ID – Your Azure Active Directory tenant identifier
- Client ID – From an Azure App Registration
- Client Secret – Generated for the App Registration
These details are entered directly in Labra during the cloud connection flow.
Do I need to give admin consent?
Yes. Admin consent is required so Labra can access Partner Center without repeated logins.
Without admin consent, certain actions—such as creating Private Offers—will fail.
Can I use an existing App Registration?
Yes. You can use an existing App Registration as long as it has the required API permissions enabled.
If not, you’ll need to update permissions or create a new registration.
What happens if my Client Secret expires?
If your Client Secret expires, you’ll need to:
- Generate a new Client Secret in Azure
- Update it in Labra
This ensures uninterrupted access to Partner Center.
Can I connect multiple Azure tenants?
Yes. If your organization manages multiple Azure tenants or publisher accounts, you can connect each one separately in Labra.
Does connecting Azure give Labra full control of my account?
No. Labra only accesses what’s required through secure APIs.
You retain full ownership and control of your Partner Center account at all times.
Private Offers
Why can’t I add custom dimensions directly to a Private Offer?
Azure Marketplace only allows dimensions (SKUs) that belong to an existing plan in your listing.
Dimensions must be defined at the plan level first, then selected when creating a Private Offer.
How do I support multiple SKUs in a Private Offer?
You have two supported approaches:
Option 1: Bundle SKUs under one private plan
Best if you consistently sell the same SKUs together.
- Create a single privately visible plan
- Include all relevant SKUs in that plan
- Select this plan when building the Private Offer
Option 2: Create separate private plans per SKU
Best if SKUs vary by deal.
- Each SKU lives in its own private plan
- Select only the relevant plan per Private Offer
- Pricing is fully controlled at the Private Offer level
Both options are supported and can be used in parallel.
How does acceptance work when multiple SKUs are involved?
Azure has an important buyer-side limitation:
- A customer can accept only one plan per Private Offer
Recommended approach (best practice):
- Create separate Private Offers, one per SKU
- The customer accepts each Private Offer individually
This is the cleanest and least error-prone setup and is generally recommended by Labra.
Alternative (supported but less ideal):
- Reusing a single Private Offer across SKUs
- This often causes confusion during acceptance and requires additional coordination
Which option should I choose?
- Choose bundled plans if your packaging is fixed across customers
- Choose separate plans per SKU if you mix and match SKUs per deal
Most sellers start with separate plans for flexibility and create separate Private Offers per SKU for a smoother acceptance experience.
Are private plans publicly visible?
No. Private plans are not publicly listed in Azure Marketplace.
Only Azure accounts explicitly assigned to the plan can view, accept, and purchase it.
How do private plans become visible to specific customers?
Azure requires at least one Azure Tenant ID to be assigned when creating a private plan.
To create and finalize a private plan, you must provide:
- At least one Azure Tenant ID belonging to a customer you intend to send a Private Offer to
Once assigned:
- Only that Azure account can view, accept, and purchase the plan
Additional tenant IDs can be added later if you want the same plan to be available to more customers.
Until a tenant ID is added, the private plan cannot be finalized or used in a Private Offer.
What information is required to create private plans?
For each SKU or plan:
- Plan ID (unique)
- Plan name
- Short description
- Price (USD)
- At least one Azure Tenant ID
Most other settings—such as regions, billing cadence, and contract length—can be reused across plans.
Can Private Offers support usage-based (metered) billing?
Yes. Metered billing must be defined at plan creation time and cannot be changed later.
If a SKU requires metering, this should be identified upfront.
What currencies are supported?
Azure requires plan pricing to be set in USD.
Azure automatically converts pricing to the customer’s local currency.
How does currency conversion work?
- Conversion happens when pricing is saved in Azure Partner Center
- The converted local price is locked at that time
- The customer pays that fixed amount for the full contract term
- Prices do not fluctuate with exchange rates after publishing
You can review converted local currency values before finalizing the offer.
What contract terms are supported for Azure Private Offers?
Azure supports predefined contract durations, such as one-year or multi-year terms.
Custom or partial-year terms (for example, 3 or 6 months) are not supported unless explicitly allowed by Azure for your offer type.