Selecting issues on Agent Size, Maximum Agents, and Images in Azure Deployment Environment (Create a Managed DevOps Pool)

SeanHong 0 Reputation points
2025-05-26T04:10:45.9666667+00:00

Screenshot 2025-05-26 112732.png
Screenshot 2025-05-26 112229.png

Request for help when Selecting the default Agent Size it having issues on Maximum Agent either 1 also can't be accept. After request quota for different Agent Size it will not matching with any of the Images. Please help me to fix this issues. Thank you.

Azure DevOps
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Durga Reshma Malthi 4,905 Reputation points Microsoft External Staff Moderator
    2025-05-26T09:36:11.07+00:00

    Hi SeanHong

    As per the 1st screenshot.

    1. The selected agent size (Standard A8m v2) belongs to V1 generation, but the image (Ubuntu Server 24.04 LTS - x64 Gen 2) requires V2. Either select an agent size that supports V2 generation or use an image compatible with V1. Example: Standard_DS1_v2
    2. Look for Ubuntu Server images explicitly marked as V1 compatible.

    As per the 2nd screenshot,

    1. Instead of Standard D2pls v5 (which requires Arm64), select an agent size that supports x64. Examples of x64 agent sizes include Standard_D2s_v5 or Standard_D4s_v5.
    2. If you want to keep Standard D2pls v5, select an OS image designed for Arm64.

    Additional References:

    https://learn.microsoft.com/en-us/azure/devops/managed-devops-pools/quickstart-azure-portal?view=azure-devops

    https://learn.microsoft.com/en-us/azure/devops/managed-devops-pools/features-timeline?view=azure-devops

    Configure Images

    Hope this helps!

    Please Let me know if you have any queries.

    1 person found this answer helpful.
    0 comments No comments

  2. SeanHong 0 Reputation points
    2025-05-27T00:57:30.6933333+00:00

    Screenshot 2025-05-27 085429.png

    After I select Standard_D2s_v5 for Window Server 2022, I still reached the maximum agent limitation. May I know why?

    0 comments No comments

  3. Durga Reshma Malthi 4,905 Reputation points Microsoft External Staff Moderator
    2025-05-27T05:49:31.5633333+00:00

    Hi SeanHong

    It seems you are facing a quota limitation when attempting to provision the Standard_D2s_v5 size for Windows Server 2022 in the Southeast Asia region. Here are some reasons and suggestions:    

    1. The subscription might have a limit on the number of agents allowed per region or pool. Go to Azure Portal -> Subscriptions -> Select your Subscription -> Usage+Quotas to confirm the agent limit for your region. Check if the Standard_D2s_v5 SKU may have reached its quota in your subscription for your selected region. Request an increase if needed. To adjust the quota, you must be part of the Contributor role or higher. Please refer to this doc: Request for quota adjustment.
    2. Alternatively, some regions like Southeast Asia may have restrictions on VM allocation due to demand. Try switching to a region where you have existing quota, for example: East US, West Europe, or Southeast Australia.
    3. You can choose Standard D2s v5 SKU and the Ubuntu Server 24.04 LTS - x64 Gen 2 image as it is working for me. User's image

    Hope this helps!

    Please Let me know if you have any queries.

    If you found the information helpful, please click "Upvote" on the post to let us know and consider accepting the answer as a token of appreciation. Thank You.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.