Merge pull request #25624 from microsoftgraph/tannikaM-patch-1

Update servicestatus.md with more details about protectionChangeLocke…

Author: Lauragra

api-reference/beta/resources/servicestatus.md

@@ -6,6 +6,7 @@ ms.reviewer: "manikantsinghms"
 ms.localizationpriority: medium
 ms.subservice: "m365-backup-storage"
 doc_type: resourcePageType
+ms.date: 11/29/2024
 ---
 
 # serviceStatus resource type
@@ -57,6 +58,17 @@ Represents the tenant-level service status of the backup service.
 |restoreLocked | Service is locked with no protection change and no restore. The protection policy can't be created or updated. No new protection items can be added or removed. No restore can be performed.|
 |unknownFutureValue | Evolvable enumeration sentinel value. Don't use.|
 
+#### protectionChangeLocked
+
+A service is locked with no change in protection allowed in the following scenarios:
+
+- 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.
+- 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.
+
+#### restoreLocked
+
+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).
+
 ## Relationships
 
 None.

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

@@ -56,6 +56,17 @@ Represents the tenant-level service status of the backup service.
 |restoreLocked | Service is locked with no protection change and no restore. The protection policy can't be created or updated. No new protection items can be added or removed. No restore can be performed.|
 |unknownFutureValue | Evolvable enumeration sentinel value. Don't use.|
 
+#### protectionChangeLocked
+
+A service is locked with no change in protection allowed in the following scenarios:
+
+- 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.
+- 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.
+
+#### restoreLocked
+
+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).
+
 ## Relationships
 
 None.