Azure: transferring Azure resources to Telstra

You can begin transferring any existing Azure resources to Telstra as soon as you've submitted the forms for linking your Azure AD tenant to Cloud Sight.

Learn how to link an existing Azure AD tenant to Telstra

You don't have to wait until your tenancy linking is complete.

Why transfer your resources to Telstra?

• Get a single Telstra bill containing all your fees
• Get support for all your cloud services from Telstra
• Use all the features Cloud Sight has to offer to help manage your resources

Transferring your Azure resources

The process for transferring your resources to Telstra depends on the sort of agreement you have with Microsoft. There are three types:

1. Enterprise Agreement (EA) with Microsoft
2. Pay-as-you-go or Microsoft direct
3. Agreement with another service provider

Transferring resources in an Enterprise Agreement with Microsoft

As an Azure Expert MSP Telstra offers best in class managed services in Azure. We have access to the automated Azure subscription transition tool. Through this tool we can initiate the transfer request and invite you to transition to Telstra CSP.

Microsoft has provided the following points you, as an Enterprise customer, should evaluate before transferring your resources to a Cloud Services Provider (CSP) such as Telstra. (Please note all references to 'the CSP' or 'CSP partner' refer, in this instance, to Telstra.) 

• Transition applicability. The automated subscription tool is applicable only on Direct EA subscriptions. Indirect EA subscriptions are excluded from this transition tool. 
• Enterprise enrollment commitments do not transfer to CSP. As part of an EA a customer may have committed to fixed Azure consumption. These commits are paid through monetary commitments (MC) or committed to consume through Microsoft Azure Consumption Commitment (MACC). Azure consumption for workloads migrated to CSP will not be deducted from the remaining Azure monetary commitment. To avoid forfeiture of these funds customers should wait until the commitment period expires or continue to run other workloads on the Enterprise enrollment. Azure consumption of workloads migrated to CSP will not count against Microsoft Azure Consumption Commitment (MACC) associated with the Enterprise enrollment. If other workloads have not been identified to retire this commitment, an invoice at the end of the term of the Enterprise Enrollment may result.
• Azure reservations do not transfer to CSP. Although reservation entitlements purchased under the Enterprise enrollment will not move to CSP, the underlying resources receiving these benefits will move to CSP along with the subscriptions. Customers may decide which subscriptions will be transferred to ensure reservation entitlements are not left under-utilized post-transfer.
• Discounts and investments applied to the Enterprise enrollment will not transfer to CSP. The price of Azure services is determined between customer and partner. This includes:
  • End Customer Investment Funds (ECIF)
  • Azure Credit Offer Balances
  • Price discounts
    Refer to the published Azure services prices here.
• Customized EA contract terms will not transfer to CSP. Standard Microsoft Customer Agreement (MCA) terms apply. Customer must accept the MCA before transferring the subscriptions to CSP.
• The CSP partner will provide support. Support will be provided by the CSP partner on those workloads migrated to CSP and managed by that partner. Support entitlements purchased by customer through their EA may not be used to raise support tickets for the Azure workloads transferred to CSP.
• Additional review of transfer requests may be needed. Some transfer requests from customers to CSP partners may need to undergo additional review and approval due to the nature of their existing enterprise enrollment structure. Partners will be notified on those exception requirements and will need to engage with their Partner Development Managers (PDMs) and Account Executives, respectively, to help complete this review process.
• Access permissions will be kept intact when moving to CSP. Please refer the access permission details here to understand how to add/remove external guest access and perform required changes before transferring a subscription to CSP. The customer is advised to discuss with
  partner the RBAC roles needed to perform managed services and provision accordingly before the transfer. Alternatively, customers can provision access to the partner through Azure Lighthouse. More details can be found here. 
• Enterprise dev/test subscriptions are not available in CSP. Those subscriptions will be transferred with standard CSP prices if the customer choses to transfer.
• Availability of Azure Marketplace items in CSP are not available in CSP. Marketplace subscriptions will be blocked by the transfer tool. Customer and partner are required to ensure they evaluate all Marketplace items installed and subsequent availability in CSP before selecting a subscription for transfer.

After you've considered all of the above, contact us to begin the resource transfer process. 

Transferring resources in a Pay-as-you-go or Microsoft direct agreement 

If you've purchased your Azure services through Microsoft you're in a 'Microsoft direct' agreement. If you're using a credit card to pay for your Azure services you're likely to be a Pay-as-you-go customer. 

If you've got either of the above agreements, contact us to begin the resource transfer process.

Transferring resources currently in an agreement with another service provider

 If you've purchased your Azure resources through a service provider that's not Telstra or Microsoft, we can help you move these subscriptions to Telstra. Contact us to begin the resource transfer process.