Pay As You Go (PAYG)

to CSP

SmartGuide

(SES)

Introduction Often times partners need to migrate between subscription models. Maybe you deployed the customer's POC on a free trial subscription. Maybe you are taking over some shadow IT for a customer, or just got started under a different model. This guide will show you how to migrate from an Pay - As - You – Go (PAYG) subscription to a CSP subscription. There are a few steps and if we do the appropriate planning up front, this will be a smooth process.

This process will outline 5 major steps for you to make this switch: 1. Provisioning | Requesting an Azure Subscription in StreamOne Enterprise Solutions Platform

(SES) 2. Migrating your PAYG to an Azure AD Based Directory 3. Performing an Assessment 4. Migration from ASM to ARM 5. Migrating your resources from PAYG to CSP

Provisioning | Requesting an Azure CSP Subscription

Tech Data is your go-to-source for all of your Microsoft Cloud needs.

Before purchasing or “requesting" a new CSP Azure subscription (or account) in StreamOne Enterprise Solutions Platform, your client organization must be associated to a Microsoft Identity. The Microsoft identity can be their domain (abc.com) or some sub-set of their domain (abctest.onmicrosoft.com). When a new Azure CSP Subscription (or account) is approved, admin rights are provisioned to the individual whose email address entered in the platform. To summarize the steps to creating a new CSP subscriptions are:

1) Associate a Microsoft Tenant ID to the customer organization in SES

2) Request a new Azure Subscription in SES

3) Request approved, subscription is provisioned and admin rights delivered to end customer contact

Keep in mind: Only one (1) Microsoft ID can be associated to a Customer Organization in SES. If a customer has

more than one Microsoft ID, you will need to create another customer account in SES for each Microsoft ID.

Once a Microsoft ID is associated to a Customer organization, you can request multiple Subscription

Adding a New Customer to StreamOne Enterprise Solutions To establish a Microsoft Identity for a customer (or client), follow these steps:

1. If your customer doesn't exist in the SES platform, create a customer. Customer accounts can be created two ways.

a) Resellers can create the customer account using the reseller portal access

b) Customers can request an account through the reseller end-customer portal, also known as the widget, using the Signup feature. (Recommended)

Note: For more information regarding configuring the customer widget, click on this link

Follow these steps to add a customer. 1. From the StreamOne Enterprise Solutions Home screen, select the “Customer” module

2. On the next screen, click “Add”

3. In the Client Section, you may enter the company information. Once entered, click on the “Save” button. a. Organization: Enter the company name. b. Name: Enter the contact name. c. Title: Enter the title for the contact. d. Email: Enter the email address for the contact name.

This is the individual who will receive platform/system notifications. e. Phone: Enter the phone number for the contact. f. Address: Enter the company address.

Here’s the detailed how-to Knowledge Base article: “How to Create Platform Customer Accounts”

Linking a Microsoft Tenant ID to Customer in SES Before you can create a new CSP Azure subscription, you must complete this step. There are three options to associate a Tenant (or domain ID) to an SES Customer. They include: Create New Customer Identity Add Linked Customer Identity (Tenant ID already exists in our Partner Center) Request Link Customer Identity (Send an invitation from the SES to existing Tenant) See below for steps on each one.

a. Create New Tenant Identity

1. Go to Customer Module – Cloud Providers. Toggle on Microsoft Azure, then select and click “Edit”

2. Select the “CSP Customer Pricebook”

3. Under Microsoft Azure Identity, select “Create new customer identity” from the drop-down list

4. Complete all the required fields (noted by an “*’). Then, click “Save”

SES Cloud Support will authorize the request and the reseller is notified.

The account is now ready for a new Azure Subscription.

b. Add Linked Customer Identity

1. Send an e-mail to your customer using the content provided below

2. Go to Customer Module – Cloud Providers. Toggle on Microsoft Azure, then select and click “Edit”

3. Select the “CSP Customer Pricebook”

4. Under Microsoft Azure Identity, select “Add Linked Customer Identity” from the drop-down list

5. Enter the customer’s Microsoft ID number, and then click “Save”.

The Customer SES account is now ready to request a new Azure CSP subscription.

C. Request Link Customer Identity

1. Go to Customer Module – Cloud Providers. Toggle on Microsoft Azure, then select and click “Edit” 2. Select the “CSP Customer Pricebook” 3. Under Microsoft Azure Identity, select “Request Link Customer Identity” from the drop-down list

4. Enter the customer’s domain

5. Enter the email address of the person with admin or owner right under the domain

6. Click “Save”

When this step is complete, the Customer will appear in the Tech Data partner center and the tenant ID will update in the platform.

The account is now ready for a new Azure Subscription.

Dear Customer, Click the following link to accept this invitation and authorize Tech Data Corporation to be your Microsoft Cloud Solution Provider.

https://portal.office.com/partner/partnersignup.aspx?type=ResellerRelationship&id=d3e363db-81d0-4c04-9bb4-bced62c60825&csp=1&msppid=0

When this is complete, please notify me and provide me your Microsoft ID number so that we can complete your setup in our platform.

Request an Azure Subscription

1. Go to Customers Module

2. Go to Cloud Accounts and click the “Request” button a) In the dropdown select Microsoft Azure b) Enter a Friendly Name c) Click REQUEST

The request will be sent to the SES Cloud Support team for approval. When approved the subscription is provisioned and delegated admin rights are provided to the customer.

Migrating to an Azure AD Based Directory

By default, EA subscriptions are using a Microsoft account for sign up (Think Live ID.) We need to move this to an Azure AD Based format to successfully perform a migration. The easiest way to do this is tying it to your customer's Microsoft tenant. We had you purchase a new Azure subscription in step one, so at this point you should have your new Azure Subscription’s Admin credentials. In doing this we will hand over the billing control to this new alias as well.

1. Sign in at Azure Account Center as the Account Admin. To find out who is the Account Admin of the subscription follow the steps below- The Account Administrator is the person who signed up for or bought the Azure subscription. They're authorized to access the Account Center and perform various management tasks like create subscriptions, cancel subscriptions, change the billing for a subscription, or change the Service Administrator. If you're not sure who the account administrator is for a subscription, use the following steps to find out.

a. Visit the Subscriptions page in the Azure portal.

b. Select the subscription you want to check, then look under settings.

c. Select Properties. The account administrator of the subscription is displayed in the Account Admin box.

2. Select the subscription to transfer.

3. Verify that your subscription is eligible for self-serve transfer by checking the Offer and Offer ID with the list below:

4. Click Transfer subscription.

5. Specify the recipient.

6. The recipient automatically gets an email with an acceptance link. Recipient clicks the link, and follows the instructions, including entering the payment information.

7. The recipient clicks the link and follows the instructions, including entering their payment information.

8. Success! The subscription is now transferred.

Performing an Assessment

This step will direct you to a Microsoft designed tool. This tool compares your existing services against the available services in CSP and will identify any issues you may encounter as well as explain remediation steps for potential issues. The goal here is to identify potential issues BEFORE starting your migration.

Migration assessment

1. Go to the Azure CSP Migration Assessment Tool.

2. Sign in to the assessment tool by using your Azure Active Directory (Azure AD) credentials. Note: If you have trouble signing in to the tool, you might be using the Microsoft Account (LiveID) credentials that you use to sign in to your Azure subscription. To use the assessment tool, you must first switch from your Microsoft Account to an Azure AD based account. For detailed instructions about how to switch to Azure AD account, see Transfer ownership of an Azure subscription to another account.

3. On the Welcome page, for Account Type, select either EA or Other. Other is for direct or open Azure accounts.

4. Based on your selection in step 3, complete the rest of the settings on the Welcome page:

a. For Enterprise Agreement accounts, enter the relevant information in the EA Enrollment

Number box and the Primary/Secondary Access Key box.

b. For open or direct accounts, ensure that the URL for the account that is signed in is correct.

5. Select the Run Assessment button.

It might take a minute for the assessment tool to collect usage details.

6. On the EA Assessment Report page, the results show a list of all subscriptions that are associated with this account. Select the subscription name.

7. The assessment report displays the subscriptions. The CSP Status column shows one of the following for migration status:

NO ISSUES (green) means the subscription is ready to be moved to Azure CSP.

MODIFY (yellow) means that one or more resources in the subscription need to be modified before they can be moved to Azure CSP.

BLOCKED (red) means that one or more resources in the subscription cannot be moved to Azure CSP at this time. These resources must be excluded if you want to migrate the subscription.

8. The Suggested Approach column suggests a migration approach for each resource. The suggested approach is either a one-step migration (Azure Resource Manager to Azure CSP) or a two-step migration (Azure classic deployment model to Resource Manager, and then Resource Manager to Azure CSP).

If the assessment identified issues proceed to step 4. If no issues were identified proceed straight to step 5.

Migration from ASM to ARM

The migration process involves three major steps:

Move VMs. You can do this by using PowerShell or the Azure command-line interface (Azure CLI).

Move dependencies that are in the same resource group. You also do this by using PowerShell. Remove the "secrets" dependency. After the VMs are in Resource Manager, you must remove a

secrets dependency that is part of Windows Remote Management (WinRM).

The migration process creates three resource groups:

One for each cloud service. Name the resource group [cloud service]-migrated. This resource

group contains all the VMs in that cloud service.

One for the virtual network. Name the resource group [virtual network]-migrated. One for storage accounts. Name the resource group [storage account]-migrated.

When you've finished this migration process, you can move resources between resource groups. You can configure names and permissions without any downtime in service.

Move VMs

For detailed information about moving your VMs by using PowerShell, see Migrate resources from classic to Azure Resource Manager by using Azure PowerShell.

For detailed information about moving your VMs by using Azure CLI, see Migrate resources from classic to Azure Resource Manager by using Azure CLI.

Move dependencies

For detailed information about moving dependencies within a resource group by using PowerShell or Azure CLI, see Move resources to a new resource group or subscription.

Remove the secrets dependency

VMs that you originally created by using the classic deployment model have a specific secrets dependency that you must remove before you can move the VMs to an Azure CSP subscription. You can remove these dependencies by using one of the following options:

PowerShell Azure CLI Azure Resource Explorer

PowerShell

PowerShell Copy

$vm = Get-AzureRmVM -ResourceGroupName $rgName -Name $vmName

$vm.OSProfile.Secrets = New-Object -TypeName

"System.Collections.Generic.List[Microsoft.Azure.Management.Compute.Models.VaultSecretGr

oup]"

Update-AzureRmVM -ResourceGroupName $rgName -VM $vm -Debug

Azure CLI

az vm update -g rgname -n vmname --set osProfile.Secrets=[]

Azure Resource Explorer

1. Go to resources.azure.com, and then select subscriptions > resourceGroups. Find the name of the resource group where the objects were migrated.

2. For each VM, select the Microsoft.Computer resource, remove the secrets values (highlighted in the following screenshot), and then select the PUT button. (See example picture in next page)

3. When the secrets dependency has been removed, the page looks similar to this:

4. Repeat this process for all migrated VMs.

After verifying the status of your resources and VM’s you are ready to move from the PAYG subscription to the new Azure CSP Subscription.

Migrating your resources from PAYG to CSP

After you've upgraded all Azure classic deployment model resources to the Azure Resource Manager model, you can migrate the resources from an Enterprise Agreement (EA) or pay-as-you-go (PAYG) subscription to an Azure Cloud Solution Provider (Azure CSP) subscription by using Azure Resource Move.

Note: Resource Move is a detailed process. If you don't want to perform this upgrade, you can leave the resources as is and migrate only those that were created in Resource Manager mode.

Although the following scenario shows the procedure for a single subscription, the procedure also applies to multiple subscriptions. In the procedure, the term source subscription refers to the EA, Open, or PAYG subscription that is to be migrated. The term destination subscription refers to the Azure CSP subscription.

Move resources from the source subscription to the Azure CSP subscription

Choose a resource group in the source subscription that you want to migrate to the Azure CSP subscription. Select Move, and then select Move to another subscription.

Cross-subscription migrations require resources and all their dependencies to be moved at once. If you have VM resources in one resource group, and that VM's disks are stored in a storage account in another resource group, first move all dependent resources to a single resource group, and then migrate them to another subscription at the same time.

Select all resources that you want to migrate from the source subscription to the Azure CSP subscription, and then select a resource group in the destination subscription. After you select OK, the migration possibility is validated. Select OK again to confirm the migration of selected resources from the source subscription to the Azure CSP subscription.

Migration usually takes from several seconds to a few minutes. To ensure that all resources are migrated without errors, check the activity status.

At this point, all resources in the selected resource group have been moved. In this example, the resource group includes the VMs and all storage accounts, public IPs, and NICs that are associated with the running VMs. After the migration is complete, the source resource group is displayed as empty.

For any questions

or additional assistance, please contact our team.

tdcloud@techdata.com

1-800-237-8931 www.techdatacloud.com