You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/governance/access-reviews-downloadable-review-history.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Create and manage downloadable access review history report (Preview) - Azure Active Directory
2
+
title: Create and manage downloadable access review history report - Azure Active Directory
3
3
description: Using Azure Active Directory access reviews, you can download a review history for access reviews in your organization.
4
4
services: active-directory
5
5
documentationcenter: ''
@@ -10,11 +10,11 @@ ms.workload: identity
10
10
ms.tgt_pltfrm: na
11
11
ms.topic: conceptual
12
12
ms.subservice: compliance
13
-
ms.date: 03/25/2021
13
+
ms.date: 02/18/2022
14
14
ms.author: ajburnle
15
15
---
16
16
17
-
# Create and manage downloadable access review history report (Preview) in Azure AD access reviews
17
+
# Create and manage downloadable access review history report in Azure AD access reviews
18
18
19
19
With Azure Active Directory (Azure AD) Access Reviews, you can create a downloadable review history to help your organization gain more insight. The report pulls the decisions that were taken by reviewers when a report is created. These reports can be constructed to include specific access reviews, for a specific time frame, and can be filtered to include different review types and review results.
# Deploy a Java application with Azure Database for PostgreSQL server to Open Liberty or WebSphere Liberty on an Azure Kubernetes Service (AKS) cluster
Copy file name to clipboardExpand all lines: articles/app-service/app-service-web-restore-snapshots.md
+85-31Lines changed: 85 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,60 +4,114 @@ description: Learn how to restore your app from a snapshot. Recover from unexpec
4
4
5
5
ms.assetid: 4164f9b5-f735-41c6-a2bb-71f15cdda417
6
6
ms.topic: article
7
-
ms.date: 09/02/2021
7
+
ms.date: 02/17/2022
8
8
ms.reviewer: nicking
9
9
ms.custom: seodec18
10
10
11
11
---
12
12
# Restore an app in Azure from a snapshot
13
-
This article shows you how to restore an app in [Azure App Service](../app-service/overview.md) from a snapshot. You can restore your app to a previous state, based on one of your app's snapshots. You do not need to enable snapshots, the platform automatically saves a snapshot of all apps for data recovery purposes.
13
+
This article shows you how to restore an app in [Azure App Service](../app-service/overview.md) from a snapshot. You can restore your app to a previous state, based on one of your app's snapshots. You do not need to enable snapshot backups; the platform automatically saves a hourly snapshot of each app's content and configuration for data recovery purposes. Hourly snapshots for the last 30 days are available. The retention period and snapshot frequency are not configurable.
14
14
15
-
Snapshots are incremental shadow copies of your App Service app. When your app is in Premium tier or higher, App Service takes periodic snapshots of both the app's content and its configuration. They offer several advantages over [standard backups](manage-backup.md):
15
+
Restoring from snapshots is available to apps running in one of the **Standard** or **Premium** tiers. For information about scaling up your app, see [Scale up an app in Azure](manage-scale-up.md).
16
+
17
+
> [!NOTE]
18
+
> Snapshot restore is not available for:
19
+
>
20
+
> - App Service environments (**Isolated** tier)
21
+
> - Azure Functions in the [**Consumption**](../azure-functions/consumption-plan.md) or [**Elastic Premium**](../azure-functions/functions-premium-plan.md) pricing plans.
22
+
>
23
+
> Snapshot restore is available in preview for Azure Functions in [dedicated (App Service)](../azure-functions/dedicated-plan.md)**Standard** or **Premium** tiers.
24
+
25
+
## Snapshots vs Backups
26
+
27
+
Snapshots are incremental shadow copies and offer several advantages over [standard backups](manage-backup.md):
16
28
17
29
- No file copy errors due to file locks.
18
-
- Higher maximum snapshot size (30GB).
19
-
- No configuration required for supported pricing tiers.
20
-
- Snapshots can be restored to a new App Service app in any Azure region.
30
+
- Higher snapshot size (maximum 30 GB).
31
+
- Enabled by default in supported pricing tiers and no configuration required.
32
+
- Restore to a new or existing App Service app or slot in any Azure region.
33
+
34
+
## What snapshot restore includes
35
+
36
+
The following table shows which content is restored when you restore a snapshot:
37
+
38
+
|Settings| Restored?|
39
+
|-|-|
40
+
|**Windows apps**: All app content under `%HOME%` directory<br/>**Linux apps**: All app content under `/home` directory<br/>**Custom containers (Windows and Linux)**: Content in [persistent storage](configure-custom-container.md?pivots=container-linux#use-persistent-shared-storage)| Yes |
41
+
| Content of the [run-from-ZIP package](deploy-run-package.md)| No |
42
+
| Content from any [custom mounted Azure storage](configure-connect-to-azure-storage.md?pivots=container-windows)| No |
21
43
22
-
Restoring from snapshots is available to apps running in **Premium** tier or higher. For information about scaling
23
-
up your app, see [Scale up an app in Azure](manage-scale-up.md).
44
+
> [!NOTE]
45
+
> Maximum supported size for snapshot restore is 30GB. Snapshot restore fails if your storage size is greater than 30GB. To reduce your storage size, consider moving files like logs, images, audios, and videos to [Azure Storage](../storage/index.yml), for example.
24
46
25
-
## Limitations
47
+
The following table shows which app configuration is restored:
26
48
27
-
- Maximum supported size for snapshot restore is 30GB. Snapshot restore fails if your storage size is greater than 30GB. To reduce your storage size, consider moving files like logs, images, audios, and videos to [Azure Storage](../storage/index.yml), for example.
28
-
- Any connected database that [standard backup](manage-backup.md#what-gets-backed-up) supports or [mounted Azure storage](configure-connect-to-azure-storage.md?pivots=container-windows) is *not* included in the snapshot. Consider using the native backup capabilities of the connected Azure service (for example, [SQL Database](../azure-sql/database/automated-backups-overview.md) and [Azure Files](../storage/files/storage-snapshots-files.md)).
29
-
- App Service stops the target app or target slot while restoring a snapshot. To minimize downtime for the production app, restore the snapshot to a [staging slot](deploy-staging-slots.md) first, then swap into production.
30
-
- Snapshots for the last 30 days are available. The retention period and snapshot frequency are not configurable.
31
-
- App Services running on an App Service environment do not support snapshots.
49
+
|Settings| Restored?|
50
+
|-|-|
51
+
|[Native log settings](troubleshoot-diagnostic-logs.md), including the Azure Storage account and container settings | Yes |
| Network features, such as [private endpoints](networking/private-endpoint.md), [hybrid connections](app-service-hybrid-connections.md), and [virtual network integration](overview-vnet-integration.md)| No|
|[Managed identities](overview-managed-identity.md)| No |
57
+
|[Custom domains](app-service-web-tutorial-custom-domain.md)| No |
58
+
|[TLS/SSL](configure-ssl-bindings.md)| No |
59
+
|[Scale out](../azure-monitor/autoscale/autoscale-get-started.md?toc=/azure/app-service/toc.json)| No |
60
+
|[Diagnostics with Azure Monitor](troubleshoot-diagnostic-logs.md#send-logs-to-azure-monitor)| No |
61
+
|[Alerts and Metrics](../azure-monitor/alerts/alerts-classic-portal.md)| No |
62
+
|[Backup](manage-backup.md)| No |
63
+
|Associated [deployment slots](deploy-staging-slots.md)| No |
64
+
|Any connected database that [standard backup](manage-backup.md#what-gets-backed-up) supports| No |
32
65
33
-
## Restore an app from a snapshot
66
+
## Restore from a snapshot
34
67
35
-
1. On the **Settings** page of your app in the [Azure portal](https://portal.azure.com), click **Backups** to display the **Backups** page. Then click **Restore** under the **Snapshot(Preview)** section.
68
+
> [!NOTE]
69
+
> App Service stops the target app or target slot while restoring a snapshot. To minimize downtime for the production app, restore the snapshot to a [deployment slot](deploy-staging-slots.md) first, then [swap](deploy-staging-slots.md#swap-two-slots) into production.
70
+
71
+
# [Azure portal](#tab/portal)
72
+
73
+
1. On the **Settings** page of your app in the [Azure portal](https://portal.azure.com), click **Backups** to display the **Backups** page. Then click **Restore** under the **Snapshot** section.
36
74
37
-
75
+
:::image type="content" source="./media/app-service-web-restore-snapshots/1.png" alt-text="Screenshot that shows how to restore an app from a snapshot.":::
38
76
39
77
2. In the **Restore** page, select the snapshot to restore.
40
78
41
-
79
+
<!-- -->
42
80
43
-
3. Specify the destination for the app restore in **Restore destination**.
81
+
3. Specify the destination for the app restore in **Restore destination**. To restore to a [deployment slot](deploy-staging-slots.md), select **Existing app**.
44
82
45
-
83
+
<!-- -->
46
84
47
-
> [!WARNING]
48
-
> As a best practice we recommend restoring to a new slot then performing a swap. If you choose **Overwrite**, all existing data in your app's current file system is erased and overwritten. Before you click **OK**, make sure that it is what you want to do.
49
-
>
85
+
> [!NOTE]
86
+
> It's recommended that you restore to a deployment slot and then perform a swap into production. If you choose **Overwrite**, all existing data in your app's current file system is erased and overwritten. Before you click **OK**, make sure that it is what you want to do.
50
87
>
51
88
52
-
> [!Note]
53
-
> Due to current technical limitations, you can only restore to apps in the same scale unit. This limitation will be removed in a future release.
54
-
>
55
-
>
56
-
57
-
You can select **Existing App** to restore to a slot. Before you use this option, you should have already created a slot in your app.
58
-
59
89
4. You can choose to restore your site configuration.
60
90
61
-
91
+
:::image type="content" source="./media/app-service-web-restore-snapshots/4.png" alt-text="Screenshot that shows how to restore site configuration.":::
62
92
63
93
5. Click **OK**.
94
+
95
+
# [Azure CLI](#tab/cli)
96
+
97
+
1. List the restorable snapshots for your app and copy the timestamp of the one you want to restore.
98
+
99
+
```azurecli-interactive
100
+
az webapp config snapshot list --name <app-name> --resource-group <group-name>
101
+
```
102
+
103
+
2. To restore the snapshot by overwriting the app's content and configuration:
To restore app content only and not the app configuration, use the `--restore-content-only` parameter. For more information, see [az webapp config snapshot restore](/cli/webapp/config/snapshot#az_webapp_config_snapshot_restore).
# Customer intent: As a data professional, I want to understand why my solutions would benefit from running with Azure Arc-enabled data services so that I can leverage the capability of the feature.
Copy file name to clipboardExpand all lines: articles/azure-monitor/containers/container-insights-enable-existing-clusters.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Monitor an Azure Kubernetes Service (AKS) cluster deployed | Microsoft Do
3
3
description: Learn how to enable monitoring of an Azure Kubernetes Service (AKS) cluster with Container insights already deployed in your subscription.
0 commit comments