Update virtual-networks.md with network isolation note #615
Conversation
Added a note about network isolation support in the Foundry portal.
|
@aktsuda : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 5f50151: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
This PR adds a NOTE callout to inform users about network isolation limitations in the new Foundry portal experience, directing them to use alternative methods (classic portal, SDK, or CLI) when network isolation is enabled.
- Adds informational NOTE about network isolation support limitations
- Provides guidance on alternative access methods for users with network isolation enabled
| > See the [FAQ article](../faq.yml#virtual-networking) for common questions when working with Virtual Networks. | ||
| > [!NOTE] | ||
| > End-to-end network isolation is not supported in the new Foundry portal experience. Please use the classic Foundry portal experience or the SDK or CLI to securely access your Foundry projects when network isolation, PNA disabled Foundry with a private endpoint and virutal network injected Agents, is enabled. |
There was a problem hiding this comment.
Spelling error: "virutal" should be "virtual".
| > End-to-end network isolation is not supported in the new Foundry portal experience. Please use the classic Foundry portal experience or the SDK or CLI to securely access your Foundry projects when network isolation, PNA disabled Foundry with a private endpoint and virutal network injected Agents, is enabled. | |
| > End-to-end network isolation is not supported in the new Foundry portal experience. Please use the classic Foundry portal experience or the SDK or CLI to securely access your Foundry projects when network isolation, PNA disabled Foundry with a private endpoint and virtual network injected Agents, is enabled. |
| > See the [FAQ article](../faq.yml#virtual-networking) for common questions when working with Virtual Networks. | ||
| > [!NOTE] | ||
| > End-to-end network isolation is not supported in the new Foundry portal experience. Please use the classic Foundry portal experience or the SDK or CLI to securely access your Foundry projects when network isolation, PNA disabled Foundry with a private endpoint and virutal network injected Agents, is enabled. |
There was a problem hiding this comment.
Sentence structure issue: The phrase "network isolation, PNA disabled Foundry with a private endpoint and virutal network injected Agents, is enabled" is unclear and difficult to parse. Consider restructuring for clarity, such as: "when you have enabled network isolation (a PNA-disabled Foundry with a private endpoint and virtual network injected Agents)".
| > End-to-end network isolation is not supported in the new Foundry portal experience. Please use the classic Foundry portal experience or the SDK or CLI to securely access your Foundry projects when network isolation, PNA disabled Foundry with a private endpoint and virutal network injected Agents, is enabled. | |
| > End-to-end network isolation isn't supported in the new Foundry portal experience. Use the classic Foundry portal, SDK, or CLI to securely access your Foundry projects when you've enabled network isolation (a PNA-disabled Foundry with a private endpoint and virtual network injected Agents). |
| > See the [FAQ article](../faq.yml#virtual-networking) for common questions when working with Virtual Networks. | ||
| > [!NOTE] | ||
| > End-to-end network isolation is not supported in the new Foundry portal experience. Please use the classic Foundry portal experience or the SDK or CLI to securely access your Foundry projects when network isolation, PNA disabled Foundry with a private endpoint and virutal network injected Agents, is enabled. |
There was a problem hiding this comment.
Writing style issue: The phrase "Please use" should be rewritten in imperative mood without "Please". According to Microsoft Writing Style Guide conventions, instructions should use imperative mood directly. Suggested revision: "Use the classic Foundry portal experience or the SDK or CLI to securely access..."
| > [!NOTE] | ||
| > End-to-end network isolation is not supported in the new Foundry portal experience. Please use the classic Foundry portal experience or the SDK or CLI to securely access your Foundry projects when network isolation, PNA disabled Foundry with a private endpoint and virutal network injected Agents, is enabled. | ||
|
|
There was a problem hiding this comment.
[nitpick] Extra blank line: Remove the extra blank line. One blank line after the NOTE block is sufficient for proper spacing.
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
3 participants
Added a note about network isolation support in the Foundry portal.