Problem with Graph API beta and V2

Hi,

As you know Microsoft Graph API is migrating

https://dori-uw-1.kuma-moon.com/fi-fi/graph/api/resources/alert?view=graph-rest-beta

Looking at the documentation of Microsoft Graph Security we know that for legacy alerts the request should be:

GET https://graph.microsoft.com/v1.0/security/alerts/<alert_id>

If we take a real example that is retrieving results:

Request:

GET https://graph.microsoft.com/v1.0/security/alerts/<alert_id>

Response:

{

"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#security/alerts/$entity",

"id": "xxxx",

"azureTenantId": "xxxx",

"azureSubscriptionId": "xxxx",

"riskScore": null,

"tags": [],

"activityGroupName": null,

"assignedTo": null,

"category": "xxxxx",

"closedDateTime": null,

"comments": [],

"confidence": null,

"createdDateTime": "2026-04-06T13:53:34.0293018Z",

"description": "xxxxx ",

"detectionIds": [],

"eventDateTime": "2026-04-06T12:47:52.0409645Z",

"feedback": null,

"incidentIds": [],

"lastEventDateTime": null,

"lastModifiedDateTime": "2026-04-06T13:53:34.3474396Z",

"recommendedActions": [],

"severity": "high",

"sourceMaterials": [],

"status": "newAlert",

"title": "xxxxx",

"vendorInformation": {

    "provider": "Azure Sentinel",

    "providerVersion": null,

    "subProvider": null,

    "vendor": "Microsoft"

},

"alertDetections": [],

"cloudAppStates": [],

"fileStates": [],

"hostStates": [],

"historyStates": [],

"investigationSecurityStates": [],

"malwareStates": [],

"messageSecurityStates": [],

"networkConnections": [],

"processes": [],

"registryKeyStates": [],

"securityResources": [],

"triggers": [],

"userStates": [

    {

        "aadUserId": null,

        "accountName": "xxxxx",

        "domainName": "xxxxx",

        "emailRole": "unknown",

        "isVpn": null,

        "logonDateTime": "2026-04-06T12:47:52.0409645Z",

        "logonId": null,

        "logonIp": "xxxxxx",

        "logonLocation": null,

        "logonType": null,

        "onPremisesSecurityIdentifier": null,

        "riskScore": null,

        "userAccountType": null,

        "userPrincipalName": "xxxxx"

    },

    {

        "aadUserId": null,

        "accountName": "xxxxxx",

        "domainName": "xxxx",

        "emailRole": "unknown",

        "isVpn": null,

        "logonDateTime": "2026-04-06T12:47:52.0409645Z",

        "logonId": null,

        "logonIp": "xxxx",

        "logonLocation": null,

        "logonType": null,

        "onPremisesSecurityIdentifier": null,

        "riskScore": null,

        "userAccountType": null,

        "userPrincipalName": "xxxxx"

    }

],

"uriClickSecurityStates": [],

"vulnerabilityStates": []

}

From what the documentation says the only difference to alerts_v2 is the request path:

GET https://graph.microsoft.com/v1.0/security/alerts_v2/<alert_id>

If we try:

Request:

GET https://graph.microsoft.com/v1.0/security/alerts_v2/<alert_id>

Response:

{

"error": {

    "code": "ResourceNotFound",

    "message": "Alert xxxxx was not found",

    "innerError": {

        "date": "2026-04-07T13:23:27",

        "request-id": "xxxxx",

        "client-request-id": "xxxxx"

    }

}

}

As you can see we cant retrieve the same alert in the other API.

Another related issue that is also happening is for example, if we check available alerts of alerts_v2 API we can retrieve them but then if we take their ids and try on alert v1 sometimes we are able to retrieve them and somestimes dont.

Could you help us with this situation?