Deploy Ecosystem from a Solution Template | Teradata VantageCloud Enterprise on Azure (DIY) - Deploying a Teradata VantageCloud and Ecosystem Software from a Solution Template - Teradata® VantageCloud Enterprise on Azure

VantageCloud Enterprise on Azure (DIY) Installation and Administration Guide - 3.2.0.0
Deployment
VantageCloud
Edition
Enterprise
Product
Teradata® VantageCloud Enterprise on Azure
Release Number
3.2.0.0
Published
March 2026
ft:locale
en-US
ft:lastEdition
2026-04-07
dita:mapPath
cvo1751050001343.ditamap
dita:ditavalPath
kou1751058502043.ditaval
dita:id
eqk1475705518038
Product Category
Cloud
Prerequisite
  • You must log into the Azure portal using an account with sufficient permissions in the Azure subscription and be assigned the Owner role at the subscription level. See Azure Documentation Center.
  • You might need to increase Azure service limits. See Azure Service Limits.
A solution template allows you to deploy multiple Teradata products simultaneously. At deployment, you can create a new resource group or use an existing, empty resource group that contains the VNet, VMs, storage accounts, network security groups, and so on. A solution template creates one NSG for each product launched during the deployment process. Some ports to these NSGs open automatically after completing this procedure. For more information, see Network Security Groups and Ports.
  1. Log in to the Azure Marketplace and search for Teradata.
  2. Under Teradata® VantageCloud Enterprise on Azure (DIY), click Get it now.
  3. From the Software plan menu, select the appropriate solution template, then click Continue.
    Solution Template Purchase Option
    Hourly Annual License (Private Offer)
    VantageCloud Enterprise (DIY) ●  
    VantageCloud Enterprise DIY Private Offer    
    See Teradata Software Purchase Options.
  4. Read through the summary, then click Create.
  5. In the solution template, configure the settings on the Basics blade, then click OK.
    If the interface times out while completing this procedure, return to the previous blade and click OK again so you can continue where you left off.
    Parameter Action
    User name Enter a user name.**
    Authentication type Select an authentication method.
    For security reasons, we strongly recommend an SSH public key.
    SSH public key
    Copy and paste an Open SSH public key which can be generated with tools such as PuTTY or SecureCRT.
    Password
    Enter a password of at least 12 characters, using at least 1 lower case character, 1 upper case character, 1 number, and 1 special character.Enter the password again to confirm.
    Subscription Select a subscription.
    Resource group Select one of the following:
    • Create new and enter a name for the resource group.
    • Use existing and select an empty existing resource group.
    See Resource Groups.
    Location Select a region to deploy the solution.

    See Location and Time Zone Considerations.

    ** To comply with CIS hardening requirements, VantageCloud Enterprise (DIY) uses a predefined OS user account during provisioning. The default OS username is azureuser and is fixed while provisioning and you cannot change this.

    This approach is to align with CIS hardening security baseline by default

    To manage additional users, you can add the additional usernames after provisioning. Add them explicitly to the Allow Users list.
    You donot have to provision the site after adding or removing users.
  6. Configure the settings on the VantageCloud Enterprise blade, then click OK.
    Parameter Action
    Database Deployment Type You can select either Enterprise Cluster (SQL Engine) or Externally Managed OTF (Native Iceberg Reads).
    System name prefix Accept the default or enter a prefix for all nodes in the cluster.

    The default is database. The prefix displays in the Azure portal after the VM deploys.
    DBC password Enter a new default VantageCloud password, using 12 to 15 characters starting with a letter. The following special characters are allowed: ! @ # $ % ^ & * < >.

    For security reasons, you must change the default DBC password to a different password.
    Confirm DBC password Enter the password again to confirm.
    Japanese language support Click Yes to optimize the hashing algorithm to spread data across all AMPs when using Kanji characters for primary indexes. The default setting is No.
    VantageCloud Tier Select Enterprise, Advanced or, Base for Enterprise Cluster (SQL Engine) and Select Enterprise or Advanced for Externally Managed OTF (Native Iceberg Reads), or the free Developer tier.

    See Teradata VantageCloud License Tiers.
    VM Size Select a supported VM size.

    See Supported Database VM Sizes.
    Data disk Storage Type Based on the region selected for deployment, this defaults to either Premium SSDv1 or Premium SSDv2. For regions supporting Premium SSdv2, this is the default.
    Availability Zone For Premium SSDv2, Select Zone for VM deployment. Applies to all components . Regions with SSDv2 support but no zonal support will automatically pick No Zone.
    Storage Size Per Node (in TB) Select a supported storage size per node (in TB).

    See Supported Database Disk Sizes.
    Number of nodes Enter the starting number of nodes (x) you want to deploy.

    To determine supported options for scaling out or scaling in, see Supported Node Counts during Scale Out / In.
    Temporal Select Yes to enable Temporal. The default setting is No.

    When enabled, Temporal data is displayed in UTC time, so you must set the time zone parameter to UTC.
    Teradata Intelligent Memory (TIM)

    [A, E only1]

    		 Click Yes to enable TIM. The default setting is No.
    TIM Cache Percent If you enabled TIM, type a cache percent from 1 to 80 to specify the size of the hot cylinder cache as a percentage of FSG cache.

    See the ctl utility in Database Utilities and the Teradata® Intelligent Memory Orange Book. To find an Orange Book, go to https://support.teradata.com, log in, and search for the book title.
    Row Level Security Click Yes to enable row-level security. The default setting is No.
    Secure Zones Click Yes to enable secure zones. The default setting is No.
    Sub-pools per Node Select number of Sub-pools per clique. The dropdown displays the value as per the selected Instance Type.
    AMPs per sub-pool Depending on the Sub-pools per clique value, AMPS per Sub-pool is automatically calculated and the dropdown displays the possible values. For more details, see Variable AMP Feature in Supported Database VM Sizes.
    You can configure mainframe connectivity, with maximum of 15 nodes, post deployment.

    1 License tiers: B/Base, A/Advanced, E/Enterprise

  7. [Optional] On the Viewpoint blade, click Yes to configure the settings, then click OK.
    You must configure Viewpoint if you plan to use the following software:
    • Teradata Data Mover
    • Teradata Data Stream Controller
    • Teradata QueryGrid*
    • Teradata Server Management
    • Teradata Viewpoint
    *For QueryGrid, you must use Viewpoint (Multiple Systems). You can use an on-premises installation or follow these steps to deploy on Azure.
    Parameter Action
    Viewpoint system name prefix Accept the default or enter a prefix for all nodes in the cluster.

    The default is viewpoint. The prefix displays in the Azure portal after deploying the VM.
    System nickname Enter a nickname to use to configure Viewpoint.
    Viewpoint portal admin user password Enter the Viewpoint administrator password for the Viewpoint portal, using 12 to 15 characters, starting with a letter. It can contain only letters and numbers.

    Use this password to log in to the Viewpoint portal with the admin user name.
    Confirm portal admin user password Enter the password again to confirm.
    Viewpoint Image version Select a Viewpoint image:
    • Vantage:
      • Teradata Viewpoint
      • Teradata Viewpoint (Multiple Systems)
    See Teradata Software Purchase Options.
    VM size Select a supported VM size (storage size is per node).

    See Supported Software VM Sizes.
  8. [Optional] On the Server Management (PSIM) blade, click Yes to configure the settings, then click OK.
    Parameter Action
    Site ID

    [B, A, E only1]

    		String that identifies this Teradata deployment for Teradata Customer Support (AZRTDB followed by up to 9 numbers). If you do not have the site ID, you can continue without it and add it later. See Site IDs.
    Server Management System name prefix Accept the default or enter a name for all deployed Server Management VMs.
    Server Management admin password Enter the Server Management administrative password, using 12 to 15 characters, starting with a letter. It can consist of only letters and numbers.
    Confirm admin password Enter the password again to confirm.
    VM Size Select a supported VM size (storage size is per node).

    See Supported Software VM Sizes.

    1 License tiers: D/Developer, B/Base, A/Advanced, E/Enterprise.

  9. [Optional] On the Teradata Query Service blade, click Yes to configure the settings, then click OK.
    Parameter Action
    Teradata Query Service system name prefix Enter a prefix for all Query Service nodes in the cluster.
    VM size Select a supported VM size (storage size is per node).

    See Supported Software VM Sizes.
  10. [Optional] On the Data Stream Controller blade, click Yes to configure the settings, then click OK.
    Parameter Action
    DBC password Enter a new default VantageCloud password.

    For security reasons, you must change the default DBC password to a different password.
    Confirm DBC password Enter the password again to confirm.
    DSC admin password Enter the DSC administrative password, using 12 to 15 characters, starting with a letter. The password can contain only letters and numbers.
    Confirm DSC admin password Enter the password again to confirm.
    DSC system name prefix Enter a prefix for all DSC nodes.

    After the VM is created, a dsc prefix appears in the Azure portal followed by a VM number. For example, dsc-vm0, dsc-vm1, dsc-vm2, and so on.
    VM size Select a supported VM size (storage size is per node).

    See Supported Software VM Sizes.
  11. [Optional] On the Data Mover blade, click Yes to configure the settings, then click OK.
    Parameter Action
    DBC USER user password Enter a VantageCloud password, using 12 to 15 characters. The password can contain letters and numbers, but numbers are not required. The following special characters are allowed: ! @ # $ % ^ & * < >.

    For security reasons, you must change the default DBC password to a different password.
    Confirm DBC user password Enter the password again to confirm.
    DATAMOVER user password Enter a user password to access the internal DATAMOVER repository, using 12 to 15 characters, starting with a letter. The password can contain only letters and numbers.

    For security reasons, you must change the default datamover password to a different password.
    Confirm DATAMOVER user password Enter the password again to confirm.
    Data Mover system name prefix Enter a prefix for all Data Mover nodes.
    After the VM is created, this prefix appears in the Azure portal followed by the agent name and number. For example, a 4-node Data Mover cluster displays the following:
    • prefix-DM-Master-Agent1
    • prefix-DM-Agent2
    • prefix-DM-Agent3
    • prefix-DM-Agent4
    Additional agents Enter the number of additional agents (nodes) you want to deploy from 0 to 3. One node is already included for the master.
    Deployment of additional agents along with DM Master node is not supported using the UI (Azure Marketplace offer). If additional agents are required, contact Teradata Support team for deployment.
    VM size Select a supported VM size (storage size is per node).

    Although other sizes are available, the recommended size for production workloads is DS5_v2.

    See Supported Software VM Sizes.
  12. [Optional] On the QueryGrid Manager blade, click Yes to configure the settings, then click OK.
    Prerequisite: To use QueryGrid Manager, you must use Teradata Viewpoint Multiple Systems. You can use an on-premises installation or follow these steps to deploy on Azure.
    Parameter Action
    QueryGrid system name prefix Enter a prefix for all QueryGrid nodes.

    After the VM is created, a querygrid prefix appears in the Azure portal followed by a VM number. For example, querygrid_manager1, querygrid_manager2, and so on.
    VM size Select a supported VM size (storage size is per node).

    See Supported Software VM Sizes.
  13. Click the General Settings blade to configure additional settings applicable to all components, then click OK.
    Parameter   Action
    Virtual network Name Accept the default or enter a name for the virtual network.

    The default is (new) vnet-teradata. The name displays in the Azure portal as a resource after the VM deploys.
    Subnets VM subnet name Enter a name for the VM subnet.
    VM subnet address prefix Enter a CIDR block for the private subnet. The template creates a new private subnet in the selected VNet using this CIDR address.

    For multi-node VMs, make sure the CIDR range you calculate is 2 IPs per node, plus 5 additional IPs for the subnet. Other Teradata ecosystem products also need IPs in this subnet. For example, you can have up to 9 VMs, you need 9 additional IPs.

    See VNets.

    In the Azure portal, make sure the CIDR address you enter is not being used by existing subnets in the same VNet.
    NTP server list   Use the default or enter one or more network time protocol servers, separated by commas.
    Time zone   Enter the operating system time zone. The default time zone is UTC.

    The time zone for Teradata Server Management is UTC and cannot be changed by this parameter.

    If you enable Temporal, you must set the time zone parameter to UTC.
    Enable Customer-Managed Encryption Keys (CMEK)   Select whether you want to use own Encryption keys for disk encryption (No by default)1. See Customer Managed Encryption Key for more details.
    Select Key Vault   Select Key vault name if you want to use your own encryption keys.1
    Key Name   Select key name for the above key vault1
    Key Version   Select the key version to use.
    Important: 1KEY vault provided by user should have enable-purge-protection set as true. If not, it fails to encrypt the disk. Also, the key vault must be located in the same region as the Site.
  14. Click the Summary blade, review the information, then click OK.
  15. Click the Buy blade, review the terms of use and privacy policy, then click Create.
    This process can take 20 to 60 minutes, depending on your configuration and the availability of resources in your region.
    Trying to SSH into the VM may cause the creation of the VM to fail. Do not try to SSH into the VM until you get confirmation the VM was created or you receive a failure notification.
  16. To monitor the VM creation progress, do the following from the Azure portal:
    1. Click "" to see notifications the deployment started.
      Notifications send alerts only if you have set them prior to starting the deployment.
    2. From the left panel, click the Resource groups blade.
    3. Under the Name column, select a resource.
    4. Under Settings, click Deployments.
    5. Select any resources and look at the right pane to see if they are being deployed.
      The deployment is not complete until all VMs in the cluster are provisioned and the automatic process of configuring the database has finished.
      Under Operation details, a blue status symbol appears in the first column next to each resource to indicate the deployment process is continuing.
    6. Click "" located at the top of the right pane to refresh the pane.
      Under Operation details, the blue status symbol changes to a green check mark in the first column next to each resource to indicate the deployment process has finished.
    7. Under Operation details, when the STATUS column displays OK, select the resource.
      The PROVISIONING STATE displays Succeeded.
  17. If you are using Data Mover, Data Stream Controller, Query Service, or Viewpoint and want to use public IP addresses, do the following after creating the VMs:
    1. Create the public IP addresses and assign these addresses to a VM.
      See https://docs.microsoft.com/azure/virtual-network/virtual-network-public-ip-address.
    2. Adjust the NSG rules to accept connections using public IP addresses to allow access.
      The solution template defines an NSG for each software product VM.
  18. If you deployed QueryGrid Manager, you must deploy the desired QueryGrid connectors.
    For instructions, see Teradata® QueryGrid™ Installation and User Guide.
    Teradata VantageCloud Solution Template Obtaining Connectors
    VantageCloud Enterprise Contact Teradata Consulting Services to purchase QueryGrid connectors.
  19. If you enabled row-level security, go to the SSH client console and type the following:
    # dbscontrol -a | grep -i rls

    Sample output:

    RLSPurchased = True
    See Security Administration.
  20. If you enabled secure zones, go to the SSH client console and type the following:
    # dbscontrol -a | grep -i securezones

    Sample output:

    SecureZonesPurchased = True
    See Security Administration.
Related information