Added the migrate method to the crossTenantMigrationJob resource.
Why it matters: API deprecation — update before it's removed
From Microsoft's description: “Added the migrate method to the crossTenantMigrationJob resource.”
displayName, completeAfterDateTime, sourceTenantId, exchangeSettings, workloads, resourceType, resourcesvalidatemigrateAdded the migrate method to the crossTenantMigrationJob resource. Changed the behavior of the validate method on the crossTenantMigrationJob resource to validate an existing job as an entity-bound action. Going forward, use the POST /solutions/migrations/crossTenantMigrationJobs/{crossTenantMigrationJobId}/validate endpoint to trigger the validation of an existing cross-tenant migration job. Removed the displayName parameter from the validate method. Removed the completeAfterDateTime parameter from the validate method. Removed the sourceTenantId parameter from the validate method. Removed the exchangeSettings parameter from the validate method. Removed the workloads parameter from the validate method. Removed the resourceType parameter from the validate method. Removed the resources parameter from the validate method.
How this was classified (derived by the tracker — not Microsoft's label)
- deprecation · 80% confidence · matched Graph API removal/deprecation
Removed the displayName parameter from the validate method
Affected: Microsoft Graph, Tenants