Merge pull request #216335 from jimmart-dev/jammart-redundancy-limitations-2

failover feature conflicts - 2nd set

Author: prmerger-automator[bot]

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

@@ -5,12 +5,12 @@ description: Learn about change feed logs in Azure Blob Storage and how to use t
 author: normesta
 
 ms.author: normesta
-ms.date: 06/15/2022
+ms.date: 10/28/2022
 ms.topic: how-to
 ms.service: storage
 ms.subservice: blobs
 ms.reviewer: sadodd 
-ms.custom: devx-track-azurepowershell
+ms.custom: devx-track-azurepowershell, engagement-fy23
 ---
 
 # Change feed support in Azure Blob Storage
@@ -544,6 +544,7 @@ This section describes known issues and conditions in the current release of the
 - 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 the ListContainers API. You can view the contents by calling the ListBlobs API on the $blobchangefeed container directly.
+- [Storage account failover](../common/storage-disaster-recovery-guidance.md) is not supported on accounts with the change feed enabled. Disable the change feed before initiating a failover.
 - 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.
 
 ## Feature support

articles/storage/common/redundancy-migration.md

@@ -7,10 +7,10 @@ author: jimmart-dev
 
 ms.service: storage
 ms.topic: how-to
-ms.date: 09/21/2022
+ms.date: 10/28/2022
 ms.author: jammart
 ms.subservice: common 
-ms.custom: devx-track-azurepowershell
+ms.custom: devx-track-azurepowershell, engagement-fy23
 ---
 
 # Change how a storage account is replicated
@@ -210,12 +210,29 @@ For more detailed guidance on how to perform a manual migration, see [Move an Az
 
 Limitations apply to some replication change scenarios depending on:
 
-- [Storage account type](#storage-account-type)
 - [Region](#region)
+- [Feature conflicts](#feature-conflicts)
+- [Storage account type](#storage-account-type)
 - [Access tier](#access-tier)
 - [Protocol support](#protocol-support)
 - [Failover and failback](#failover-and-failback)
 
+### Region
+
+Make sure the region where your storage account is located supports all of the desired replication settings. For example, if you are converting your account to zone-redundant (ZRS, GZRS, or RA-GZRS), make sure your storage account is in a region that supports it. See the lists of supported regions for [Zone-redundant storage](storage-redundancy.md#zone-redundant-storage) and [Geo-zone-redundant storage](storage-redundancy.md#geo-zone-redundant-storage).
+
+The [customer-initiated conversion (preview)](#customer-initiated-conversion-preview) to ZRS is available in all public ZRS regions except for the following:
+
+- (Europe) West Europe
+- (Europe) UK South
+- (North America) Canada Central
+- (North America) East US
+- (North America) East US 2
+
+### Feature conflicts
+
+Some storage account features are not compatible with other features or operations. For example, the ability to failover to the secondary region is the key feature of geo-redundancy, but other features are not compatible with failover. For more information about features and services not supported with failover, see [Unsupported features and services](storage-disaster-recovery-guidance.md#unsupported-features-and-services). Converting an account to GRS, GZRS, or RA-GZRS might be blocked if a conflicting feature is enabled, or it might be necessary to disable the feature later before initiating a failover.
+
 ### Storage account type
 
 When planning to change your replication settings, consider the following limitations related to the storage account type.
@@ -281,18 +298,6 @@ az storage account update -g <resource_group> -n <storage_account> --set kind=St
 
 To manually migrate your ZRS Classic account data to another type of replication, follow the steps to [perform a manual migration](#manual-migration).
 
-### Region
-
-Make sure the region where your storage account is located supports all of the desired replication settings. For example, if you are converting your account to zone-redundant (ZRS, GZRS, or RA-GZRS), make sure your storage account is in a region that supports it. See the lists of supported regions for [Zone-redundant storage](storage-redundancy.md#zone-redundant-storage) and [Geo-zone-redundant storage](storage-redundancy.md#geo-zone-redundant-storage).
-
-The [customer-initiated conversion (preview)](#customer-initiated-conversion-preview) to ZRS is available in all public ZRS regions except for the following:
-
-- (Europe) West Europe
-- (Europe) UK South
-- (North America) Canada Central
-- (North America) East US
-- (North America) East US 2
-
 If you want to migrate your data into a zone-redundant storage account located in a region different from the source account, you must perform a manual migration. For more details, see [Move an Azure Storage account to another region](storage-account-move.md).
 
 ### Access tier

articles/storage/common/storage-disaster-recovery-guidance.md

@@ -10,6 +10,7 @@ ms.topic: conceptual
 ms.date: 10/28/2022
 ms.author: jammart
 ms.subservice: common
+ms.custom: engagement-fy23
 ---
 
 # Disaster recovery and storage account failover
@@ -161,7 +162,7 @@ Keep in mind that any data stored in a temporary disk is lost when the VM is shu
 
 The following features and services are not supported for account failover:
 
-- Storage accounts that have [change feed](../blobs/storage-blob-change-feed.md) enabled are not supported for failover. Since [operational backup of Azure Blob Storage enables the change feed feature](../../backup/blob-backup-support-matrix.md#limitations), storage accounts that have operational backup of blobs configured do not support failover.
+- Storage accounts that have [change feed](../blobs/storage-blob-change-feed.md) enabled are not supported for failover. For example, [operational backup of Azure Blob Storage](../../backup/blob-backup-support-matrix.md#limitations) requires the change feed. For this reason, storage accounts that have operational backup configured do not support failover. You must disable operational backup and any other features that require the change feed before initiating a failover.
 - Azure File Sync does not support storage account failover. Storage accounts containing Azure file shares being used as cloud endpoints in Azure File Sync should not be failed over. Doing so will cause sync to stop working and may also cause unexpected data loss in the case of newly tiered files.
 - Storage accounts that have hierarchical namespace enabled (such as for Data Lake Storage Gen2) are not supported at this time.
 - A storage account containing premium block blobs cannot be failed over. Storage accounts that support premium block blobs do not currently support geo-redundancy.