Managing Microsoft Transfers

Introduction

The transfer process enables a customer to move their subscriptions from a Source Partner to a Target Partner. This transition requires mutual agreement between the customer and both partners.

Core Workflow

1. Relationship: The customer accepts a relationship request from the Target Partner.

2. Request: The Target Partner initiates a transfer request.

3. Review: The Source Partner reviews the request and selects specific subscriptions for transfer.

4. Completion: Once approved, billing ownership shifts to the Target Partner.

Additional Resources: For additional details on Microsoft’s specific requirements, see their guides on New Commerce license-based transfers and Azure subscription transfers.

Transfer Paths and Business Rules

• Direct Bill > Direct Bill

• Direct Bill > Indirect Provider

• Indirect Provider > Indirect Provider

• Indirect Provider > Direct Bill

Key Rules

• Initiation: The Target Partner always starts the process.

• Consent: Both partners must explicitly approve the transfer. No partner is obligated to send or approve a request.

• Permissions: Authorized CloudBlue Agents can approve transfers.

• Indirect Resellers: Must coordinate with their Indirect Provider (the billing owner) to execute transfers.

• Transitioning Partners: Direct Bill partners moving to an Indirect model can transfer customers to their new Indirect Provider.

Note: For additional information, see Microsoft's documentation.

CloudBlue Supported Scenarios

Scenario	Actions in CloudBlue
Inbound Transfers	The Inbound Transfer process must be performed in the Microsoft Partner Center, but you can use Seamless Move to import subscriptions once the transfer is Completed in Partner Center.
Outbound Transfers	Use Seamless Move to approve Pending transfer requests or create cancellation orders for Completed transfers.