Skip to content

Commit 848fa23

Browse files
committed
fixing spacing
1 parent 942f66a commit 848fa23

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/sentinel/move-to-defender.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -157,12 +157,12 @@ The following table lists fields that are important in the response snippets, an
157157

158158
| Functionality | Azure portal | Defender portal |
159159
|----------------|--------------|----------------|
160-
| Link to the incident| `incidentUrl`: The direct URL to the incident in the Microsoft Sentinel portal | `providerIncidentUrl` : This additional field provides a direct link to the incident, which can be used to synchronize this information with a third-party ticketing system like ServiceNow. `incidentUrl` is still available, but it points to the Microsoft Sentinel portal. |
161-
| The sources that triggered the detection and published the alert | `alertProductNames` | `alertProductNames`: Requires adding `?$expand=alerts` to the GET. For example, `https://graph.microsoft.com/v1.0/security/incidents/368?$expand=alerts`|
162-
| The name of the alert provider| `providerName` = "Azure Sentinel" | `providerName` = "Microsoft XDR" |
163-
| The service or product that created the alert | |`serviceSource` For example, "microsoftDefenderForCloudApps" |
164-
| The detection technology or sensor that identified the notable component or activity | | `detectionSource` For example, "cloudAppSecurity"|
165-
| The name of the product which published this alert. | |`productName` For example, "Microsoft Defender for Cloud Apps" |
160+
| **Link to the incident**| `incidentUrl`: The direct URL to the incident in the Microsoft Sentinel portal | `providerIncidentUrl` : This additional field provides a direct link to the incident, which can be used to synchronize this information with a third-party ticketing system like ServiceNow. <br><br>`incidentUrl` is still available, but it points to the Microsoft Sentinel portal. |
161+
| **The sources that triggered the detection and published the alert** | `alertProductNames` | `alertProductNames`: Requires adding `?$expand=alerts` to the GET. <br><br>For example, `https://graph.microsoft.com/v1.0/security/incidents/368?$expand=alerts`|
162+
| **The name of the alert provider**| `providerName` = "Azure Sentinel" | `providerName` = "Microsoft XDR" |
163+
| **The service or product that created the alert** |Doesn't exist in the Azure portal |`serviceSource` <br><br>For example, "microsoftDefenderForCloudApps" |
164+
| **The detection technology or sensor that identified the notable component or activity** | Doesn't exist in the Azure portal| `detectionSource` For example, "cloudAppSecurity"|
165+
| **The name of the product which published this alert** |Doesn't exist in the Azure portal |`productName` For example, "Microsoft Defender for Cloud Apps" |
166166

167167
## Run operations in the Defender portal
168168

0 commit comments

Comments
 (0)