Document Details

How To Enable Private Link Application Gateway
Home / Scan #41 / How To Enable Private Link Application Gateway
Sad Tux - Windows bias detected
This page contains Windows bias

About This Page

This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
GitHub View on GitHub 📚 View on Microsoft Learn

Bias Analysis

Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents three main pivots: Portal, PowerShell, and Azure CLI. The PowerShell (Windows-centric) section is given equal prominence to the CLI, but is listed before the CLI in the zone_pivot_groups and in the page structure. There are no Linux shell (bash) or cross-platform scripting examples outside of Azure CLI, and PowerShell is emphasized as a primary automation method. There are no explicit Linux-specific instructions or troubleshooting notes, nor are there references to Linux tools or environments.
Recommendations
  • Ensure that the Azure CLI section is given equal or higher prominence than PowerShell, as CLI is cross-platform and preferred by many Linux users.
  • Add explicit bash shell examples or scripts for common operations, especially for steps that involve string manipulation or resource ID construction.
  • Include troubleshooting notes or tips relevant to Linux environments (e.g., file permissions, path differences, CLI installation on Linux).
  • Clarify that Azure CLI commands work natively on Linux, macOS, and Windows, and provide links to Linux installation guides.
  • Where PowerShell is mentioned, note that PowerShell Core is cross-platform, but also provide bash alternatives where possible.
  • Consider adding a table or section comparing PowerShell and CLI usage, highlighting cross-platform compatibility.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2025-07-12 23:44 #41 cancelled Biased Biased
2025-07-12 00:58 #8 cancelled Clean Clean
2025-07-10 05:06 #7 processing Clean Clean

Flagged Code Snippets

1. Use [New-AzFrontDoorCdnOriginGroupLoadBalancingSettingObject](/powershell/module/az.cdn/new-azfrontdoorcdnorigingrouploadbalancingsettingobject) to create an in-memory object for storing load balancing settings.

    
1. Run [New-AzFrontDoorCdnOriginGroup](/powershell/module/az.cdn/new-azfrontdoorcdnorigingroup) to create an origin group that contains your application gateway.

    
1. Get the frontend IP configuration name of the Application Gateway with the [Get-AzApplicationGatewayFrontendIPConfig](/powershell/module/az.network/get-azapplicationgatewayfrontendipconfig) command.

    
1. Use the [New-AzFrontDoorCdnOrigin](/powershell/module/az.cdn/new-azfrontdoorcdnorigin) command to add your application gateway to the origin group.

    
    > [!NOTE]
    > `SharedPrivateLinkResourceGroupId` is the name of the Azure Application Gateway frontend IP configuration.

## Approve the private endpoint

1. Run [Get-AzPrivateEndpointConnection](/powershell/module/az.network/get-azprivateendpointconnection) to retrieve the connection name of the private endpoint connection that needs approval.

    
2. Run [Approve-AzPrivateEndpointConnection](/powershell/module/az.network/approve-azprivateendpointconnection) to approve the private endpoint connection details. Use the *Name* value from the output in the previous step for approving the connection.

    
## Complete Azure Front Door setup

Use the [New-AzFrontDoorCdnRoute](/powershell/module/az.cdn/new-azfrontdoorcdnroute) command to create a route that maps your endpoint to the origin group. This route forwards requests from the endpoint to your origin group.