Skip to content

Commit d1b35ca

Browse files
Merge pull request #276569 from AbhishekMallick-MS/May-29-2024-Freshness
Freshness - Updated vault properties via REST
2 parents 0f34392 + a07bb95 commit d1b35ca

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

articles/backup/use-restapi-update-vault-properties.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,12 @@
11
---
22
title: Update Recovery Services vault configuration with REST API
33
description: In this article, learn how to update vault's configuration using REST API.
4-
ms.topic: conceptual
5-
ms.date: 12/06/2019
4+
ms.topic: how-to
5+
ms.date: 11/02/2023
66
ms.assetid: 9aafa5a0-1e57-4644-bf79-97124db27aa2
77
author: AbhishekMallick-MS
88
ms.author: v-abhmallick
9+
ms.custom: engagement-fy24
910
---
1011
# Update Azure Recovery Services vault configurations using REST API
1112

@@ -17,11 +18,11 @@ Deleting backups of a protected item is a significant operation that has to be m
1718

1819
But there are scenarios in which this capability isn't required. An Azure Recovery Services vault can't be deleted if there are backup items within it, even soft-deleted ones. This may pose a problem if the vault needs to be immediately deleted. For example: deployment operations often clean up the created resources in the same workflow. A deployment can create a vault, configure backups for an item, do a test restore and then proceed to delete the backup items and the vault. If the vault deletion fails, the entire deployment might fail. Disabling soft-delete is the only way to guarantee immediate deletion.
1920

20-
So you need to carefully choose whether or not to disable soft-delete for a particular vault depending on the scenario. For more information, see the [soft-delete article](backup-azure-security-feature-cloud.md).
21+
So you need to carefully choose to disable the soft delete feature for a particular vault depending on the scenario. Learn more about [soft delete](backup-azure-security-feature-cloud.md).
2122

2223
### Fetch soft delete state using REST API
2324

24-
By default, the soft-delete state will be enabled for any newly created Recovery Services vault. To fetch/update the state of soft-delete for a vault, use the backup vault's config related [REST API document](/rest/api/backup/backup-resource-vault-configs)
25+
By default, the soft delete state will be enabled for any newly created Recovery Services vault. To fetch/update the state of soft-delete for a vault, use the backup vault's config related [REST API document](/rest/api/backup/backup-resource-vault-configs)
2526

2627
To fetch the current state of soft-delete for a vault, use the following *GET* operation
2728

@@ -61,7 +62,7 @@ Once the 'GET' request is submitted, a 200 (successful) response is returned.
6162

6263
### Update soft delete state using REST API
6364

64-
To update the soft-delete state of the Recovery Services vault using REST API, use the following *PUT* operation
65+
To update the soft delete state of the Recovery Services vault using REST API, use the following *PUT* operation
6566

6667
```http
6768
PUT https://management.azure.com/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupconfig/vaultconfig?api-version=2019-06-15
@@ -88,7 +89,7 @@ For more details, refer to [the REST API documentation](/rest/api/backup/backup-
8889

8990
#### Example request body
9091

91-
The following example is used to update the soft-delete state to 'disabled'.
92+
Use the following example to update the soft delete state to 'disabled'.
9293

9394
```json
9495
{

0 commit comments

Comments
 (0)