Cloning removes user assigned identity

[foxdrodd]

Describe the bug When I clone a pool that has set a user assigned identity, then this user identity is not set in the cloned pool.

To Reproduce Steps to reproduce the behavior:

1. Go to Azure portal and create pool with a user assigned identity
2. Change to Batch Explorer and clone this pool
3. Check the cloned pool in the Azure portal, if the user assigned identity is set
4. See error, the user assigned identity is not set on the cloned pool

Expected behavior The setting of the user assigned identity should be cloned as well to the new pool.

Version (please complete the following information):

• OS: Windows
• Version 2.9.0-stable.511

[dpwatrous]

Just wanted to follow up to say we're aware of the issue and plan to address it. It's unfortunately not a quick fix, as Batch Explorer communicates directly with the Batch service for pools, and calls to assign managed identities need to go through ARM (management.azure.com) and call a different API.

[LaszloKoller]

With the pending 29 Feb 2024 retirement¹ of support for Azure Batch account certificates, supporting user-assigned managed identities in Azure Batch pools via Batch Explorer is critical. Using Batch Explorer to manage pools, which implement managed identities, is not possible today.

Has there been any progress on implementing pool management (add/edit) support for this concept (i.e., user-assigned managed identity) via the Batch Explorer application? (As of this post, the 11-month count down has started...)

¹Reference: https://learn.microsoft.com/en-us/azure/batch/batch-certificate-migration-guide