Skip to content

Commit a9a127a

Browse files
authored
Update Invoke-AzStorageSyncChangeDetection.md (#22901)
* Update Invoke-AzStorageSyncChangeDetection.md * Update Invoke-AzStorageSyncChangeDetection.md
1 parent 0973958 commit a9a127a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/StorageSync/StorageSync/help/Invoke-AzStorageSyncChangeDetection.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ schema: 2.0.0
88
# Invoke-AzStorageSyncChangeDetection
99

1010
## SYNOPSIS
11-
This command can be used to manually initiate the detection of namespace changes. It can be targeted to the entire share, subfolder or set of files. When running the command with the -DirectoryPath or -Path parameters, a maximum of 10,000 items can be detected. If the scope of changes is known to you, limit the execution of this command to parts of the namespace, so change detection can finish quickly and within the 10,000 item limit. Alternatively, you can avoid the item limit by running the cmdlet without these parameters, invoking share-level change detection.
11+
This command can be used to manually initiate the detection of namespace changes. It can be targeted to the entire share, subfolder or set of files. When running the command with the -DirectoryPath or -Path parameters, a maximum of 10,000 items can be detected. If the scope of changes is known to you, limit the execution of this command to parts of the namespace, so change detection can finish quickly and within the 10,000 item limit. Alternatively, you can avoid the item limit by running the cmdlet without these parameters, invoking share-level change detection.
1212

1313
> [!Note]
1414
> If run with -DirectoryPath or -Path parameters, the command will not detect the following changes in the Azure file share:
@@ -78,7 +78,7 @@ Invoke-AzStorageSyncChangeDetection [-InputObject] <PSCloudEndpoint> [-PassThru]
7878
```
7979

8080
## DESCRIPTION
81-
Periodically, Azure File Sync checks the namespace inside a syncing Azure file share for changes that came into the file share by other means than sync. The goal is to identify these changes and ultimately sync them to connected servers. This command can be used to manually initiate the detection of namespaces changes. It can be targeted to the entire share, subfolder or set of files. If the scope of changes is known to you, limit the execution of this command to parts of the namespace, so individual item change detection can finish quickly and within the 10,000 items limit. Otherwise, run the command without the -DirectoryPath or -Path parameters to invoke full share-level change detection.
81+
Periodically, Azure File Sync checks the namespace inside a syncing Azure file share for changes that came into the file share by other means than sync. The goal is to identify these changes and ultimately sync them to connected servers. This command can be used to manually initiate the detection of namespaces changes. It can be targeted to the entire share, subfolder or set of files. If the scope of changes is known to you, limit the execution of this command to parts of the namespace, so individual item change detection can finish quickly and within the 10,000 items limit. Otherwise, run the command without the -DirectoryPath or -Path parameters to invoke full share-level change detection. The Invoke-AzStorageSyncChangeDetection cmdlet will cancel a cloud change enumeration job that is in progress. To avoid cancelling a currently running job, go to the Cloud Endpoint properties in the portal to check if a job is currently running.
8282

8383
## EXAMPLES
8484

0 commit comments

Comments
 (0)