Skip to content

Conversation

@gukoff
Copy link
Contributor

@gukoff gukoff commented Jan 21, 2026

Source (Microsoft-internal link) - see this Viva Engage post and its referenced sources: https://engage.cloud.microsoft/main/org/microsoft.com/threads/eyJfdHlwZSI6IlRocmVhZCIsImlkIjoiMzY4MTUzMzQxMjQ4MzA3MiJ9?trk_copy_link=V2_HTML

These claims about code interpreter need verification. Can we get a PM to review?

In particular, there's no authoritative source for this information:

  • Code Interpreter sandbox runs in the same Azure region as your Foundry project
  • The sandbox doesn't inherit your agent subnet configuration, and dynamic sessions are prevented from making outbound network requests. (<- this seems to be true when I experiment with Code Interpreter)

@prmerger-automator
Copy link
Contributor

@gukoff : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 028017e:

💡 Validation status: suggestions

File Status Preview URL Details
articles/ai-foundry/default/agents/how-to/tools/code-interpreter.md 💡Suggestion Details

articles/ai-foundry/default/agents/how-to/tools/code-interpreter.md

  • Line 258, Column 143: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/azure/container-apps/sessions-code-interpreter' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 84d5568:

✅ Validation status: passed

File Status Preview URL Details
articles/ai-foundry/default/agents/how-to/tools/code-interpreter.md ✅Succeeded

For more details, please refer to the build report.

@alvinashcraft
Copy link
Contributor

#assign-reviewer: @lindazqli

@alvinashcraft
Copy link
Contributor

@lindazqli Can you review whether this information is correct from a product standpoint? It looks good from the docs formatting/style side of things.

@v-regandowner
Copy link
Contributor

@lindazqli

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged C+L Pull Request Review Team label label Jan 21, 2026
- **Region**: The Code Interpreter sandbox runs in the same Azure region as your Foundry project.
- **Session lifetime**: A Code Interpreter session is active for up to 1 hour, with an idle timeout (see the Important note earlier in this article).
- **Isolation**: Each session runs in an isolated environment. If your agent invokes Code Interpreter concurrently in different conversations, separate sessions are created.
- **Network isolation and internet access**: The sandbox doesn't inherit your agent subnet configuration, and dynamic sessions are prevented from making outbound network requests.
Copy link

Choose a reason for hiding this comment

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

Would be good to properly document the expected behavior. For instance, what if I want the code interpreter to make requests to read/write files on my storage account - would this be possible? Or is any API call gets blocked? Can we control this?

@github-actions
Copy link

github-actions bot commented Feb 5, 2026

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

@github-actions github-actions bot added the inactive This PR is inactive for more than 14 days label Feb 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants