Skip to content

Revise network traffic security section for clarity - #546

Open
spotakash wants to merge 2 commits into
MicrosoftDocs:mainfrom
spotakash:patch-1
Open

Revise network traffic security section for clarity#546
spotakash wants to merge 2 commits into
MicrosoftDocs:mainfrom
spotakash:patch-1

Conversation

@spotakash

Copy link
Copy Markdown

Updated the section on network traffic security to clarify the flow of traffic and the use of Azure ExpressRoute. Added notes on ExpressRoute peering models and architectural considerations for private connectivity.

Updated the section on network traffic security to clarify the flow of traffic and the use of Azure ExpressRoute. Added notes on ExpressRoute peering models and architectural considerations for private connectivity.
@prmerger-automator

Copy link
Copy Markdown
Contributor

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

@prmerger-automator

Copy link
Copy Markdown
Contributor

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

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 6fb94a7:

💡 Validation status: suggestions

File Status Preview URL Details
data-integration/gateway/service-gateway-onprem-indepth.md 💡Suggestion Details

data-integration/gateway/service-gateway-onprem-indepth.md

  • Line 52, Column 79: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/azure/expressroute/expressroute-faqs?#microsoft-peering' 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.

@v-dirichards
v-dirichards requested a review from Copilot July 29, 2026 15:32
@v-dirichards

Copy link
Copy Markdown
Contributor

@whhender

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

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the on-premises gateway architecture documentation to clarify the network traffic flow between the gateway, Azure Relay, and the Power BI backend, and to add guidance on how Azure ExpressRoute peering models influence private connectivity design choices.

Changes:

  • Clarifies the end-to-end traffic flow and describes how ExpressRoute can avoid public internet traversal.
  • Adds an admonition note explaining how ExpressRoute peering models affect connectivity and suggests an architecture pattern when Private Peering is required.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread data-integration/gateway/service-gateway-onprem-indepth.md
Comment thread data-integration/gateway/service-gateway-onprem-indepth.md Outdated
@whhender

Copy link
Copy Markdown
Contributor

@spotakash - There are a couple of suggestions from GitHub. Can you review and apply those?

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 0828dbe:

💡 Validation status: suggestions

File Status Preview URL Details
data-integration/gateway/service-gateway-onprem-indepth.md 💡Suggestion Details

data-integration/gateway/service-gateway-onprem-indepth.md

  • Line 52, Column 79: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/azure/expressroute/expressroute-faqs#microsoft-peering' 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.

@spotakash

Copy link
Copy Markdown
Author

@whhender applied fix for suggestion, please check and proceed for next steps

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