Skip to content

Commit f4459a1

Browse files
authored
Merge pull request #192182 from Jak-MS/public-move-89696
Public move 89696
2 parents f0117c4 + 64cfa76 commit f4459a1

File tree

1 file changed

+17
-21
lines changed
  • articles/azure-app-configuration

1 file changed

+17
-21
lines changed

articles/azure-app-configuration/faq.yml

Lines changed: 17 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -105,22 +105,17 @@ sections:
105105
- question: How does App Configuration ensure high data availability?
106106
answer: |
107107
Azure App Configuration supports Azure Availability Zones to protect your application and data from single datacenter failures. All Availability Zone enabled regions consist of a minimum of 3 availability zones, where each is a physically independent datacenter. For resiliency, this support in App Configuration is enabled for all customers at no extra cost. Following are regions that App Configuration has enabled Availability Zone support. For more information, see [Regions and Availability Zones in Azure.](../availability-zones/az-overview.md)
108-
- Central US
109-
- South Central US
110-
- East US
111-
- East US 2
112-
- West US 2
113-
- West US 3
114-
- Canada Central
115-
- Brazil South
116-
- France Central
117-
- Germany West Central
118-
- North Europe
119-
- UK South
120-
- West Europe
121-
- Southeast Asia
122-
- Japan East
123-
- Korea Central
108+
109+
| Americas | Europe | Africa | Asia Pacific |
110+
|--------------------|----------------------|---------------------|----------------|
111+
| Brazil South | France Central | | Australia East |
112+
| Canada Central | Germany West Central | | Southeast Asia |
113+
| Central US | North Europe | | Japan East |
114+
| East US | Sweden Central | | Korea Central |
115+
| East US 2 | UK South | | |
116+
| South Central US | West Europe | | |
117+
| West US 2 | | | |
118+
| West US 3 | | | |
124119
125120
- question: Are there any limits on the number of requests made to App Configuration?
126121
answer: |
@@ -146,15 +141,16 @@ sections:
146141
147142
- question: Why can't I create an App Configuration store with the same name as one that I just deleted?
148143
answer: |
149-
When a standard tier App Configuration store is deleted the name is reserved for seven days after deletion. It is possible to recreate a store with the same name before the reservation period has elapsed but it must be in the same subscription, resource group, and region as the original store. If the resource group that contained the store was deleted it will need to be recreated in the same subscription first before recreating the store inside of it.
150-
151-
The App Configuration store cannot be created in a different subscription/resource group until the retention period has elapsed. However, the resource can be recreated in the original subscription/resource group and then moved to a new subscription/resource group by following [these instructions](../azure-resource-manager/management/move-resource-group-and-subscription.md#use-the-portal).
144+
All App Configuration stores in the standard tier have automatically enabled the [soft-delete](concept-soft-delete.md) feature. When a standard tier App Configuration store is deleted, its name is reserved for the retention period. To recreate a store with the same name before the retention period expires, you need to [purge the soft-deleted store](howto-recover-deleted-stores-in-azure-app-configuration.md#list-recover-or-purge-a-soft-deleted-app-configuration-store) first, provided the store doesn't have purge protection enabled. If the purge protection is enabled, you must wait for the retention period to elapse.
152145
153-
Recreating an App Configuration store during the retention period is currently only supported by the Azure CLI using the `az appconfig create` [command](/cli/azure/appconfig#az_appconfig_create).
146+
App Configuration previously offered an option to overwrite a soft-deleted store as instructed below. This option will be retired on April 30, 2022. Migrate to use the purge function or set a shorter retention period if you often need to recreate a store with the same name.
147+
* It is possible to recreate a store with the same name before the retention period has elapsed, but it must be in the same subscription, resource group, and region as the original store. If the resource group that contained the store was deleted it will need to be recreated in the same subscription first before recreating the store inside of it.
148+
* The App Configuration store cannot be created in a different subscription/resource group until the retention period has elapsed. However, the resource can be recreated in the original subscription/resource group and then moved to a new subscription/resource group by following [these instructions](../azure-resource-manager/management/move-resource-group-and-subscription.md#use-the-portal).
149+
* Recreating an App Configuration store during the retention period is currently only supported by the Azure CLI using the `az appconfig create` [command](/cli/azure/appconfig#az_appconfig_create).
154150
155151
- question: How can I restore an App Configuration store that I deleted mistakenly?
156152
answer: |
157-
Standard tier App Configuration stores can be recovered within seven days of being deleted. To recover a mistakenly deleted App Configuration store contact Microsoft Support.
153+
All App Configuration stores in the standard tier support the [soft-delete](concept-soft-delete.md) feature, which cannot be disabled. You can recover a deleted store within its retention period. Follow these [instructions](howto-recover-deleted-stores-in-azure-app-configuration.md) to recover a mistakenly deleted App Configuration store.
158154
159155
- question: How can I receive announcements on new releases and other information related to App Configuration?
160156
answer: |

0 commit comments

Comments
 (0)