Merge pull request #114807 from xyh1/patch-113

new regions and capabilities

Author: PRMerger12

articles/storage/blobs/storage-blob-change-feed.md

@@ -31,6 +31,8 @@ Change feed support is well-suited for scenarios that process data based on obje
   - Build solutions to backup, mirror, or replicate object state in your account for disaster management or compliance.
 
   - Build connected application pipelines that react to change events or schedule executions based on created or changed object.
+  
+Change feed is a prerequisite feature for [Point-in-time restore for block blobs](point-in-time-restore-overview.md).
 
 > [!NOTE]
 > Change feed provides a durable, ordered log model of the changes that occur to a blob. Changes are written and made available in your change feed log  within an order of a few minutes of the change. If your application has to react to events much quicker than this, consider using [Blob Storage events](storage-blob-event-overview.md) instead. [Blob Storage Events](storage-blob-event-overview.md) provides real-time one-time events which enable your Azure Functions or applications to quickly react to changes that occur to a blob. 
@@ -50,7 +52,7 @@ Here's a few things to keep in mind when you enable the change feed.
 - Only GPv2 and Blob storage accounts can enable Change feed. Premium BlockBlobStorage accounts, and hierarchical namespace enabled accounts are not currently supported. GPv1 storage accounts are not supported but can be upgraded to GPv2 with no downtime, see [Upgrade to a GPv2 storage account](../common/storage-account-upgrade.md) for more information.
 
 > [!IMPORTANT]
-> The change feed is in public preview, and is available in the **westcentralus** and **westus2** regions. See the [conditions](#conditions) section of this article. To enroll in the preview, see the [Register your subscription](#register) section of this article. You must register your subscription before you can enable change feed on your storage accounts.
+> The change feed is in public preview, and is available in the **West Central US**, **West US 2**, **France Central**, **France South**, **Canada Central**, and **Canada East** regions. See the [conditions](#conditions) section of this article. To enroll in the preview, see the [Register your subscription](#register) section of this article. You must register your subscription before you can enable change feed on your storage accounts.
 
 ### [Portal](#tab/azure-portal)
 
@@ -204,6 +206,12 @@ The change feed files contain a series of change event records. Each change even
 
 Change feed files are stored in the `$blobchangefeed/log/` virtual directory as [append blobs](https://docs.microsoft.com/rest/api/storageservices/understanding-block-blobs--append-blobs--and-page-blobs#about-append-blobs). The first change feed file under each path will have `00000` in the file name (For example `00000.avro`). The name of each subsequent log file added to that path will increment by 1 (For example: `00001.avro`).
 
+The following event types are captured in the Change feed records:
+- BlobCreated
+- BlobDeleted
+- BlobPropertiesUpdated
+- BlobSnapshotCreated
+
 Here's an example of change event record from change feed file converted to Json.
 
 ```json
@@ -233,7 +241,7 @@ Here's an example of change event record from change feed file converted to Json
 }
 ```
 
-For a description of each property, see [Azure Event Grid event schema for Blob Storage](https://docs.microsoft.com/azure/event-grid/event-schema-blob-storage?toc=%2fazure%2fstorage%2fblobs%2ftoc.json#event-properties).
+For a description of each property, see [Azure Event Grid event schema for Blob Storage](https://docs.microsoft.com/azure/event-grid/event-schema-blob-storage?toc=%2fazure%2fstorage%2fblobs%2ftoc.json#event-properties). The BlobPropertiesUpdated and BlobSnapshotCreated events are currently exclusive to Change feed and not yet supported for Blob Storage Events.
 
 > [!NOTE]
 > The change feed files for a segment don't immediately appear after a segment is created. The length of delay is within the normal interval of publishing latency of the change feed which is within a few minutes of the change.
@@ -305,13 +313,13 @@ az provider register --namespace 'Microsoft.Storage'
 ## Conditions and known issues (Preview)
 
 This section describes known issues and conditions in the current public preview of the change feed. 
-- For preview, you must first [register your subscription](#register) before you can enable change feed for your storage account in the westcentralus or westus2 regions. 
-- The change feed captures only create, update, delete, and copy operations. Metadata updates are not currently captured in preview.
+- For preview, you must first [register your subscription](#register) before you can enable change feed for your storage account in the West Central US, West US 2, France Central, France South, Canada Central, and Canada East regions. 
+- The change feed captures only create, update, delete, and copy operations. Blob property and metadata changes are also captured. However the access tier property is not currently captured. 
 - Change event records for any single change might appear more than once in your change feed.
-- You can't yet manage the lifetime of change feed log files by setting time-based retention policy on them and you cannot delete the blobs 
+- You can't yet manage the lifetime of change feed log files by setting time-based retention policy on them and you cannot delete the blobs.
 - The `url` property of the log file is currently always empty.
 - The `LastConsumable` property of the segments.json file does not list the very first segment that the change feed finalizes. This issue occurs only after the first segment is finalized. All subsequent segments after the first hour are accurately captured in the `LastConsumable` property.
-- You currently cannot see the **$blobchangefeed** container when you call ListContainers API and the container does not show up on Azure portal or Storage Explorer
+- You currently cannot see the **$blobchangefeed** container when you call ListContainers API and the container does not show up on Azure portal or Storage Explorer. You can view the contents by calling the ListBlobs API on the $blobchangefeed container directly.
 - Storage accounts that have previously initiated an [account failover](../common/storage-disaster-recovery-guidance.md) may have issues with the log file not appearing. Any future account failovers may also impact the log file during preview.
 
 ## FAQ