Microsoft Graph · Schema

microsoft.graph.riskDetection

Azure ADCollaborationContactsDocumentsEmailGraphIdentityMicrosoftOffice 365PresentationsProductivitySpreadsheetsT1Task
View JSON Schema on GitHub

JSON Schema

microsoft-graph-microsoftgraphriskdetection-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "#/components/schemas/microsoft.graph.riskDetection",
  "title": "microsoft.graph.riskDetection",
  "allOf": [
    {
      "$ref": "#/components/schemas/microsoft.graph.entity"
    },
    {
      "title": "riskDetection",
      "required": [
        "@odata.type"
      ],
      "type": "object",
      "properties": {
        "activity": {
          "anyOf": [
            {
              "$ref": "#/components/schemas/microsoft.graph.activityType"
            },
            {
              "type": "object",
              "nullable": true
            }
          ],
          "description": "Indicates the activity type the detected risk is linked to."
        },
        "activityDateTime": {
          "pattern": "^[0-9]{4,}-(0[1-9]|1[012])-(0[1-9]|[12][0-9]|3[01])T([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]([.][0-9]{1,12})?(Z|[+-][0-9][0-9]:[0-9][0-9])$",
          "type": "string",
          "description": "Date and time that the risky activity occurred. The DateTimeOffset type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is look like this: 2014-01-01T00:00:00Z",
          "format": "date-time",
          "nullable": true
        },
        "additionalInfo": {
          "type": "string",
          "description": "Additional information associated with the risk detection in JSON format. For example, '[{/'Key/':/'userAgent/',/'Value/':/'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36/'}]'. Possible keys in the additionalInfo JSON string are: userAgent, alertUrl, relatedEventTimeInUtc, relatedUserAgent, deviceInformation, relatedLocation, requestId, correlationId, lastActivityTimeInUtc, malwareName, clientLocation, clientIp, riskReasons. For more information about riskReasons and possible values, see riskReasons values.",
          "nullable": true
        },
        "correlationId": {
          "type": "string",
          "description": "Correlation ID of the sign-in associated with the risk detection. This property is null if the risk detection is not associated with a sign-in.",
          "nullable": true
        },
        "detectedDateTime": {
          "pattern": "^[0-9]{4,}-(0[1-9]|1[012])-(0[1-9]|[12][0-9]|3[01])T([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]([.][0-9]{1,12})?(Z|[+-][0-9][0-9]:[0-9][0-9])$",
          "type": "string",
          "description": "Date and time that the risk was detected. The DateTimeOffset type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 looks like this: 2014-01-01T00:00:00Z",
          "format": "date-time",
          "nullable": true
        },
        "detectionTimingType": {
          "anyOf": [
            {
              "$ref": "#/components/schemas/microsoft.graph.riskDetectionTimingType"
            },
            {
              "type": "object",
              "nullable": true
            }
          ],
          "description": "Timing of the detected risk (real-time/offline). The possible values are: notDefined, realtime, nearRealtime, offline, unknownFutureValue."
        },
        "ipAddress": {
          "type": "string",
          "description": "Provides the IP address of the client from where the risk occurred.",
          "nullable": true
        },
        "lastUpdatedDateTime": {
          "pattern": "^[0-9]{4,}-(0[1-9]|1[012])-(0[1-9]|[12][0-9]|3[01])T([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]([.][0-9]{1,12})?(Z|[+-][0-9][0-9]:[0-9][0-9])$",
          "type": "string",
          "description": "Date and time that the risk detection was last updated. The DateTimeOffset type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is look like this: 2014-01-01T00:00:00Z",
          "format": "date-time",
          "nullable": true
        },
        "location": {
          "anyOf": [
            {
              "$ref": "#/components/schemas/microsoft.graph.signInLocation"
            },
            {
              "type": "object",
              "nullable": true
            }
          ],
          "description": "Location of the sign-in."
        },
        "requestId": {
          "type": "string",
          "description": "Request ID of the sign-in associated with the risk detection. This property is null if the risk detection is not associated with a sign-in.",
          "nullable": true
        },
        "riskDetail": {
          "anyOf": [
            {
              "$ref": "#/components/schemas/microsoft.graph.riskDetail"
            },
            {
              "type": "object",
              "nullable": true
            }
          ],
          "description": "Details of the detected risk."
        },
        "riskEventType": {
          "type": "string",
          "description": "The type of risk event detected. The possible values are adminConfirmedUserCompromised, anomalousToken, anomalousUserActivity, anonymizedIPAddress, generic, impossibleTravel, investigationsThreatIntelligence, suspiciousSendingPatterns, leakedCredentials, maliciousIPAddress,malwareInfectedIPAddress, mcasSuspiciousInboxManipulationRules, newCountry, passwordSpray,riskyIPAddress, suspiciousAPITraffic, suspiciousBrowser,suspiciousInboxForwarding, suspiciousIPAddress, tokenIssuerAnomaly, unfamiliarFeatures, unlikelyTravel. If the risk detection is a premium detection, will show generic. For more information about each value, see Risk types and detection.",
          "nullable": true
        },
        "riskLevel": {
          "anyOf": [
            {
              "$ref": "#/components/schemas/microsoft.graph.riskLevel"
            },
            {
              "type": "object",
              "nullable": true
            }
          ],
          "description": "Level of the detected risk. The possible values are: low, medium, high, hidden, none, unknownFutureValue."
        },
        "riskState": {
          "anyOf": [
            {
              "$ref": "#/components/schemas/microsoft.graph.riskState"
            },
            {
              "type": "object",
              "nullable": true
            }
          ],
          "description": "The state of a detected risky user or sign-in. The possible values are: none, confirmedSafe, remediated, dismissed, atRisk, confirmedCompromised, unknownFutureValue."
        },
        "source": {
          "type": "string",
          "description": "Source of the risk detection. For example, activeDirectory.",
          "nullable": true
        },
        "tokenIssuerType": {
          "anyOf": [
            {
              "$ref": "#/components/schemas/microsoft.graph.tokenIssuerType"
            },
            {
              "type": "object",
              "nullable": true
            }
          ],
          "description": "Indicates the type of token issuer for the detected sign-in risk. The possible values are: AzureAD, ADFederationServices, UnknownFutureValue."
        },
        "userDisplayName": {
          "type": "string",
          "description": "The user principal name (UPN) of the user.",
          "nullable": true
        },
        "userId": {
          "type": "string",
          "description": "Unique ID of the user.",
          "nullable": true
        },
        "userPrincipalName": {
          "type": "string",
          "description": "The user principal name (UPN) of the user.",
          "nullable": true
        },
        "@odata.type": {
          "type": "string"
        }
      }
    }
  ],
  "x-ms-discriminator-value": "#microsoft.graph.riskDetection"
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/microsoft-graph-microsoftgraphriskdetection"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.