Merge pull request #178340 from cynthn/vmapps-updates

Fixing CLI

Author: denrea

articles/virtual-machines/vm-applications-how-to.md

@@ -5,7 +5,7 @@ ms.service: virtual-machines
 ms.subservice: shared-image-gallery
 ms.topic: how-to
 ms.workload: infrastructure
-ms.date: 10/27/2021
+ms.date: 11/02/2021
 ms.reviewer: amjads
 ms.custom: 
 
@@ -84,36 +84,35 @@ If you have more than one VM application to install, you can set the install ord
 
 ### [CLI](#tab/cli)
 
+VM applications requires [Azure CLI](/cli/azure/install-azure-cli) version 2.30.0 or later.
+
 Crate the VM application definition using [az sig gallery-application create](/cli/azure/sig/gallery-application#az_sig_gallery_application_create). In this example we are creating a VM application definition named *myApp* for Linux-based VMs.
 
 ```azurecli-interactive
 az sig gallery-application create \
-    --gallery-application-name myApp \
+    --application-name myApp \
     --gallery-name myGallery \
     --resource-group myResourceGroup \
     --os-type Linux \
     --location "East US"
 ```
 
-Create a VM application version using [az sig gallery-application-version create](/cli/azure/sig/gallery-application#az_sig_gallery_application_version_create). Allowed characters for version are numbers and periods. Numbers must be within the range of a 32-bit integer. Format: *MajorVersion*.*MinorVersion*.*Patch*.
+Create a VM application version using [az sig gallery-application version create](/cli/azure/sig/gallery-application/version#az_sig_gallery_application_version_create). Allowed characters for version are numbers and periods. Numbers must be within the range of a 32-bit integer. Format: *MajorVersion*.*MinorVersion*.*Patch*.
 
 Replace the values of the parameters with your own.
 
 ```azurecli-interactive
-az sig gallery-application-version create \
-   --gallery-application-version 1.0.0 \
-   --gallery-application-name myApp \
+az sig gallery-application version create \
+   --version-name 1.0.0 \
+   --application-name myApp \
    --gallery-name myGallery \
    --location "East US" \
    --resource-group myResourceGroup \
    --package-file-link "https://<storage account name>.blob.core.windows.net/<container name>/<filename>" \
    --install-command "mv myApp .\myApp\myApp" \
    --remove-command "rm .\myApp\myApp" \
    --update-command  "mv myApp .\myApp\myApp \
-   --target-regions "westcentralus" "southcentralus=1" \
    --default-configuration-file-link "https://<storage account name>.blob.core.windows.net/<container name>/<filename>"\
-   --publishing-profile-end-of-life-date "01/01/2023" \
-   --description "Initial version of the Linux application."
 ```
 
 

articles/virtual-machines/vm-applications.md

@@ -6,7 +6,7 @@ ms.service: virtual-machines
 ms.subservice: gallery
 ms.topic: conceptual
 ms.workload: infrastructure
-ms.date: 10/27/2021
+ms.date: 11/02/2021
 ms.author: cynthn
 ms.reviewer: amjads
 ms.custom: 
@@ -114,7 +114,7 @@ The install/update/remove commands should be written assuming the application pa
 
 ## File naming
 
-During the preview, when the application file gets downloaded to the VM, the file name is the same as the name you use when you create the VM application. For example, if I name my VM applicaton `myApp`, the file that will be downloaded to the VM will also be named `myApp`, regardless of what the file name is used in the storage account. If you VM application also has a configuration file, that file is the name of the application with `_config` appended. If `myApp` has a configuration file, it will be named `myApp_config`.
+During the preview, when the application file gets downloaded to the VM, the file name is the same as the name you use when you create the VM application. For example, if I name my VM application `myApp`, the file that will be downloaded to the VM will also be named `myApp`, regardless of what the file name is used in the storage account. If you VM application also has a configuration file, that file is the name of the application with `_config` appended. If `myApp` has a configuration file, it will be named `myApp_config`.
 
 For example, if I name my VM application `myApp` when I create it in the Gallery, but it is stored as `myApplication.exe` in the storage account, when it gets downloaded to the VM the file name will be `myApp`. My install string should start by renaming the file to be whatever the it needs to be to run on the VM (like myApp.exe).