Skip to content

Commit 139e082

Browse files
authored
Update security-teamsmessageevidence documentation
1 parent b9bc6f3 commit 139e082

File tree

2 files changed

+8
-8
lines changed

2 files changed

+8
-8
lines changed

api-reference/beta/resources/security-teamsmessageevidence.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -32,12 +32,12 @@ Inherits from [alertEvidence](../resources/security-alertevidence.md).
3232
| groupId | String | The identifier of the team or group that this message is part of. |
3333
| isExternal | Boolean | Indicates whether the message is owned by the organization that reported the security detection alert. |
3434
| isOwned | Boolean | Indicates whether the message is owned by your organization. |
35-
| lastModifiedDateTime | DateTimeOffset | Date and time when the message was last edited. |
35+
| lastModifiedDateTime | DateTimeOffset | Date and time when the message was last edited. The Timestamp type represents date and time information using ISO 8601 format and is always in UTC. For example, midnight UTC on Jan 1, 2014 is `2014-01-01T00:00:00Z`. |
3636
| messageDirection | microsoft.graph.security.antispamTeamsDirection | The direction of the Teams message. |
3737
| messageId | String | Non unique identifier of a message |
38-
| owningTenantId | Guid | Tenant ID (GUID) of the owner of the message. |
38+
| owningTenantId | String | Tenant ID (GUID) of the owner of the message. |
3939
| parentMessageId | String | Identifier of the message to which the current message is a reply; otherwise, it's the same as the **messageId**. |
40-
| receivedDateTime | DateTimeOffset | The received date of this message. |
40+
| receivedDateTime | DateTimeOffset | The received date of this message. The Timestamp type represents date and time information using ISO 8601 format and is always in UTC. For example, midnight UTC on Jan 1, 2014 is `2014-01-01T00:00:00Z`. |
4141
| recipients | String collection | The recipients of this Teams message. |
4242
| remediationStatus | [microsoft.graph.security.evidenceRemediationStatus](../resources/security-alertevidence.md#evidenceremediationstatus-values) | Status of the remediation action taken. The possible values are: `none`, `remediated`, `prevented`, `blocked`, `notFound`, `unknownFutureValue`, `active`, `pendingApproval`, `declined`, `unremediated`, `running`, `partiallyRemediated`. Use the `Prefer: include-unknown-enum-members` request header to get the following values from this [evolvable enum](/graph/best-practices-concept#handling-future-members-in-evolvable-enumerations): `active`, `pendingApproval`, `declined`, `unremediated`, `running`, `partiallyRemediated`. |
4343
| remediationStatusDetails | String | Details about the remediation status. |
@@ -80,7 +80,7 @@ The following JSON representation shows the resource type.
8080
"lastModifiedDateTime": "String (timestamp)",
8181
"messageDirection": "String",
8282
"messageId": "String",
83-
"owningTenantId": "Guid",
83+
"owningTenantId": "String",
8484
"parentMessageId": "String",
8585
"receivedDateTime": "String (timestamp)",
8686
"recipients": ["String"],

api-reference/v1.0/resources/security-teamsmessageevidence.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -30,12 +30,12 @@ Inherits from [alertEvidence](../resources/security-alertevidence.md).
3030
| groupId | String | The identifier of the team or group that this message is part of. |
3131
| isExternal | Boolean | Indicates whether the message is owned by the organization that reported the security detection alert. |
3232
| isOwned | Boolean | Indicates whether the message is owned by your organization. |
33-
| lastModifiedDateTime | DateTimeOffset | Date and time when the message was last edited. |
33+
| lastModifiedDateTime | DateTimeOffset | Date and time when the message was last edited. The Timestamp type represents date and time information using ISO 8601 format and is always in UTC. For example, midnight UTC on Jan 1, 2014 is `2014-01-01T00:00:00Z`. |
3434
| messageDirection | microsoft.graph.security.antispamTeamsDirection | The direction of the Teams message. |
3535
| messageId | String | Non unique identifier of a message |
36-
| owningTenantId | Guid | Tenant ID (GUID) of the owner of the message. |
36+
| owningTenantId | String | Tenant ID (GUID) of the owner of the message. |
3737
| parentMessageId | String | Identifier of the message to which the current message is a reply; otherwise, it's the same as the **messageId**. |
38-
| receivedDateTime | DateTimeOffset | The received date of this message. |
38+
| receivedDateTime | DateTimeOffset | The received date of this message. The Timestamp type represents date and time information using ISO 8601 format and is always in UTC. For example, midnight UTC on Jan 1, 2014 is `2014-01-01T00:00:00Z`. |
3939
| recipients | String collection | The recipients of this Teams message. |
4040
| remediationStatus | [microsoft.graph.security.evidenceRemediationStatus](../resources/security-alertevidence.md#evidenceremediationstatus-values) | Status of the remediation action taken. The possible values are: `none`, `remediated`, `prevented`, `blocked`, `notFound`, `unknownFutureValue`, `active`, `pendingApproval`, `declined`, `unremediated`, `running`, `partiallyRemediated`. Use the `Prefer: include-unknown-enum-members` request header to get the following values from this [evolvable enum](/graph/best-practices-concept#handling-future-members-in-evolvable-enumerations): `active`, `pendingApproval`, `declined`, `unremediated`, `running`, `partiallyRemediated`. |
4141
| remediationStatusDetails | String | Details about the remediation status. |
@@ -78,7 +78,7 @@ The following JSON representation shows the resource type.
7878
"lastModifiedDateTime": "String (timestamp)",
7979
"messageDirection": "String",
8080
"messageId": "String",
81-
"owningTenantId": "Guid",
81+
"owningTenantId": "String",
8282
"parentMessageId": "String",
8383
"receivedDateTime": "String (timestamp)",
8484
"recipients": ["String"],

0 commit comments

Comments
 (0)