Align Subscription Billing with standard user experience and terminology
Important
Some of the functionality described in this release plan has not been released. Delivery timelines may change and projected functionality may not be released (see Microsoft policy). Learn more: What's new and planned
| Enabled for | Public preview | General availability |
|---|---|---|
| Users, automatically | - | Apr 2025 |
Business value
We're making it easier to work with Subscription Billing by updating the terminology we use for its features in the product and documentation.
Feature details
While Subscription Billing is a subscription-oriented module, it supports other valuable scenarios. Until this release the underlying objects and the user-facing elements were impacted by the broad and multipurpose applications and scenarios supported by Subscription Billing. Now we are simplifying the user and developer experiences by embracing the subscription-based nature of the module.
Generally, we're renaming objects and UX elements (such as captions) that were called "Service" to "Subscription". For example, the "Service Object" entity now becomes the "Subscription" entity. The goal is to improve the user experience, the clarity of the documentation, and the consistency of the terminology across the application.