Find Communities by: Category | Product

CSP.png

 

Microsoft’s Cloud Solution Provider (CSP) program allows partners to completely own their end-to-end customer lifecycle, which may include activities such as deployment of new services, provisioning, management, pricing and billing.  The CSP program helps value-added resellers (VARs) and managed service providers (MSPs) sell Microsoft software and Cloud Service licenses with additional support so that you can become more involved with your customer base. This means that every cloud solution from Azure to Office 365 could be resold to your customers at a price that you set, and with unique value added by you. The goal of the CSP program is not simply to resell Microsoft services, but to enhance them and deliver them in a way that makes sense for you and your customers.

 

 

What's the fuss all about Azure Stack CSPs?

 

As an Azure Stack Product Technologist, one question I am frequently asked by customers who are existing Microsoft CSPs is, how to operate and offer services on Microsoft Azure Stack in a CSP model. Although this information is available through Microsoft Azure Stack online documentation and videos from various events, I am trying to consolidate that information into this blogpost as well as trying to explain the various CSP operating models in Azure Stack and the steps required to successfully manage and operate Azure Stack as a CSP.

 

The key difference between operating as an Azure CSP vs Azure Stack CSP is the additional responsibility of managing the Azure Stack Integrated system. Really? well, it really depends on the CSP operating model which we will discuss in detail in the subsequent sections in this blog.

 

What's the Business Opportunity here?

 

Today, Azure services are available in 54 regions spread across various geographical locations. Which also means that Azure services are not available in every nook and corner of the globe. This could be due to poor internet connectivity or no connectivity or customers want to operate in a disconnected mode or to simply meet the regulatory compliance, adhering to the policy guidelines and laws in the respective country of origin. Most importantly it is your geographical presence that differentiates you as a CSP who can deliver consistent Azure services in that region. With the rise of Edge computing, it becomes more and more critical that data is processed as close to the edge as possible, and as a result we see more and more cloud services moving back towards the edge. As a result, as a CSP not only is your geographical location important, but you can also provide differentiated or specialized applications while serving the needs of certain industries with a specific requirement.

 

What are the various CSP operating models for Azure Stack?

 

When you make the decision to be an Azure Stack CSP, you will need to explore and understand the two CSP operating models. You must ensure that you understand which model aligns best with your organization. So let's try and understand the two CSP operating models.

 

Direct CSP: DirectCSP.png

In this model CSP operates Azure Stack and has a direct billing relationship with Microsoft. All usage of Azure Stack is directly billed to the CSP. The CSP in turn generates a bill for each customer or tenant who is consuming the services offered by the CSP. The period of billing, the amount you bill, and what you bill for are entirely in your hands as a CSP.

 




Indirect CSP:IndirectCSP.png

          In this model, Indirect CSP is also referred to as Distributor, is responsible to operate Azure Stack. Here a network of Resellers can help sell CSP offered services to the end customers. Indirect CSP has direct billing relationship with Microsoft and hence all usage of Azure Stack resources are billed to the Indirect CSP. The indirect CSP in turn bills either the reseller or the end customer





Now that you've familiarized yourself with Azure Stack CSP operating models, it is important to understand the two types of CSP subscriptions that are available.

 

  • Azure Partner Shared Services (APSS) Subscription

According to Microsoft's definition, Azure Partner Shared Services (APSS) are the preferred choice for registration when a direct CSP or an indirect CSP, also known as CSP distributor operates Azure Stack. This means a CSP directly purchases Azure subscription from Microsoft for their own use. This creates opportunity for CSPs to build differentiated solutions and offer them to their tenants.

 

  • CSP Subscription

This is the most common subscription model. In this either a CSP reseller or the customer operates the Azure Stack admin and tenant spaces, or in many cases splits the responsibility, with CSP managing the Admin space and customer managing the Tenant.

 

Roles and Responsibilities in a CSP Model:

With so many myriads of options available in a CSP model involving various personas such as Direct CSPs, Indirect CSPs, Resellers and End Customers along with two types of CSP subscriptions, let's try and understand from the chart below on the various roles and responsibilities associated with each persona and the right CSP subscription applicable for each scenario.

 

Persona

Subscription Type

Azure Stack Operator

Usage and Billing

Selling

Support

Direct CSP

APSS

Direct CSP

Direct CSP

Direct CSP

Direct CSP

Indirect CSP

or

Distributor

APSS

Distributor

Distributor

Reseller

Distributor

or

Reseller

Reseller

CSP

Reseller

Indirect CSP

or

Distributor

Reseller

Distributor

or

Reseller

End Customer

CSP

End Customer

Indirect CSP

or

Distributor

Reseller

or

Distributor

Distributor

or

Reseller

Note: When End Customer operates Azure Stack, multi-tenancy is not required. The end customer needs a CSP subscription from the CSP partner, then uses it for the initial (default) registration. Usage is billed to the Distributor or Indirect CSP.


How do you get started?

 

Once you have made the decision on the type of CSP model you will be operating Azure Stack, we will now dive into the nitty-gritties of how to make Azure Stack operational in this model. To be able to successfully operate and run Azure Stack, you will need to take some steps to plan on how you want to offer services and configure Azure Stack. Let's look at what are some of the key steps in this planning phase.

 

  • Billing: During this phase, you will need to come up with a plan on how you want to bill your end customers based on the usage of services you offer. This is where you will need to plan on how to register Azure Stack and plan the integration of your billing system. You will also need to plan on coming up with appropriate pricing model for the services you offer. During this phase you may also want to explore some of the third party billing services offered by ISVs.

 

  • Services:  In this phase you will come up with a plan on what are the various native Azure Stack services you would want to offer your end customers. You may also plan on offering differentiated value added services to your end customers. This will determine how you configure quotas, plans and offers on the Azure Stack system. For more information on how to create quotas, plans and offers please refer to this video.

 

  • On boarding End Customers: Once you have planned on billing and services for your end customers, you will need to onboard new customers and users to your Azure Stack system. Let's look at how to do this in the following section.

 

Note: This blogpost assumes that you already have access to the Microsoft Partner Center and have some knowledge on CSP Program. If you need access to training materials on CSP Program please refer to the Microsoft Partner Center documentation.

 

Customer On boarding Flow

CSP-Flow.png


  1. First create a CSP or APSS Subscription depending on the CSP operating model that best fits your organization from Microsoft Partner Center
    1. For Azure Partner Shared Services subscription (APSS) - Please go through Microsoft documentation on How to create APSS Subscription
    2. CSP Subscription - Please go through Microsoft documentation on How to create CPS Subscription
  2. Register Azure Stack against the CSP subscription as opted in Step 1. Steps on how to register Azure Stack can be found here
  3. After Azure Stack is registered, you need to enable multi-tenancy if you are planning to offer Azure Stack services to multiple tenants. If you don't enable multi-tenancy, all usage will be reflected against the subscription which was used for Azure Stack registration. You can refer to Microsoft documentation on How to Enable multi-tenancy
  4. Once multi-tenancy is enabled, you will need to first create End Customers or tenants in the Partner Center portal so that when those End Customers consume the services you offer, Azure Stack reports the usage to their CSP subscription.
    1. You can refer to the Microsoft documentation on How to add tenants in Partner Center as shown below

                   Add_Customer.png

    1. Create an Azure subscription for each End Customer you created in the above step in Partner Center. You can refer to Creating New Subscriptions as shown below

                    AddSub.png

    1. Create guest users in the End Customer's directory: The reason you do this is because by default, you as a CSP will not have access to the End Customer's Azure Stack subscription. If the End Customer wants you to manage their resources they can add your account as owner/contributor to their Azure Stack subscription. In order to do that they will need to add your account as a guest user in their Azure AD tenant. It is recommended that you as a CSP use a different account other than your CSP account to manage your Enc Customer's Azure Stack subscription.
    2. Update the registration in Azure Stack with the End Customer's Azure Stack subscription. By doing this End Customer's usage is tracked using the customer's identity in Partner Center thereby ensuring that usage tracking and billing is made easier. You can refer to this link on How to update Azure Stack registration
    3. On board tenants to Azure Stack to enable users from multiple Azure AD tenant directory to use services you offer on Azure Stack. You can refer to the link How to Enable multi-tenancy
    4. As a last step you need to ensure you are able to create a resource in the End Customer's Azure Stack subscription using the guest user account created in Step c

By now you should be all set to successfully operate and offer services on Azure Stack. To track usage and billing, CSPs can use APIs or use the Partner Center. CSPs can also work with third party billing solution providers like Cloud Assert or Exivity for a more customized billing solutions for those who need more flexibility in the pricing and billing model.

 

Sources:

Manage usage and billing for Azure Stack as a Cloud Solution Provider

All you need to know about CSP by Alfredo Pizzirani and Tiberiu Radu

How to Register and Manage Tenants on Azure Stack for CSPs

co-authored by jayanth_yk and janakarangama


In a previous blogpost on "Update on Updates", we’ve walked you through the journey from manually executing the Patch & Update (P&U) process for Dell EMC Cloud for Microsoft Azure Stack to Dell EMC's commitment in delivering the promise to automate the P&U process in 1805 release. 

 

We are now pleased to announce that with 1811 release, P&U Automation Tool is even better with improvements and feature additions. We now automate P&U for firmware of Switches (Dell EMC TOR and BMC switches), OS updates for VMs (OME - OpenManage Essentials and OMNM - OpenManage Network Administrator) on Hardware Lifecycle Host (HLH), OS and Driver update for HLH itself, in addition to automation of firmware update on Scale Unit (SU) nodes and HLH node.

 

Woah! A P&U Automation Tool which saves umpteen hours of keyboard time, avoids human errors and now extends itself beyond firmware update to incorporate driver and OS update to its already rich feature set for a hassle-free lifecycle management on your Dell EMC Cloud for Microsoft Azure Stack, we believe we have ticked all the right boxes by listening to your valuable feedback and suggestions. We also think that the key differentiator we bring to the table is the option to update the firmware of Dell EMC TOR and BMC switches which gives you the automation advantage on your network as well.

 

Great! With that let’s spend some time trying to understand the various bits of lifecycle management on your Dell EMC Cloud for Microsoft Azure Stack and running the P&U Automation Tool. First let’s look at the update options available from both Microsoft and Dell EMC.


Brief overview of all the updates available in Dell EMC Cloud for Microsoft Azure Stack system (Microsoft and Dell EMC updates)


Type of Updates

Dell EMC Updates

Microsoft Updates

Update Method

OS Update for the SU Nodes

 

MS Azure Stack Admin Portal

Azure Stack Software Updates

 

MS Azure Stack Admin Portal

Driver Update for the SU Nodes

 

MS Azure Stack Admin Portal

HLH OS and Driver Update

 

Dell EMC P&U Automation Tool

OME and OMNM OS Update

 

Dell EMC P&U Automation Tool

Firmware Updates for HLH and Compute Nodes

 

Dell EMC P&U Automation Tool

Firmware Updates for TOR and BMC Switches

 

Dell EMC P&U Automation Tool

 

Note that, on the Microsoft Azure Stack software front all the updates are handled via the MS Azure Stack Administrator Portal and the detailed process from Microsoft can be found here.


Now that we have understood the various bits of lifecycle management, let’s run you through the P&U Automation Tool.


Prerequisites before running the P&U tool


Note: Currently 1811 P&U Automation Tool is applicable to 14G hardware only.

  1. Download the latest Dell EMC Customer Toolkit v1.1.1811.1 here
  2. Download the Dell EMC Patch and Update Automation Tool v1.1.1811.1 from here
  3. Upgrade SupportAssist Enterprise to 2.0.0.53. Please refer to the P&U User Guide
  4. Upgrade OME to 2.4.0.930. Please refer to the P&U User Guide
  5. Upgrade OMNM to 6.5.3. Please refer to the P&U User Guide
  6. Also refer to the Switch Firmware pre-requisites from the P&U User Guide

 

Installing and running the P&U Automation Tool


Step 1: Run the P&U Automation Tool msi from the downloaded location on the OME VM and follow the installation wizard to complete the installation.

Note: As the P&U Automation Tool installs the updates, it restarts the HLH for completing the update process. This would in turn restart OME and OMNM VMs. If you want to optionally enable automatic login to the OME and OMNM VMs, you may follow the steps mentioned in the User Guide.

 

Step 2: Launch the Patch and Update Automation Tool by double clicking on the icon on your OME VM’s desktop. Then a welcome window appears, and you must accept the Terms and Conditions to proceed.

1) Welcome page.JPG.jpg


Step 3: Under the Configuration - Profile section, pay attention to the Notification banner and take the necessary action. Enter all the credentials in the text fields and click Next.

 

Note: In the OME VM, you need to copy the DeploymentData File and ConfigurationData File to C:\Program Files (x86)\DellEMC\DeploymentJSON. You can get the DeploymentData File and   ConfigurationData File from the HLH host in D:\DeploymentFiles\JSONS location.

2) Profile tab.JPG.jpg


Step 4: Under Configuration - Workflow section, select the path of Dell EMC Customer Toolkit File and update the ERCS Endpoint IP Address text field and click Next.

3) Workflow tab.JPG.jpg


Step 5: Under Configuration - Settings section click Next to begin the update process while you get to attend other priority tasks.

4) Settings tab.JPG.jpg

 

Step 6: Under the Status section, you can see the progress of Pre-checker. Once the scan is complete, click on Update to begin the process of updating Firmware of Scale Units and HLH, OS and Driver update for the HLH, OS update for OME and OMNM VMs and Firmware update for the TOR and BMC switches. After all the updates are complete, click on the Finish button.

 

Note: The entire update process may take several hours with no user intervention or repetitive tasks involved throughout the process.

5 i) Precheck workflow.JPG.jpg

 

Step 7: That’s it. You are done! The Summary page will be as shown below.
9) Summery.jpg

 

We at Dell EMC Cloud for Microsoft Azure Stack Product Engineering team, are continuously improving the innovation we bring to Dell EMC Cloud for Microsoft Azure Stack and thus you can look forward to ongoing feature Improvements in the Dell EMC Patch and Update Automation Tool in future releases. Therefore, we request you to send in your valuable feedback and comments to help us delight you!


We will be publishing a detailed video on Dell EMC Patch and Update Automation Tool soon. Please watch this space for an update.


Update! The all new 1901 PnU tool is out with 13G hardware support as well. Please download the 1901 PnU tool from here

As promised we are also pleased to bring you the video presentation and demo on PnU tool. Please click here to view the video presentation


Important Note: Starting from the release 1901, Microsoft is using the new ZIP format for the OEM package update. The legacy formats (<package>.exe and <package>.bin) are no longer supported in 1901 and the later releases. When updating an existing cluster using the Patch and Update Guide, you will update using the 1901 OEM Extension (.zip file).

Filter Blog

By date:
By tag: