Once the toggle button is turned ON, a pop-up window appears, allowing the Storefront Buyer user to align the subscription end date with another existing NCE subscription, which will be chosen via a list of available subscriptions. The list of available subscriptions is populated based on the rules mentioned above.

On this drop-down list, Storefront Buyer users can see the existing subscriptions that fit the profile already mentioned, their subscriptions' friendly names-name, billing cycles (terms), and end dates.

In case of no eligible active NCE seat-based subscription availability, an informative message appears within the pop-up stating: “No active non-trial NCE subscriptions to align with”.

Once the Storefront Buyer user select selects a subscription to align with, they can see the new end date of their subscription to be created on a preview, on the same pop-up window, under the section called Adjustment Preview.

When the Storefront Buyer user have has selected a specific end date from an existing NCE subscription and click clicks on the Save button, the pop-up window closes, and they can see their chosen end date next to the End Day Alignment toggle, along with a pencil icon, in case they wish to re-edit the end date of the subscription.

If Storefront Buyer user users no longer want to apply the End-Date Alignment, they can simply switch the toggle button OFF again, and the subscription end date will return to its original value.
Once the Storefront Buyer user successfully complete completes the checkout process, the new NCE subscription will be created and will have the same end date as the existing active NCE subscription that the user had previously chosen.

NCE Coterminosity Examples

In this section, you can find five tabs with end-date alignment examples from the Microsoft documentationto better understand how the actual NCE Coterminosity functions.

Rw ui tabs macro
Rw tab title 1-Month to 1-Month Rw tab title 1-Month to 1-Year Rw tab title 1-Year to 1-Year Rw tab title 3-Years to 1-Year Rw tab title 1-Year to 3-Years

Managing Coterminated NCE Subscriptions

The following bullet points briefly explain how the coterminated NCE subscriptions are managed.

• Invoices: The prorated amount of a coterminated NCE subscription is calculated similarly to a subscription with proration, which essentially creates a mini billing cycle at from the beginning(first billing cycle) until the second billing cycle, when the two subscriptions will be fully aligned.

• Upgrade: The full and partial upgrades of coterminated NCE subscriptions are fully supported since they create a new subscription from scratch, and that new subscription has as the Start Date the date of ’s end date of the coterminated NCE subscription was based on.

• Suspension: The new commerce experience (NCE) suspension policies also apply here, as well. Microsoft Partners can suspend and then resume a coterminated NCE subscription at any time without cancellation or termination. However, the billing of the Partner continues during the suspension.

• Cancellation: The new commerce experience (NCE) cancellation policies also apply here, as well. Therefore, the new coterminated NCE subscription has a 7-day cancellation window, within which it can be canceled, in the prorated way. As a result of a cancellation within the allowed timeframe, a prorated credit invoice is created and is based on the number of active days in this first (short) billing cycle.

• Installments: Currently, the feature of coterminosity is incompatible with the feature of Installments. However, in the upcoming releases, it will become available.

• Import Customers Tool: Coterminated NCE subscriptions are fully supported on the Import Customers Tool.

• Health Check Mechanism: The Health Check Mechanism (HCM) fully support supports coterminated subscriptions.

• Price Protection: The coterminated NCE are price protected with the same rules that apply to for all NCE subscriptions. Since the first billing cycle of the newly created coterminated NCE subscription is short, the price protection effective end date also follows that logic. On renewal, the subscription will enter a new price-protected period, and the protected prices will be the prices that are in effect on renewal.

For example:

• Let’s assume you are ordering an NCE Product with a price protection term=12 on an annual unit.

• The existing NCE subscription End Date (the one that you want to be aligned to) is 31/10/2023.

• The new NCE subscription is eligible for cotermination and has a Start Date of 20/6/2023.

➡️ The first (short) billing cycle of the (new) coterminated NCE subscriptions is: 20/06/2023 - 31/10/2023

➡️ The second (normal) renewed billing cycle of the (new) coterminated NCE subscription is: 01/11/2023 - 31/10/2024

Therefore, the prices of the (new) coterminated NCE subscription will be protected during the first (short) billing cycle, and on subscription renewal, the latest prices and price protection will be automatically retrieved one last time, and those new price-protected prices will be applied for the rest of the term, which in this case is 12 months.

Coterminosity for Tenant Organizations

Storefront users of a tenant reseller organization can create an NCE subscription with a coterminated end date through coterminosity with an existing subscription. However, for coterminosity to be available for tenant reseller organizations, a root organization that never had enabled coterminosity before has to perform a Get Services Definition action in the respective instance. Afterwards, the products that have been imported to the catalog via the Get Services Definition action and have the Enable Custom End Date feature set to True on the root organization need to be transferred as such to the tenant organization, as well.

• For existing tenants (existing before the coterminosity feature was enabled in the root organization), an 'Update Tenant' action needs to be executed within the root organization to enable coterminosity in the Tenant Organization.

• For new tenants (created after enabling coterminosity in the root organization) will automatically inherit the coterminosity settings during their creation.

Furthermore, concerning the invoicing and backordering of coterminated NCE subscriptions from tenant organizations,they are back ordered as such back to root organization. Different time zones between the Root and the Tenant organizations do not influence end-date alignment in any way. Also, the coterminated end date is the same as with Microsoft Partner Center in both the root and tenant organization when backordering is active.