Marketplace

Architecture Summary

Dr Migrate supports two distinct Azure Marketplace deployment models, depending on how discovery data is collected:

  1. Azure Migrate–based Marketplace Deployment
  2. DMC (Dr Migrate Collector)–based Marketplace Deployment

These models are mutually exclusive. A deployment will use one or the other, not both.

Deployment Models Overview

Azure Migrate Marketplace Deployment (Customer-Tenant Hosted)

In this model, Azure Migrate is responsible for all discovery and performance data collection.
Dr Migrate is deployed into the customer’s Azure subscription via the Azure Marketplace and synchronizes with the Azure Migrate Project using a limited-scope Service Principal (SPN).

Characteristics:

  • Discovery data remains inside the customer’s Azure tenant
  • Azure Migrate appliances perform all on-premises scanning
  • Dr Migrate has no direct access to on-prem infrastructure
  • Data is accessed via Azure Migrate REST APIs

DMC Marketplace Deployment (Customer-Tenant Hosted)

In this model, Dr Migrate is deployed into the customer’s Azure subscription via the Azure Marketplace, as in the Azure Migrate model. The Dr Migrate Collector (DMC) is deployed on-premises and connects directly to:

  • VMware vCenter
  • Hypervisors
  • Guest operating systems (Windows / Linux)
  • SQL Servers
  • Network telemetry (where enabled)

Collected data is written to a local encrypted package. The customer moves the package onto the Dr Migrate VM in their Azure tenant and uploads it in the Dr Migrate app.

Characteristics:

  • Discovery data remains inside the customer’s Azure tenant
  • No Azure Migrate appliances
  • No Azure Migrate Project required
  • No data leaves the customer network until the customer moves the package
  • No inbound firewall rules
  • Supports deeper application, SQL, and network insights
  • Ideal for locked-down or Azure-light environments

Key Architecture Differences

Area Azure Migrate Model DMC Model
On-prem collector Azure Migrate Appliance DMC Collector
vCenter integration Yes Yes
Guest-level insights Limited Deep
Network telemetry Limited Full
Primary data location Customer Azure tenant Customer Azure tenant
Azure Migrate required Yes No
Marketplace deployment Yes Yes
Inbound firewall rules None None

Architecture Diagrams

DMC Marketplace Deployment

Marketplace deployment using DMC for data collection
Marketplace (customer-hosted). DMC collects data on-premises and the encrypted payload is uploaded directly to Dr Migrate in your Azure tenant.

Azure Migrate Marketplace Deployment

Marketplace deployment using Azure Migrate for data collection
Marketplace (customer-hosted). Azure Migrate appliances collect data and Dr Migrate reads it via REST API within your Azure tenant.

Identity & Authentication

Azure Migrate Model

  • User access via Azure AD
  • Dr Migrate uses a customer-owned Service Principal
  • Permissions scoped to:
    • Azure Migrate Project (read-only)
    • Dr Migrate managed resources

DMC Model

  • User access via Azure Bastion to the Dr Migrate VM, using the credentials set during deployment
  • The Dr Migrate app on the VM uses the same credentials as the Bastion connection
  • The DMC package is encrypted, and its decryption key is entered when the package is uploaded
  • No persistent credentials stored on-premises

Dr Migrate Managed Resource Group

For Azure Migrate–based Marketplace deployments, a Managed Resource Group is created automatically in the customer subscription.

Dr Migrate Marketplace plans are private offers and must be explicitly enabled for a subscription during licensing.

Resource Purpose
Managed Resource Group RBAC and isolation boundary
Dr Migrate VM Executes analysis and reporting workloads
Azure Key Vault Stores SPN secrets and internal keys
Azure Storage Account Intermediate assessment data (private access only)
Service Principal Reads Azure Migrate Project data
Azure Bastion Secure VM access without public IPs
Virtual Network Network isolation
Network Security Groups VM and Bastion traffic control

DMC-only Marketplace deployments do not require this full resource set unless explicitly requested.

VM Sizing Guidance

Estate Size Azure VM SKU vCPU Memory
Under 4,000 servers Standard_B8ms 8 32 GB
Over 4,000 servers Standard_B16ms 16 64 GB

Large estates with heavy SQL or network telemetry may require larger VM sizes regardless of server count.

Data Flow

Azure Migrate Model

Azure Migrate Appliance → Azure Migrate Project → Dr Migrate (Marketplace VM)

  • HTTPS only (443)
  • Encrypted in transit and at rest
  • No direct on-prem access by Dr Migrate

DMC Model

DMC Collector → Encrypted Package → Dr Migrate (Marketplace VM)

  • DMC writes results to a local encrypted package (dmc_output.zip). No data leaves the customer network until the customer chooses to move it.
  • The customer moves the package onto the Dr Migrate VM by any method that suits their security policy, for example a temporary storage account accessed through Bastion. The staging location is only needed during the transfer.
  • The package is uploaded in the Dr Migrate app on the VM from Discover > Data Sources > DMC by clicking Upload Scan Results and entering the decryption key. It stays encrypted until it reaches the VM. See Uploading & Viewing Results.
  • No inbound firewall rules
  • Upload timing fully controlled by the customer

Frequently Asked Questions

Does Dr Migrate require access to on-premises servers?

  • Azure Migrate model: No
  • DMC model: Yes (read-only)

Does DMC use Azure Migrate?
No. DMC is a standalone collection framework.

Where is assessment data stored?

  • Azure Migrate model: Customer Azure tenant
  • DMC model: Customer Azure tenant

Network Connectivity Requirements

  • Outbound HTTPS (443) only
  • No inbound firewall rules
  • No VPN required
  • No persistent credentials stored on-premises

Existing Azure allow-list guidance remains valid.

Choosing the Right Deployment Model

Both models keep Dr Migrate and all assessment data inside the customer’s Azure tenant. Choose based on how discovery data is collected.

Use Azure Migrate if:

  • Infrastructure-level insights are sufficient
  • Azure Migrate is already in use

Use DMC if:

  • Deep application or SQL insight is required
  • Network dependency analysis is needed
  • Azure footprint is minimal or non-existent
  • Faster assessment turnaround is required
© 2025 Altra Technologies