Merge pull request #241803 from cynthn/portal-reporting

AnnaMHuff · web-flow · commit 2545f1fcba07 · 2023-08-30T12:49:06.000-06:00
Prepare for GA
diff --git a/articles/virtual-machines/TOC.yml b/articles/virtual-machines/TOC.yml
@@ -485,7 +485,7 @@
         href: share-using-app-registration.md
       - name: Direct share
         href: share-gallery-direct.md
-      - name: Community gallery
+      - name: Community gallery (preview)
         href: share-gallery-community.md
     - name: Images
       items:
diff --git a/articles/virtual-machines/includes/community-gallery-artifacts.md b/articles/virtual-machines/includes/community-gallery-artifacts.md
@@ -6,8 +6,8 @@
  ms.service: virtual-machines
  ms.subservice: gallery
  ms.topic: include
- ms.date: 04/18/2023
+ ms.date: 08/30/2023
  ms.custom: include file
 ---
 
-Artifacts made available in [community galleries](../share-gallery-community.md) aren't verified or tested by Microsoft. You're solely responsible for any artifact you deploy or use. You're responsible for your dealings with the publishers of artifacts.
+[Community images](../share-gallery-community.md) and associated publisher information aren't verified or tested by Microsoft. You're solely responsible for any Community image you deploy or use. You're responsible for your dealings with the publishers of images. For approved operating system base images, see: [approved base images](https://go.microsoft.com/fwlink/?linkid=2245050). For other images created by our verified publishers, see [Azure Marketplace](https://go.microsoft.com/fwlink/?LinkId=2243198).
diff --git a/articles/virtual-machines/share-gallery-community.md b/articles/virtual-machines/share-gallery-community.md
@@ -6,7 +6,7 @@ ms.service: virtual-machines
 ms.subservice: gallery
 ms.topic: how-to
 ms.workload: infrastructure
-ms.date: 05/24/2023
+ms.date: 08/15/2023
 ms.author: saraic
 ms.reviewer: cynthn, mattmcinnes
 ms.custom: template-how-to
@@ -15,21 +15,16 @@ ms.devlang: azurecli
 
 # Share images using a community gallery (preview)
 
-To share a gallery with all Azure users, you can create a [community gallery (preview)](azure-compute-gallery.md#community-gallery). Community galleries can be used by anyone with an Azure subscription. Someone creating a VM can browse images shared with the community using the portal, REST, or the Azure CLI.
+To share a gallery with all Azure users, you can create a [community gallery](azure-compute-gallery.md#community-gallery). Community galleries can be used by anyone with an Azure subscription. Someone creating a VM can browse images shared with the community using the portal, REST, or the Azure CLI.
 
-Sharing images to the community is a new capability in [Azure Compute Gallery](./azure-compute-gallery.md#community). In the preview, you can make your image galleries public, and share them to all Azure customers. When a gallery is marked as a community gallery, all images under the gallery become available to all Azure customers as a new resource type under Microsoft.Compute/communityGalleries. All Azure customers can see the galleries and use them to create VMs. Your original resources of the type `Microsoft.Compute/galleries` are still under your subscription, and private.
+Sharing images to the community is a new capability in [Azure Compute Gallery](./azure-compute-gallery.md#community). You can make your image galleries public, and share them to all Azure customers. When a gallery is marked as a community gallery, all images under the gallery become available to all Azure customers as a new resource type under Microsoft.Compute/communityGalleries. All Azure customers can see the galleries and use them to create VMs. Your original resources of the type `Microsoft.Compute/galleries` are still under your subscription, and private.
 
 
 > [!IMPORTANT]
-> Azure Compute Gallery – community galleries is currently in PREVIEW and subject to the [Preview Terms for Azure Compute Gallery - community gallery](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
->
 > Microsoft does not provide support for images you share to the community.
 > 
-> [!INCLUDE [community-gallery-artifacts](./includes/community-gallery-artifacts.md)]
-> 
-> To publish a community gallery, you'll need to enable the preview feature using the Azure CLI: `az feature register --name CommunityGalleries --namespace Microsoft.Compute` or PowerShell: `Register-AzProviderFeature -FeatureName "CommunityGalleries" -ProviderNamespace "Microsoft.Compute"`. For more information on enabling preview features and checking the status, see [Set up preview features in your Azure subscription](../azure-resource-manager/management/preview-features.md). Creating VMs from community gallery images is open to all Azure users. 
-> 
-> You can't currently create a Flexible virtual machine scale set from an image shared by another tenant.
+
+
 
 
 There are three main ways to share images in an Azure Compute Gallery, depending on who you want to share with:
@@ -40,13 +35,18 @@ There are three main ways to share images in an Azure Compute Gallery, depending
 | RBAC + [Direct shared gallery](./share-gallery-direct.md)  | Yes | Yes | Yes | Yes | No |
 | RBAC + [Community gallery](./share-gallery-community.md) | Yes | Yes | Yes | No | Yes |
 
+## Disclaimer
+
+[!INCLUDE [community-gallery-artifacts](./includes/community-gallery-artifacts.md)]
+
 ## Limitations for images shared to the community
 
 There are some limitations for sharing your gallery to the community:
-- For the preview, image resources need to be created in the same region as the gallery. For example, if you create a gallery in West US, the image definitions and image versions should be created in West US if you want to make them available during the public preview.
-- For the preview, you can't share [VM Applications](vm-applications.md) to the community.
-- The image version region in the gallery should be same as the region home region, creating of cross-region version where the home region is different than the gallery isn't supported, however once the image is in the home region it can be replicated to other regions
-- To find images shared to the community from the Azure portal, you need to go through the VM create or scale set creation pages. You can't search the portal or Azure Marketplace for the images
+- You can't convert an existing private gallery to Community gallery.
+- You can't use a third party image from Marketplace and publish it to the community. For a list of approved operating system base images, please see: [approved base images](https://go.microsoft.com/fwlink/?linkid=2245050).
+- Encrypted images are not supported
+- Image resources need to be created in the same region as the gallery. For example, if you create a gallery in West US, the image definitions and image versions should be created in West US if you want to make them available.
+- You can't share [VM Applications](vm-applications.md) to the community yet.
 
 
 ## How sharing with the community works
@@ -59,7 +59,7 @@ The end-users can only interact with the proxy resources, they never interact wi
 
 Azure users can see the latest image versions shared to the community in the portal, or query for them using the CLI. Only the latest version of an image is listed in the community gallery.
 
-When creating a community gallery, you will need to provide contact information for your images. The objective and underlying intention of this information is to facilitate communication between the consumer of the image and the publisher, like if the consumer needs assistance. Be aware that Microsoft does not offer support for these images. This information will be shown **publicly**, so be careful when providing it:
+When creating a community gallery, you will need to provide contact information for your images. The objective and underlying intention of this information is to facilitate communication between the consumer of the image and the publisher, like if the consumer needs assistance. Microsoft doesn't offer support for these images. This information will be shown **publicly**, so be careful when providing it:
 - Community gallery prefix
 - Publisher support email
 - Publisher URL
@@ -69,8 +69,7 @@ Information from your image definitions will also be publicly available, like wh
 
 > [!WARNING]
 > If you want to stop sharing a gallery publicly, you can update the gallery to stop sharing, but making the gallery private will prevent existing virtual machine scale set users from scaling their resources.
->
-> If you stop sharing your gallery during the preview, you won't be able to re-share it.
+
 
 ## Why share to the community?
 
@@ -93,20 +92,25 @@ Why use a marketplace mage?
 - Microsoft certified images
 - Can be used for production workloads
 - First party and third party images
-- Free and Paid images with additional software offerings
+- Paid images with additional software offerings
 - Supported by Microsoft
 
 When to use a community image?
 - You trust and know how to contact the publisher
 - You're looking for a community version of an image published by open-source community
 - Using the image for testing
-"- Community images are free images. However, if the image used to build the community image was an Azure marketplace image with a cost associated with it, you will be billed for those same costs. You can see what costs are associated with a Marketplace image by looking at the **Plans + Pricing** tab for the image in the Azure portal."
+- Community images are free
 - Supported by the owner of the image, not Microsoft.
 
 ## Reporting issues with a community image
 Using community-submitted virtual machine images has several risks. Images could contain malware, security vulnerabilities, or violate someone's intellectual property. To help create a secure and reliable experience for the community, you can report images when you see these issues.
 
-Use the following links to report issues:
+The easiest way to report issues with a community gallery is to use the portal, which will pre-fill information for the report:
+- For issues with links or other information in the fields of an image definition, select **Report community image**.
+- If an image version contains malicious code or there are other issues with a specific version of an image, select **Report** under the **Report version** column in the table of image versions.
+
+You can also use the following links to report issues, but the forms won't be pre-filled:
+
 - Malicious images: Contact [Abuse Report](https://msrc.microsoft.com/report/abuse).
 - Intellectual Property violations: Contact [Infringement Report](https://msrc.microsoft.com/report/infringement).
  
diff --git a/articles/virtual-machines/shared-image-galleries.md b/articles/virtual-machines/shared-image-galleries.md
@@ -7,7 +7,7 @@ ms.service: virtual-machines
 ms.subservice: gallery
 ms.topic: conceptual
 ms.custom: devx-track-azurepowershell
-ms.date: 05/23/2023
+ms.date: 08/15/2023
 ms.reviewer: cynthn
 #Customer intent: As an IT administrator, I want to learn about how to create shared VM images to minimize the number of post-deployment configuration tasks.
 ---
diff --git a/articles/virtual-machines/vm-generalized-image-version.md b/articles/virtual-machines/vm-generalized-image-version.md
@@ -6,7 +6,7 @@ ms.service: virtual-machines
 ms.subservice: gallery
 ms.topic: how-to
 ms.workload: infrastructure
-ms.date: 03/23/2023
+ms.date: 08/15/2023
 ms.author: saraic
 ms.reviewer: cynthn, mattmcinnes 
 ms.custom: devx-track-azurecli, devx-track-azurepowershell
@@ -570,19 +570,23 @@ New-AzVM -ResourceGroupName $resourceGroup -Location $location -VM $vmConfig
 ```
 
 ---
-## Community gallery
+
+<a name="community-gallery"></a>
+
+## Community gallery (preview)
 
 > [!IMPORTANT]
-> Azure Compute Gallery – community galleries is currently in PREVIEW and subject to the [Preview Terms for Azure Compute Gallery - community gallery](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
->
->To publish a community gallery, you'll need to [set up preview features in your Azure subscription](/azure/azure-resource-manager/management/preview-features?tabs=azure-portal). Creating VMs from community gallery images is open to all Azure users. 
->
 > Microsoft does not provide support for images in the [community gallery](azure-compute-gallery.md#community).
 
 ## Reporting issues with a community image 
 Using community-submitted virtual machine images has several risks. Images could contain malware, security vulnerabilities, or violate someone's intellectual property. To help create a secure and reliable experience for the community, you can report images when you see these issues.
 
-Use the following links to report issues:
+The easiest way to report issues with a community gallery is to use the portal, which will pre-fill information for the report:
+- For issues with links or other information in the fields of an image definition, select **Report community image**.
+- If an image version contains malicious code or there are other issues with a specific version of an image, select **Report** under the **Report version** column in the table of image versions.
+
+You can also use the following links to report issues, but the forms won't be pre-filled:
+
 - Malicious images: Contact [Abuse Report](https://msrc.microsoft.com/report/abuse).
 - Intellectual Property violations: Contact [Infringement Report](https://msrc.microsoft.com/report/infringement).
 
diff --git a/articles/virtual-machines/vm-specialized-image-version.md b/articles/virtual-machines/vm-specialized-image-version.md
@@ -6,7 +6,7 @@ ms.service: virtual-machines
 ms.subservice: gallery
 ms.workload: infrastructure-services
 ms.topic: how-to
-ms.date: 03/23/2023
+ms.date: 08/15/2023
 ms.author: saraic
 ms.reviewer: cynthn, mattmcinnes
 ms.custom: devx-track-azurecli, devx-track-azurepowershell
@@ -390,14 +390,17 @@ New-AzVM `
 ## Community gallery
 
 > [!IMPORTANT]
-> Azure Compute Gallery – community galleries is currently in PREVIEW and subject to the [Preview Terms for Azure Compute Gallery - community gallery](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
->
 > Microsoft does not provide support for images in the [community gallery](azure-compute-gallery.md#community).
 
 ## Reporting issues with a community image 
 Using community-submitted virtual machine images has several risks. Images could contain malware, security vulnerabilities, or violate someone's intellectual property. To help create a secure and reliable experience for the community, you can report images when you see these issues.
 
-Use the following links to report issues:
+The easiest way to report issues with a community gallery is to use the portal, which will pre-fill information for the report:
+- For issues with links or other information in the fields of an image definition, select **Report community image**.
+- If an image version contains malicious code or there are other issues with a specific version of an image, select **Report** under the **Report version** column in the table of image versions.
+
+You can also use the following links to report issues, but the forms won't be pre-filled:
+
 - Malicious images: Contact [Abuse Report](https://msrc.microsoft.com/report/abuse).
 - Intellectual Property violations: Contact [Infringement Report](https://msrc.microsoft.com/report/infringement).
 
@@ -452,7 +455,7 @@ To create the VM from community gallery image, you must accept the license agree
 1. For **Security type**, make sure *Standard* is selected.
 1. For your **Image**, select **See all images**. The **Select an image** page will open.
    :::image type="content" source="media/shared-image-galleries/see-all-images.png" alt-text="Screenshot showing the link to select to see more image options.":::
-1. In the left menu, under **Other Items**, select **Community images (PREVIEW)**. The **Other Items | Community Images (PREVIEW)** page will open.
+1. In the left menu, under **Other Items**, select **Community images**. The **Other Items | Community Images** page will open.
    :::image type="content" source="media/shared-image-galleries/community.png" alt-text="Screenshot showing where to select community gallery images.":::
 1. Select an image from the list. Make sure that the **OS state** is *Specialized*. If you want to use a specialized image, see [Create a VM using a generalized image version](vm-generalized-image-version.md). Depending on the image choose, the **Region** the VM will be created in will change to match the image.
 1. Complete the rest of the options and then select the **Review + create** button at the bottom of the page.
