Azure contract fields and an External Client App in Salesforce package 1.71
Last updated: October 23, 2026
Overview
Until now, Clazar Contract records in Salesforce showed only the object ID of the Azure purchaser and beneficiary. Also, the Clazar Salesforce package did not include an app for Clazar AI to connect to your org.
Version 1.71 of the Clazar Salesforce package makes two changes. It adds six fields to the Clazar Contract object for the PUID, email address and tenant ID of the Azure purchaser and beneficiary. It also installs a Salesforce External Client App, which your org needs before you can connect Salesforce to Clazar AI.
Value it drives
Purchaser details: The new Azure Purchaser PUID, Azure Purchaser Email Id and Azure Purchaser Tenant Id fields show the user and the tenant that purchased the subscription.
Beneficiary details: The new Azure Beneficiary PUID, Azure Beneficiary Email Id and Azure Beneficiary Tenant Id fields show the user and the tenant that the subscription is for. Microsoft records the beneficiary separately from the purchaser, and the two can be different.
Reports and list views: You can filter Salesforce reports and list views on the six fields. For example, filter a contract report on Azure Beneficiary Tenant Id to list all contracts for one Azure tenant.
External Client App for Clazar AI: The package installs the External Client App for you, with the name Clazar AI Connector. Your Salesforce admin does not need to create an app to connect Salesforce to Clazar AI.
Clazar Contracts (clazar__Contract__c):
Field label | API name | Type | What it contains |
|---|---|---|---|
Azure Purchaser PUID |
| Text(255) | The PUID that Microsoft assigns to the user who purchased the subscription. |
Azure Purchaser Email Id |
| Text(255) | Email address of the user who purchased the subscription. |
Azure Purchaser Tenant Id |
| Text(255) | Microsoft Entra tenant ID of the user who purchased the subscription. |
Azure Beneficiary PUID |
| Text(255) | The PUID that Microsoft assigns to the beneficiary of the subscription. |
Azure Beneficiary Email Id |
| Text(255) | Email address of the beneficiary of the subscription. |
Azure Beneficiary Tenant Id |
| Text(255) | Microsoft Entra tenant ID of the beneficiary of the subscription. |
How to get started
Check the package version: In Salesforce, go to Setup → Installed Packages. Make sure that the Clazar package shows version 1.71 or later. If the version is earlier, reach out to your Clazar support contact.
Check the contract writeback: In Clazar, go to Integrations → Salesforce → Setup. In the Enable Objects Write-back step, make sure that Clazar Contracts is in the list of enabled objects. If it is not, click Enable Write-back or Modify Write-back. Then select Clazar Contracts.
Open an Azure contract: In Salesforce, open a Clazar Contract record for an Azure contract. The six fields show values after the next regular writeback.
Review the External Client App (optional): In Salesforce, go to Setup → External Client App Manager and open Clazar AI Connector. Choose which users can use it.
The External Client App needs no other action now. Clazar shares the steps to connect Salesforce to Clazar AI when the connection is available.
Things to note
Empty contract fields: Clazar fills the six fields only for Azure contracts. A field also stays empty when Microsoft does not send a value for that contract.
Existing contracts: Existing Azure contracts get the values during the next regular writeback. You do not need to do anything in Clazar.
Record pages: If you customized the Clazar Contract record page, the new fields do not show on it automatically. A Salesforce admin can add them. For the steps, see Updating customized record pages for new fields.
External Client App access: The app stays inactive until a user connects Salesforce to Clazar AI and approves access. After that, it gives Clazar AI only the Salesforce access of that user.