Forum Discussion

ph_richardson's avatar
ph_richardson
Copper Contributor
Oct 20, 2025

Azure customer usage attribution (CUA) - report or validate it is working?

Per this article - https://learn.microsoft.com/en-us/partner-center/marketplace-offers/azure-partner-customer-usage-attribution#example-azure-powershell

If we use Azure PowerShell along with the ISV/SDC's Tracking GUID (created earlier in Partner Centre), to provision Azure VM's and other resources in end-customer tenants directly related to our IP as an ISV/SDC - how do we report or validate that this CUA is working?

 

azure
partner center
pracr

8 Replies

  • justinroyal's avatar
    justinroyal
    Icon for Microsoft rankMicrosoft
    Oct 25, 2025

    Hi ph_richardson​ -

     

    Here's some additional information related to your question: 

    Customer Usage Attribution (CUA) validation is critical when you’re using Azure PowerShell with the ISV/SDC Tracking GUID to provision resources in a customer tenant. Here’s how you can report and validate that the attribution is working - take a look below and let me know if you have any additional questions.

    How CUA Works

    • The Tracking GUID (also called PartnerId) is passed during resource creation (e.g., VM deployment) via Azure PowerShell or ARM templates.
    • Azure logs this GUID in the resource metadata, which is then used for attribution in Partner Center.

    How to Validate CUA

    1. Check Resource Metadata
      • After provisioning, inspect the resource properties in the customer tenant:PowerShellLook for the tag PartnerId or MicrosoftPartnerNetworkID with your GUID.
      • Show more lines
      • Get-AzResource -ResourceGroupName <RGName> -Name <ResourceName> | Select-Object -ExpandProperty Tags
    2. Use Azure Activity Logs
      • Query the Activity Log for the deployment operation:PowerShellConfirm that the deployment includes the PartnerId.
      • Show more lines
      • Get-AzActivityLog -StartTime (Get-Date).AddDays(-7) -ResourceGroupName <RGName>
    3. Partner Center Reporting
      • Attribution data flows into Partner Center Analytics (under Customer Usage Attribution reports) within 24–48 hours.
      • Navigate to: Partner Center → Insights → Customer Usage Attribution
        • Filter by your MPN ID or Tracking GUID.
        • Validate that the usage metrics (VM hours, resource consumption) appear.
    4. Optional: Azure Resource Graph
      • For bulk validation across subscriptions:PowerShell
      • Show more lines
      • Search-AzGraph -Query "Resources | where tags['PartnerId'] == '<YourGUID>'"

    Common Pitfalls

    • GUID not applied: Ensure you use the correct parameter (-Tag @{ 'PartnerId'='<GUID>' }) during deployment.
    • Cross-tenant provisioning: Attribution only works when resources are deployed in the customer tenant, not in your own subscription.
    • Delay in reporting: Partner Center updates are not real-time; allow up to 48 hours.
    • ph_richardson's avatar
      ph_richardson
      Copper Contributor
      Dec 19, 2025

      Hi justinroyal​ - regards Partner Centre reporting, I don't appear to see the items you pointed out:

      Partner Center Reporting

      • Attribution data flows into Partner Center Analytics (under Customer Usage Attribution reports) within 24–48 hours.
      • Navigate to: Partner Center → Insights → Customer Usage Attribution
      • Filter by your MPN ID or Tracking GUID.
      • Validate that the usage metrics (VM hours, resource consumption) appear.

      Any advice?

       

      Thanks

      • v-kylecallahan's avatar
        v-kylecallahan
        Brass Contributor
        Dec 30, 2025

        Hi ph_richardson​ sorry for any confusion. 

        There is reporting for usage of Marketplace purchased solutions, which can be found in Usage dashboard of Insights workspace in Partner Center. However, this will not include reporting of Azure customer usage attribution. 

        The original documentation page you referenced has directions on how to verify deployments tracked with a GUID.  Microsoft does not share Azure consumption data tracked via Customer Usage Attribution externally with Partners.

        I hope that clarifies reporting and that you were able to validate your tracking ID is working as intended.

Resources