Topic Last Modified: 2015-10-15
This is an old version of the topic. To see the current version, change the |
This cmdlet is available only in the cloud-based service.
Use the Stop-HistoricalSearch cmdlet to stop an existing historical search that has a status value of
For information about the parameter sets in the Syntax section below, see Syntax.
A historical search provides message trace and report details in a comma-separated value (CSV) file for messages that are between seven and ninety days old.
After you start a historical search by using the Start-HistoricalSearch cmdlet, the search is queued, but not actually running. While the search is queued and has the status value of
NotStarted, you can use the Stop-HistoricalSearch cmdlet to stop it. After the search is actively running, and has a status value of
InProgress, you can't stop it. When you stop a historical search, it's given a status value of
You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "View Reports" entry in the Feature permissions in Exchange Online topic.
The JobId parameter specifies the identity GUID value of the historical search that you want to stop.
The Organization parameter is reserved for internal Microsoft use.
To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.