[Doc-a-thon] Updating build-image-with-packer.md

Adding sudo to bash commands, making AZ CLI to use the interactive option, adding a clarification in the json template to replace the values accordingly given ubuntu is being used in the sample template

Author: divargas-msft

articles/virtual-machines/linux/build-image-with-packer.md

@@ -6,7 +6,7 @@ ms.service: virtual-machines
 ms.subservice: imaging
 ms.topic: how-to
 ms.workload: infrastructure
-ms.date: 05/07/2019
+ms.date: 04/11/2023
 ms.author: cynthn
 ms.collection: linux
 ---
@@ -20,23 +20,23 @@ Each virtual machine (VM) in Azure is created from an image that defines the Lin
 > [!NOTE]
 > Azure now has a service, Azure Image Builder, for defining and creating your own custom images. Azure Image Builder is built on Packer, so you can even use your existing Packer shell provisioner scripts with it. To get started with Azure Image Builder, see [Create a Linux VM with Azure Image Builder](image-builder.md).
 
-
 ## Create Azure resource group
+
 During the build process, Packer creates temporary Azure resources as it builds the source VM. To capture that source VM for use as an image, you must define a resource group. The output from the Packer build process is stored in this resource group.
 
 Create a resource group with [az group create](/cli/azure/group). The following example creates a resource group named *myResourceGroup* in the *eastus* location:
 
-```azurecli
+```azurecli-interactive
 az group create -n myResourceGroup -l eastus
 ```
 
-
 ## Create Azure credentials
+
 Packer authenticates with Azure using a service principal. An Azure service principal is a security identity that you can use with apps, services, and automation tools like Packer. You control and define the permissions as to what operations the service principal can perform in Azure.
 
 Create a service principal with [az ad sp create-for-rbac](/cli/azure/ad/sp) and output the credentials that Packer needs:
 
-```azurecli
+```azurecli-interactive
 az ad sp create-for-rbac --role Contributor --scopes /subscriptions/<subscription_id> --query "{ client_id: appId, client_secret: password, tenant_id: tenant }"
 ```
 
@@ -52,14 +52,14 @@ An example of the output from the preceding commands is as follows:
 
 To authenticate to Azure, you also need to obtain your Azure subscription ID with [az account show](/cli/azure/account):
 
-```azurecli
+```azurecli-interactive
 az account show --query "{ subscription_id: id }"
 ```
 
 You use the output from these two commands in the next step.
 
-
 ## Define Packer template
+
 To build images, you create a template as a JSON file. In the template, you define builders and provisioners that carry out the actual build process. Packer has a [provisioner for Azure](https://www.packer.io/docs/builders/azure.html) that allows you to define Azure resources, such as the service principal credentials created in the preceding step.
 
 Create a file named *ubuntu.json* and paste the following content. Enter your own values for the following parameters:
@@ -73,7 +73,6 @@ Create a file named *ubuntu.json* and paste the following content. Enter your ow
 | *managed_image_resource_group_name* | Name of resource group you created in the first step |
 | *managed_image_name*                | Name for the managed disk image that is created |
 
-
 ```json
 {
   "builders": [{
@@ -114,6 +113,10 @@ Create a file named *ubuntu.json* and paste the following content. Enter your ow
   }]
 }
 ```
+
+> [!NOTE]
+> Replace the `image_publisher`, `image_offer`, `image_sku` values and `inline` commands accordingly.
+
 You can also create a filed named *ubuntu.pkr.hcl* and paste the following content with your own values as used for the above parameters table.
 
 ```HCL
@@ -148,27 +151,26 @@ build {
 }
 ```
 
-
 This template builds an Ubuntu 16.04 LTS image, installs NGINX, then deprovisions the VM.
 
 > [!NOTE]
 > If you expand on this template to provision user credentials, adjust the provisioner command that deprovisions the Azure agent to read `-deprovision` rather than `deprovision+user`.
 > The `+user` flag removes all user accounts from the source VM.
 
-
 ## Build Packer image
+
 If you don't already have Packer installed on your local machine, [follow the Packer installation instructions](https://www.packer.io/docs/install).
 
 Build the image by specifying your Packer template file as follows:
 
 ```bash
-./packer build ubuntu.json
+sudo ./packer build ubuntu.json
 ```
 
 You can also build the image by specifying the *ubuntu.pkr.hcl* file as follows:
 
 ```bash
-packer build ubuntu.pkr.hcl
+sudo packer build ubuntu.pkr.hcl
 ```
 
 An example of the output from the preceding commands is as follows:
@@ -234,11 +236,11 @@ ManagedImageLocation: eastus
 
 It takes a few minutes for Packer to build the VM, run the provisioners, and clean up the deployment.
 
-
 ## Create VM from Azure Image
+
 You can now create a VM from your Image with [az vm create](/cli/azure/vm). Specify the Image you created with the `--image` parameter. The following example creates a VM named *myVM* from *myPackerImage* and generates SSH keys if they don't already exist:
 
-```azurecli
+```azurecli-interactive
 az vm create \
     --resource-group myResourceGroup \
     --name myVM \
@@ -253,18 +255,18 @@ It takes a few minutes to create the VM. Once the VM has been created, take note
 
 To allow web traffic to reach your VM, open port 80 from the Internet with [az vm open-port](/cli/azure/vm):
 
-```azurecli
+```azurecli-interactive
 az vm open-port \
     --resource-group myResourceGroup \
     --name myVM \
     --port 80
 ```
 
 ## Test VM and NGINX
+
 Now you can open a web browser and enter `http://publicIpAddress` in the address bar. Provide your own public IP address from the VM create process. The default NGINX page is displayed as in the following example:
 
 ![NGINX default site](./media/build-image-with-packer/nginx.png) 
 
-
 ## Next steps
 You can also use existing Packer provisioner scripts with [Azure Image Builder](image-builder.md).