Page Comparison

We're excited to announce the availability of scheduled billing plan changes upon renewal for Microsoft NCE subscriptions. This Storefront feature allows you to schedule a change of the billing plan (when applicable) that will take place during the renewal date of the NCE subscription. Possible billing plans include the Monthly, Annual, and One-time Payment.

💎 Value: This feature in the Storefront portal gives you greater control and flexibility over your Microsoft subscriptions by allowing you to automate billing plan changes at the renewal date to reduce administrative overhead and improve forecasting. This proactive approach simplifies subscription management.

🚀 Activation: Key prerequisites for the feature to function include:

• Auto-renewal option to be enabled,

• Billing plans to be active on both the instance and the account,

• Billing plans to be supported for the product SKU by Microsoft.
  

⚙️ How it works: From the Subscription view page in Storefront, click the Manage Renewal option from the I want to… button. In the respective pop-up window that appears, select the desired billing frequency (e.g., monthly, annual, or one-time payment) for the next term, provided the product supports it and your account and instance meet the necessary prerequisites mentioned above (like auto-renewal and billing plans being enabled).^{These changes are then saved by clicking on the Submit button and automatically applied when the subscription renews.}

⌛ Coming soon: Upcoming releases will add the ability to change the Billing Term in the Storefront portal.

In this release, we have established a Locked Window period when managing future changes to Microsoft NCE subscriptions during renewals. This measure aims to prevent billing cycle inconsistencies between our system and the Microsoft Partner Center (MPC). Specifically, the Locked Window restricts the scheduling of changes for a period of 2-3 days before and after the renewal date of NCE subscriptions. This enforced timeframe helps to address potential errors caused by discrepancies in subscription start and end dates, as well as renewal dates between the two aforementioned platforms.

💎 Value: This Locked Window for changes during NCE subscription renewals minimizes errors and ensures seamless processing by preventing changes during critical renewal periods. This improves reliability and reduces the need for manual intervention, leading to a more predictable and consistent experience aligned with the Microsoft Partner Center.

⚙️How it works: This window is calculated automatically by comparing the renewal dates between our platform and MPC, converting them to UTC, and applying a 24-hour tolerance. During the Locked Window, scheduling or revoking scheduled (future) changes is prohibited. If renewal dates between the two platforms differ by more than 24 hours, all scheduled actions are blocked, and you must contact our support team.

💡 Tip: Ensure you plan any necessary scheduled changes during the renewal of your NCE subscription three days before or after your renewal date. This ensures alignment between systems and minimizes errors.

We are now enforcing a stricter validation process at the API level, ensuring that only authorized Storefront users can make sensitive changes to other users and their passwords, based on their role and permissions.

💎 Value: This improvement prevents unauthorized sensitive changes and reduces the risk of potential security breaches or accidental modifications via API, making user management compliant and safer.

We have successfully eliminated the unnecessary credit limit check that was previously preventing the Adobe “VIP MP Migration” and the “Reseller Change” tool processes from completing successfully. Now, these tools can run smoothly and without interruptions.

💎 Value: This improvement creates a seamless workflow and an improved user experience for migrations and reseller changes.

We are glad to introduce a new option inside our Adobe Administration Tool that allows you to review and confirm or update your customers' contact details, such as their email and phone number, and automatically trigger the resend of the “Welcome email” dispatched directly from Adobe.

💎 Value: This option allows users to resend the Adobe Welcome email directly to a customer after changing (or not changing) their email address, eliminating the need for external support or workarounds.

⚙️ How it works: Navigate to the Adobe Administration Tool, via the BSS Setup module, select the three dots (“…”) next to your chosen customer, and select the Manage Adobe Contact option. A new pop-up window will appear, allowing you to review and, if needed, update your customer's contact details (email address and phone number). By enabling the checkbox and then clicking on the Send Details button, regardless of whether changes are made, you authorize Adobe to use this information to resend the Welcome email to the provided (new or existing) contact email address.

The following issue was addressed, with fixes applied where necessary:

1. Issue with Reducing Add-On Quantity Before Auto-Renewal - Issue Resolved: We have resolved an issue where users encountered errors when trying to reduce the add-on quantity before auto-renewal. Customers were being prevented from decreasing the quantity from 1500 to 1000, even when all conditions were met. The fix involves adding extra validations for product type quantity limits during the subscription management renewal process. This ensures that add-on quantity changes or cancellations at the end of the billing cycle are now processed correctly, without errors.

2. Issue with Subscription Cancellation Notification Error - Issue Resolved: We have resolved an issue where, in the latest release, 3.28.178, an error occurred with the new notification template "Alert for Subscription cancellation failure," triggering mass emails for all subscription cancellation actions. This issue was caused by the notification service sending bulk notifications due to a misconfiguration of a field. The issue has been fixed by ensuring the misconfigured field was receiving the proper value, preventing it from being incorrectly processed and triggering mass emails.

3. Incorrect Bundle Invoice Amounts Display - Issue Resolved: We have resolved an issue where bundle item invoices displayed incorrect amounts in the transaction currency, which differed from those in the base currency. This discrepancy occurred due to the inclusion of bundle and sub-items, resulting in inflated totals. The problem was traced to a scalar function, which has now been corrected to exclude bundle child items. This fix ensures that the totals in the transaction currency are accurate.

4. Sync Issue for Existing Microsoft Tenants - Issue Resolved: We have resolved an issue where there was a problem preventing existing accounts from syncing due to a domain conflict, where users encountered errors indicating the domain was already in use. Following recent API changes by Microsoft, we identified and resolved the issue swiftly. Users can now successfully sync their existing accounts without encountering errors. This fix ensures smoother integration and operation for all affected tenants.