Skip to content

Deploy sample application in container app - Python#89

Closed
tirthdoshi009 wants to merge 131 commits intomainfrom
users/tirthdoshi/local-playground
Closed

Deploy sample application in container app - Python#89
tirthdoshi009 wants to merge 131 commits intomainfrom
users/tirthdoshi/local-playground

Conversation

@tirthdoshi009
Copy link
Contributor

@tirthdoshi009 tirthdoshi009 commented Dec 1, 2025

The sample application was not receiving a response when we ran agentsplayground. This change makes sure that when we run the agentsplayground, we can get responses from the agent directly on the window of agentsplayground.

Testing:

image

pontemonti and others added 30 commits November 5, 2025 10:19
* Added CODEOWNERS

* Added .gitignore

---------

Co-authored-by: Johan Broberg <johanb@microsoft.com>
Co-authored-by: Johan Broberg <johanb@microsoft.com>
Co-authored-by: Johan Broberg <johanb@microsoft.com>
Co-authored-by: Jesus Terrazas <jterrazas@microsoft.com>
Co-authored-by: Johan Broberg <johanb@microsoft.com>
Co-authored-by: Jesus Terrazas <jterrazas@microsoft.com>
* Adding Python Agent Framework Sample

* update to latest

---------

Co-authored-by: Jesus Terrazas <jterrazas@microsoft.com>
Co-authored-by: Rahul Devikar <radevika@microsoft.com>
* Revise README for Agent 365 Sample Agent

Updated the README to improve clarity and correct typos. Added sections on prerequisites, running the sample, and troubleshooting.

* Update README to remove external sample reference

Removed reference to the semantic-kernel-multiturn sample.
Co-authored-by: Rahul Devikar <radevika@microsoft.com>
* update agents sdk version for langchain

* Accept more recent versions

* remove authority field, this is set by default

---------

Co-authored-by: Jesus Terrazas <jterrazas@microsoft.com>
* Adding Notifications on AF

* Update readme

* PR comments

* small fix

* removed observability

* update manifest

* changes

* setup fix
Added comprehensive instructions for GitHub Copilot to follow during code reviews, including rules for checking keywords, copyright headers, and Agent 365 sample validation.
* update with api change

* update claude to tool service api name change

* name change

---------

Co-authored-by: Jesus Terrazas <jterrazas@microsoft.com>
* Add Vercel AI SDK sample

* fix comments

---------

Co-authored-by: Dominik Bezic <dominikbezic@microsoft.com>
* introducing perplexity sample agent

* applying changes from code review

* updated readme file with features list

---------

Co-authored-by: aubreyquinn <aubreyquinn+odspmdb@microsoft.com>
* Add OpenAI Nodejs Sample

* fix: model to string

* Add copyright headers

* Add build script

* fix typo

* fix typo in doc

* take comments

* update doc for env name change

* update license path in readme

* update walkthrough to follow same structure as AF

* include agentsplayground in readme

---------

Co-authored-by: Jesus Terrazas <jterrazas@microsoft.com>
…ion (#31)

* Initial plan

* Rename "Microsoft Agents A365" to "Microsoft Agent 365"

Co-authored-by: pontemonti <7850950+pontemonti@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: pontemonti <7850950+pontemonti@users.noreply.github.com>
Co-authored-by: Jesus Terrazas <jterrazas@microsoft.com>
* add updated nodejs claude implementation

* fix typos

* change mcp endpoint to prod

* review comments

* add auth from agents-hosting

* remove lock
* quickstart initial code

* rename folder

* update docs on quickstart

* add links and update docs

* include rename change

* copilot suggestions

---------

Co-authored-by: Jesus Terrazas <jterrazas@microsoft.com>
* Introducing playground notification handling in Perplexity agent

* Introducing playground Teams messaging notification handling in Perplexity agent

* applying changes from code review

* Apply suggestion from @Copilot

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

* applying changes from code review

* Add missing copyright header to playgroundActivityTypes.ts (#36)

* Initial plan

* Add Microsoft copyright header to playgroundActivityTypes.ts

Co-authored-by: aubreyquinn <80953505+aubreyquinn@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: aubreyquinn <80953505+aubreyquinn@users.noreply.github.com>

* Add copyright header to playgroundActivityTypes.ts (#35)

* Initial plan

* Add Microsoft copyright header to playgroundActivityTypes.ts

Co-authored-by: aubreyquinn <80953505+aubreyquinn@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: aubreyquinn <80953505+aubreyquinn@users.noreply.github.com>

---------

Co-authored-by: aubreyquinn <aubreyquinn+odspmdb@microsoft.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>
* Cursor IDE prompt usage



---------

Co-authored-by: shirahman <shirahman@microsoft.com>
* Update samples to remove environment id from calls and settings

* remove env id from newer samples

* Update python/agent-framework/sample-agent/.env.template

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

---------

Co-authored-by: Jesus Terrazas <jterrazas@microsoft.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Fix formatting of 'Microsoft Agent365' to 'Microsoft Agent 365'

* Update README to reflect Microsoft Agent 365 SDK

* Fix typo in Agent365 authentication comment

* Fix comment formatting in client.ts

Updated comments to improve clarity and consistency.

* Fix typo in AGENT-TESTING.md

* Fix description formatting in pyproject.toml

* Update package description for clarity

* Fix formatting of Agent 365 configuration comment

* Update README to reference Microsoft Agent 365 SDK

* Fix typo in Agent 365 Observability SDK comment

* Update package description for clarity

* Fix description formatting in pyproject.toml

* Fix formatting in .env.template for Agent 365

* Update README.md

* Update README.md

* Fix naming in README for Agent Framework and SDK

Updated README to correct naming conventions for Agent Framework and Microsoft Agent 365 SDK.

* Update license link in README.md

* Update perplexityClient.ts

* Update README to reference Microsoft Agent 365 SDK

* Fix typo in LangChain client documentation

* Update README to reflect Microsoft Agent 365 SDK
- Add service connection authentication variables (CLIENT_ID, CLIENT_SECRET, TENANT_ID, SCOPES)
- Add agentic user authorization configuration
- Add ENABLE_OTEL and ENABLE_SENSITIVE_DATA for observability
- Add Application Insights configuration (optional)
- Add container app logs viewing step
- All env vars now match .env.template requirements
- Add service connection authentication variables (CLIENT_ID, CLIENT_SECRET, TENANT_ID, SCOPES)
- Add agentic user authorization configuration
- Add ENABLE_OTEL and ENABLE_SENSITIVE_DATA for observability
- Add Application Insights configuration (optional)
- Add container app logs viewing step
- All env vars now match .env.template requirements
@Josina20 Josina20 force-pushed the users/tirthdoshi/local-playground branch from a55f300 to a18f5a9 Compare December 22, 2025 20:02
@github-actions
Copy link

github-actions bot commented Jan 5, 2026

🚀 Deployment Successful!

Your Python Agent Framework has been deployed to Azure Container Apps.

🔗 Deployment Links

📦 Deployment Details

  • Container App: agent-framework-python
  • Resource Group: agent365-samples-rg
  • Image Tag: a2493d8
  • Commit: a2493d8

🧪 Testing with Agents Playground

Option 1: Direct Testing (Simple)

# Check health
curl https://agent-framework-python.proudbush-4649d800.eastus.azurecontainerapps.io/api/health

# Send a test message (requires authentication)
curl -X POST https://agent-framework-python.proudbush-4649d800.eastus.azurecontainerapps.io/api/messages \
  -H "Content-Type: application/json" \
  -d '{"type":"message","text":"Hello Agent!"}'

Option 2: Test with Agents Playground (Interactive)

  1. Install and authenticate ngrok:

    # Download ngrok from https://ngrok.com/download
    # Authenticate with your token
    ngrok authtoken YOUR_NGROK_TOKEN
  2. Start ngrok tunnel:

    ngrok http 2000

    Copy the HTTPS forwarding URL (e.g., https://abc123.ngrok.io)

  3. Launch Agents Playground:

    agentsplayground -p 2000 -e https://agent-framework-python.proudbush-4649d800.eastus.azurecontainerapps.io/api/messages --su 'YOUR_NGROK_URL/_connector'

    Replace YOUR_NGROK_URL with the ngrok URL from step 2.

  4. Test your agent in the playground UI at http://localhost:2000


Deployed from commit a2493d8 by @tirthdoshi009

@github-actions
Copy link

github-actions bot commented Jan 5, 2026

🚀 Deployment Successful!

Your Python Agent Framework has been deployed to Azure Container Apps.

🔗 Deployment Links

📦 Deployment Details

  • Container App: agent-framework-python
  • Resource Group: agent365-samples-rg
  • Image Tag: ea6be0a
  • Commit: ea6be0a

🧪 Testing with Agents Playground

Option 1: Direct Testing (Simple)

# Check health
curl https://agent-framework-python.proudbush-4649d800.eastus.azurecontainerapps.io/api/health

# Send a test message (requires authentication)
curl -X POST https://agent-framework-python.proudbush-4649d800.eastus.azurecontainerapps.io/api/messages \
  -H "Content-Type: application/json" \
  -d '{"type":"message","text":"Hello Agent!"}'

Option 2: Test with Agents Playground (Interactive)

  1. Install and authenticate ngrok:

    # Download ngrok from https://ngrok.com/download
    # Authenticate with your token
    ngrok authtoken YOUR_NGROK_TOKEN
  2. Start ngrok tunnel:

    ngrok http 2000

    Copy the HTTPS forwarding URL (e.g., https://abc123.ngrok.io)

  3. Launch Agents Playground:

    agentsplayground -p 2000 -e https://agent-framework-python.proudbush-4649d800.eastus.azurecontainerapps.io/api/messages --su 'YOUR_NGROK_URL/_connector'

    Replace YOUR_NGROK_URL with the ngrok URL from step 2.

  4. Test your agent in the playground UI at http://localhost:2000


Deployed from commit ea6be0a by @tirthdoshi009

@tirthdoshi009 tirthdoshi009 marked this pull request as ready for review January 5, 2026 20:56
@tirthdoshi009 tirthdoshi009 changed the title Update activity for sample application Deploy sample application in container app - Python Jan 5, 2026
@@ -0,0 +1,283 @@
name: Deploy Python Agent Framework to Azure Container Apps
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why this has to be in .github workflow folders? This sounds like it's specific to agent framework. Shouldn't it be moved to sample agent folder?

Copy link
Contributor Author

@tirthdoshi009 tirthdoshi009 Jan 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes it is specific to the agent framework. Since it's a github actions workflow it needs to be under .github. That's the reason to keep the path :
image

So it will only run on those specific changes.

--memory 1.0Gi \
--env-vars \
PORT=3978 \
AZURE_OPENAI_ENDPOINT=${{ secrets.AZURE_OPENAI_ENDPOINT }} \
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if someone wants to use some other llm?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a good point Rahul. The purpose of this workflow is help users test their changes without having to deploy any models. That's the reason of defaulting to one.

If one wants to use another model, the best way is locally running in that case.

--tail 50 \
--follow false

- name: Comment on PR with Deployment URL
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not fully following the this yml. Is the expectation to deploy this sample from this repo itself? What is the use case and business need? What if someone wants to use non-azure infrastructure?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah apologies, I might have not specified the context. We are working on an AI first project that needs verification of the packages. For example, if copilot makes any changes to the sdk, we want to ensure that the changes don't really affect the execution of the sdk.

This workflow helps to verify that the changes are deployed and verified correctly.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In that case, I don't think this is a right approach to validate the SDK. There is an entire E2E integration test feature being built right now that deploys the samples to the resource group and test different areas. In your case, you are just checking if the app is healthy or not, but that does not guarantee if the application components where changes were made is correct. Besides that, you are exposing the secrets in the pipeline in OSS, which any PR can expose secrets to outside world(obviously they will fork, but still there are number of reason we should avoid secrets in pipeline)

Copy link
Collaborator

@rahuldevikar761 rahuldevikar761 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes related to docker-container is seems somewhat specific to business need. I'm not seeing what is the requirement to deploy agent from the github repo itself.

@sellakumaran
Copy link
Contributor

Closing this old PR. Please create a new one if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.