diff --git a/hugo/config/_default/menus/partners.en.yaml b/hugo/config/_default/menus/partners.en.yaml index 64d204253ce..d7f508a73ab 100644 --- a/hugo/config/_default/menus/partners.en.yaml +++ b/hugo/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: 40 + - name: Customer Contracts + url: /partners/multi_tenant_billing/customer-contracts-management/ + identifier: multi-tenant-billing-customer-contracts-management + parent: multi-tenant-billing + weight: 50 + - name: Troubleshooting + url: /partners/multi_tenant_billing/troubleshooting/ + identifier: multi-tenant-billing-troubleshooting + parent: multi-tenant-billing + weight: 70 diff --git a/hugo/content/en/partners/getting_started/_index.md b/hugo/content/en/partners/getting_started/_index.md index d2698c1f623..5b296c0b3e4 100644 --- a/hugo/content/en/partners/getting_started/_index.md +++ b/hugo/content/en/partners/getting_started/_index.md @@ -14,6 +14,7 @@ This section covers best practices and helps you get started monitoring your cli - [Data Intake][2]: Explains how data can be fed into Datadog and which prerequisites need to be met in your environments. - [Delivering Value][3]: Walks through recommended steps after you have data flowing into Datadog. - [Billing and Usage Reporting][4]: Covers monitoring individual client and aggregate usage of the Datadog platform in single and multi-organization account setups. +- [Multi-Tenant Usage Metering and Billing][12]: Covers the Admin Org, used to centrally manage usage, costs, and billing for end customers. ## Partner Sales Enablement guide @@ -46,12 +47,13 @@ Explore other important resources to stay up to date with Datadog: {{< nextlink href="https://github.com/DataDog/integrations-core/" >}}Integrations core: Agent Integrations that Datadog officially develops and supports.{{< /nextlink >}} {{< nextlink href="https://github.com/DataDog/integrations-extras/" >}}Integrations extras: Community-maintained Datadog Integrations.{{< /nextlink >}} {{< nextlink href="https://github.com/DataDog/Miscellany" >}}Miscellany: Miscellaneous scripts and tools from Datadog.{{< /nextlink >}} + {{< nextlink href="https://github.com/DataDog/dpn" >}}DPN: Sample applications for partners.{{< /nextlink >}} {{< /whatsnext >}} {{< whatsnext desc="Datadog blog and social media" >}} {{< nextlink href="https://www.datadoghq.com/blog/" >}}Datadog blog{{< /nextlink >}} {{< nextlink href="https://www.linkedin.com/company/datadog/" >}}LinkedIn{{< /nextlink >}} - {{< nextlink href="https://twitter.com/datadoghq" >}}Twitter{{< /nextlink >}} + {{< nextlink href="https://x.com/datadoghq" >}}X{{< /nextlink >}} {{< nextlink href="https://www.facebook.com/datadoghq/" >}}Facebook{{< /nextlink >}} {{< /whatsnext >}} @@ -61,6 +63,9 @@ Explore other important resources to stay up to date with Datadog: {{< /whatsnext >}} {{< whatsnext desc="Dash Conferences playlists" >}} + {{< nextlink href="https://www.youtube.com/playlist?list=PLdh-RwQzDsaPzYWUp9NA8IfbC47zxM57M" >}}Dash 2026{{< /nextlink >}} + {{< nextlink href="https://www.youtube.com/playlist?list=PLdh-RwQzDsaO91zHnerkZ5EZJ-qcqK4ib" >}}Dash 2025{{< /nextlink >}} + {{< nextlink href="https://www.youtube.com/playlist?list=PLdh-RwQzDsaNd5cmcY3ey4QoeyDk6aMKz" >}}Dash 2024{{< /nextlink >}} {{< nextlink href="https://www.youtube.com/playlist?list=PLdh-RwQzDsaPhn1p7Sz6nc_6-9YInd__u" >}}Dash 2023{{< /nextlink >}} {{< nextlink href="https://www.youtube.com/playlist?list=PLdh-RwQzDsaOlLse2WlvFXYRJ8iirG2QO" >}}Dash 2022{{< /nextlink >}} {{< nextlink href="https://www.youtube.com/playlist?list=PLdh-RwQzDsaO-_rgnDSBn221gWacNCkDr" >}}Dash 2021{{< /nextlink >}} @@ -79,4 +84,5 @@ Explore other important resources to stay up to date with Datadog: [8]: https://datadogon.datadoghq.com/ [9]: https://status.datadoghq.com [10]: https://status.datadoghq.eu +[12]: /partners/multi_tenant_billing/ [11]: https://datadogintegrations.statuspage.io diff --git a/hugo/content/en/partners/multi_tenant_billing/_index.md b/hugo/content/en/partners/multi_tenant_billing/_index.md new file mode 100644 index 00000000000..a7f5cbf16b4 --- /dev/null +++ b/hugo/content/en/partners/multi_tenant_billing/_index.md @@ -0,0 +1,67 @@ +--- +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, you can 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; partners are invited to it with a Partner Role. + +
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 capability below adds supported pricing workflows.
+ +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 GovCloud sites, which require their 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. + +## Requesting an Admin Org + +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 request an Admin Org by contacting [partner-support@datadoghq.com][16]. Include in the request whether the partner also needs the Trial Org Provisioner capability enabled, for self-serve trial organization creation. + +## Getting started + +{{< whatsnext desc="To get started with an Admin Org, see the following documentation.">}} + {{< nextlink href="/partners/multi_tenant_billing/customer-onboarding">}}Onboarding a New Customer: Take a prospective customer from a registered deal to a connected customer organization.{{< /nextlink >}} + {{< nextlink href="/partners/multi_tenant_billing/trial-org-provisioning">}}Trial Org Provisioning: Provision trial organizations for prospective customers directly from an Admin Org.{{< /nextlink >}} + {{< nextlink href="/partners/multi_tenant_billing/troubleshooting">}}Troubleshooting: Resolve common issues with Admin Org and Trial Org provisioning.{{< /nextlink >}} +{{< /whatsnext >}} + +## Use cases + +Here are some ways an Admin Org can help: + +| Use case | Capability | +|---|---| +| Self-serve Trial Org creation for prospective customers. | [Trial Org Provisioning][3]: Create Trial Orgs directly from an Admin Org. | +| 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. | +| 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. | Customer Pricing: Configure per-customer pricing. | +| Manage the book of business in one place. | [Customer Contracts][10]: Track customers, contracts, invoices, and renewals. | + +## 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/ +[10]: /partners/multi_tenant_billing/customer-contracts-management/ diff --git a/hugo/content/en/partners/multi_tenant_billing/centralized-usage-metrics.md b/hugo/content/en/partners/multi_tenant_billing/centralized-usage-metrics.md new file mode 100644 index 00000000000..425b7daf8db --- /dev/null +++ b/hugo/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 + +Centralized Usage Metrics lets the Partner Admin Organization (Admin Org) oversee usage and estimated usage metrics from every connected customer org. Metrics roll up to the Admin Org tagged by customer, so partners can filter and attribute usage across their entire book of business from a single set of dashboards, monitors, and alerts. + +Datadog produces two kinds of usage metrics: + +- **Estimated usage metrics** in the `datadog.estimated_usage.*` namespace. These metrics 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. These metrics 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. + +## 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. + +## Related docs + +- [Cost and Usage Visibility][2]: cost and billable usage data across connected customer orgs. + +[1]: /account_management/billing/usage_metrics/ +[2]: /partners/multi_tenant_billing/cost-and-usage-visibility/ diff --git a/hugo/content/en/partners/multi_tenant_billing/cost-and-usage-visibility.md b/hugo/content/en/partners/multi_tenant_billing/cost-and-usage-visibility.md new file mode 100644 index 00000000000..2664fab6701 --- /dev/null +++ b/hugo/content/en/partners/multi_tenant_billing/cost-and-usage-visibility.md @@ -0,0 +1,41 @@ +--- +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 Organization (Admin Org) automatically when its contract includes the partnership and is active. After connecting, a customer's usage and cost data becomes visible from the Admin Org, across all Datadog sites the customer uses. The connection is removed automatically 30 days after the contract expires, giving the partner a grace period to retain visibility while the contract is being renewed. + +**Note**: 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` | + +## Related docs + +- [Centralized Usage Metrics][3]: Usage metrics rolled up from every connected customer org. +- [Trial Org Provisioning][4]: Provision 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 diff --git a/hugo/content/en/partners/multi_tenant_billing/customer-contracts-management.md b/hugo/content/en/partners/multi_tenant_billing/customer-contracts-management.md new file mode 100644 index 00000000000..b2080f6cd4a --- /dev/null +++ b/hugo/content/en/partners/multi_tenant_billing/customer-contracts-management.md @@ -0,0 +1,40 @@ +--- +title: Customer Contracts +description: "Manage the partner's book of business - customers, contracts, and invoices - from an Admin Org." +--- + +
+Customer Contracts is in Preview. +
+ +## Overview + +Customer Contracts gives a partner a single place to manage customers, contracts, and invoices for their book of business with Datadog. Partners can look up this information directly, instead of relying on the partner account team for routine lookups. + +Go to {{< ui >}}Plan & Usage{{< /ui >}} > {{< ui >}}Customer Contracts{{< /ui >}} in the Admin Org; see [Requesting an Admin Org][2] if one isn't set up yet. + +{{< img src="partners/multi_tenant_billing/customer_contracts.png" alt="Customer Contracts tab under Plan & Usage in an Admin Org, listing customers and contracts." style="width:100%;" >}} + +**Note**: The Billing Read permission is required to view Customer Contracts. + +## What's included + +- All customers connected to the Admin Org, and their current and historical contracts, with renewal reminders for contracts coming up for renewal or already past their renewal date. +- Contract MRR (CMRR), Usage MRR (UMRR), influence status, and contract start and end dates, along with rates per product and order form PDFs. +- For drawdown contracts, the remaining balance, projected overshoot, and projected depletion date compared to the contract end date. +- For MSP contracts, which customers belong to each contract. +- Discount and margin visibility per contract. +- Whether Customer Pricing is enabled for each customer, not yet configured, or needs an update after a contract change. +- Key contacts per customer: The Datadog CSM, the Datadog AE, the partner account team, and the billing contact receiving invoices. + +{{< img src="partners/multi_tenant_billing/customer_contracts_detail.png" alt="Customer Contracts detail panel showing spend overview, drawdown depletion, contract info, and contacts for a customer." style="width:100%;" >}} + +Invoices are listed per customer with issue and due dates, amount, and payment status, and roll up into overdue counts and totals on the main Customer Contracts page: + +{{< img src="partners/multi_tenant_billing/customer_contracts_invoices.png" alt="Customer Contracts invoices tab listing invoice numbers, dates, amounts, and status for a customer." style="width:100%;" >}} + +## Related docs + +- [Requesting an Admin Org][2] + +[2]: /partners/multi_tenant_billing/#requesting-an-admin-org diff --git a/hugo/content/en/partners/multi_tenant_billing/customer-onboarding.md b/hugo/content/en/partners/multi_tenant_billing/customer-onboarding.md new file mode 100644 index 00000000000..a6ddd53cd05 --- /dev/null +++ b/hugo/content/en/partners/multi_tenant_billing/customer-onboarding.md @@ -0,0 +1,51 @@ +--- +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 proof of value, and work with the partner account team through the opportunity to establish and size a contract. + +Each step below matters: it keeps the opportunity properly registered with Datadog and, after the contract is established, gives the partner visibility into the customer's billing information in the Admin Org. + +## 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 Provisioner capability enabled; see [Requesting an Admin Org][3] if one isn't set up yet. + +When selecting a region for the Trial Org, match the prospect's environment where possible, considering 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 + +Share the new Trial Org information 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. + +## Related docs + +- [Cost and Usage Visibility][5]: How usage and cost data appears from the Admin Org after a customer organization's contract is activated. +- [Troubleshooting][6]: Common issues along the way. + +[1]: https://partners.datadoghq.com +[2]: mailto:partner-support@datadoghq.com +[3]: /partners/multi_tenant_billing/#requesting-an-admin-org +[4]: /partners/multi_tenant_billing/trial-org-provisioning/ +[5]: /partners/multi_tenant_billing/cost-and-usage-visibility/ +[6]: /partners/multi_tenant_billing/troubleshooting/ diff --git a/hugo/content/en/partners/multi_tenant_billing/trial-org-provisioning.md b/hugo/content/en/partners/multi_tenant_billing/trial-org-provisioning.md new file mode 100644 index 00000000000..1dcc09d27e3 --- /dev/null +++ b/hugo/content/en/partners/multi_tenant_billing/trial-org-provisioning.md @@ -0,0 +1,56 @@ +--- +title: Trial Org Provisioning +description: "Provision trial Datadog organizations for customers directly from an Admin Org." +--- + +## Overview + +An Admin Org with the Trial Org Provisioner capability enabled can provision trial Datadog organizations for prospective customers directly. This speeds up running proof-of-concept engagements at scale. The underlying opportunity should still be registered with Datadog, so the deal is tracked and credited to the partner; see [Onboarding a New Customer][4] for the full process. Trial Orgs created this way run for 30 days, instead of the standard 14-day trial period. + +{{< img src="partners/multi_tenant_billing/trial_org_provisioning.png" alt="Trial Org Provisioning page on the Admin Org homepage." style="width:100%;" >}} + +If the {{< ui >}}Trial Org Provisioning{{< /ui >}} page isn't available in the Admin Org, contact [partner-support@datadoghq.com][1] to have this capability enabled. + +## Provision a Trial Org + +1. Log in to the Admin Org. The {{< ui >}}Trial Org Provisioning{{< /ui >}} page appears as the homepage. To return to it from elsewhere in the Admin Org, click the Datadog logo in the top left. +2. Complete the form: + + | Field | Required | Description | + |---|---|---| + | Region | Yes | `ap1`, `eu1`, `us1`, `us3`, or `us5`. Match the customer's cloud provider, geography, and compliance needs where possible; default to `us1` if there are no specific requirements. | + | Trial Org Name | Yes | Must not exceed 32 characters. | + | Customer Name | Yes | The end customer this Trial Org is for. | + | Partner Notes | No | Any context worth sharing with the Datadog account team. | + | Invitee(s) List | Yes | Comma-separated emails to invite to the new org with the Admin role. | + +3. Click {{< ui >}}Submit{{< /ui >}}. + +The Trial Org is created immediately. The result panel shows the new org's name, org ID, and status message. + +## Find the Trial Org ID + +If the org ID from the result panel wasn't captured, retrieve it by logging in to the Trial Org and opening the browser's JavaScript console: + +```javascript +JSON.parse(document.querySelector('#_current_user_json').value).org.id +``` + +A bookmarklet works too: create a bookmark named `Get Datadog Org ID` with the following as its URL, then click it from any page in the Trial Org to display the ID in a browser alert: + +```javascript +javascript:(function() {var orgId = JSON.parse(document.querySelector('#_current_user_json').value).org.id; alert("Datadog Org ID is " + orgId);})(); +``` + +## After provisioning + +A Trial Org's usage is not visible from the Admin Org on its own. Share the new Trial Org's name and org ID with the partner account team so it can be associated with the opportunity registered on the [Partner Portal][2]. The customer organization becomes connected to the Admin Org, and its usage visible, once it has an active contract associated with the partnership. + +## What's next + +See [Cost and Usage Visibility][3] for how usage and cost data appears from the Admin Org after a customer organization is connected. + +[1]: mailto:partner-support@datadoghq.com +[2]: https://partners.datadoghq.com +[3]: /partners/multi_tenant_billing/cost-and-usage-visibility/ +[4]: /partners/multi_tenant_billing/customer-onboarding/ diff --git a/hugo/content/en/partners/multi_tenant_billing/troubleshooting.md b/hugo/content/en/partners/multi_tenant_billing/troubleshooting.md new file mode 100644 index 00000000000..2607124cb22 --- /dev/null +++ b/hugo/content/en/partners/multi_tenant_billing/troubleshooting.md @@ -0,0 +1,26 @@ +--- +title: Troubleshooting +description: "Common issues partners encounter with Admin Org, Trial Org provisioning, and customer org connections." +--- + +## Trial Org creation fails or returns an error + +Submit the {{< ui >}}Trial Org Provisioning{{< /ui >}} form again. If the error persists, contact [partner-support@datadoghq.com][1] with the Trial Org name and region that failed. + +## A customer org isn't appearing under an Admin Org + +A customer org connects to the partner Admin Org automatically when its contract includes the partnership and is active. If a customer's org is missing, contact [partner-support@datadoghq.com][1] for support. + +## The Trial Org Provisioning page isn't available + +This capability must be enabled on the Admin Org. Contact [partner-support@datadoghq.com][1] to have it enabled. + +## A partner isn't invited to a new Admin Org + +If a partner isn't invited after an Admin Org is created, contact [partner-support@datadoghq.com][1]. + +## Further help + +For any issue not covered above, contact [partner-support@datadoghq.com][1]. Include the Admin Org ID or name and, where relevant, the Trial Org ID or customer org ID. + +[1]: mailto:partner-support@datadoghq.com diff --git a/hugo/static/images/partners/multi_tenant_billing/admin_org_hierarchy.png b/hugo/static/images/partners/multi_tenant_billing/admin_org_hierarchy.png new file mode 100644 index 00000000000..cedd3c3520e Binary files /dev/null and b/hugo/static/images/partners/multi_tenant_billing/admin_org_hierarchy.png differ diff --git a/hugo/static/images/partners/multi_tenant_billing/customer_contracts.png b/hugo/static/images/partners/multi_tenant_billing/customer_contracts.png new file mode 100644 index 00000000000..12a9ec9d9f4 Binary files /dev/null and b/hugo/static/images/partners/multi_tenant_billing/customer_contracts.png differ diff --git a/hugo/static/images/partners/multi_tenant_billing/customer_contracts_detail.png b/hugo/static/images/partners/multi_tenant_billing/customer_contracts_detail.png new file mode 100644 index 00000000000..b663e97078f Binary files /dev/null and b/hugo/static/images/partners/multi_tenant_billing/customer_contracts_detail.png differ diff --git a/hugo/static/images/partners/multi_tenant_billing/customer_contracts_invoices.png b/hugo/static/images/partners/multi_tenant_billing/customer_contracts_invoices.png new file mode 100644 index 00000000000..6a0d26bd613 Binary files /dev/null and b/hugo/static/images/partners/multi_tenant_billing/customer_contracts_invoices.png differ diff --git a/hugo/static/images/partners/multi_tenant_billing/partner_portal_registration.png b/hugo/static/images/partners/multi_tenant_billing/partner_portal_registration.png new file mode 100644 index 00000000000..d607aa8ac82 Binary files /dev/null and b/hugo/static/images/partners/multi_tenant_billing/partner_portal_registration.png differ diff --git a/hugo/static/images/partners/multi_tenant_billing/trial_org_provisioning.png b/hugo/static/images/partners/multi_tenant_billing/trial_org_provisioning.png new file mode 100644 index 00000000000..a0edc903f1a Binary files /dev/null and b/hugo/static/images/partners/multi_tenant_billing/trial_org_provisioning.png differ diff --git a/hugo/static/images/partners/multi_tenant_billing/usage_metrics_rollup.png b/hugo/static/images/partners/multi_tenant_billing/usage_metrics_rollup.png new file mode 100644 index 00000000000..57bec1e7b6a Binary files /dev/null and b/hugo/static/images/partners/multi_tenant_billing/usage_metrics_rollup.png differ