Merge pull request #236515 from cynthn/patch-82

Update share-gallery-community.md

Author: v-dirichards

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: 03/30/2023
+ms.date: 05/24/2023
 ms.author: saraic
 ms.reviewer: cynthn, mattmcinnes
 ms.custom: template-how-to
@@ -43,23 +43,19 @@ There are three main ways to share images in an Azure Compute Gallery, depending
 ## Limitations for images shared to the community
 
 There are some limitations for sharing your gallery to the community:
-- Encrypted images aren't supported.
-- TrustedLaunch and TVMSupported Image is not supported
-- CVMSuppored image is not supported
 - 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 gallery must be created as a community gallery. For the preview, there is no way to migrate an existing private gallery to be a community gallery
-- 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 is not supported, however once the image is in the home region it can be replicated to other regions
+- 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
 
 
 ## How sharing with the community works
 
 You [create a gallery resource](create-gallery.md#create-a-community-gallery) under `Microsoft.Compute/Galleries` and choose `community` as a sharing option.
 
-When you are ready, you flag your gallery as ready to be shared publicly. Only the  owner of a subscription, or a user or service principal with the `Compute Gallery Sharing Admin` role at the subscription or gallery level, can enable a gallery to go public to the community. At this point, the Azure infrastructure creates proxy read-only regional resources, under `Microsoft.Compute/CommunityGalleries`, which are public.
+When you're ready, you flag your gallery as ready to be shared publicly. Only the  owner of a subscription, or a user or service principal with the `Compute Gallery Sharing Admin` role at the subscription or gallery level, can enable a gallery to go public to the community. At this point, the Azure infrastructure creates proxy read-only regional resources, under `Microsoft.Compute/CommunityGalleries`, which are public.
 
-The end-users can only interact with the proxy resources, they never interact with your private resources. As the publisher of the private resource, you should consider the private resource as your handle to the public proxy resources. The `prefix` you provide when you create the gallery will be used, along with a unique GUID, to create the public facing name for your gallery.
+The end-users can only interact with the proxy resources, they never interact with your private resources. As the publisher of the private resource, you should consider the private resource as your handle to the public proxy resources. The `prefix` you provide when you create the gallery is used, along with a unique GUID, to create the public facing name for your gallery.
 
 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.
 
@@ -88,17 +84,35 @@ As a content publisher, you might want to share a gallery to the community:
 
 - You don’t want to deal with the complexity of multi-tenant authentication when sharing with multiple tenants on Azure.
 
-## Reporting issues with a public image 
-Utilizing community-submitted virtual machine images has several risks. Certain images could harbor malware, security vulnerabilities, or violate someone's intellectual property. To help create a secure and reliable experience for the community, you can report images in which you see these issues.
 
-### Reporting images externally:
-- Malicious images: Contact [Abuse Report](https://msrc.microsoft.com/report/abuse).
+## Should I use a marketplace image or a community gallery image?
+
+There are a variety of reasons why you might want to use an Azure Marketplace image instead of a community gallery image. The primary reason to choose an Azure Marketplace image is that they're supported by Microsoft, while community images aren't. 
+
+Why use a marketplace mage?
+- Microsoft certified images
+- Can be used for production workloads
+- First party and third party images
+- 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
+- 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:
+- Malicious images: Contact [Abuse Report](https://msrc.microsoft.com/report/abuse).
 - Intellectual Property violations: Contact [Infringement Report](https://msrc.microsoft.com/report/infringement).
 
 ## Best practices
 
-- Images published to the community gallery should be [generalized](generalize.md) images, that have had sensitive or machine specific information removed. For more information about preparing an image, see the OS specific information for [Linux](./linux/create-upload-generic.md) or [Windows](./windows/prepare-for-upload-vhd-image.md).
+- Images published to the community gallery should be [generalized](generalize.md) images that have had sensitive or machine specific information removed. For more information about preparing an image, see the OS specific information for [Linux](./linux/create-upload-generic.md) or [Windows](./windows/prepare-for-upload-vhd-image.md).
 ## FAQ
 
 **Q: What are the charges for using a gallery that is shared to the community?**
@@ -109,15 +123,15 @@ Utilizing community-submitted virtual machine images has several risks. Certain
 
 **Q: Is it safe to use images shared to the community?**
 
-**A**: Users should exercise caution while using images from non-verified sources, since these images aren't subject to certification and not scanned for malware/vulnerabilities and publisher details are not verified.
+**A**: Users should exercise caution while using images from non-verified sources, since these images aren't subject to certification and not scanned for malware/vulnerabilities and publisher details aren't verified.
 
 **Q: If an image that is shared to the community doesn’t work, who do I contact for support?**
 
-**A**: Azure isn't responsible for any issues users might encounter with community-shared images. The support is provided by the image publisher. Please look up the publisher contact information for the image and reach out to them for any support.  
+**A**: Azure isn't responsible for any issues users might encounter with community-shared images. The support is provided by the image publisher. Look up the publisher contact information for the image and reach out to them for any support.  
 
 **Q: Is Community gallery sharing functionality part of Azure Marketplace?**
 
-**A**: No, Community gallery sharing is not part of Azure Marketplace, it's a feature of 'Azure Compute Gallery'. Anyone with an Azure subscription can use 'Community gallery' and make their images public.
+**A**: No, Community gallery sharing isn't part of Azure Marketplace, it's a feature of 'Azure Compute Gallery'. Anyone with an Azure subscription can use 'Community gallery' and make their images public.
 
 **Q: I have concerns about an image, who do I contact?**
 
@@ -138,7 +152,7 @@ In order to share a gallery publicly, it needs to be created as a community gall
 
 ### [CLI](#tab/cli)
 
-Once you are ready to make the gallery available to the public, enable the community gallery using [az sig share enable-community](/cli/azure/sig/share#az-sig-share-enable-community). Only a user in the `Owner` role definition can enable a gallery for community sharing.
+Once you're ready to make the gallery available to the public, enable the community gallery using [az sig share enable-community](/cli/azure/sig/share#az-sig-share-enable-community). Only a user in the `Owner` role definition can enable a gallery for community sharing.
 
 ```azurecli-interactive
 az sig share enable-community \
@@ -171,7 +185,7 @@ When you're ready to make the gallery public:
 1. On the page for the gallery, select **Sharing** from the left menu.
 1. Select **Share** from the top of the page.
    :::image type="content" source="media/create-gallery/share.png" alt-text="Screenshot showing the Share button for sharing your gallery to the community.":::
-1. When you are done, select **Save**.
+1. When you're done, select **Save**.
 
 
 ---