sensorMigration: migrate

Namespace: microsoft.graph.security

Important

APIs under the /beta version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported. To determine whether an API is available in v1.0, use the Version selector.

Migrate the specified sensors to the unified security portal. This action initiates the migration process for one or more Microsoft Defender for Identity sensors.

Permissions

Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions only if your app requires it. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.

Permission type	Least privileged permissions	Higher privileged permissions
Delegated (work or school account)	SecurityIdentitiesMigration.ReadWrite.All	Not available.
Delegated (personal Microsoft account)	Not supported.	Not supported.
Application	SecurityIdentitiesMigration.ReadWrite.All	Not available.

Important

For delegated access using work or school accounts, the signed-in user must be assigned the Security Administrator Microsoft Entra role or a custom role with supported permissions created through the Microsoft Defender XDR Unified Role-Based Access Control (RBAC).

HTTP request

POST /security/identities/sensorMigration/migrate

Request headers

Name	Description
Authorization	Bearer {token}. Required. Learn more about authentication and authorization.
Content-Type	application/json. Required.

Request body

In the request body, supply a JSON representation of the parameters.

The following table shows the parameters that can be used with this action.

Parameter	Type	Description
sensorIds	String collection	The collection of sensor IDs to migrate.

Response

If successful, this action returns a 200 OK response code and a migrateSensorsResult object in the response body.

Examples

Request

The following example shows a request.

POST https://graph.microsoft.com/beta/security/identities/sensorMigration/migrate
Content-Type: application/json

{
  "sensorIds": [
    "fdce0c43-15e8-e322-7656-aff297505af5",
    "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
  ]
}

Response

The following example shows the response.

Note: The response object shown here might be shortened for readability.

HTTP/1.1 200 OK
Content-Type: application/json

{
  "@odata.type": "#microsoft.graph.security.migrateSensorsResult",
  "successfulMigrationSensorIds": [
    "fdce0c43-15e8-e322-7656-aff297505af5"
  ],
  "failedMigrationSensorIds": [
    "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
  ]
}