[BillingTrust] Add Microsoft.BillingTrust TypeSpec API spec (2026-03-17-preview)

[abhimrnandan-ms]

Summary

New ARM resource provider: Microsoft.BillingTrust

• API version: 2026-03-17-preview (preview)
• Resources: Assessments (CRUD + list), Rules (CRUD + list)
• TypeSpec source with generated OpenAPI
• Provides Assessment and Rule resources used to evaluate trust attributes (such as education-domain qualification and business verification) of a billing account

Previously merged in azure-rest-api-specs-pr PR #28678.

Release Plan

• Release Plan: #34897
• Service Tree ID: 403a7ada-b47f-4ac7-ad33-cd76e1fa7614

Packages

• Azure.ResourceManager.BillingTrust (.NET)
• azure-mgmt-billingtrust (Python)
• azure-resourcemanager-billingtrust (Java)
• @azure/arm-billingtrust (JavaScript)
• armbillingtrust (Go)

[github-actions]

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

Comment generated by summarize-checks workflow run.

[github-actions]

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language	API Review for Package
Swagger	Microsoft.BillingTrust-BillingTrust
TypeSpec	Microsoft.BillingTrust
Go	sdk/resourcemanager/billingtrust/armbillingtrust
Python	azure-mgmt-billingtrust
JavaScript	@azure/arm-billing-trust
Java	com.azure.resourcemanager:azure-resourcemanager-billing-trust

---

Comment generated by After APIView workflow run.

[abhimrnandan-ms]

The Microsoft.BillingTrust namespace was merged to RPSaaSMaster in azure-rest-api-specs-pr via PR 28678 (ARM review signed off). However, the CI-RpaaSRPNotInPrivateRepo check does not appear to detect it.

Private repo PR link : https://github.com/Azure/azure-rest-api-specs-pr/pull/28678
Could someone from the ARM review team help investigate and unblock this PR?

[abhimrnandan-ms]

/azp run

[azure-pipelines]

You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list.

[abhimrnandan-ms]

@microsoft-github-policy-service agree [company="Microsoft"]

[abhimrnandan-ms]

@microsoft-github-policy-service agree

[abhimrnandan-ms]

@gary-x-li
This issue was raised and resolved during the ARM review of the private repo PR (azure-rest-api-specs-pr#28678), which was merged with ARMSignedOff. Here is the context:

1. BillingRP owns GDPR handling. BillingTrust is a read-only projection of the billing account's sold-to data — not the system of record. GDPR cleanup (right-to-erasure, etc.) is handled by BillingRP, and BillingTrust reflects/propagates changes and cleanup automatically.

2. PII tagging is already in place. The SoldTo model @doc carries an explicit PII classification block, and every PII-bearing field has a per-field "PII — postal address" or "PII — contact" marker in its documentation.

3. ARG indexing is disabled on the rules resource type. We set resourceGraphConfiguration.enabled: false on assessments/rules so the PII fields never reach the ARG cache. The parent assessments RT (which does not carry PII) keeps ARG indexing enabled.

4. expandCustomerData query parameter is not feasible for this resource type. Reads are served by MetaRP from its tracked-resources cache — the RP is not invoked on the read path. Implementing an expand pattern would require registering ResourceRead extensions and changing the read architecture. Given that ARG indexing is disabled on the rules RT, disabling ARG is the proportionate fix per the architect's guidance.

The soldTo, registrationNumber, and taxIds fields are all @visibility(Lifecycle.Read) (read-only, server-managed) — they are populated from the billing account at rule creation time and cannot be supplied or modified by end users.

[abhimrnandan-ms]

@gary-x-li — Friendly follow-up. The ARG002 finding on SoldTo was already reviewed and accepted during the private repo ARM review (PR #28678, merged with ARMSignedOff). The mitigation is disabling ARG indexing on the rules resource type (resourceGraphConfiguration.enabled: false). Full justification is in my earlier comment above.

Could you please review and sign off? We're targeting a Public Preview release this month. Thank you!

[msyyc]

python fails for a known issue and I have sought help in teams channel

[msyyc]

python check pass