Add Multi-Tenant Usage Metering and Billing partner docs (PSAOKR-5462)

config/_default/menus/partners.en.yaml

@@ -37,5 +37,39 @@ menu:
       identifier: cloud-cost-management-aws
       parent: cloud-cost-management
       weight: 50
+    - name: Multi-Tenant Usage Metering and Billing
+      url: /partners/multi_tenant_billing/
+      identifier: multi-tenant-billing
+      weight: 4
+    - name: Onboarding a New Customer
+      url: /partners/multi_tenant_billing/customer-onboarding/
+      identifier: multi-tenant-billing-customer-onboarding
+      parent: multi-tenant-billing
+      weight: 10
+    - name: Trial Org Provisioning
+      url: /partners/multi_tenant_billing/trial-org-provisioning/
+      identifier: multi-tenant-billing-trial-org-provisioning
+      parent: multi-tenant-billing
+      weight: 20
+    - name: Cost and Usage Visibility
+      url: /partners/multi_tenant_billing/cost-and-usage-visibility/
+      identifier: multi-tenant-billing-cost-and-usage-visibility
+      parent: multi-tenant-billing
+      weight: 30
+    - name: Centralized Usage Metrics
+      url: /partners/multi_tenant_billing/centralized-usage-metrics/
+      identifier: multi-tenant-billing-centralized-usage-metrics
+      parent: multi-tenant-billing
+      weight: 35
+    - name: Customer Pricing Management
+      url: /partners/multi_tenant_billing/customer-pricing-management/
+      identifier: multi-tenant-billing-customer-pricing-management
+      parent: multi-tenant-billing
+      weight: 37
+    - name: Troubleshooting
+      url: /partners/multi_tenant_billing/troubleshooting/
+      identifier: multi-tenant-billing-troubleshooting
+      parent: multi-tenant-billing
+      weight: 40
 
 

content/en/partners/multi_tenant_billing/_index.md

@@ -0,0 +1,75 @@
+---
+title: Multi-Tenant Usage Metering and Billing
+description: "Centrally manage usage, costs, and billing for end customers through an Admin Org."
+cascade:
+    algolia:
+        subcategory: 'Multi-Tenant Usage Metering and Billing'
+---
+
+## Overview
+
+As a Datadog Solution Provider, use a **partner admin organization** (Admin Org) to view and monitor cost and usage across customer organizations, provision trial organizations, and view billing across the customer base. An Admin Org is separate from any customer organization and is owned by Datadog, but partners are invited with a Partner Role.
+
+<div class="alert alert-info">By default, an Admin Org grants read-only access to cost and usage data for connected customer organizations, and personal or internal Datadog usage on the Admin Org is not supported. The Preview capabilities below add supported pricing and contract-management workflows.</div>
+
+A customer organization is connected to an Admin Org automatically when its Datadog contract includes the partnership and is active. After connecting, a customer's usage and cost data is visible from the Admin Org, across all Datadog sites (for example, AP1, EU1, US1, US3, US5), except US1-FED, which requires its own Admin Org for regulatory purposes.
+
+{{< img src="partners/multi_tenant_billing/admin_org_hierarchy.png" alt="An Admin Org connected to multiple customer organizations" style="width:100%;" >}}
+
+See [Onboarding a New Customer][15] for how these pieces fit into the path from a registered deal to a connected customer organization.
+
+## Getting started
+
+Before requesting an Admin Org, the partner must:
+
+- Be registered with Datadog on the [Datadog Partner Portal][1].
+- Have signed the agreement to transact with Datadog as a Solution Provider.
+- Be approved as a Datadog partner.
+
+Partners not yet registered can [Register Now][17] on the Datadog Partner Portal.
+
+{{< img src="partners/multi_tenant_billing/partner_portal_registration.png" alt="Datadog Partner Portal registration page" style="width:100%;" >}}
+
+Registered partners can contact [partner-support@datadoghq.com][16] to request an Admin Org. Partners planning to provision customer trials should request the Trial Org Creator capability at the same time.
+
+{{< whatsnext desc="To get started with an Admin Org, see the following documentation.">}}
+  {{< nextlink href="/partners/multi_tenant_billing/customer-onboarding">}}<u>Onboarding a New Customer</u>: Take a prospective customer from a registered deal to a connected customer organization.{{< /nextlink >}}
+  {{< nextlink href="/partners/multi_tenant_billing/trial-org-provisioning">}}<u>Trial Org Provisioning</u>: Provision trial organizations for prospective customers directly from an Admin Org.{{< /nextlink >}}
+  {{< nextlink href="/partners/multi_tenant_billing/cost-and-usage-visibility">}}<u>Cost and Usage Visibility</u>: Monitor cost and billable usage across all connected customer organizations.{{< /nextlink >}}
+  {{< nextlink href="/partners/multi_tenant_billing/centralized-usage-metrics">}}<u>Centralized Usage Metrics</u>: Monitor usage metrics across all connected customer organizations.{{< /nextlink >}}
+  {{< nextlink href="/partners/multi_tenant_billing/troubleshooting">}}<u>Troubleshooting</u>: Resolve common issues with Admin Org and Trial Org provisioning.{{< /nextlink >}}
+{{< /whatsnext >}}
+
+## Use cases
+
+Discover some ways an Admin Org can help:
+
+| Use case | Capability |
+|---|---|
+| Monitor cost and usage across all customers in one place. | [Cost and Usage Visibility][2]: view estimated, historical, and projected cost and billable usage data. |
+| Self-serve Trial Org creation for prospective customers. | [Trial Org Provisioning][3]: create Trial Orgs directly from an Admin Org. |
+| Track usage metrics across the book of business. | [Centralized Usage Metrics][8]: roll customer usage metrics up into an Admin Org. |
+| Let customers see their estimated costs based on the partner's pricing. (Preview) | [Customer Pricing Management][9]: configure per-customer pricing. |
+| Manage the book of business in one place. (Preview) | [Customer contracts management](#customer-contracts-management-preview): track customers, contracts, invoices, and renewals. |
+
+### Customer contracts management (Preview)
+
+Review and manage the book of business from {{< ui >}}Plan & Usage{{< /ui >}} > {{< ui >}}Customer Contracts{{< /ui >}}: customers, contracts, invoices, renewal alerts, and margin visibility, in one place inside the Admin Org.
+
+{{< img src="partners/multi_tenant_billing/customer_contracts.png" alt="Customer Contracts tab under Plan & Usage in an Admin Org" style="width:100%;" >}}
+
+<div class="alert alert-info">Preview capabilities are available to a limited set of partners while Datadog validates them. Contact <a href="mailto:partner-support@datadoghq.com">partner-support@datadoghq.com</a> to join a preview.</div>
+
+## Troubleshooting
+
+For help with common Admin Org and Trial Org issues, see [Troubleshooting][7].
+
+[1]: https://partners.datadoghq.com
+[2]: /partners/multi_tenant_billing/cost-and-usage-visibility/
+[3]: /partners/multi_tenant_billing/trial-org-provisioning/
+[7]: /partners/multi_tenant_billing/troubleshooting/
+[8]: /partners/multi_tenant_billing/centralized-usage-metrics/
+[15]: /partners/multi_tenant_billing/customer-onboarding/
+[16]: mailto:partner-support@datadoghq.com
+[17]: https://partners.datadoghq.com/s/login/
+[9]: /partners/multi_tenant_billing/customer-pricing-management/

content/en/partners/multi_tenant_billing/centralized-usage-metrics.md

@@ -0,0 +1,57 @@
+---
+title: Centralized Usage Metrics
+description: "Monitor usage metrics across all connected customer organizations from an Admin Org."
+---
+
+## Overview
+
+Datadog produces two kinds of usage metrics:
+
+- **Estimated usage metrics**, in the `datadog.estimated_usage.*` namespace, update within minutes and provide a near real-time view of usage. Estimated usage metrics can differ from billable usage by roughly 10-20% on average, with larger variance for low-usage organizations. See [Estimated Usage Metrics][1] for the full metrics reference.
+- **Usage metrics**, in the `datadog.usage.*` namespace, come from the same metering and billing pipeline that produces the bill, so they track Plan & Usage closely. Usage metrics are less immediate than estimated usage metrics, but accurate enough for billing conversations.
+
+Use estimated usage metrics to catch usage spikes early, and usage metrics to report numbers that reconcile with the bill.
+
+In an Admin Org, usage metrics from every connected customer organization roll up into one place, tagged by customer. This gives a single set of dashboards, monitors, and alerts across the entire book of business.
+
+## Attribution tags
+
+Rolled-up metrics carry two tags:
+
+- `account_name`: the parent org name (the Admin Org).
+- `child_org_name`: the child org name (the customer organization), relative to the parent.
+
+## Query usage metrics
+
+When building a dashboard widget or monitor:
+
+- For estimated usage metrics, select {{< ui >}}Metrics{{< /ui >}} as the source and use a `datadog.estimated_usage.*` metric.
+- For usage metrics, select {{< ui >}}Usage{{< /ui >}} as the source and choose a usage type, for example Infra Hosts.
+
+| Product | Estimated usage metric | Usage metric |
+|---|---|---|
+| Infrastructure hosts | `datadog.estimated_usage.hosts` | `datadog.usage.infra.hosts` |
+| APM hosts | `datadog.estimated_usage.apm_hosts` | `datadog.usage.apm.hosts` |
+| Custom metrics | `datadog.estimated_usage.metrics.custom` | `datadog.usage.metrics.custom` |
+| Indexed logs | `datadog.estimated_usage.logs.ingested_events` | `datadog.usage.logs.indexed_logs` |
+
+Scope a query to one customer with `child_org_name`, or break out every customer with `by {child_org_name}`:
+
+```
+# Estimated usage metric (Metrics source)
+sum:datadog.estimated_usage.hosts{*} by {child_org_name}
+
+# Usage metric (Usage source)
+sum:datadog.usage.infra.hosts{*} by {child_org_name}
+```
+
+{{< img src="partners/multi_tenant_billing/usage_metrics_rollup.png" alt="Dashboard querying usage metrics rolled up from customer orgs, filtered by child_org_name" style="width:100%;" >}}
+
+To match Plan & Usage totals, use a 1-hour rollup for host-style products and graph in UTC, since Plan & Usage reports in UTC.
+
+## What's next
+
+See [Cost and Usage Visibility][2] for cost and billable usage data.
+
+[1]: /account_management/billing/usage_metrics/
+[2]: /partners/multi_tenant_billing/cost-and-usage-visibility/

content/en/partners/multi_tenant_billing/cost-and-usage-visibility.md

@@ -0,0 +1,42 @@
+---
+title: Cost and Usage Visibility
+description: "Monitor cost and billable usage across all connected customer organizations from an Admin Org."
+---
+
+## Overview
+
+A customer organization connects to the partner Admin Org automatically when its contract includes the partnership and is active. The connection is removed automatically if the contract expires. After connecting, a customer's usage and cost data becomes visible from the Admin Org, across all Datadog sites the customer uses. A Trial Org's usage is not included here until its customer organization is connected this way; see [Trial Org Provisioning][4].
+
+## View cost and usage data
+
+Go to {{< ui >}}Plan & Usage{{< /ui >}} > {{< ui >}}Usage & Cost{{< /ui >}} in the Admin Org to view estimated, historical, and projected cost and billable usage data across all connected customer organizations, grouped and filtered by customer, product, or account. See [Plan and Usage Experience for Partners][1] for details.
+
+Cost and usage data is also available programmatically through the following [Usage Metering API][2] endpoints:
+
+| API | What it's for | Note |
+|---|---|---|
+| [Get Estimated Cost Across Your Account][6] | Estimated cost for the current and previous month | Requires `include_connected_accounts=true` |
+| [Get Historical Cost Across Your Account][7] | Historical cost for previous months | Requires `include_connected_accounts=true` |
+| [Get Projected Cost Across Your Account][8] | Projected end-of-month cost for the current month | Requires `include_connected_accounts=true` |
+| [Get Billable Usage Across Your Account][9] | Billable usage summaries | Requires `include_connected_accounts=true` |
+| [Get Usage Across Your Account][10] | Usage summary data across the account | Requires `include_connected_accounts=true` |
+| [Get Hourly Usage by Product Family][11] | Hourly usage broken down by product family | Requires `filter[include_connected_accounts]=true` |
+
+**Note**: Standard GovCloud boundaries apply to this visibility. A non-GovCloud Admin Org cannot see cost and usage data for a GovCloud customer organization.
+
+**Note**: Usage and cost views may include estimated or projected values during the billing period. Final invoices remain the authoritative source for billed amounts.
+
+## What's next
+
+See [Centralized Usage Metrics][3] for usage metrics rolled up across the book of business, or [Trial Org Provisioning][4] to start provisioning trial organizations for prospective customers.
+
+[1]: /account_management/plan_and_usage/partner_experience/
+[2]: /api/latest/usage-metering/
+[3]: /partners/multi_tenant_billing/centralized-usage-metrics/
+[4]: /partners/multi_tenant_billing/trial-org-provisioning/
+[6]: /api/latest/usage-metering/#get-estimated-cost-across-your-account
+[7]: /api/latest/usage-metering/#get-historical-cost-across-your-account
+[8]: /api/latest/usage-metering/#get-projected-cost-across-your-account
+[9]: /api/latest/usage-metering/#get-billable-usage-across-your-account
+[10]: /api/latest/usage-metering/#get-usage-across-your-account
+[11]: /api/latest/usage-metering/#get-hourly-usage-by-product-family

content/en/partners/multi_tenant_billing/customer-onboarding.md

@@ -0,0 +1,48 @@
+---
+title: Onboarding a New Customer
+description: "How a partner takes a prospective customer from a registered deal to a connected customer organization."
+---
+
+## Overview
+
+When a partner has a prospect interested in Datadog, the path from that first conversation to a connected customer organization has three parts: register the opportunity, create a Trial Org for the prospect, and work with the partner account team through to a signed contract. An Admin Org is what makes the Trial Org step self-service.
+
+## Register the opportunity
+
+Register the opportunity on the [Partner Portal][1] as early as possible. Registering:
+
+- Increases the chance the opportunity is recognized as partner-sourced.
+- Gives Datadog visibility into the partner's involvement if Datadog is already engaged with the same prospect, enabling collaboration instead of overlap.
+- Creates a shared, transparent record between Datadog and the partner for tracking the opportunity to close.
+
+To register a deal:
+
+1. Log in to the [Partner Portal][1].
+2. From the {{< ui >}}Deal Dashboard{{< /ui >}}, click {{< ui >}}Register Deal{{< /ui >}}.
+3. Complete the required fields, including as much detail as possible: opportunity name, customer name, expected close date, use cases, key stakeholders, and estimated ARR.
+4. Click {{< ui >}}Submit{{< /ui >}}.
+
+After submitting, notify the partner account team that a new opportunity was registered. Contact [partner-support@datadoghq.com][2] if unsure who to reach.
+
+## Create a Trial Org
+
+After the opportunity is registered, create a Trial Org for the prospect. This requires an Admin Org with the Trial Org Creator capability enabled; see [Getting started][3] if one isn't set up yet.
+
+When selecting a region for the Trial Org, match the prospect's environment where possible: cloud provider, geography, and compliance needs. For example, a prospective Azure customer is a fit for the US3 (Azure) site. Default to US1 if there are no specific constraints, or align with the partner account team when unsure.
+
+See [Trial Org Provisioning][4] for the full form walkthrough.
+
+## Share the Trial Org with the account team
+
+A Trial Org's usage is not visible from the Admin Org on its own. Share the new Trial Org's ID with the partner account team so it can be associated with the registered opportunity. Continue working with the partner account team as the opportunity progresses to a signed contract; the customer organization connects to the Admin Org, and its usage becomes visible, once that contract is active and associated with the partnership.
+
+## What's next
+
+See [Cost and Usage Visibility][5] for how usage and cost data appears from the Admin Org after a customer organization is connected, or [Troubleshooting][6] for common issues along the way.
+
+[1]: https://partners.datadoghq.com
+[2]: mailto:partner-support@datadoghq.com
+[3]: /partners/multi_tenant_billing/#getting-started
+[4]: /partners/multi_tenant_billing/trial-org-provisioning/
+[5]: /partners/multi_tenant_billing/cost-and-usage-visibility/
+[6]: /partners/multi_tenant_billing/troubleshooting/

content/en/partners/multi_tenant_billing/customer-pricing-management.md

@@ -0,0 +1,50 @@
+---
+title: Customer Pricing Management
+description: "Configure per-customer pricing so customers can see their own estimated Datadog costs."
+---
+
+## Overview
+
+Customer Pricing Management lets a partner configure per-customer pricing so a customer can see their own estimated Datadog costs, based on the partner's rates, directly within their org. This capability is in preview.
+
+Partner-configured pricing powers the [Bill Overview][1] page in the customer's own org: an estimated month-to-date cost total, a daily cost breakdown, and the ability to break costs down by product and sub-org.
+
+## Configure pricing for a customer
+
+1. Log in to the Admin Org. Go to {{< ui >}}Plan & Usage{{< /ui >}} > {{< ui >}}Customer Pricing{{< /ui >}}.
+2. Select a customer from the dropdown. Only connected customers with an eligible contract appear; see [Limitations](#limitations).
+3. Review the customer's contracted products and their sales prices in the table.
+4. Click {{< ui >}}Edit{{< /ui >}} and enter prices for each contracted product, individually or in bulk.
+5. Set a default pricing rule for products not on the contract: bill at list price, or apply a percentage markup to the sales price.
+6. Click {{< ui >}}Save Draft{{< /ui >}}, review the entries, then click {{< ui >}}Publish{{< /ui >}}.
+
+Pricing is a one-time setup per customer. Published pricing can be updated and republished at any time; changes take effect within 24 hours.
+
+{{< img src="partners/multi_tenant_billing/customer_pricing.png" alt="Customer Pricing tab under Plan & Usage in an Admin Org" style="width:100%;" >}}
+
+**Note**: The Billing Edit permission is required to configure and publish pricing. The Billing Read permission allows viewing saved or published rates, but not editing them.
+
+## What the customer sees
+
+After publishing, the customer sees their estimated month-to-date cost, a daily cost breakdown, and the ability to group by product or sub-org, on their own [Bill Overview][1] page.
+
+**Note**: All costs shown to the customer are estimated. They typically match the partner's invoice, though minor differences of a few cents can occur.
+
+## Limitations
+
+This capability is in preview and does not support:
+
+- Pricing per child org, for example for legacy MSP contracts, which have multiple customers under a single contract.
+- Customers procuring through two channel partners at once.
+- GovCloud customer organizations.
+- Cloud marketplace customers (AWS, Azure, or GCP Marketplace) without a drawdown agreement.
+- Projected costs, cost by tag, or Datadog costs in Cloud Cost Management.
+
+On-demand costs for off-contract ingest SKUs can run up to approximately 3% higher than actual cost.
+
+## What's next
+
+Contact [partner-support@datadoghq.com][2] to join the preview.
+
+[1]: /account_management/plan_and_usage/bill_overview/
+[2]: mailto:partner-support@datadoghq.com