Work 365

Azure Plan

202 views February 28, 2020 June 18, 2020 0

What is Azure Plan?

Essentially, Azure plan is a group of subscriptions, which collectively contribute to the overall consumption for the customer.

In Work 365, Azure plan is set up as a usage based subscription with a different provider part number. This applies to both the Azure Plan and the corresponding ‘entitlement’ subscriptions. The Azure Plan subscription is created as the parent of the ‘entitlement’ subscriptions by default, although this can be modified by Work 365 users.

Prerequisites to Azure Plan:

  • Customer must have signed the Microsoft Customer Agreement.

Steps to provisioning an Azure plan subscription from Work 365.

  • Create the Azure Plan product.
    • Product Name: Azure Plan
    • Product ID: Azure Plan
    • Billing Type: Usage
    • Provider Part Number: DZH318Z0BPS6:0001
  • Create a new usage based subscription, and select Azure Plan as the product.
  • Then Work 365 will attempt to provision this new subscription with Partner Center.
  • After an Azure Plan subscription is created and sync’ed with Partner Center, the corresponding Azure entitlement subscription is not available immediately – it will be sync’ed as part of the daily Partner Center to Work 365 sync process (once every 24 hours). Subscriptions can also be synced manually directly from the Billing Contract via the “Sync Subscriptions” button.
  • The entitlement subscription will sync to Work 365 automatically as a billable addon subscription to the parent Azure plan subscription.

Note: Only one Azure Plan per customer is allowed by Microsoft. An Azure Plan subscription which is created for a customer who already has an Azure Plan subscription will fail to provision.

Additional Azure plan entitlement subscriptions will also sync to Work 365 via the daily sync process,

Note: Mixing of Azure Plan with ‘classic Azure subscriptions’ is also not allowed. A customer cannot have a classic Azure subscription and an Azure Plan subscription. An Azure Plan subscription which is created for a customer who already has one or more classic Azure subscriptions will fail to provision.

  • Currently, transitioning from a classic Azure subscription to Azure Plan must be done via the Partner Center (https://docs.microsoft.com/en-us/partner-center/azure-plan-transition).
  • Classic Azure subscriptions which are transitioned to the Azure Plan in Partner Center will do the following:
    • Create an Azure plan in Partner Center which will sync to Work 365 as a subscription.
    • The previous “classic” Azure subscription becomes the new corresponding entitlement subscription. This Azure subscription will have the same provider part number as before.
    • In Work 365, to associate this entitlement subscription to the Azure plan, it must become a child subscription of the Azure plan.
    • Action: As the previous Azure subscription is already created in Work 365, the system will not automatically map the Parent Azure Plan subscription to the entitlement “Microsoft Azure” subscription. Thus, this association must be set up manually.
      • Open the “Microsoft Azure” subscription, and in the Parent subscription field of the subscription form search for and select the Azure plan subscription belonging to the same customer. This will establish the Azure plan subscription as the Parent subscription.

Note: Currently, daily Usage Details data is not available for Azure Plan based subscriptions.

Note: Usage Summary data for Azure Plan is provided via the modern (G-Series) Provider Invoice. Usage Summary data is synchronized against each entitlement subscription, rather than at the Azure Plan level. As consumption is synced at the entitlement level, any additional markup % applied to an Azure plan subscription should also be added at the entitlement level. Note Azure plan consumption is calculated the same as classic Azure consumption; therefore, the markup % applied should be the same markup applied to classic Azure subscriptions. 

How to deactivate an Azure Plan

To deactivate the Azure Plan, please follow these steps:

  • Go to the Azure Portal and deactivate all the entitlements under the Azure Plan
  • Go to Partner Center and deactivate the Azure Plan
  • In Work 365, go to the License Change Logs tab on the Azure Plan subscription, there should be a new line item for the deactivation event

Changes to Usage-based invoicing to support Azure Plan

With the introduction of Azure Plan, v3.0 introduces a new invoicing feature for usage-based subscriptions. This feature applies only when both parent and child subscription are usage-based. The following charts points to various invoicing scenarios with Azure plan, depending on how Azure Plan and the associated entitlement subscriptions are set up in Work 365.

  • Child subscriptions: When you have a product bundle with a billable parent subscription and nonbillable child subscription(s)
  • Addon subscriptions: When you have a product bundle with a billable parent subscription and billable addon subscription(s)

 

Invoicing Scenarios:

1 Azure Plan to 1 Azure Entitlement Ratio

  1. Azure Plan: billable
    1. Azure entitlement billable(addon): billed at entitlement level
  2. Azure Plan billable:
    1. Azure entitlement non-billable (child): billed at Azure Plan level
  3. Azure Plan non-billable
    1. Azure entitlement billable: billed at entitlement level
  4. Azure plan non-billable
    1. Azure entitlement nonbillable: not billed (Warning)

1 Azure Plan to Multiple Azure Entitlements

  1. Azure Plan: billable
    1. Multiple Azure entitlements all non-billable: billed at Azure Plan level
  2. Azure plan: billable
    1. Multiple Azure entitlements all billable: billed at entitlements level
  3. Azure plan: billable
    1. Multiple Azure entitlements non-billable: billed at Azure Plan level
    2. Multiple Azure entitlements billable: billed at entitlements level
  4. Azure Plan: non-billable
    1. Multiple Azure entitlements non-billable: not billed (Warning)
    2. Multiple Azure entitlements billable: billed at Azure Plan level

 

 

 

 

Was this helpful?