When a paid subscription is created in reseller's BSS and it's for a service the is offered by the distributor, it is copied automatically to distributor BSS. if this is the first paid subscription for reseller's end customer, we first copy the customer in distributor BSS before proceeding with subscription creation. |
There will always be an one-to-one relation between the subscriptions in distributor and reseller BSSs. The subscription we create in distributor BSS will have the following values:
For the distributor to easily understand that a subscription has been copied in his BSS from reseller's BSS, we display a ribbon with the note: “This subscription is managed by <RESELLER NAME> Tenant Reseller”
What about trial subscriptions? We don't copy any trial subscriptions from reseller's BSS to distributor BSS. But when a trial is upgraded to a paid subscription, then we treat this subscription as a new one and we copy it to distributor BSS |
When a subscription is updated in the reseller’s BSS, the following actions will be applied in distributor's BSS. These changes happen simultaneously in both BSSs.
For each of these actions, a history record will be added in subscription details page in distributor's BSS.
Management of Azure subscriptions Any Azure subscriptions created in the reseller's BSS will be copied also in the distributor's BSS. Each time the Azure Service runs and updates usages on the Azure subscription in the reseller's BSS, it will also update the subscription's usage records in distributor BSS. The invoicing of the subscription will be done by collecting the invoice items from Microsoft Billing API and by applying the pricing rule the distributor has defined for the reseller. |
Below is a list of actions that the distributor is not allowed to execute:
Below is a list of action that the distributor is allowed to execute:
Below is a list of actions that the Tenant Reseller is not allowed to execute: