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
Bias Types:
⚠️
powershell_heavy
⚠️
windows_tools
⚠️
windows_first
Summary:
The documentation provides comprehensive coverage for both Azure CLI and PowerShell, but the PowerShell section is notably detailed and includes full sample scripts, which may favor Windows users. PowerShell is a Windows-centric tool, and its inclusion as a primary automation method can be seen as a Windows bias. The documentation does not mention or provide examples for Linux-native scripting environments (such as Bash), nor does it clarify cross-platform PowerShell Core compatibility. The order of presentation (CLI before PowerShell) is good, but the heavy PowerShell focus and lack of Linux-native examples indicate some Windows bias.
Recommendations:
- Add explicit Bash shell script examples for Linux/macOS users, especially for automation scenarios.
- Clarify that Azure CLI commands work cross-platform and can be run in Bash, Zsh, or other Linux shells.
- If PowerShell examples are included, specify whether they are compatible with PowerShell Core (cross-platform) or only Windows PowerShell.
- Consider including a section or note for Linux users, highlighting any differences or prerequisites.
- Ensure parity in the depth and complexity of examples between CLI and PowerShell sections.
Create pull request
Flagged Code Snippets
## Use PowerShell
This section shows you how to create a private endpoint for a topic or domain using PowerShell. Here's a sample script with comments.
### Approve a private endpoint connection
The following sample PowerShell snippet shows you how to approve a private endpoint.
> [!NOTE]
> The steps shown in this section are for topics. You can use similar steps to approve private endpoints for **domains**.
### Reject a private endpoint connection
The following example shows you how to reject a private endpoint using PowerShell. You can get the GUID for the private endpoint from the result of the previous GET command.
> [!NOTE]
> The steps shown in this section are for topics. You can use similar steps to reject private endpoints for **domains**.