Document Details
How To Enable Private Link Application Gateway
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.
Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents a clear Windows-first bias by listing the Azure Portal (GUI) and PowerShell methods before the Azure CLI approach. The PowerShell section is detailed and assumes the use of PowerShell or Azure Cloud Shell, which is more familiar to Windows users. While a CLI section is present (which is cross-platform), it is placed after the PowerShell section, and there are no explicit Linux- or Bash-specific examples or troubleshooting notes. No Linux-specific tools or workflows are highlighted.
Recommendations
- Reorder the technical pivots so that Azure CLI (which is cross-platform and preferred by many Linux users) appears before PowerShell, or at least give them equal prominence.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash-specific notes or troubleshooting tips where relevant.
- Where PowerShell is referenced, also mention that Azure Cloud Shell supports Bash, and provide equivalent Bash/CLI snippets for any PowerShell-specific logic.
- In the prerequisites and tool installation sections, include instructions for installing Azure CLI and PowerShell on Linux, and clarify that both are supported.
- Add a note in the introduction or prerequisites highlighting that all workflows can be completed from Linux, macOS, or Windows, and link to platform-specific setup guides.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
 Clean
|
| 2026-01-13 00:00 | #246 | completed |
Clean
|
| 2026-01-11 00:00 | #240 | completed |
Clean
|
| 2026-01-10 00:00 | #237 | completed |
Clean
|
| 2026-01-09 00:34 | #234 | completed |
Clean
|
| 2026-01-08 00:53 | #231 | completed |
Clean
|
| 2026-01-06 18:15 | #225 | cancelled |
Clean
|
| 2025-08-17 00:01 | #83 | cancelled |
Clean
|
| 2025-07-13 21:37 | #48 | completed |
Clean
|
| 2025-07-09 13:09 | #3 | cancelled |
Clean
|
| 2025-07-08 04:23 | #2 | cancelled |
Biased
|
Flagged Code Snippets
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.
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.
## 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.