Skip to content

Commit f359ed6

Browse files
authored
Update servicestatus.md
1 parent 848d977 commit f359ed6

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

api-reference/v1.0/resources/servicestatus.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -58,14 +58,14 @@ Represents the tenant-level service status of the backup service.
5858

5959
#### protectionChangeLocked
6060

61-
The following scenarios describe when a service is locked with no change in protection allowed:
61+
A service is locked with no change in protection allowed in the following scenarios:
6262

63-
- **Scenario 1**: Tenant has no active service apps. If no active service apps are found for the tenant, the feature status of the tenant changes from `enabled` to `protectionChangeLocked`. To resolve this issue, the tenant needs to activate a service app and call the [enable](../api/backuprestoreroot-enable.md) API.
64-
- **Scenario 2**: Tenant has an unhealthy billing profile. When an unhealthy billing profile is found for a tenant, the feature status is automatically moved from `enabled` to `protectionChangeLocked`, and the policies are deactivated right away. To resolve this issue, the tenant needs to update the billing profile with a healthy one and wait for 24-48 hours for the changes to take effect.
63+
- The tenant has no active service apps. If no active service apps are found for the tenant, the feature status of the tenant changes from `enabled` to `protectionChangeLocked`. To resolve this issue, the tenant needs to activate a service app and call the [enable](../api/backuprestoreroot-enable.md) API.
64+
- The tenant has an unhealthy billing profile. When an unhealthy billing profile is found for a tenant, the feature status is automatically moved from `enabled` to `protectionChangeLocked`, and the policies are deactivated right away. To resolve this issue, the tenant needs to update the billing profile with a healthy one and wait for 24-48 hours for the changes to take effect.
6565

6666
#### restoreLocked
6767

68-
When a tenant stays in the `protectionChangeLocked` status for 30 days, the status changes from `protectionChangeLocked` to `restoreLocked`. With this change, restore capabilities are blocked, and billing also stops. To resolve this issue, the tenant needs to follow the specific steps depending on the previous scenarios (1 or 2) it belongs to.
68+
When a tenant stays in the `protectionChangeLocked` status for 30 days, the status changes from `protectionChangeLocked` to `restoreLocked`. With this change, restore capabilities are blocked, and billing also stops. To resolve this issue, the tenant needs to follow the steps to resolve the issue based on the scenarios described in [protectionChangeLocked](#protectionchangelocked).
6969

7070
## Relationships
7171

0 commit comments

Comments
 (0)