Comment
Honored Contributor III

@KiranAnand - Thanks for the documentation. 

The questions I have are around the 'Classic Compute' and it may not matter for the Managed/VNet-injected workspace.

1) VM Lifecycle management - Does the Azure Admin get any opportunity to contol the Azure VM in terms of allocation of 'same private IP address and hostname after termination/restart' ? 

2) Any antivirus/endpoint protection/security baselines be injected into these 'ephemeral' VMs - like init script?

3) Any visibility does a customer have into underlying OS or runtime patching?

4) while looking to use 'serverless' for data processing in databricks, are there any Databricks scenarios (maintenance jobs etc) which will force to use classic compute?