Bulk Detach Volumes

Detach multiple volumes from their attached virtual machines in a single request. Each volume detach is handled as its own async workflow job.

Every listed id is checked before any job is created — that it exists, is in your tenant and sits in a resource group you reach (404 otherwise), and that you hold the verb there (403 otherwise). The first refused id, in the order listed, answers for the whole request, records its denied row, and nothing is started. A failure starting a job after every id has passed still rejects the request while jobs already started keep running, so re-read the volumes before retrying.

• Validates each volume exists, is in your tenant, and sits in a resource group you reach
• Answers 404 for an id you do not reach, exactly as the single-volume route does, so the batch never confirms a volume you cannot see
• Creates separate detach jobs for each volume
• Returns job tracking information for all detach operations