License Usage

License Usage helps teams analyze software license allocation, product usage, user activity, workspace usage, sign-in activity, and device security posture across tenants and products.

Use this Analytics cube to understand how licenses are assigned, consumed, and available across the organization. It helps SaaS, IT, finance, and governance teams identify unused capacity, review adoption, validate product activity, and support license spend decisions.

For shared Analytics workspace behavior, report building, visualizations, filters, saved reports, and pre-aggregations, refer to Getting Started with Analytics.

What License Usage helps you answer

License Usage helps teams answer questions such as:

• Which products have available licenses that are not being used?

• Which tenants have the highest license consumption?

• Which users are assigned licenses but show low or no product activity?

• Which applications have active user activity?

• Which Power BI workspaces are active, modified, or assigned to dedicated capacity?

• Which Teams workspaces show active usage?

• Which users have recent or stale sign-in activity?

• Which Defender-enrolled devices carry risk or exposure signals?

• Which vendors, tenants, or products require license review?

Access License Usage

To open License Usage analytics:

1. Navigate to Analytics

2. Select License Usage

The page opens the License Usage analytics cube.

License Usage data sources

License Usage can use license, product, activity, workspace, and device data loaded into Yarken.

Data may come from:

• Tenant license usage uploads

• Individual license usage uploads

• AI License Register uploads

• Product usage uploads

• Microsoft Graph API integrations

• Power BI activity data

• Microsoft Teams activity data

• Entra ID sign-in activity

• Microsoft Defender enrolled device data

The available fields depend on the integrations, uploads, and tenant configuration in the environment.

Tenant License Usage

The Tenant License Usage group provides product-level license allocation across tenants.

Common fields include:

Use this group to review allocation, consumption, and available capacity by tenant and product.

Individual License Usage

The Individual License Usage group supports user-level license reporting.

Common fields include:

Use this group to review who holds licenses and where assigned licenses may need follow-up.

AI License Register

The AI License Register group provides monthly AI license-assignment data across providers and services.

Use this group to analyze:

• who holds each AI license,

• AI provider and service,

• license type and tier,

• assignment status and role,

• assigned, removed, and last-used dates,

• configured caps, and

• license changes over time.

Measures include:

Dimensions include:

• Month Start

• Collector Source

• Provider Name

• Service Name

• Billing Account Id

• Principal Id

• User Email

• Licence Type

• Licence Tier

• SKU Id

• Role

• Status

• Assigned At

• Removed At

• Last Used At

• Cap Unit

• Cap Period

• Cap Source

• Snapshot At

• Tags

Use the standard Year and Month dimensions to filter by reporting period.

Automatically collected AI licence data

Yarken collects supported seat and licence-assignment data daily from OpenAI (ChatGPT Enterprise), Anthropic (Claude Enterprise), and GitHub Copilot using separate Advanced seat pipelines. Collected records are available in the AI License Register dataset in Analytics > License Usage.

Use the existing Licences and Users measures with provider, service, status, licence type, tier, and reporting-period dimensions to review:

• Licence holders and assigned seats by provider and service.

• Assignment status and available assigned, removed, and last-used dates.

• Licence inventory trends across reporting periods.

For the supported seat pipelines, connection requirements, and data-collection workflow, see AI License Register.

Rates

The Rates dataset in License Usage provides the monthly AI seat rates maintained under Yarken Designer > Consumption > Rates. Use these fields to review configured prices across providers, services, licence types, and tiers.

Available measures

Available dimensions

• Provider Name

• Service Name

• Licence Type

• Licence Tier

• Currency Code

• Valid From

• Valid To

Use these fields to compare the configured price for a service or tier and review recorded validity periods. New uploads appear in Analytics after the cube refresh completes, usually within a few minutes.

To create, upload, or manage rates, see Manage AI seat rates.

Product Usage

The Product Usage group helps analyze application-level usage.

Common fields include:

Use this group to compare assigned licenses against actual product activity.

Power BI Workspaces

The Power BI Workspaces group provides workspace-level reporting for Power BI usage and administration.

Common fields include:

• Report Date

• Workspace Name

• Status

• Dedicated Capacity

• Modified Since

• Count

• User Count

Use this group to review workspace activity, capacity assignment, and user participation across Power BI environments.

Teams Activity Details

The Teams Activity Details group supports Microsoft Teams usage analysis.

Common fields include:

• Report Date

• Team Name

• Team Type

• Last Activity Date

• Count

• Active Users

Use this group to review active teams, inactive teams, and user activity across Teams workspaces.

Sign In Activity Details

The Sign In Activity Details group supports user access and adoption analysis.

Common fields include:

• Report Date

• User Email

• User Name

• Last Accessed App

• Last Activity Date

• Count

Use this group to identify dormant users, recent activity, and applications associated with sign-in behavior.

Defender Enrolled Devices

The Defender Enrolled Devices group supports device-level security and endpoint visibility.

Common fields include:

• Report Date

• Computer DNS Name

• OS Platform

• OS Version

• Health Status

• Exposure Level

• Risk Score

• Is AAD Joined

• AAD Device ID

• Last Seen

• First Seen

• Count

Use this group to analyze enrolled devices, endpoint health, exposure levels, and device activity dates.

Timeline and tenant dimensions

License Usage includes supporting dimensions for time and tenant analysis.

Common timeline fields include:

• Year

• Quarter

• Month

Common tenant fields include:

• Name

• Tenant Id

• Tenant Domain Name

• Vendor

Use these fields to compare usage across reporting periods, tenants, vendors, and product environments.

License allocation and usage analysis

License Usage helps compare entitlement with activity.

Use these views together to support renewal planning, license reclaim decisions, and adoption reviews.

Recommended report structures

Start with a clear license question, then select the fields that explain allocation, consumption, activity, or risk.

Save recurring views for license reviews, SaaS governance, renewal planning, and product adoption reporting.

Relationship with SaaS and license governance

License Usage supports software license governance by combining allocation, activity, tenant, and product data.

Use it to:

• Review license availability before renewals

• Identify products with unused capacity

• Compare assigned licenses with user activity

• Support reclaim and reassignment decisions

• Track tenant and product adoption

• Review workspace and device activity

• Improve license planning conversations with finance and IT owners

This gives teams the operational evidence needed for license management decisions.

Relationship with integrations and uploads

License Usage depends on data loaded through uploads or integrations.

Upload-based sources can support:

• Tenant license usage

• Individual license usage

• AI License Register

• Product usage

Integration-based sources can support:

• Microsoft license details

• Product usage details

• Entra ID activity details

• Teams activity details

• Defender enrolled device details

• Power BI workspace activity

Use the Analytics view after the data has been loaded, validated, and refreshed.

Relationship with Multi Cube

License Usage can be analyzed on its own or combined with other data in Multi Cube.

Multi Cube can help connect license data with employee, asset, spend, or product information where matching fields are available.

Example use cases include:

• Linking user email to employee or asset records

• Comparing license usage with application spend

• Reviewing product adoption against cost

• Connecting tenant-level license data with vendor or contract reporting

Use Multi Cube when the question cannot be answered from the License Usage cube alone.

Common use cases

License Usage is commonly used for:

• SaaS license review

• Renewal planning

• License reclaim analysis

• Product adoption reporting

• Tenant-level usage review

• User-level license investigation

• Power BI workspace governance

• Teams activity reporting

• Sign-in activity review

• Defender device visibility

• Vendor and product usage analysis

Recommended practices

Use these practices when working with License Usage:

• Review total, consumed, and available licenses together

• Compare individual license assignment with product and sign-in activity

• Filter by tenant, product, vendor, and month before reviewing large datasets

• Use Power BI, Teams, and sign-in fields to understand actual activity

• Review Defender device fields separately from license allocation analysis

• Save standard license review reports for recurring governance meetings

• Confirm upload or integration freshness before using results for renewal decisions

• Use Multi Cube for cross-domain license and cost analysis

Consistent license reporting improves spend control, product adoption visibility, and governance quality.

Troubleshooting License Usage results

If License Usage does not show expected results, check:

• The active Month, Year, Tenant, Product, or Vendor filters

• Whether the relevant upload or integration completed successfully

• Whether the selected reporting period contains license data

• Whether tenant identifiers match the uploaded or integrated records

• Whether product names and SKU IDs are mapped consistently

• Whether user email values match source data

• Whether Microsoft Graph, Power BI, Teams, Entra ID, or Defender data has refreshed

• Whether the selected field belongs to the expected License Usage group

• Whether the AI License Register upload completed successfully and contains data for the selected reporting period

• Whether you selected fields from the AI License Register group when building an AI license report

Next step

• Multi Cube

Related content

• Getting Started with Analytics

• Software License Intelligence

• Tenant License Usage

• Individual License Usage

• AI License Register

• Product Usage

• Monthly License Usage

• Application Usage

• Connected Data Sources (Integrations)

• Manage AI seat rates