Share via

versions/ 'web app' deployment from Foundry (classic)

Bhatt, Nitin 0 Reputation points
2026-02-25T19:32:20.43+00:00

I am not able to create version for my Agents ,i dont see any option to dothat. versions are required for deployment . i am using gpt-4.1 in my agent.

If i use 'chat playground' , then i can see DEPLOY .. as web app option.

Is there a tutorial or documentation available on how to do ' 'web app' deployment from Foundry (classic)' . here is how my Foundry left pane looks - its classic.

User's image

Foundry Tools
Foundry Tools

Formerly known as Azure AI Services or Azure Cognitive Services is a unified collection of prebuilt AI capabilities within the Microsoft Foundry platform

{count} votes

1 answer

Sort by: Most helpful
  1. Anshika Varshney 7,970 Reputation points Microsoft External Staff Moderator
    2026-02-25T20:20:43.5466667+00:00

    Hi Bhatt, Nitin,

    Thanks for raising this, the behavior you’re seeing is expected when working in Foundry (classic).

    In the classic Foundry experience, agents don’t support versioning in the way required for web app deployments. That’s why you don’t see an option to create versions in the left pane. Versioned deployments (and the “web app” deployment flow that depends on them) are available only in the new Azure AI Foundry experience, not in classic.

    A few clarifying points:

    Foundry (classic) is effectively in maintenance mode and doesn’t expose agent version management.

    Agent versioning is mandatory for web app deployments, so classic projects can’t complete that deployment path.

    There isn’t a tutorial for “web app deployment from Foundry (classic)” because that flow isn’t supported there.

    What to do next

    Create a new Foundry project using the new Azure AI Foundry portal.

    Recreate or migrate your agent into that project.

    From the new experience, you’ll be able to:

    Create agent versions

      Promote versions
      
         Deploy the agent as a web app
         
    

    If you want, you can keep classic for experimentation, but for production deployments (web apps, versioning, promotion), the new Foundry is the supported path.

    I Hope this helps. Do let me know if you have any further queries.

    Thankyou!

    1 person found this answer helpful.

Your answer

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