VM/VMSS support add-proxy-agent-extension parameter #32154

Activity

1. Huimin Yan (huiminyan2017)

   added

   feature-request

   on Sep 22, 2025
2. yonzhan commented on Sep 22, 2025

   

   Yong Zhang (yonzhan)

   on Sep 22, 2025

   Collaborator

   More actions

   Thank you for opening this issue, we will look into it.
3. microsoft-github-policy-service

   added

   Computeaz vm/vmss/image/disk/snapshotaz vm/vmss/image/disk/snapshot

   on Sep 22, 2025
4. microsoft-github-policy-service

   assigned

   Julie Zhu (yanzhudd)

   and

   Xing Zhou (zhoxing-ms)

   on Sep 22, 2025
5. microsoft-github-policy-service

   added

   Auto-AssignAuto assign by botAuto assign by bot

   Azure CLI TeamThe command of the issue is owned by Azure CLI teamThe command of the issue is owned by Azure CLI team

   questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

   on Sep 22, 2025
6. github-actions

   added

   Possible-Solution

   Similar-Issue

   on Sep 22, 2025
7. github-actions commented on Sep 22, 2025

   

   github-actionsbot

   on Sep 22, 2025 – with GitHub Actions

   More actions

   Here are some similar issues that might help you. Please check if they can solve your problem.

   • VM/VMSS to support Azure Metadata Security Protocol #27729
   • VM/VMSS support add-proxy-agent-extension parameter #32124
   • VM/VMSS to support v2 Version of Azure Metadata Security Protocol #29279

   ---

   Possible solution (Extracted from existing issue, might be incorrect; please verify carefully)

   Solution 1:

   Please test with a Linux image:

   set resourceGroupName="huiya-eastus2euap"
   set locationName="WestUS2"
   set vmName="vm2"
   set adminPassword="your password"
   az login
   az vm create -g %resourceGroupName% --location %locationName% --image Canonical:0001-com-ubuntu-server-jammy:22_04-lts:latest --size Standard_D2s_v5 --admin-username test_admin --admin-password %adminPassword% --enable-proxy-agent --add-proxy-agent-extension --name %vmName%
   

   Without setting add-proxy-agent-extension, the creation will fail with: :[{"code":"OSProvisioningInternalError","message":"OS Provisioning failed for VM 'vm2' due to an internal error."}]
   With setting add-proxy-agent-extension, the creation will succeed.

   Reference:

   • VM/VMSS support add-proxy-agent-extension parameter #32124 (comment)

   Solution 2:

   The Swagger PR has been merged, and the official Python SDK will be released by the SDK team around 03/28/2025. Please work on top of that release.

   Reference:

   • VM/VMSS to support v2 Version of Azure Metadata Security Protocol #29279 (comment)

   Powered by issue-sentinel
8. github-actions commented on Sep 22, 2025

   

   github-actionsbot

   on Sep 22, 2025 – with GitHub Actions

   More actions

   This issue is related to security. Please pay attention.

   Powered by issue-sentinel
9. github-actions

   added

   Security-Issue

   on Sep 22, 2025
10. Huimin Yan (huiminyan2017)

    changed the title [-]VM/VMSS support add-proxy-agent-extension parameter #32124[/-] [+]VM/VMSS support add-proxy-agent-extension parameter[/+] on Sep 22, 2025
11. Yong Zhang (yonzhan)

    removed

    questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

    on Sep 22, 2025
12. Yong Zhang (yonzhan)

    added this to the Backlog milestone on Sep 22, 2025
13. Xing Zhou (zhoxing-ms)

    modified the milestones: Backlog, November 2025 (2025-11-04) on Sep 23, 2025
14. zhoxing-ms commented on Sep 23, 2025

    

    Xing Zhou (zhoxing-ms)

    on Sep 23, 2025

    Contributor

    More actions

    Huimin Yan (@huiminyan2017) We will schedule this feature request for the next sprint, and its release time is 11-04
15. naga-nandyala commented on Oct 26, 2025

    

    Naga Nandyala (naga-nandyala)

    on Oct 26, 2025

    Contributor

    More actions

    Hi Huimin Yan (@huiminyan2017)

    Due to other high-priority items, we were unable to complete the build and required testing before the code cutoff date.
    We plan to postpone this feature to the next sprint (2025-11-18).

    Please let us know if that works.

    Thanks
16. huiminyan2017 commented on Nov 4, 2025

    

    Huimin Yan (huiminyan2017)

    on Nov 4, 2025

    Author

    More actions

    Hi @huiminyan2017

    Due to other high-priority items, we were unable to complete the build and required testing before the code cutoff date. We plan to postpone this feature to the next sprint (2025-11-18).

    Please let us know if that works.

    Thanks

    Can you confirm it will release at 2025-11-18? This feature is already GA-ed and we need to get the support as soon as possible.
17. Julie Zhu (yanzhudd)

    closed this as completedin #32298on Nov 5, 2025