Skip to content

Commit bd03225

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-mto-provisioning-logs-error-codes
2 parents 486383f + b0ddd40 commit bd03225

File tree

2 files changed

+14
-3
lines changed

2 files changed

+14
-3
lines changed

articles/app-service/manage-disaster-recovery.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,18 +3,22 @@ title: Recover from region-wide failure
33
description: Learn how Azure App Service helps you maintain business continuity and disaster recovery (BCDR) capabilities. Recover your app from a region-wide failure in Azure.
44

55
ms.topic: how-to
6-
ms.date: 06/09/2020
6+
ms.date: 03/31/2023
77
ms.custom: "UpdateFrequency3, subject-moving-resources"
88

99
#Customer intent: As an Azure service administrator, I want to recover my App Service app from a region-wide failure in Azure.
1010
---
11-
1211
# Move an App Service app to another region
1312

13+
> [!IMPORTANT]
14+
> **Beginning 31 March 2025, we'll no longer place Azure App Service web applications in disaster recovery mode in the event of a disaster in an Azure region.** We strongly encourage you to implement [commonly used disaster recovery techniques](./overview-disaster-recovery.md) to prevent loss of functionality or data for your web apps if there's a regional disaster.
15+
1416
This article describes how to bring App Service resources back online in a different Azure region during a disaster that impacts an entire Azure region. When a disaster brings an entire Azure region offline, all App Service apps hosted in that region are placed in disaster recovery mode. Features are available to help you restore the app to a different region or recover files from the impacted app.
1517

1618
App Service resources are region-specific and can't be moved across regions. You must restore the app to a new app in a different region, and then create mirroring configurations or resources for the new app.
1719

20+
21+
1822
## Prerequisites
1923

2024
- None. [Restoring an automatic backup](manage-backup.md#restore-a-backup) usually requires **Standard** or **Premium** tier, but in disaster recovery mode, it's automatically enabled for your impacted app, regardless which tier the impacted app is in.
@@ -85,4 +89,4 @@ If you only want to recover the files from the impacted app without restoring it
8589
![Screenshot of a FileZilla file hierarchy. The wwwroot folder is highlighted, and its shortcut menu is visible. In that menu, Download is highlighted.](media/manage-disaster-recovery/download-content.png)
8690

8791
## Next steps
88-
[Backup and restore](manage-backup.md)
92+
[Backup and restore](manage-backup.md)

articles/container-registry/container-registry-skus.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,13 @@ Azure Container Registry is available in multiple service tiers (also known as S
1919

2020
The Basic, Standard, and Premium tiers all provide the same programmatic capabilities. They also all benefit from [image storage][container-registry-storage] managed entirely by Azure. Choosing a higher-level tier provides more performance and scale. With multiple service tiers, you can get started with Basic, then convert to Standard and Premium as your registry usage increases.
2121

22+
For example :
23+
24+
- If you purchase a Basic tier registry, it includes a storage of 10 GB. The price you pay here is $0.167 per day. Prices are calculated based on US dollars.
25+
- If you have a Basic tier registry and use 25 GB storage, you are paying $0.003/day*15 = $0.045 per day for the additional 15 GB.
26+
- So, the pricing for the Basic ACR with 25 GB storage is $0.167+$0.045= 0.212 USD per day with other related charges like networking, builds, etc, according to the [Pricing - Container Registry.](https://azure.microsoft.com/pricing/details/container-registry/)
27+
28+
2229
## Service tier features and limits
2330

2431
The following table details the features and registry limits of the Basic, Standard, and Premium service tiers.

0 commit comments

Comments
 (0)