Appearance
Latest updates
Overview
This page explains release maturity labels used in the source product materials. It also lists examples explicitly marked as new or Beta. This is not a dated changelog of every release. Availability depends on your environment, purchases, permissions, and configuration.
Maturity labels
| Label | Meaning | What to confirm |
|---|---|---|
| New | The source identifies this version as replacing or enhancing an older capability | Whether your organization uses the new or legacy mode |
| Beta | The capability is in testing or limited release | Eligible organizations, accounts, and current entry points |
| Phased rollout | The capability is available only to selected organizations, accounts, or scenarios | Whether it is enabled for your tenant |
| Legacy | The source retains the capability, but a newer version or replacement exists | Whether existing data and processes still depend on it |
| Retired | The capability is no longer recommended for new configuration or use | Whether migration, replacement, or compatibility work is required |
Examples in the current materials
| Capability | Current label | Confirmed behavior | Source |
|---|---|---|---|
| Spare part consumption | New | The new version uses a master-detail structure and records multiple parts. Some features differ among simple, standard, and advanced modes. | New spare part consumption |
| Service status overview | Beta | The source groups this capability under the Service Data Dashboard (Beta). | View the service status overview |
| Service provider account | New | The source marks this account capability as new. Confirm the active provider account mode before use. | Configure service provider accounts and engineers |
This table records only maturity and behavior explicitly stated by the source. It does not infer release dates, rollout size, or automatic upgrades.
Recommendations
- For a New feature, confirm the active mode before reading its configuration and usage guides.
- For Beta or Phased rollout, confirm account access before treating a missing entry point as a permission error.
- For Legacy or Retired, identify dependent data and processes before planning migration or replacement.
- For purchase, permission, or process questions, see Purchase and activate Service Pass, Roles and permissions reference, and Feature versions and usage restrictions.