Merge pull request #251865 from ericd-mst-github/erd-vm-applications-how-to

VM Applications block blob updates

Author: prmerger-automator[bot]

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

@@ -6,8 +6,8 @@ ms.service: virtual-machines
 ms.subservice: gallery
 ms.topic: how-to
 ms.workload: infrastructure
-ms.date: 02/03/2022
-ms.reviewer: amjads
+ms.date: 09/08/2023
+ms.reviewer: erd
 ms.custom: devx-track-azurepowershell, devx-track-azurecli
 ---
 
@@ -44,7 +44,7 @@ if ($remainder -ne 0){
     }
 ```
 
-You need to make sure the files are publicly available, or you'll need the SAS URI for the files in your storage account. You can use [Storage Explorer](../vs-azure-tools-storage-explorer-blobs.md) to quickly create a SAS URI if you don't already have one.
+Ensure the storage account has public level access or use an SAS URI with read privilege, as other restriction levels fail deployments. You can use [Storage Explorer](../vs-azure-tools-storage-explorer-blobs.md) to quickly create a SAS URI if you don't already have one.
 
 If you're using PowerShell, you need to be using version 3.11.0 of the Az.Storage module.
 
@@ -59,7 +59,7 @@ Choose an option below for creating your VM application definition and version:
 
 1. Go to the [Azure portal](https://portal.azure.com), then search for and select **Azure Compute Gallery**.
 1. Select the gallery you want to use from the list.
-1. On the page for your gallery, select **Add** from the top of the page and then select **VM application definition** from the drop-down. The **Create a VM application definition** page will open.
+1. On the page for your gallery, select **Add** from the top of the page and then select **VM application definition** from the drop-down. The **Create a VM application definition** page opens.
 1. In the **Basics** tab, enter a name for your application and choose whether the application is for VMs running Linux or Windows.
 1. Select the **Publishing options** tab if you want to specify any of the following optional settings for your VM application definition:
     - A description of the VM application definition.
@@ -70,10 +70,10 @@ Choose an option below for creating your VM application definition and version:
 1. When you're done, select **Review + create**.
 1. When validation completes, select **Create** to have the definition deployed.
 1. Once the deployment is complete, select **Go to resource**.
-1. On the page for the application, select **Create a VM application version**. The **Create a VM Application Version** page will open.
+1. On the page for the application, select **Create a VM application version**. The **Create a VM Application Version** page opens.
 1. Enter a version number like 1.0.0.
 1. Select the region where you've uploaded your application package.
-1. Under **Source application package**, select **Browse**. Select the storage account, then the container where your package is located. Select the package from the list and then click **Select** when you're done. Alternatively, you can paste the SAS URI in this field if preferred.
+1. Under **Source application package**, select **Browse**. Select the storage account, then the container where your package is located. Select the package from the list and then select **Select** when you're done. Alternatively, you can paste the SAS URI in this field if preferred.
 1. Type in the **Install script**. You can also provide the **Uninstall script** and **Update script**. See the [Overview](vm-applications.md#command-interpreter) for information on how to create the scripts.
 1. If you have a default configuration file uploaded to a storage account, you can select it in **Default configuration**.
 1. Select **Exclude from latest** if you don't want this version to appear as the latest version when you create a VM.
@@ -91,7 +91,7 @@ Select the VM application from the list, and then select **Save** at the bottom
 
 :::image type="content" source="media/vmapps/select-app.png" alt-text="Screenshot showing selecting a VM application to install on the VM.":::
 
-If you've more than one VM application to install, you can set the install order for each VM application back on the **Advanced tab**.
+If you have more than one VM application to install, you can set the install order for each VM application back on the **Advanced tab**.
 
 You can also deploy the VM application to currently running VMs. Select the **Extensions + applications** option under **Settings** in the left menu when viewing the VM details in the portal.
 
@@ -116,7 +116,7 @@ To show the VM application status for VMSS, go to the VMSS page, Instances, sele
 
 VM applications require [Azure CLI](/cli/azure/install-azure-cli) version 2.30.0 or later.
 
-Create the VM application definition using [az sig gallery-application create](/cli/azure/sig/gallery-application#az_sig_gallery_application_create). In this example we're creating a VM application definition named *myApp* for Linux-based VMs.
+Create the VM application definition using [az sig gallery-application create](/cli/azure/sig/gallery-application#az_sig_gallery_application_create). In this example, we're creating a VM application definition named *myApp* for Linux-based VMs.
 
 
 ```azurecli-interactive
@@ -360,7 +360,7 @@ PUT
 | defaultConfigurationLink | Optional. The url containing the default configuration, which may be overridden at deployment time. | Valid and existing storage url |
 | Install | The command to install the application | Valid command for the given OS |
 | Remove | The command to remove the application | Valid command for the given OS |
-| Update | Optional. The command to update the application. If not specified and an update is required, the old version will be removed and the new one installed. | Valid command for the given OS |
+| Update | Optional. The command to update the application. If not specified and an update is required, the old version is removed and the new one installed. | Valid command for the given OS |
 | targetRegions/name | The name of a region to which to replicate | Validate Azure region |
 | targetRegions/regionalReplicaCount | Optional. The number of replicas in the region to create. Defaults to 1. | Integer between 1 and 3 inclusive |
 | endOfLifeDate | A future end of life date for the application version. Note this is for customer reference only, and isn't enforced. | Valid future date |
@@ -436,10 +436,10 @@ The order field may be used to specify dependencies between applications. The ru
 | Case | Install Meaning | Failure Meaning |
 |--|--|--|
 | No order specified | Unordered applications are installed after ordered applications. There's no guarantee of installation order amongst the unordered applications. | Installation failures of other applications, be it ordered or unordered doesn’t affect the installation of unordered applications. |
-| Duplicate order values | Application will be installed in any order compared to other applications with the same order. All applications of the same order will be installed after those with lower orders and before those with higher orders. | If a previous application with a lower order failed to install, no applications with this order will install. If any application with this order fails to install, no applications with a higher order will install. |
-| Increasing orders | Application will be installed after those with lower orders and before those with higher orders. | If a previous application with a lower order failed to install, this application won't install. If this application fails to install, no application with a higher order will install. |
+| Duplicate order values | Application is installed in any order compared to other applications with the same order. All applications of the same order will be installed after those with lower orders and before those with higher orders. | If a previous application with a lower order failed to install, no applications with this order install. If any application with this order fails to install, no applications with a higher order install. |
+| Increasing orders | Application will be installed after those with lower orders and before those with higher orders. | If a previous application with a lower order failed to install, this application won't install. If this application fails to install, no application with a higher order installs. |
 
-The response will include the full VM model. The following are the
+The response includes the full VM model. The following are the
 relevant parts.
 
 ```rest
@@ -477,7 +477,7 @@ GET
 /subscriptions/\<**subscriptionId**\>/resourceGroups/\<**resourceGroupName**\>/providers/Microsoft.Compute/virtualMachines/\<**VMName**\>/instanceView?api-version=2019-03-01
 ```
 
-The result will look like this:
+The result looks like this:
 
 ```rest
 {
@@ -503,15 +503,15 @@ The result will look like this:
     ]
 }
 ```
-The VM App status is in the status message of the result of the VMApp extension in the instance view.
+The VM App status is in the status message of the result of the VM App extension in the instance view.
 
 To get the status for a VMSS Application:
 
 ```rest
 GET
 /subscriptions/\<**subscriptionId**\>/resourceGroups/\<**resourceGroupName**\>/providers/Microsoft.Compute/ virtualMachineScaleSets/\<**VMSSName**\>/virtualMachines/<**instanceId**>/instanceView?api-version=2019-03-01
 ```
-The output will be similar to the VM example earlier.
+The output is similar to the VM example earlier.
 
 ---
 

articles/virtual-machines/vm-applications.md

@@ -5,7 +5,7 @@ ms.service: virtual-machines
 ms.subservice: gallery
 ms.topic: conceptual
 ms.workload: infrastructure
-ms.date: 07/17/2023
+ms.date: 09/18/2023
 author: ericd-mst-github
 ms.author: nikhilpatel
 ms.reviewer: erd
@@ -30,7 +30,9 @@ Application packages provide benefits over other deployment and packaging method
 
 - Support for virtual machines, and both flexible and uniform scale sets
 
-- If you have Network Security Group (NSG) rules applied on your VM or scale set, downloading the packages from an internet repository might not be possible. And  with storage accounts, downloading packages onto locked-down VMs would require setting up private links.
+- If you have Network Security Group (NSG) rules applied on your VM or scale set, downloading the packages from an internet repository might not be possible. And with storage accounts, downloading packages onto locked-down VMs would require setting up private links.
+
+- Support for Block Blobs: This feature allows the handling of large files efficiently by breaking them into smaller, manageable blocks. Ideal for uploading large amounts of data, streaming, and background uploading. 
 
 ## What are VM app packages?
 
@@ -46,7 +48,7 @@ The VM application packages use multiple resource types:
 
 - **No more than 3 replicas per region**: When you're creating a VM Application version, the maximum number of replicas per region is three.
 
-- **Public access on storage**: Only public level access to storage accounts work, as other restriction levels fail deployments.
+- **Storage with public access or SAS URI with read privilege:** The storage account needs to has public level access or use an SAS URI with read privilege, as other restriction levels fail deployments.
 
 - **Retrying failed installations**: Currently, the only way to retry a failed installation is to remove the application from the profile, then add it back.