Azure Batch Pool Deployment in VNet with Batch-Service and User Subscription Modes

Question

I'm trying to understand how Azure Batch deploys pools to a Virtual Network (VNet) in both Batch-Service mode and User subscription mode.

I successfully created a Batch pool in Batch-Service mode and deployed it into a VNet in my own Azure subscription (with some issues but portal allowed me to do this). However, I’m confused about how Azure Batch is able to deploy VMs from a different subscription (Batch-managed) into my VNet. In User subscription mode, I assume everything (VMs, disks, networking) is in my subscription, so it’s straightforward.

Answer 1

Hi AzureKnwGt-8579,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

In Azure Batch Pool can be deployed using two modes Batch-Service Mode (Batch-managed resources) and User Subscription Mode (user-managed resources).

In Batch-Service mode, Azure Batch manages the VMs and related resources in Azure’s subscription (Batch-managed). However, you can still deploy these VMs into a VNet within your own subscription. This is possible because Azure Batch is granted Network Contributor access to the subnet in your VNet, allowing VMs from Azure’s subscription to connect to your VNet.

In User subscription mode, everything (VMs, disks, networking) is deployed and billed under your own subscription. This mode is more straightforward because all resources are fully managed within your subscription, including the VMs and networking.

The main difference between the two modes is that in Batch-Service Mode, Azure manages the VMs in its subscription, but the VMs can still connect to your VNet through granted network access. In User Subscription Mode, everything stays within your subscription, providing full control.

For more detailed information, you can refer to the Azure Batch and Virtual Networks

If you have any further queries, do let us know. If the comment is helpful, please click "Upvote".