Manually Provisioning Azure VMs
Views > Inventory > Applications
View > Service Requests > Request Details
Administrator, Operator, Operator with Approval Access Rights
This topic covers manual deployment of Azure VMs.
Use Commander to:
- Deploy a requested service or VM component by clicking Deploy at the appropriate level of the tree in the Request Details dialog. Note that once a component in a service has been deployed, it's no longer possible to deploy at the service level; you must deploy at the component level.
- Deploy a VM from a private Azure image. Right-click an image and choose Provisioning > Deploy to VM. The VM must be deployed into an existing resource group.
- Deploy a VM from a public Azure image. In the Public Images folder, right-click an image and choose Provisioning > Deploy to VM. The VM must be deployed into an existing resource group.
Note: When deploying an entire service, if the deployment of one or more components fails, Commander will still attempt to deploy other components in the service.
You can also manually provision ARM templates. For more information, see Manually Provisioning ARM Templates.
The following sections provide details and additional help links for the manual deployment wizard. The pages and options displayed depend on whether you're deploying an entire service or a VM component.
- Let the system name this VM automatically: See also Customizing Naming Conventions.
- Manually name this VM: The name must be unique in the target resource group. Note that you can't use variables in this field, but you can use variables in the global VM naming convention.
- Placement Options: Although the option you choose here allows Commander to preselect destination choices for you, you can change those selections throughout this wizard. The available options are:
- Last Specified: Uses the placement location that was last used to deploy this service or component. If the service or component has not been previously deployed, no destination is selected.
- User Specified: No destination is selected; the destination must be selected manually.
- Automated Deployment: Uses the placement options configured for automated deployment. When multiple deployment destinations are valid, the first alphabetically is used. If you see the error "Automated deployment has not been configured", see Azure: Configuring destinations for automated deployment to learn how to set up automated deployment.
- Destination: Choose a resource group where the VM will be deployed. You must deploy into an existing resource group. If you're deploying a private (custom) image, you can select from the resource groups in the source region. If you're deploying a public image, all regions are available for selection. The default public images are available in all regions, but if you've customized the public images, make sure to select a resource group in a region where the public image is available. Otherwise, deployment will fail.
This page allows you to customize VM resources and security settings. This page doesn't appear if you're deploying an entire service as individual components (that is, if you clicked Deploy at the Service level in the Request Details dialog rather than at the Component level).
- Instance Type: Select an instance type from the drop-down menu. This option isn't available if you're deploying an entire service as individual components — that is, if you clicked Deploy at the Service level in the Request Details dialog (rather than at the Component level). Click Details to see more information about the selected instance type. Note that only instance types supporting the number of data disks already attached to the image are displayed.
- Credentials: If you're deploying a prepared (generalized) template, select credentials from the drop-down menu. Prepared templates contain no built-in authentication information, as opposed to Specialized templates, which already have credentials configured. You can confirm that a template is prepared by checking the value for the Customizable OS property in the General section of the template's Summary tab; a value of Yes means the template is prepared.
Note: Due to an Azure limitation, the value for the Customizable OS property for Azure images is always Yes (Generalized), even for prepared images. Because Commander can't determine whether the image requires credentials, this wizard always allows you to specify credentials. To prevent deployment failures, be sure to specify credentials only when required.
Public images are always generalized (prepared), and always require credentials.
Click Add Credentials to create a new set of credentials if required. You can specify:
- Username/Password credentials: Azure user names must contain from 1 to 64 characters, must contain only lowercase letters, numbers, hyphens and underscores, and must start with a lowercase letter. You can't use one of the following user names: user, root, admin or administrator. Azure passwords must contain from 12 to 72 characters and must contain three of the following: one lowercase character, one uppercase character, one number and one special character. User names are validated when you click Next, but passwords are validated at provisioning time. See also Naming Conventions for Azure Resources in the Microsoft documentation.
- RSA Key credentials, for Linux prepared images only. See Adding credentials to learn more.
Caution: Don't lose this user name and password, or the VM will be inaccessible.
- Network Security Group: Select a network security group from the drop-down menu. All network security groups from the target region are available for selection.
- Diagnostics Storage Account: To enable memory usage monitoring, a storage account needs to be selected either by automated deployment destination or manually.
- Availability Set: Microsoft Azure availability sets ensure both fault tolerance and service availability. Select an availability set from the drop-down menu, if configured for the service catalog entry. Or, enter text in the text field. If you enter the name of an availability set that doesn't already exist, it will be created. Availability set names are case-insensitive.
This page allows you to configure storage resources. Note that when deploying an entire service, all VMs in the service are deployed with the same storage options, and you can't edit disk information.
- Type: Select Managed or Unmanaged storage in the drop-down menu. All of a VM's disks must have the same storage type. For private (custom) images with managed storage, you can't change the storage type. If you selected an availability set on the previous page, the storage type is determined by that availability set.
Existing disks are listed with their projected location, depending on the storage type selected. Storage accounts are filtered based on the image's region and selected instance type.
- add a disk by clicking Add. Note that the number of disks you can add is controlled by the selected instance type.
- delete a disk (other than the OS disk and existing data disks, which can't be deleted) by selecting it in the Disks list and clicking Delete.
- modify a disk by selecting it in the Disks list and editing its settings as required:
- SSD: Premium disks (SSD) are backed by solid-state drives and offer consistent, low-latency performance. They provide the best balance between price and performance, and are ideal for I/O-intensive applications and production workloads. Premium disks are not supported for all instance types.
- HDD: Standard disks (HDD) are backed by magnetic drives and are preferable for applications where data is accessed infrequently.
- Limitation: You can't configure encryption for a new disk.
- Each Azure instance type has limitations for the number and type of disks that can be added.
Device Name: Edit the suggested device name if required. Managed disk names must be unique in the target resource group. Unmanaged disk names must unique within the VM. The name must contain from 1 to 64 characters, must contain only letters, numbers, hyphens, dots and underscores, and must start with a letter or number.
Limitation: Even though you can edit the name for a managed disk, the suggested name will be used.
Capacity: Specify the disk capacity in GB. Note that you can't shrink existing disks, and you can't resize existing unmanaged disks.
Disk Type: Select one of the following types from the drop-down menu:
Storage Account: For unmanaged disks, select a storage account from the list. You can select only storage accounts that are available in the image's region and support the selected Disk Type.
This page doesn't appear if you're deploying an entire service as individual components (that is, if you clicked Deploy at the Service level in the Request Details dialog rather than at the Component level).
- Network: By default, the first network (alphabetically) in the destination resource group is selected. Select a different network from the drop-down list if required. Only networks in the image's region are available for selection. The Network drop-down list groups networks by resource group.
- Subnet: All subnets in the selected network are displayed. Choose a subnet from the list.
To assign a public IP address to the VM, select Create Public IP Address and select either Static or Dynamic in the Allocation Method drop-down list.
Otherwise, leave the default selection, No Public IP Address.
This page appears only when deploying an entire requested service. That is, you clicked Deploy at the Service level in the Request Details dialog, rather than at the Component level.
All components in the service are listed. Custom components contained in the service are listed for information purposes only.
Deselect the components you don't want to deploy at this time.
Components are deployed serially, not in parallel.
Custom attributes allow you to provide more management information about your virtualized infrastructure.
This page doesn't appear when deploying an entire service that's configured to be deployed as individual VM components.
For information on custom attributes, see Working with Custom Attributes.
When deploying an entire service, values entered on this page will be applied only to the components of the service.
If the Expiry Date form element or the Primary Owner form element has been added to the Component request form, users can specify expiry and/or ownership information for requested components. Their selection isn't displayed in the manual Service deployment wizard. In this case, you should deploy each component separately by clicking Deploy at the Component level of the Request Details, rather than at the Service level. Doing so ensures that you won't override the requester's individual selections for all components in the service.
- VM Name: If name you specified on the Name page isn't unique in the target resource group, an error message is displayed. Click Edit. In the Modify VM Name dialog, edit the name and click Validate to verify that it meets naming rules. Click OK, and if the name you specified doesn't already exist in the target resource group, the warning disappears. See also Customizing Naming Conventions.
- Expiry Date: Click Edit to set or override the expiry date, or to specify that the service will never expire. See also Managing Service Expirations.
- Expiry Group: Click Edit and choose an expiry group from the drop-down.
- Maintenance Group: Click Edit and choose a maintenance group from the drop-down.
- Power Schedule Group: Click Edit and choose a power schedule group from the drop-down. Displayed for VM components only.
- Rightsizing Group: Click Edit and choose a rightsizing group from the drop-down. Displayed for VM components only.
Owners: To edit ownership assignment, click Edit. In the Edit Ownership dialog, if the user you assign is a member of an organization, make sure to select the owner's organization to ensure the service is visible to organization members. To assign users, enter a username or email address. See also Assigning Service Ownership.
- Service Request: When deploying a service request, the Release checkbox is visible and is enabled by default, so that components advance to completion automatically. When the Release checkbox is enabled, if one or more completion workflows have been assigned, the service request is automatically transferred to the completion workflow process. If no completion workflows are assigned, once all components in a service are deployed, releasing the components makes the service visible to the requester (for example, the Service Portal user).
If there are manual steps in your provisioning process, disable the Release checkbox so that you can carry out these steps before the completion workflow starts. For example, you may need to install software, check operating system patches, or migrate VMs. Click Comment to enter more information for the service request comment log.
A summary of your settings is displayed. New public cloud VMs are always powered on when created.
- Policy Actions: If one or more policies will be triggered once deployment occurs, policy actions are listed here.
If the deployment operation is canceled or fails, Commander doesn't delete any additional VM resources, such as NICs, that were created before the operation was canceled. These must be deleted in the Azure portal.