Microsoft Invoicing and Reporting

Microsoft CSP Invoicing and Reporting Customization

OneNeck can provide Microsoft CSP invoicing and reporting options to help ease administration of your billing information and enable distribution of costs to internal cost centers based on the following: tenant, source, subscription, resource group or Azure tags.

Based on the grouping choice you make, you can choose to receive a single or multiple invoices and a report that groups resource consumption in various ways.

Clients will typically configure on one or two of the available reporting options.

A specific resource will only be reported in one way, at the lowest level (5 is the lowest level) that it is referenced - see below.

Any resources that have not been configured at the lowest level can be configured to be caught at a higher level as a catch-all. (ie, when you use tagging, but forget to tag a new resource, it will be caught on at the source or subscription level.)

Option Applicable Description of Reporting Why Use Invoice Choice Report

Base Setup

Level 2

Level 3

Level 5 (lowest)

Level 1 (highest)

No reporting (default)

Azure, M365 Licensing

All resource consumption will be provided on a single invoice.

Normal billing requirements

Single invoice

No report

Option Applicable Description of Reporting Why Use Invoice Choice Report

Tenant

Azure, M365 Licensing

Report resourced consumption by tenant.

Multiple tenants

Single invoice

Spreadsheet showing resource consumption grouped by Microsoft Tenant. (optional)

Level 4

Option Applicable Description of Reporting Why Use Invoice Choice Report

Source (catch-all for subscription and Azure tagging)

Azure, M365 Licensing

Group resource consumption by the source from Microsoft:

Report resource consumption by source and provide separate invoices (example: create a report that groups licensing consumption separate invoice from Azure consumption.)

Single or multiple invoice(s)

Spreadsheet showing resource consumption grouped by source. (optional)

Licensing (typically M365) Azure Usage Azure Marketplace & One-time Usage This is across all subscriptions, sources and tenants.

Option Applicable Description of Reporting Why Use Invoice Choice Report

Subscription (catch-all for Azure tagging)

Azure only

Group resource consumption by subscription. Applicable to Azure consumption only. Consumption not mapped to subscription will be grouped by source catch-all.

Report Azure resource consumption by subscription

Single or multiple invoice(s)

Spreadsheet report showing resource consumption grouped by source. (optional)

Option Applicable Description of Reporting Why Use Invoice Choice Report

Resource Group

Azure only

Group resource consumption by Resource Group. Applicable to Azure consumption only. Consumption not mapped to a specific Resource Group or Groups will be grouped by source or subscription catch-all.

Report Azure resource consumption by Resource Group (in a specific subscription or across all subscriptions)

Single or multiple invoice(s)

Spreadsheet report showing resource consumption of a resource group itemized separately. (optional)

Option Applicable Description of Reporting Why Use Invoice Choice Report

Azure Tag

Azure plan subscriptions only

Group resource consumption by keys in Azure tags on resources used within Azure. Resources not tagged will be grouped separately as blank.

Report Azure resource consumption at a more granular level.

Single invoice

Spreadsheet report showing Azure consumption grouped by client defined key in Azure tag.

Reporting Azure and Licensing Usage by Tenant

Reporting Azure Usage and Licensing by Source

Reporting Azure Usage by Subscription (Azure only)

Reporting Azure Usage by Resource Group

Many OneNeck CSP clients have multiple Tenants within Azure. By choosing customized and reporting by tenant, a report showing Azure usage and licensing by tenant will be provided by email each month. All Azure usage and licensing will be presented on a single invoice.

Microsoft provides monthly usage information from a few different sources. By choosing customized invoicing and reporting by source, a report showing Azure usage and licensing by source will be provided by email each month. The current sources available are: 1. Azure Usage, 2. Licensing, and 3. One-time, Reserved Instances & MarketPlace. Azure usage and licensing can be provided on a single invoice or multiple invoices by source.

Many OneNeck clients have multiple Azure subscriptions and want to report or invoice on them separately. By choosing customized invoicing and reporting by subscription, a report showing Azure usage for each subscription will be provided by email each month. Invoicing of Azure usage by subscription can be provided on a single invoice or multiple invoices. This is for Azure subscriptions only.

Microsoft provides monthly usage information from a few different sources. By choosing customized invoicing and reporting by Resource Group, a report showing Azure usage and licensing by Resource Group will be provided by email each month. This feature is typically used to report separately on a specify resource group or groups that you want to separate. A resource group can be specified within a single subscription or across all subscriptions.

Setting Up Resource Tagging in Azure for Customized Microsoft CSP Invoicing and Reporting

OneNeck enables clients with Azure Plan subscriptions to group resource consumption using a 3-level hierarchy of tags. Typically, clients define a primary tag name that describes a cost center or department (such as Billing Group or Department or Cost Center). Up to 2 secondary tag names can be defined to further categorize resource consumption.

LEARN MORE ABOUT AZURE TAGS

Tagging in Azure

Resources in Azure can have tags added. Tags are passed to OneNeck with the monthly Microsoft billing information. OneNeck can parse through this information, looking for specific keys. A report can be generated that is sorted and grouped by metadata in the tags.

Tag Format

OneNeck will use three tags, one for the primary billing group and two additional tags that can be used for further grouping. The primary tag will determine the billing groups in the reporting. Where: - required for Azure tag grouping (ex. department, cost center number or name) , - optional tags used for grouping

Tag Name: Tag Value: Tag Name: Tag Value: Tag Name: Tag Value:

Notes:

Customer provides tag names Tag names that do not match will be ignored

Examples

The following examples describe formatting syntax and how OneNeck billing will interpret tagging. Client would like to see a report showing Azure consumption by BillingGroup and optionally Owner and Application.

Primary Tag (required) Billing Group Commerce Marketing Backoffice Secondary Tag (optional) Owner Smith Smith Johnson Patal Rogers Chen Tertiary Tag (optional) Application Rating Engine Reporting Orders Inventory Product Catalog Web Front End

Split Tagging with Cost Distributed Unevenly Across 2 Groups (Implicit Percentage)

The cost for this resource will be distributed evenly across two groups - "Commerce" and "Marketing" and sub-grouped with Owner = "Smith" and Application = "Rating". Note: The cost percentage is not specified.

The cost for this resource will be distributed unevenly across two groups – 10% to “Commerce” and 90% to “Marketing” and sub-grouped with Owner = “Smith” and Application = “Rating” Note: Percentage is specified for both groups.

Simple Tagging on an Azure Resource with Primary Tags and Secondary Tags

Split Tagging with Cost Distributed Evenly Across 2 Groups

Split Tagging with Cost Distributed Unevenly Across 2 Groups Using Percentages

Simple Tagging on an Azure Resource with Primary Tag Only

Split Tagging with Cost Distributed Unevenly Across 3 Groups (Implicit Percentage)

Split Tagging with Cost Distributed Unevenly Across 3 Groups

Misspelled Tag Value for Billing Group

Untagged Resource or Misspelled Tag name

(Over-allocated, Reducing 2nd Percentage and Dropping Unspecified Allocation)

(Over-allocated, Dropping Unspecified Allocation)

Simplest tagging for customized reporting. Only one billing group value is assigned. 100% of the resource consumption cost will be attributed to this single billing group. This resource will be grouped under "Commerce".

This resource will be grouped under "Commerce", and sub-grouped where Owner = "Smith" and Application = "Rating".

The cost for this resource will be distributed evenly across three groups – 10% “Commerce”, and 45% each for “Marketing” and “Backoffice” Note: Percentage is not specified for all values.

The cost for this resource will be distributed 20% “Commerce”, 80% for “Marketing” and 0% “Backoffice” Note: Percentage is not specified for all values.

The cost for this resource will be distributed 10% “Commerce”, 90% for “Marketing” and 0% “Backoffice” Note: Percentage is not specified for all values. Note: Percentages are incorrectly specified. OneNeck will start reducing from the unspecified or lowest percentage to reduce the total percentage to 100.

This resource will be grouped under a new value “Commmerce” (with 3 m’s) Note: the value is misspelled or not present.

Untagged or misspelled tag names will be reported under a blank billing group. Note: The tag name is misspelled or not present (extra “s” on the end of tag name.)

Fill out the form with your Azure billing requests.

2022 OneNeck IT Solutions

Setting up resource tagging in Azure

Azure billing requests

Setting up resource tagging in Azure

Azure billing requests