diff --git a/pd-configuration-file.md b/pd-configuration-file.md
index c128d49a9def1..700255b7070ed 100644
--- a/pd-configuration-file.md
+++ b/pd-configuration-file.md
@@ -496,6 +496,8 @@ Configuration items related to labels, which only support the `reject-leader` ty
 > **Note:**
 >
 > Starting from v5.2, the configuration items related to labels are deprecated. It is recommended to use [Placement Rules](/configure-placement-rules.md#scenario-2-place-five-replicas-in-three-data-centers-in-the-proportion-of-221-and-the-leader-should-not-be-in-the-third-data-center) to configure the replica policy.
+>
+> In PD microservice mode, the `scheduling` microservice does not support `label-property`. Use [Placement Rules](/configure-placement-rules.md) or `evict-leader-scheduler` instead.
 
 ### `key` (deprecated)
 
diff --git a/pd-microservices.md b/pd-microservices.md
index a3b26777f7918..067e413070d75 100644
--- a/pd-microservices.md
+++ b/pd-microservices.md
@@ -33,6 +33,7 @@ In addition, when the scheduling module is changed, you can update the `scheduli
 - Microservices are not compatible with the [Data Replication Auto Synchronous (DR Auto-Sync)](/two-data-centers-in-one-city-deployment.md) feature.
 - Microservices are not compatible with the TiDB system variable [`tidb_enable_tso_follower_proxy`](/system-variables.md#tidb_enable_tso_follower_proxy-new-in-v530).
 - Because [hibernate Regions](/tikv-configuration-file.md#hibernate-regions) might exist in a cluster, during a primary and secondary switchover of the `scheduling` microservice, the scheduling function of the cluster might be unavailable for a certain period (up to [`peer-stale-state-check-interval`](/tikv-configuration-file.md#peer-stale-state-check-interval), which is five minutes by default) to avoid redundant scheduling.
+- The `scheduling` microservice does not support the deprecated `label-property` configuration, so `reject-leader` label properties do not take effect when the `scheduling` microservice is enabled. To keep leaders off specific stores, use [Placement Rules](/configure-placement-rules.md) or `evict-leader-scheduler`. If no `scheduling` microservice is available and PD schedules by itself through `enable-scheduling-fallback` (enabled by default), `label-property` takes effect again.
 
 ## Usage