Merge pull request #258344 from ericd-mst-github/erd-aib-registration-cmd-updates

AIB registration cmd updates

Author: v-dirichards

articles/virtual-machines/image-builder-api-update-release-notes.md

@@ -5,7 +5,7 @@ author: kof-f
 ms.service: virtual-machines
 ms.topic: conceptual
 ms.workload: infrastructure
-ms.date: 11/01/2023
+ms.date: 11/10/2023
 ms.reviewer: erd
 ms.subservice: image-builder
 ms.custom: references_regions
@@ -26,6 +26,9 @@ Azure Image Builder is enabling Isolated Image Builds using Azure Container Inst
 
 You might observe a different set of transient Azure resources appear temporarily in the staging resource group but that does not impact your actual builds or the way you interact with Azure Image Builder. For more information, please see [Isolated Image Builds](./security-isolated-image-builds-image-builder.md).
 
+> [!IMPORTANT]
+> Make sure your subscription is registered for the `Microsoft.ContainerInstance` provider.
+
 ### April 2023
 New portal functionality has been added for Azure Image Builder. Search “Image Templates” in Azure portal, then click “Create”. You can also [get started here](https://ms.portal.azure.com/#create/Microsoft.ImageTemplate) with building and validating custom images inside the portal.
 

articles/virtual-machines/image-builder-triggers-how-to.md

@@ -7,7 +7,7 @@ ms.reviewer: erd
 ms.service: virtual-machines
 ms.subservice: image-builder
 ms.topic: how-to
-ms.date: 10/16/2023
+ms.date: 11/10/2023
 ms.custom: template-how-to-pattern, devx-track-azurecli
 ---
 
@@ -25,16 +25,17 @@ Before setting up your first trigger, ensure you're using Azure Image Builder AP
 
 ## How to set up a trigger in Azure Image Builder
 
-### Register the features
+### Register the providers
 
-To use VM Image Builder with triggers, you need to register the below features. Check your registration by running the following commands:
+To use VM Image Builder with triggers, you need to register the below providers. Check your registration by running the following commands:
 
 ```azurecli-interactive
 az provider show -n Microsoft.VirtualMachineImages -o json | grep registrationState
 az provider show -n Microsoft.KeyVault -o json | grep registrationState
 az provider show -n Microsoft.Compute -o json | grep registrationState
 az provider show -n Microsoft.Storage -o json | grep registrationState
 az provider show -n Microsoft.Network -o json | grep registrationState
+az provider show -n Microsoft.ContainerInstance -o json | grep registrationState
 ```
 
 If the output doesn't say registered, run the following commands:
@@ -45,6 +46,7 @@ az provider register -n Microsoft.Compute
 az provider register -n Microsoft.KeyVault
 az provider register -n Microsoft.Storage
 az provider register -n Microsoft.Network
+az provider register -n Microsoft.ContainerInstance
 ```
 Register the auto image build triggers feature:
 
@@ -67,6 +69,8 @@ additionalregion=eastus2
 acgName=ibTriggersGallery
 # Name of the image definition to be created - ibTriggersImageDef in this example
 imageDefName=ibTriggersImageDef
+# Name of the Trigger to be created - ibTrigger in this example
+ibTriggerName=ibTrigger
 # Name of the image template to be created - ibTriggersImageTemplate in this example
 imageTemplateName=ibTriggersImageTemplate
 # Reference name in the image distribution metadata
@@ -159,12 +163,12 @@ Image template requirements:
 After configuring your template use the following command to submit the image configuration to the Azure Image Builder service:
 
 ```azurecli-interactive
-az resource create --api-version 2022-07-01 --resource-group $resourceGroupName --properties @helloImageTemplateforTriggers.json --is-full-object --resource-type Microsoft.VirtualMachineImages/imageTemplates --name $imageTemplateName
+az image builder create -g $resourceGroupName -n $imageTemplateName --image-template helloImageTemplateforTriggers.json
 ```
 You can use the following command to check to make sure the image template was created successfully:
 
 ```azurecli-interactive
-az resource show --api-version 2022-07-01 --ids /subscriptions/$subscriptionID/resourcegroups/$resourceGroupName/providers/Microsoft.VirtualMachineImages/imageTemplates/$imageTemplateName
+az image builder show --name $imageTemplateName --resource-group $resourceGroupName
 ```
 > [!NOTE]
 > When running the command above the `provisioningState` should say "Succeeded", which means the template was created without any issues. If the `provisioningState` does not say succeeded, you will not be able to make a trigger use the image template.
@@ -187,12 +191,12 @@ Trigger requirements:
 Use the following command to add the trigger to your resource group.
 
 ```azurecli-interactive
-az resource create --api-version 2022-07-01 --resource-group $resourceGroupName --properties @trigger.json --is-full-object --namespace Microsoft.VirtualMachineImages --parent imageTemplates/$imageTemplateName --resource-type triggers --name source
+az image builder trigger create --name $ibTriggerName --resource-group $resourceGroupName --image-template-name $imageTemplateName --kind SourceImage
 ```
 You can also use the following command to check that the trigger was created successfully:
 
 ```azurecli
-az resource show --api-version 2022-07-01 --ids /subscriptions/$subscriptionID/resourcegroups/$resourceGroupName/providers/Microsoft.VirtualMachineImages/imageTemplates/$imageTemplateName/triggers/source
+az image builder trigger show --name $ibTriggerName --image-template-name $imageTemplateName --resource-group $resourceGroupName
 ```
 > [!NOTE]
 > When running the command above the `provisioningState` should say `Succeeded`, which means the trigger was created without any issues. In `status`, the code should say `Healthy` and the message should say `Trigger is active.`
@@ -204,14 +208,14 @@ az resource show --api-version 2022-07-01 --ids /subscriptions/$subscriptionID/r
 Use the following command to delete the trigger:
 
 ```azurecli-interactive
-az resource delete --api-version 2022-07-01 --ids /subscriptions/$subscriptionID/resourcegroups/$resourceGroupName/providers/Microsoft.VirtualMachineImages/imageTemplates/$imageTemplateName/triggers/source
+az image builder trigger delete --name $ibTriggerName --image-template-name $imageTemplateName --resource-group $resourceGroupName
 ```
 #### Deleting the image template
 
 Use the following command to delete the image template:
 
 ```azurecli-interactive
-az resource delete --api-version 2022-07-01 --ids /subscriptions/$subscriptionID/resourcegroups/$resourceGroupName/providers/Microsoft.VirtualMachineImages/imageTemplates/$imageTemplateName
+az image builder delete --name $imageTemplateName --resource-group $resourceGroupName
 ```
 
 ## Next steps

articles/virtual-machines/linux/image-builder-devops-task.md

@@ -42,8 +42,8 @@ Before you begin, you must:
 * Have an Azure DevOps Services (formerly Visual Studio Team Services, or VSTS) account, and a Build Pipeline created.
 
 * Register and enable the VM Image Builder feature requirements in the subscription that's used by the pipelines:
-  * [Azure PowerShell](../windows/image-builder-powershell.md#register-features)
-  * [The Azure CLI](../windows/image-builder.md#register-the-features)
+  * [Azure PowerShell](../windows/image-builder-powershell.md#register-providers)
+  * [The Azure CLI](../windows/image-builder.md#register-the-providers)
 
 * Create a standard Azure storage account in the source image resource group. You can use other resource groups or storage accounts. The storage account is used transfer the build artifacts from the DevOps task to the image.
 

articles/virtual-machines/linux/image-builder-gallery-update-image-version.md

@@ -3,8 +3,8 @@ title: Create a new VM image version from an existing image version by using Azu
 description: In this article, you'll learn how to create a new VM image version from an existing image version by using VM Image Builder in Linux.
 author: kof-f
 ms.author: kofiforson
-ms.reviewer: cynthn
-ms.date: 03/02/2020
+ms.reviewer: erd
+ms.date: 11/10/2020
 ms.topic: how-to
 ms.service: virtual-machines
 ms.subservice: image-builder
@@ -18,9 +18,9 @@ In this article, you learn how to update an existing image version in an [Azure
 
 To configure the image, you use a sample JSON template, [helloImageTemplateforSIGfromSIG.json](https://raw.githubusercontent.com/azure/azvmimagebuilder/master/quickquickstarts/2_Creating_a_Custom_Linux_Shared_Image_Gallery_Image_from_SIG/helloImageTemplateforSIGfromSIG.json). 
 
-## Register the features
+## Register the providers
 
-To use VM Image Builder, you need to register the features.
+To use VM Image Builder, you need to register the providers.
 
 1. Check your provider registrations. Make sure that each one returns *Registered*.
 
@@ -30,6 +30,7 @@ To use VM Image Builder, you need to register the features.
     az provider show -n Microsoft.Compute | grep registrationState
     az provider show -n Microsoft.Storage | grep registrationState
     az provider show -n Microsoft.Network | grep registrationState
+    az provider show -n Microsoft.ContainerInstance | grep registrationState
     ```
 
 1. If they don't return *Registered*, register the providers by running the following commands:
@@ -40,6 +41,7 @@ To use VM Image Builder, you need to register the features.
     az provider register -n Microsoft.KeyVault
     az provider register -n Microsoft.Storage
     az provider register -n Microsoft.Network
+    az provider register -n Microsoft.ContainerInstance
     ```
 
 ## Set variables and permissions

articles/virtual-machines/linux/image-builder-gallery.md

@@ -3,8 +3,8 @@ title: Use Azure Image Builder & Azure Compute Gallery for Linux VMs
 description: Learn how to use the Azure Image Builder, and the Azure CLI, to create an image version in an Azure Compute Gallery, and then distribute the image globally.
 author: kof-f
 ms.author: kofiforson
-ms.reviewer: cynthn
-ms.date: 04/11/2023
+ms.reviewer: erd
+ms.date: 11/10/2023
 ms.topic: how-to
 ms.service: virtual-machines
 ms.subservice: image-builder
@@ -17,11 +17,11 @@ ms.custom: devx-track-azurecli, devx-track-linux
 
 This article shows you how you can use the Azure Image Builder, and the Azure CLI, to create an image version in an [Azure Compute Gallery](../shared-image-galleries.md) (formerly known as Shared Image Gallery), then distribute the image globally. You can also do this using [Azure PowerShell](../windows/image-builder-gallery.md).
 
-We will be using a sample .json template to configure the image. The .json file we are using is here: [helloImageTemplateforSIG.json](https://github.com/azure/azvmimagebuilder/blob/master/quickquickstarts/1_Creating_a_Custom_Linux_Shared_Image_Gallery_Image/helloImageTemplateforSIG.json). 
+We'll be using a sample .json template to configure the image. The .json file we're using is here: [helloImageTemplateforSIG.json](https://github.com/azure/azvmimagebuilder/blob/master/quickquickstarts/1_Creating_a_Custom_Linux_Shared_Image_Gallery_Image/helloImageTemplateforSIG.json). 
 
 To distribute the image to an Azure Compute Gallery, the template uses [sharedImage](image-builder-json.md#distribute-sharedimage) as the value for the `distribute` section of the template.
 
-## Register the features
+## Register the providers
 
 To use Azure Image Builder, you need to register the feature.
 
@@ -33,21 +33,23 @@ az provider show -n Microsoft.KeyVault | grep registrationState
 az provider show -n Microsoft.Compute | grep registrationState
 az provider show -n Microsoft.Storage | grep registrationState
 az provider show -n Microsoft.Network | grep registrationState
+az provider show -n Microsoft.ContainerInstance | grep registrationState
 ```
 
-If they do not say registered, run the following:
+If they don't say registered, run the following:
 
 ```azurecli-interactive
 az provider register -n Microsoft.VirtualMachineImages
 az provider register -n Microsoft.Compute
 az provider register -n Microsoft.KeyVault
 az provider register -n Microsoft.Storage
 az provider register -n Microsoft.Network
+az provider register -n Microsoft.ContainerInstance
 ```
 
 ## Set variables and permissions
 
-We will be using some pieces of information repeatedly, so we will create some variables to store that information.
+We'll be using some pieces of information repeatedly, so we'll create some variables to store that information.
 
 Image Builder only supports creating custom images in the same Resource Group as the source managed image. Update the resource group name in this example to be the same resource group as your source managed image.
 
@@ -80,7 +82,7 @@ az group create -n $sigResourceGroup -l $location
 
 ## Create a user-assigned identity and set permissions on the resource group
 
-Image Builder will use the [user-identity](../../active-directory/managed-identities-azure-resources/qs-configure-cli-windows-vm.md#user-assigned-managed-identity) provided to inject the image into the Azure Compute Gallery. In this example, you will create an Azure role definition that has the granular actions to perform distributing the image to the gallery. The role definition will then be assigned to the user-identity.
+Image Builder uses the [user-identity](../../active-directory/managed-identities-azure-resources/qs-configure-cli-windows-vm.md#user-assigned-managed-identity) provided to inject the image into the Azure Compute Gallery. In this example, you'll create an Azure role definition that has the granular actions to perform distributing the image to the gallery. The role definition will then be assigned to the user-identity.
 
 ```azurecli-interactive
 # create user assigned identity for image builder to access the storage account where the script is located
@@ -115,7 +117,7 @@ az role assignment create \
 
 ## Create an image definition and gallery
 
-To use Image Builder with an Azure Compute Gallery, you need to have an existing gallery and image definition. Image Builder will not create the gallery and image definition for you.
+To use Image Builder with an Azure Compute Gallery, you need to have an existing gallery and image definition. Image Builder won't create the gallery and image definition for you.
 
 If you don't already have a gallery and image definition to use, start by creating them. First, create a gallery.
 
@@ -213,9 +215,9 @@ You should see the image was customized with a *Message of the Day* as soon as y
 
 ## Clean up resources
 
-If you want to now try re-customizing the image version to create a new version of the same image, skip the next steps and go on to [Use Azure Image Builder to create another image version](image-builder-gallery-update-image-version.md).
+If you want to now try recustomizing the image version to create a new version of the same image, skip the next steps and go on to [Use Azure Image Builder to create another image version](image-builder-gallery-update-image-version.md).
 
-This will delete the image that was created, along with all of the other resource files. Make sure you are finished with this deployment before deleting the resources.
+This deletes the image that was created, along with all of the other resource files. Make sure you're finished with this deployment before deleting the resources.
 
 When deleting gallery resources, you need delete all of the image versions before you can delete the image definition used to create them. To delete a gallery, you first need to have deleted all of the image definitions in the gallery.
 

articles/virtual-machines/linux/image-builder-troubleshoot.md

@@ -4,7 +4,7 @@ description: This article helps you troubleshoot common problems and errors you
 author: kof-f
 ms.author: kofiforson
 ms.reviewer: erd
-ms.date: 11/01/2023
+ms.date: 11/10/2023
 ms.topic: troubleshooting
 ms.service: virtual-machines
 ms.subservice: image-builder
@@ -735,10 +735,30 @@ The cause might be a timing issue because of the D1_V2 VM size. If customization
 
 To avoid the timing issue, you can increase the VM size or you can add a 60-second PowerShell sleep customization.
 
+### Unregistered Azure Container Instances provider
+
+#### Error
+```text
+Azure Container Instances provider not registered for your subscription.
+```
+
+#### Cause
+Your template subscription doesn't have the Azure Container Instances provider registered.
+
+#### Solution
+Register the Azure Container Instances provider for your template subscription and add the Azure CLI or PowerShell commands:
+
+- Azure CLI: `az provider register -n Microsoft.ContainerInstance`
+- PowerShell: `Register-AzResourceProvider -ProviderNamespace Microsoft.ContainerInstance`
+
+
+
 ### Azure Container Instances quota exceeded
 
 #### Error
-"Azure Container Instances quota exceeded"
+```text
+Azure Container Instances quota exceeded"
+```
 
 #### Cause
 Your subscription doesn't have enough Azure Container Instances (ACI) quota for Azure Image Builder to successfully build an image.

articles/virtual-machines/linux/image-builder.md

@@ -3,8 +3,8 @@ title: Use Azure VM Image Builder with an Azure Compute Gallery for Linux VMs
 description: Create Linux VM images with Azure VM Image Builder and Azure Compute Gallery.
 author: kof-f
 ms.author: kofiforson
-ms.reviewer: cynthn
-ms.date: 04/11/2023
+ms.reviewer: erd
+ms.date: 11/10/2023
 ms.topic: how-to
 ms.service: virtual-machines
 ms.subservice: image-builder
@@ -20,16 +20,17 @@ This article uses a sample JSON template to configure the image. The JSON file i
 
 To distribute the image to an Azure Compute Gallery, the template uses [sharedImage](image-builder-json.md#distribute-sharedimage) as the value for the `distribute` section of the template.
 
-## Register the features
+## Register the providers
 
-To use VM Image Builder, you need to register the feature. Check your registration by running the following commands:
+To use VM Image Builder, you need to register the providers. Check your registration by running the following commands:
 
 ```azurecli-interactive
 az provider show -n Microsoft.VirtualMachineImages -o json | grep registrationState
 az provider show -n Microsoft.KeyVault -o json | grep registrationState
 az provider show -n Microsoft.Compute -o json | grep registrationState
 az provider show -n Microsoft.Storage -o json | grep registrationState
 az provider show -n Microsoft.Network -o json | grep registrationState
+az provider show -n Microsoft.ContainerInstance -o json | grep registrationState
 ```
 
 If the output doesn't say *registered*, run the following commands:
@@ -40,6 +41,7 @@ az provider register -n Microsoft.Compute
 az provider register -n Microsoft.KeyVault
 az provider register -n Microsoft.Storage
 az provider register -n Microsoft.Network
+az provider register -n Microsoft.ContainerInstance
 ```
 
 ## Set variables and permissions