Skip to content
1 Company
2 M365
3 Azure
4 AD
5 Network
6 Region
7 Details
  • Company Details

    This worksheet is designed to assist in gathering the information upfront that helps ensure a successful NetApp Virtual Desktop Managed Service (VDMS) deployment.
  • Company Details Instructions

    Please provide the customer company name and (if applicable) the partner company name.


    Customer Company Name

    The customer company is the consumer of the virtual desktop service. The employees of this company are the end users who work in the virtual desktop service. The environment will be created in the customer company’s Microsoft 365 (aka Azure AD) tenant.


    Partner Company Name

    NetApp VDMS may be purchased through authorized NetApp partners. These service providers resell the service, provide implementation services and ongoing technical support. If this implementation is being sold and supported by a NetApp partner, enter the partner company name.

  • Technical Contact

  • Technical Contact Instructions

    Please provide the name and contact information of the contact person NetApp can work with on the technical aspects of this onboarding project. If this is a partner project, the technical contact should be from the partner company.


    Time zone

    We'll use this to assign NetApp resources to match the technical contact's availability. This data is also used to define the time zone settings for servers and logs in the environment. End user desktops will operate in their local time, regardless of this setting.

  • Purchased SKUs

  • Purchased SKUs Instructions

    Please provide a summary of the purchased SKUs to assist with the early design planning steps.


    Shared Users

    A shared user's session runs on Windows 10 EVD session hosts (virtual machines) that are simultaneously hosting other shared users' sessions. Up to 10 total user sessions can run on a single session host. Each time a shared user connects they are assigned to a session host with the fewest concurrent sessions running to optimize resource allocation across active users.

    Shared user session hosts are based on Azure virtual machine family with at least 8 CPU cores and 64GiB RAM allocated for every 10 users, typically an E-Series VM.


    VDI Users

    A VDI user's session runs on a Windows 10 EVD session host (virtual machine) that is dedicated to that user's session. Only one user session at a time will run on a VDI session host. Each time a VDI user connects they are assigned to an empty VDI session host.

    VDI user session hosts are based on the Azure virtual machine family with at least 2 CPU cores and 8GiB RAM allocated for every user, typically a D-Series VM.


    GPU Users

    A GPU user's session runs on a Windows 10 EVD session host (virtual machine) that is dedicated to that user's session. Only one user session at a time will run on a GPU session host. Each time a GPU user connects they are assigned to an empty GPU session host.

    GPU user session hosts are based on the NV-Series virtual machine family with at least 8GiB of GPU memory allocated for every user. Currently supported options are the Nvidia-based NV12s v3 and the AMD-based NV16as v4 VMs. Availability varies by Azure region.


    Business Servers

    A business server supports workloads other than hosting user sessions. This virtual machine runs Windows Server and is allocated 8 CPU cores and 64GiB RAM along with a 128GiB OS disk. As much as possible, application data (including databases) should be stored on the data storage layer (e.g. Azure NetApp Files) and not the business server OS disk.


    Additional TiB(s) Storage

    Additional storage can be purchased in 1 TiB increments, increasing the total size of the data storage layer. This additional storage capacity will be allocated to the storage type and tier as determined by the user count, adding storage will not change the type or tier of storage service used.

  • Minimum users count (10) not met.
Save & Continue Later
  • Microsoft 365 Licensing

  • VDMS is built with Microsoft Azure Virtual Desktop (AVD) technology. The VDMS service includes Azure infrastructure and technical services to deploy and support the environment. AVD prerequisites require that the end users be assigned specific Microsoft 365 (M365) licensing. This licensing is not included in the VDMS subscription and NetApp does not sell or otherwise offer this license.

    Responsibility for M365/AVD licensing compliance stays with the customer company, partner company and/or their M365 vendor.

    There are a variety of M365 plans that support the AVD licensing for VDMS, details can be found here.

    Below, please confirm you understand this requirement and that NetApp is not providing M365 licensing as part of this service.

    If this licensing is not yet in place, you can continue with this deployment wizard. You’ll simply need to implement appropriate M365 licensing before enabling end users to connect to their desktops. Below you can choose to receive a reminder email about this requirement.

  • A reminder email will be sent.
Save & Continue Later
  • Azure Reseller Relationship

  • Your Action is Required
    Review Invite Link

    Please review the invite and accept it to establish the Azure reseller relationship between the customer company and NetApp. This will also grant NetApp delegated admin permissions to the Azure AD tenant.

  • Azure Reseller Relationship Instructions

    A prerequisite of VDMS is that NetApp create a subscription within the customer company’s Azure AD tenant and that NetApp be granted delegated admin rights to deploy & manage VDMS. Establishing this relationship does not impact any existing reseller relationships or subscriptions. NetApp cannot see any other resellers/subscriptions you may already use. More information on multi-partner setups can be found here.


    New Azure Subscription

    The reseller relationship will be used to create a new subscription within the Azure AD tenant. This subscription will contain Azure resources for VDMS. NetApp will retain financial responsibility for the costs incurred in this subscription.


    Delegated Admin

    The delegated admin permissions will be used to deploy Azure Enterprise App(s) for VDMS, which in turn are used to automate the deployment and management of VDMS services and infrastructure.


    Azure Domain Name

    Please enter the domain name of this Azure AD tenant. Instructions to locate this can be found here found here.

Save & Continue Later
  • Active Directory Domain Controller

  • Sample Architecture Diagram

  • Active Directory Domain Controller Instructions


    Azure AD Connect

    AVD authentication requires that a domain controller and Azure AD be setup and synced with Azure AD Connect. If this is already setup it is strongly recommended that VDMS be integrated with the AD DC already synced to Azure AD. A new AD DC can only be deployed if it can be synced to Azure AD and only one Azure AD Connect sync is supported.


    Find AD Connect Status:

    1. Sign in to the Microsoft 365 admin center and choose DirSync Status on the home page.
    2. Alternately, you can go to Users > Active users, in the Azure Portal and on the Active users page, choose More > Directory synchronization. On the Directory Synchronization pane, choose Go to DirSync management.


    Integrate with Existing AD DC

    VDMS can be configured to integrate with your existing Active Directory Domain Controller (AD DC) or to deploy a new AD DC inside the VDMS subscription.

  • Action Item: Remove AD Connect
    Decommissioning the existing Azure AD Connect syncing process is required before we'll be able to complete the onboarding project. Please continue with this wizard and take a note to remove AD Connect syncing as soon as possible.

  • Action Item: Install AD Connect
    Installing Azure AD Connect on your existing AD DC is required before we'll be able to complete the onboarding project. Please continue with this wizard and take a note to setup AD Connect syncing as soon as possible.

  • A reminder email will be sent.
  • Existing AD DC Details

  • Sample Architecture Diagram

  • Sample Architecture Diagram

  • Section Break

  • Existing AD DC Details Instructions


    Domain Controller VM Running in Azure

    If the existing AD DC is on a VM running in Azure, we'll setup vNet peering between VDMS and the vNet of the AD DC so that VDMS machines can join the domain.


    Domain Controller VM Running Outside of Azure

    If the AD DC is running outside of Azure, we'll either establish vNet peering to an Azure network that has network connectivity to AD DC or we'll setup a dedicated Site-to-Site VPN.


    Azure AD Domain Services

    If the existing AD DC is the "domain controller as a service" Azure AD Domain Services, we'll setup vNet peering between VDMS and the vNet of AADDS so that VDMS machines can join the domain.

  • Section Break

  • Sample Architecture Diagram

  • Sample Architecture Diagram

  • Section Break

  • AD DC Network Connectivity Instructions


    Network Connectivity to AD DC

    In order to integrate with an AD DC that is outside of Azure we'll need to establish network connectivity between the network of the AD DC.

    If the AD DC is already connected to a vNet in Azure (e.g. VPN or Express Route), the best way to add network connectivity to VDMS is to establish vNet Peering between the VDMS network and the Azure network that is connected to the AD DC.

    If the AD DC is not already connected to a vNet in Azure, the best way to add network connectivity to VDMS is to establish a SIte-to-Site VPN between the VDMS network and the gateway device on the AD DC network.

  • Section Break

  • Section Break

  • Detailed Network Connectivity Instructions


    Azure Region for AD DC Network Connectivity

    Select the Azure region of the Azure vNet that has connectivity to the existing AD DC.


    Azure vNet Resource ID

    Finding the vNet Resource ID in the Azure Portal:

    1. Target: The Resource ID of the vNet that has network connectivity to the AD DC.
    2. Login to the Azure Portal with an admin account that has access to the subscription containing the target vNet
    3. Navigate to and select the target vNet
    4. Select Properties from the vertical list
    5. Copy the RESOURCE ID

  • Detailed Network Connectivity Instructions


    Gateway Device

    In order to correctly configure the Azure Site-to-site virtual gateway service, we'll need to know the brand, model and version. Please provide any other details that may be relevant


    Gateway Device Public IP

    When setting up the Site-to-Site VPN, we'll need to know the public IP address of the gateway device.


    Validated Gateway Device

    See the Azure validated device list to verify if the gateway device is listed as validated by Azure. Devices that are not validated may still work and additional investigation may be required to successfully configure the Site-to-Site VPN.

Save & Continue Later
  • Virtual Network Scope

  • Network Scope Instructions


    Virtual Network Scope

    A /20 network scope for the VDMS virtual network and subnets is required.

    It is important that you check with your current network design and select a scope that does not overlap with any other networks in your environment. If two overlapping networks are joined via VPN and/or vNet peering VDMS services will likely be impacted and significant labor required to resolve the problem.

    As an illustration, the "10.75.96.0 /20" scope will use the IP range of 10.75.96.1 - 10.75.111.254

Save & Continue Later
  • Azure Region

    Selecting the region for your VDMS deployment should consider proximity to end users, previously deployed Azure resources and available services.

  • Service availability by region:


    RegionShared Session HostVDI Session HostGPU Session HostStorage Layer
    Central USAvailableAvailableNot AvailableAvailable
    East USAvailableAvailableAvailableAvailable
    East US 2AvailableAvailableAvailableAvailable
    North Central USAvailableAvailableLimitedLimited
    South Central USAvailableAvailableAvailableAvailable
    West Central USLimitedLimitedNot AvailableLimited
    West USAvailableAvailableLimitedAvailable
    West US 2AvailableAvailableAvailableAvailable

  • Service availability for Central US:


    Shared Session HostVDI Session HostGPU Session HostStorage Layer
    Prev. Gen Intel Xeon
    VM Family: Esv3
    Available
    Prev. Gen Intel Xeon
    VM Family: Dsv3
    Available
    Intel Xeon/Nvidia Tesla M60
    VM Family: NVv3
    Not Available
    Up to 49 VDMS Users
    Azure Files: GPv2
    Available
    Current Gen Intel Xeon
    VM Family: Esv4
    Available
    Current Gen Intel Xeon
    VM Family: Dsv4
    Available
    AMD EPYC/AMD Radeon Instinct MI25
    VM Family: NVv4
    Not Available
    50-249 VDMS Users
    Azure NetApp Files: Standard
    Available
    Current Gen AMD EPYC
    VM Family: Easv4
    Available
    Current Gen AMD EPYC
    VM Family: Dasv4
    Available
    250+ VDMS Users
    Azure NetApp Files: Premium
    Available
  • Error: Central US will not support the GPU users you've purchased. Please select a different region to continue.


  • Service availability for East US:


    Shared Session HostVDI Session HostGPU Session HostStorage Layer
    Prev. Gen Intel Xeon
    VM Family: Esv3
    Available
    Prev. Gen Intel Xeon
    VM Family: Dsv3
    Available
    Intel Xeon/Nvidia Tesla M60
    VM Family: NVv3
    Available
    Up to 49 VDMS Users
    Azure Files: GPv2
    Available
    Current Gen Intel Xeon
    VM Family: Esv4
    Available
    Current Gen Intel Xeon
    VM Family: Dsv4
    Available
    AMD EPYC/AMD Radeon Instinct MI25
    VM Family: NVv4
    Available
    50-249 VDMS Users
    Azure NetApp Files: Standard
    Available
    Current Gen AMD EPYC
    VM Family: Easv4
    Available
    Current Gen AMD EPYC
    VM Family: Dasv4
    Available
    250+ VDMS Users
    Azure NetApp Files: Premium
    Available

  • Service availability for East US 2:


    Shared Session HostVDI Session HostGPU Session HostStorage Layer
    Prev. Gen Intel Xeon
    VM Family: Esv3
    Available
    Prev. Gen Intel Xeon
    VM Family: Dsv3
    Available
    Intel Xeon/Nvidia Tesla M60
    VM Family: NVv3
    Available
    Up to 49 VDMS Users
    Azure Files: GPv2
    Available
    Current Gen Intel Xeon
    VM Family: Esv4
    Available
    Current Gen Intel Xeon
    VM Family: Dsv4
    Available
    AMD EPYC/AMD Radeon Instinct MI25
    VM Family: NVv4
    Available
    50-249 VDMS Users
    Azure NetApp Files: Standard
    Available
    Current Gen AMD EPYC
    VM Family: Easv4
    Available
    Current Gen AMD EPYC
    VM Family: Dasv4
    Available
    250+ VDMS Users
    Azure NetApp Files: Premium
    Available

  • Service availability for North Central US:


    Shared Session HostVDI Session HostGPU Session HostStorage Layer
    Prev. Gen Intel Xeon
    VM Family: Esv3
    Available
    Prev. Gen Intel Xeon
    VM Family: Dsv3
    Available
    Intel Xeon/Nvidia Tesla M60
    VM Family: NVv3
    Not Available
    Up to 49 VDMS Users
    Azure Files: GPv2
    Available
    Current Gen Intel Xeon
    VM Family: Esv4
    Available
    Current Gen Intel Xeon
    VM Family: Dsv4
    Available
    AMD EPYC/AMD Radeon Instinct MI25
    VM Family: NVv4
    Available
    50-249 VDMS Users
    Azure NetApp Files: Standard
    Not Available
    Current Gen AMD EPYC
    VM Family: Easv4
    Available
    Current Gen AMD EPYC
    VM Family: Dasv4
    Available
    250+ VDMS Users
    Azure NetApp Files: Premium
    Not Available
  • Warning: North Central US will not support Nvidia GPUs for your purchased GPU users. Only AMD GPUs are available in North Central US.

  • Warning: North Central US will not support more than 50 users.

  • Error: North Central US will not support your deployment because you have more than 50 users. Please select a different region to continue.


  • Service availability for South Central US:


    Shared Session HostVDI Session HostGPU Session HostStorage Layer
    Prev. Gen Intel Xeon
    VM Family: Esv3
    Available
    Prev. Gen Intel Xeon
    VM Family: Dsv3
    Available
    Intel Xeon/Nvidia Tesla M60
    VM Family: NVv3
    Available
    Up to 49 VDMS Users
    Azure Files: GPv2
    Available
    Current Gen Intel Xeon
    VM Family: Esv4
    Available
    Current Gen Intel Xeon
    VM Family: Dsv4
    Available
    AMD EPYC/AMD Radeon Instinct MI25
    VM Family: NVv4
    Available
    50-249 VDMS Users
    Azure NetApp Files: Standard
    Available
    Current Gen AMD EPYC
    VM Family: Easv4
    Available
    Current Gen AMD EPYC
    VM Family: Dasv4
    Available
    250+ VDMS Users
    Azure NetApp Files: Premium
    Available

  • Service availability for West Central US:


    Shared Session HostVDI Session HostGPU Session HostStorage Layer
    Prev. Gen Intel Xeon
    VM Family: Esv3
    Available
    Prev. Gen Intel Xeon
    VM Family: Dsv3
    Available
    Intel Xeon/Nvidia Tesla M60
    VM Family: NVv3
    Not Available
    Up to 49 VDMS Users
    Azure Files: GPv2
    Available
    Current Gen Intel Xeon
    VM Family: Esv4
    Available
    Current Gen Intel Xeon
    VM Family: Dsv4
    Available
    AMD EPYC/AMD Radeon Instinct MI25
    VM Family: NVv4
    Not Available
    50-249 VDMS Users
    Azure NetApp Files: Standard
    Not Available
    Current Gen AMD EPYC
    VM Family: Easv4
    Not Available
    Current Gen AMD EPYC
    VM Family: Dasv4
    Not Available
    250+ VDMS Users
    Azure NetApp Files: Premium
    Not Available
  • Error: West Central US will not support the GPU users you've purchased. Please select a different region to continue.

  • Warning: West Central US will not support more than 50 users.

  • Error: West Central US will not support your deployment because you have more than 50 users. Please select a different region to continue.


  • Service availability for West US:


    Shared Session HostVDI Session HostGPU Session HostStorage Layer
    Prev. Gen Intel Xeon
    VM Family: Esv3
    Available
    Prev. Gen Intel Xeon
    VM Family: Dsv3
    Available
    Intel Xeon/Nvidia Tesla M60
    VM Family: NVv3
    Available
    Up to 49 VDMS Users
    Azure Files: GPv2
    Available
    Current Gen Intel Xeon
    VM Family: Esv4
    Available
    Current Gen Intel Xeon
    VM Family: Dsv4
    Available
    AMD EPYC/AMD Radeon Instinct MI25
    VM Family: NVv4
    Not Available
    50-249 VDMS Users
    Azure NetApp Files: Standard
    Available
    Current Gen AMD EPYC
    VM Family: Easv4
    Available
    Current Gen AMD EPYC
    VM Family: Dasv4
    Available
    250+ VDMS Users
    Azure NetApp Files: Premium
    Available
  • Warning: West US will not support AMD GPUs for your purchased GPU users. Only Nvidia GPUs are available in West US.


  • Service availability for West US 2:


    Shared Session HostVDI Session HostGPU Session HostStorage Layer
    Prev. Gen Intel Xeon
    VM Family: Esv3
    Available
    Prev. Gen Intel Xeon
    VM Family: Dsv3
    Available
    Intel Xeon/Nvidia Tesla M60
    VM Family: NVv3
    Available
    Up to 49 VDMS Users
    Azure Files: GPv2
    Available
    Current Gen Intel Xeon
    VM Family: Esv4
    Available
    Current Gen Intel Xeon
    VM Family: Dsv4
    Available
    AMD EPYC/AMD Radeon Instinct MI25
    VM Family: NVv4
    Available
    50-249 VDMS Users
    Azure NetApp Files: Standard
    Available
    Current Gen AMD EPYC
    VM Family: Easv4
    Available
    Current Gen AMD EPYC
    VM Family: Dasv4
    Available
    250+ VDMS Users
    Azure NetApp Files: Premium
    Available
  • Azure Region Instructions


    Factors in Picking an Azure Region

    Round Trip Time (RTT)

    The RTT between the end user and their virtual desktop is the primary variable that impacts the user's experience. The AVD Experience Estimator tests this metric. The most accurate way to test this critical element of your deployment is to perform it from the customer location on both the wired and wireless (if applicable) networks.


    Currently deployed Azure resources

    VDMS can be integrated with other Azure services and resources. Hosting VDMS in the same region as those resources enhances performance and user experience.


    Availability of Azure services

    VDMS relies on various VM family types and storage services as outlined below. Be sure to select a region that offers the necessary VMs and storage options for your use case.



    Azure Resource Details

    E-Series

    VDMS shared users typically run on E-Series VMs. Depending on the use case we'll select between the Esv3, Eav4 and Easv4 families.


    D-Series

    VDMS VDI users typically run on D-Series VMs. Depending on the use case we'll select between the Dsv3, Dav4 and Dasv4 families.


    AMD GPUs

    VDMS GPU users can choose the Nv16as v4, a 16 core, 56GiB VM with 8GiB GPU memory.


    Nvidia GPUs

    VDMS GPU users can choose the Nv12s v3 a 12 core, 112GiB VM with 8GiB GPU memory.


    Azure NetApp Files

    VDMS deployments with 50+ users use Azure NetApp Files (ANF) as the data storage layer. VDMS for 50+ users is only supported in regions that also support ANF.

Save & Continue Later
  • Project Details

  • Date Format: MM slash DD slash YYYY
  • Warning: Deploying this quickly may not be feasible. Our team will review it with you.
Save & Continue Later

Proudly powered by WordPress.