CSM 10.4 Documentation

Home

Request an Azure® Virtual Machine in the CSM Desktop

Use the Incident Form to request an Azure® virtual machine in the CSM Desktop Client.

Note: This functionality is only available if you have applied the Orchestration Pack for Microsoft® Azure®. For more information, refer to the mApp Solution Tech Notes documentation.

To log an Azure® in the CSM Desktop Client:

  1. Log into CSM.
  2. In the CSM Desktop Client toolbar, click New>New Incident.

    A new Incident record opens.

  3. Record the basic details (Who, What, How):
    1. Requestor (in the Quick Info Tile): Provide the name of the Customer who initiated the contact, and then press ENTER or TAB to search for the Customer Record.
    2. Title: Provide a title for the Incident.
    3. Description: Provide a detailed description for the Incident.
    4. Call Source: Select a source for the initiation.

      Azure™ mApp Record the Details

  4. Classify the Incident:
    1. Service: Select Cloud Services from the drop-down.
    2. Category: Select Virtual Machines (VM) from the drop-down.
    3. Subcategory: Select Request Azure VM from the drop-down.

      Azure™ Incident Classification

      The Request Virtual Machine Specifics form displays in the Fullfill the Service Request section.

    4. Priority: Click the Priority drop-down to reveal the Priority Matrix (determined by invoked SLA), and then click a priority number.
  5. Complete the Request Virtual Machine Specifics Form:
    Note: The Virtual Machine drop-down values are based on the Standard VM specifications (Tools>Table Management>VM Template>Standard VM).

    Azure™ Virtual Machine Template Specifics Form

    1. Virtual Machine Template: Select a predefined template from the drop-down. This field is required.
    2. Size: Select a size for the virtual machine.

      The following read-only fields are auto-populated when the size is selected: CPU Cores, Memory, Disks, Max Disk Size, Max NICs (network interface card), Max IOPS (input/output operations per second), and Template Description.

      Azure™ VM Size Populated

    3. OS Name: Select the name of the Customer's operating system from the drop-down.
    4. Justification/Rationale: Provide additional details about the VM request.
    5. VM Request Ready: Select the check box when the virtual machine is ready to be provisioned.
  6. Complete the Incident logging process

    When the virtual machine is provisioned, an Automation Process initiates a c to senOne-Step Action a request to Azure® using the Customer's credentials and specifications. If the request is successful, the One-Step Action e-mails the Customer, updates the Service Request record by creating a Journal entry, creates a new Virtual Machine CI for the VM, and changes the Service Request status to Resolved. If the request to Azure® is unsuccessful, the One-Step Action sends an e-mail to the Customer and updates the Service Request record by creating a Journal entry that includes an error message.

  7. After the VM request is fulfilled, request a second day action:
    1. In the I Want To section, select a second day action from the Request Action for this VM drop-down:
      • Power Off
      • Deallocate VM
      • Restart VM
      • Start VM
      • Reset Access

        Second Day Actions in CSM Desktop Client

    2. Click the Run Action button.

Was this article useful?