title | description | ms.service | ms.subservice | ms.topic | author | ms.author | ms.date |
---|---|---|---|---|---|---|---|
Set plan technical configuration for an Azure Container offer in Microsoft AppSource. |
Set plan technical configuration for an Azure Container offer in Microsoft AppSource. |
marketplace |
partnercenter-marketplace-publisher |
article |
keferna |
keferna |
03/24/2022 |
Container images must be hosted in a private Azure Container Registry. Use this page to provide reference information for your container image repository inside the Azure Container Registry.
After you submit the offer, your container image is copied to Azure Marketplace in a specific public container registry. All requests from Azure users to use your module are served from the Azure Marketplace public container registry, not your private container registry.
You can target multiple platforms and provide several versions of your module container image using tags. To learn more about tags and versioning, see Prepare Azure Container technical assets.
Provide the Azure subscription ID where resource usage is reported and services are billed for the Azure Container Registry that includes your container image. You can find this ID on the Subscriptions page in the Azure portal.
Provide the Azure resource group name that contains the Azure Container Registry with your container image. The resource group must be accessible in the subscription ID (above). You can find the name on the Resource groups page in the Azure portal.
Provide the Azure container registry name that has your container image. The container registry must be present in the Azure resource group you provided earlier. Provide only the registry name, not the full login server name. Omit azurecr.io from the name. You can find the registry name on the Container Registries page in the Azure portal.
Provide the Admin username for the Azure Container Registry associated with the Azure Container Registry that has your container image. The username and password (next step) are required to ensure your company has access to the registry. To get the admin username and password, set the admin-enabled property to True using the Azure CLI. You can optionally set Admin user to Enable in the Azure portal.
:::image type="content" source="media/azure-container/azure-create-12-update-container-registry-edit.png" alt-text="Illustrates the Update container registry dialog box.":::
Provide the Admin password for the Azure Container Registry for the admin username associated with the Azure Container Registry and has your container image. The username and password are required to ensure your company has access to the registry. You can get the password from the Azure portal by going to Container Registry > Access Keys or with Azure CLI using the show command.
:::image type="content" source="media/azure-container/azure-create-13-access-keys.png" alt-text="Illustrates the access key screen in the Azure portal.":::
Provide the Repository name within the Azure Container Registry that has your image. You specify the name of the repository when you push the image to the registry. You can find the name of the repository by going to the Container Registry > Repositories page. For more information, see View container registry repositories in the Azure portal. After the name is set, it can't be changed. Use a unique name for each offer in your account.
Customers must be able to automatically get updates from Azure Marketplace when you publish an update. If they don't want to update, they must be able to stay on a specific version of your image. You can do this by adding new image tags each time you make an update to the image.
Select Add Image version to include an Image tag that points to the latest version of your image on all supported platforms. It must also include a version tag (for example, starting with xx.xx.xx, where xx is a number). Customers should use manifest tags to target multiple platforms. All tags referenced by a manifest tag must also be added so we can upload them. All manifest tags (except the latest tag) must start with either X.Y- or X.Y.Z- where X, Y, and Z are integers. For example, if a latest tag points to 1.0.1-linux-x64
, 1.0.1-linux-arm32
, and 1.0.1-windows-arm32
, these six tags need to be added to this field. For details about tags and versioning, see Prepare your Azure Container technical assets.
Tip
Only the image with the “latest” tag is shown in preview. After the offer is published live, all tags are shown.
- To Co-sell with Microsoft (optional), select it in the left-nav menu. For details, see Co-sell partner engagement.
- To Resell through CSPs (Cloud Solution Partners, also optional), select it in the left-nav menu. For details, see Resell through CSP Partners.
- If you're not setting up either of these or you've finished, it's time to Review and publish your offer.