New fields on Clazar Contracts, Companies, and Azure CoSell in Salesforce
Last updated: October 12, 2026
Overview
Until now, the Clazar objects in Salesforce did not show who bought a contract, what it is worth, what the buyer entered at registration, who the Azure purchaser and beneficiary are, a company's AWS Engagement Score and MACC Eligibility, or an Azure CoSell opportunity's Customer Needs. That information was only available in Clazar.
Version 1.68 of the Clazar Salesforce package adds 27 fields: 24 on Clazar Contracts, 2 on Clazar Companies, and 1 on Clazar Azure Co-Sell Opportunity. Clazar fills them during its regular writebacks to Salesforce.
Value it drives
Revenue reporting in Salesforce: The five revenue fields and Duration In Days are Number fields. You can sum, average, and filter on them in Salesforce reports and dashboards.
Buyer context on the contract record: The buyer's name, domain, marketplace account, plan, and registration answers are on the Clazar Contract record, next to your opportunity data.
Azure purchaser and beneficiary on the contract record: For Azure contracts, the object ID, PUID, email address, and tenant ID of both the purchaser and the beneficiary are on the Clazar Contract record, so you can match the subscription to a person and a tenant without leaving Salesforce.
Account signals on companies: AWS Engagement Score and MACC Eligibility are on the Clazar Company record, so you can use them in Salesforce list views and reports.
Customer Needs on Azure cosell: The Customer Needs value from the Azure cosell opportunity is on the Clazar Azure Co-Sell Opportunity record.
Clazar Contracts (clazar__Contract__c):
Field label | API name | Type | What it contains |
|---|---|---|---|
Buyer Name |
| Text(120) | Name of the buyer's company. |
Buyer Domain |
| Text(120) | Website domain of the buyer's company. |
Buyer Account Id |
| Text(255) | The buyer's account ID in the cloud marketplace. |
External Org Id |
| Text(250) | The ID of the buyer's organization in your own product, when it is set on the contract in Clazar. |
Plan Id |
| Text(255) | ID of the plan the buyer purchased. |
Cloud Status |
| Text(120) | The contract's status, as the marketplace reports it. |
Cloud Offer Type |
| Text(100) | The offer type, as the marketplace reports it. For example, public or private. |
Metering Eligible |
| Text(120) | True when usage can be metered for the contract. Otherwise False. |
Currency Code |
| Text(50) | Currency of the contract's amounts. For example, USD. |
Gross Booking Value |
| Number(16, 2) | Value of all bookings created: the contract value plus the Usage Booking Value. |
Gross Billed Revenue |
| Number(16, 2) | The part of the Gross Booking Value that has been billed. |
Usage Booking Value |
| Number(16, 2) | Value from the usage-based (metered) parts of the contract. |
Net Disbursed Revenue |
| Number(16, 2) | Gross Billed Revenue minus marketplace listing fees and similar charges, paid out to your bank. |
Net Undisbursed Revenue |
| Number(16, 2) | Net revenue that has not been paid out yet. |
Duration In Days |
| Number(16, 2) | Length of the contract term, in days. |
Azure Purchaser Object Id |
| Text(255) | Microsoft Entra object ID of the user who purchased the subscription. Azure only. |
Azure Beneficiary Object Id |
| Text(255) | Microsoft Entra object ID of the subscription's beneficiary. Azure only. |
Registration Details |
| Long Text Area(32768) | The buyer's answers from your registration page, for the fields you have enabled. If a buyer registered more than once, it contains their latest answer for each field. |
Azure Purchaser PUID |
| Text(255) | Microsoft passport user ID (PUID) of the user who purchased the subscription. Azure only. |
Azure Purchaser Email Id |
| Text(255) | Email address of the user who purchased the subscription. Azure only. |
Azure Purchaser Tenant Id |
| Text(255) | Microsoft Entra tenant ID of the user who purchased the subscription. Azure only. |
Azure Beneficiary PUID |
| Text(255) | Microsoft passport user ID (PUID) of the subscription's beneficiary. Azure only. |
Azure Beneficiary Email Id |
| Text(255) | Email address of the subscription's beneficiary. Azure only. |
Azure Beneficiary Tenant Id |
| Text(255) | Microsoft Entra tenant ID of the subscription's beneficiary. Azure only. |
Clazar Companies (clazar__Company__c):
Field label | API name | Type | What it contains |
|---|---|---|---|
AWS Engagement Score |
| Text(255) | AWS's estimate of how likely the account is to purchase through AWS Marketplace. |
MACC Eligibility |
| Text(255) | Whether Microsoft identifies the account as having a Microsoft Azure Consumption Commitment (MACC). Eligible Microsoft Marketplace purchases can count toward this commitment. |
Clazar Azure Co-Sell Opportunity (clazar__AzureCoSellOpportunity__c):
Field label | API name | Type | What it contains |
|---|---|---|---|
Customer Needs |
| Long Text Area(32768) | What the customer is trying to solve, from the Customer Needs field of the Azure co-sell opportunity in Clazar. |
How to get started
Upgrade the Clazar Salesforce package to version 1.68: Use either of these options.
From Salesforce AppExchange: Upgrade or install the Clazar package from its AppExchange listing.
From the Clazar app: Go to Integrations → Salesforce → Setup, then click Install.
Turn on the writeback: If writeback is not already enabled for your account, you can turn it on yourself in the Clazar app. Go to Integrations → Salesforce → Setup → Enable Writeback, then select the objects to write back: Clazar Contracts, Clazar Companies, and Clazar Azure Co-Sell Opportunity. If you need help, reach out to your Clazar support contact.
Ask Clazar to enable the new fields: Clazar writes each set of new fields only once your org has the package version that defines them, so this is turned on by Clazar rather than from the Clazar app. Once you have upgraded, let your Clazar support contact know, and they will enable the new fields for your account.
Things to note
Page layouts: If you use the default Clazar page layouts, the new fields are added to them by the upgrade. If you have modified a default Clazar layout, the upgrade does not add the new fields to it. A Salesforce admin can add them to the Clazar Contracts, Clazar Companies, and Clazar Azure Co-Sell Opportunity layouts in Setup, under Object Manager. For the steps, see Updating customized record pages for new fields.
Existing records: Existing contracts, companies, and Azure co-sell opportunities get the new values during the next regular writebacks. No action is needed in Clazar.
Empty fields: A field is left empty when the marketplace does not provide a value for that contract. For example, all of the Azure Purchaser and Azure Beneficiary fields are only filled for Azure contracts.