Cloning removes user assigned identity
Open
- Dominant language
- TypeScript
- Stars
- 205
- Forks
- 75
- PR merge metrics
- No merged PRs in 30d
Description
**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
Contributor guide
Assessment
This issue has not been assessed yet.