Page Comparison

We're excited to unveil our latest expansion to the interworks.cloud platform with the introduction of the Microsoft New Commerce 'Education' and 'Non-profit' products. This enhancement is designed to empower your CSP business, fostering growth and delivering unparalleled convenience to your workflows, ensuring the vital compliance with Microsoft's latest updates and requirements. These Public Sector products are available only for Educational and Non-Profit organizations.

Key Characteristics of “Microsoft Public Sector (New Commerce)”

• Product Type: A new product type is introduced under the New Commerce ‘umbrella’: Microsoft Public Sector (New Commerce).

• Qualification: The new Product Type Characteristic emphasizes qualifications, ensuring that eligible organizations can access the right solutions.

• Pricing: No changes to pricing! Prices are automatically received from Microsoft and are based on the customer's Country.

• Streamlined Process: We’ve removed the checkbox labeled ‘Enable New Commerce’ from the Microsoft Service Manager Instances. As a result, all NCE (New Commerce Experience) products—both commercial and public sector—will now be created and/or updated automatically during the Get Services Definition process, after the 3.28.139 patch.

Identifying ‘Microsoft Public Sector’ vs ‘Microsoft Commercial (Online Services)’ Products

There are a few indicators to remember when differentiating between Public Sector New Commerce Experience (NCE) products and Commercial NCE products as well as between the two Public Sector qualifications.

1. Firstly, the Product Type field on the Product view page of the BSS portal is the key distinguishing component between the two NCE product types.

2. Secondly, the Qualification field on the Product view page of the BSS portal is also an important indicator as it differentiates between Educational Public Sector NCE products and Non-Profit Public Sector NCE products.

Important Notes:

1. Third Qualification Coming Soon: There is a third qualification called 'Government Community Cloud' which will be delivered at a later date.

2. Decoupling Exception: Organizations and instances with Decoupling will not receive Public Sector NCE products.

3. Subscription Import via the NCE Migration Tool: Please be aware that the import of Public Sector NCE subscriptions is not yet available. If you try to import them, an error message will be displayed.

In this release, we are introducing a new Storefront option called “Display My Workspace” that controls whether the My Workspace tab appears in the general menu of the Storefront. If it is disabled, it will affect your Storefront and all your Standard Edition reseller Storefronts meaning that the Storefront users will not be able to access their My Workspace page or the Manage Services from the Admin Panel. By default, this option is enabled.

With this release, Dropbox Sign product upgrade paths are introduced. The Dropbox Sign products have two plans, Standard, and Premium. A subscription with a product in the Standard Plan can only be upgraded to a Premium plan, and with the same billing term (annual to annual or monthly to monthly). Please note that the user will be notified if an upgraded or downgraded subscription does not meet the minimum quantity requirements. Lastly, downgrades are not supported for Drobox Sign plans.

With this release, we have introduced three new filters for the following endpoint of the Standard Reseller API.

• GET /api/orders -Retrieves all the orders. This can be utilized with the below filters*.

* Via the Standard Reseller API, you can utilize the following filters to find the orders through the aforementioned call:

1. Confirmed - When this filter is utilized, it returns only the Confirmed orders. The “Confirmed” orders term refers to all the orders except the orders with statuses 'Draft', 'Reseller Pending Approval', and 'Cancelled by Reseller'.

2. Draft - When this filter is utilized, it returns the orders with ‘Draft’ status.

3. All - When this filter is utilized, it returns both the ‘Confirmed’ and the ‘Draft’ orders.

We have made a minor update to the way add-ons for sub-products within a Bundle are displayed. Specifically, when an add-on of a sub-product is included as part of the Bundle configuration, it will no longer appear in the list of add-ons in the "Add-ons" section of the Bundle view page in Storefront or the "Billing" section of the Bundle view page in the BSS portal.

As you already know, from the 3.28.134 release, paid subscriptions can be created only by placing an order and only trial subscriptions will be created using the current method of creating subscriptions. The API will also be updated to match this functionality, to align with the interface. Please note that on June 15th, the following API V2.2 endpoints will be deprecated:

• POST /api/Subscriptions

• POST /api/Subscriptions/invoiced

How to Create a Paid Subscription by Executing an Order

To create a paid subscription without the use of these endpoints, use the following API V3 endpoints:

• POST /api/orders - To create an order

• POST /api/orders/{orderId}/items - To add items to the order

• POST /api/orders/{orderId}/execute - To execute the order

• GET /api/orders/{orderId}/execute/status - To retrieve the status of the order

A paid subscription based on the order will be created when the status of the order is Executed.

API V3.0 - New Endpoint Addition for the Creation of a Trial Subscription

A new endpoint has been added to API V3.0 for the purpose of creating trial subscriptions:

[POST] /api/Subscriptions/Trials

The following issues were addressed, with fixes applied where necessary:

1. Add-On Display Issue in Bundle View: An issue was fixed related to the display behavior of a deleted add-on inside the Bundle view page. Previously, when add-ons were sent to the trash, they were still being displayed inside the Bundle view page. Now that this display behavior is fixed when an add-on is trashed, it is completely removed from both the Product’s add-ons section and the Bundle view page.

2. Billing Service Invoicing Process - Issue Resolved: An issue was fixed related to the Billing Service Invoicing process. Previously, when multiple orders were being executed, for example, on the 1st of the month, alongside the Billing Service Invoicing process, prorated billing subscriptions with renewals on the 1st of the month were invoiced on the 2nd, due to deadlocks. Now the invoices align as much as possible with the correct renewal dates.

3. Enhancing Subscription Assignment in the Multitenancy Logic of the Importer Tool for Accurate Billing: An issue was fixed related to the Multitenancy Logic of the Importer Tool when an end customer of a reseller wishes to change the reseller and import two or more subscriptions under his new end customer account/contact which belongs under the new reseller. Previously the new end customer would be created under the newly chosen reseller via the Import Tool and the first of the two subscriptions of the end customer would be assigned accurately under the new reseller’s account but the second subscription would be assigned under the account of the old reseller. We have now fixed this issue inside the Import Tool and subscriptions are accurately assigned to the end customer created under the new reseller.

4. Optimization of the ‘Template Evaluation' Process in the Email Notification Service: An issue was fixed related to the Template Evaluation process in our Email Notification service. Previously, when the system and customer templates of an organization were enabled, all templates were evaluated in a loop. However, for organizations with large amounts of data, this evaluation process caused timeouts due to the preconfigured timeout of 2 hours on a single database connection. We have addressed this issue by optimizing the process. Now, each template of an organization is evaluated on a different database connection, eliminating the timeout problem and ensuring smoother and consistent performance.

5. Trial Subscription Creation via API With Null Values Caused Error - Issue Resolved: An issue was fixed related to the creation of a Trial Subscription via API when non-compulsory variations were undefined. Previously, when users were attempting to create a trial subscription without specifying non-compulsory variations or having a default one, the system encountered an internal server error. Now the issue is resolved and the system automatically inserts null values in case the user omits entering variations.