API Management
284
Total Pages
229
Linux-Friendly Pages
55
Pages with Bias
19.4%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
594 issues found
Showing 476-500 of 594 flagged pages
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. The PowerShell example is given equal prominence to the CLI example, but there is no explicit mention of Linux/macOS alternatives for PowerShell. The CLI example is cross-platform, but the documentation does not clarify this or highlight Linux/macOS workflows. The prerequisites list both Azure CLI and Azure PowerShell without noting platform differences. There is minor bias in presenting PowerShell as a primary workflow without guidance for Linux/macOS users.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add a note that Azure PowerShell is primarily for Windows, and suggest Bash or CLI for Linux/macOS.
- Consider showing Azure CLI examples first, or labeling them as recommended for non-Windows platforms.
- Explicitly state platform compatibility in the prerequisites section.
Create Pull Request
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides Azure CLI and PowerShell examples for disabling routing to a regional gateway, but lists the Azure PowerShell cmdlet before the Azure CLI command in the tools list. There are no explicit Linux/macOS-specific examples or mentions, but the Azure CLI commands shown are cross-platform. The documentation does not reference Windows-only tools or patterns, but the ordering of PowerShell and CLI tools may subtly favor Windows users.
Recommendations
- List cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell) when describing options.
- Explicitly note that Azure CLI commands work on Linux/macOS as well as Windows.
- Where possible, provide Bash shell examples alongside Azure CLI commands to demonstrate Linux parity.
- Avoid referencing PowerShell as the primary tool unless the task is Windows-specific.
API Management
Backup and restore your Azure API Management instance for disaster recovery
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides detailed PowerShell examples first for both backup and restore operations, with Bash/Azure CLI examples presented after. The PowerShell focus may create friction for Linux/macOS users, as PowerShell is traditionally associated with Windows, even though cross-platform versions exist. However, the inclusion of Azure CLI (Bash) and REST API examples ensures Linux/macOS users can complete all tasks.
Recommendations
- Explicitly mention that Azure PowerShell is cross-platform and can be installed on Linux/macOS, linking to installation instructions for those platforms.
- Consider presenting Azure CLI (Bash) examples before PowerShell, or at least side-by-side, to better reflect cross-platform parity.
- Add a short note at the start of the examples section clarifying that all shown tools (PowerShell, CLI, REST) are supported on Windows, Linux, and macOS.
- Where possible, use neutral variable names and avoid assumptions about the user's shell environment.
API Management
Deploy a Self-Hosted Gateway to Azure Kubernetes Service
...to-deploy-self-hosted-gateway-azure-kubernetes-service.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists Windows/PowerShell options before Linux equivalents in the prerequisites section, specifically when describing how to create an Azure Kubernetes cluster. However, all deployment steps and examples use cross-platform tools (kubectl) and are not Windows-specific. No PowerShell-heavy or Windows-only tools are used in the main workflow.
Recommendations
- List Linux (Azure CLI) and Windows (PowerShell) options in parallel or clarify that both are supported equally.
- Consider mentioning that Azure CLI works on Windows, Linux, and macOS, and is generally recommended for cross-platform scenarios.
- If possible, provide explicit examples for both Azure CLI and PowerShell commands, or link to documentation that does so.
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides instructions primarily using the Azure portal and Azure CLI, with a brief mention of Azure PowerShell in the section about disabling routing to a regional gateway. The PowerShell cmdlet is referenced after the Azure CLI and REST API, but no Linux-specific tools or shell examples are given. However, the Azure CLI is cross-platform and the portal is OS-agnostic, so the bias is minimal. There are no Windows-only tools or patterns, and no exclusive PowerShell-heavy sections.
Recommendations
- Ensure parity by including Bash or shell script examples where relevant, especially for automation.
- Clarify that Azure CLI commands work on Linux, macOS, and Windows.
- If mentioning PowerShell, also mention Bash or other scripting options for Linux users.
- Consider linking to documentation about using Azure CLI on Linux/macOS.
API Management
Backup and restore your Azure API Management instance for disaster recovery
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides comprehensive instructions for backing up and restoring Azure API Management instances using PowerShell, Azure CLI (Bash), and REST API. However, PowerShell examples are presented first in each section, and the documentation assumes familiarity with PowerShell cmdlets and patterns, which are more common on Windows. While Azure CLI (Bash) and REST API examples are included, the prominence and ordering of PowerShell may create a perception of Windows-first bias.
Recommendations
- Present Azure CLI (Bash) examples before PowerShell, or at least alternate the order in different sections to avoid Windows-first impression.
- Explicitly note that PowerShell cmdlets can be used cross-platform (Windows, macOS, Linux) if true, or clarify any platform limitations.
- Where possible, provide additional context or links for users on Linux/macOS who may not have PowerShell installed by default.
- Ensure that all features and steps described are equally achievable via Azure CLI and REST API, and highlight any gaps or differences.
API Management
Deploy a Self-Hosted Gateway to Azure Kubernetes Service
...to-deploy-self-hosted-gateway-azure-kubernetes-service.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows/PowerShell (Azure PowerShell) as a method for creating an AKS cluster before Linux-centric alternatives (Azure CLI), but otherwise provides cross-platform instructions using kubectl and YAML files. No exclusive Windows tools or examples are present, and Linux users can follow all steps without friction.
Recommendations
- List Azure CLI as the first option for creating an AKS cluster, as it is more universally available and preferred in cross-platform scenarios.
- Explicitly note that all kubectl commands and YAML files are cross-platform and can be run from Linux, macOS, or Windows terminals.
- Consider providing example commands for both Bash (Linux/macOS) and PowerShell (Windows) if scripting is involved, though in this case kubectl commands are universal.
API Management
Quickstart: Create Azure API Management instance by using Bicep
.../blob/main/articles/api-management/quickstart-bicep.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all deployment and management steps. However, PowerShell is a Windows-centric tool, and its inclusion alongside CLI may subtly favor Windows users. In some sections, PowerShell examples are presented immediately after CLI, but not before. There are no Linux-specific tools (e.g., Bash, shell scripts) or explicit Linux/macOS guidance, but Azure CLI is cross-platform and is presented first in all cases.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Consider adding brief notes or links for Linux/macOS users, such as installation instructions for Azure CLI on those platforms.
- Explicitly state that PowerShell examples are primarily for Windows users, while CLI is recommended for Linux/macOS.
- If relevant, mention that Bicep can be used from Bash or other shells, not just PowerShell.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. Both tools are cross-platform, but PowerShell is still more commonly associated with Windows. The documentation does not provide Linux/macOS-specific guidance or examples (e.g., Bash scripts, shell usage), and PowerShell is presented equally alongside CLI, which may create friction for Linux/macOS users. However, Azure CLI is cross-platform and the examples are generic, so Linux users can complete the task.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, but is more commonly used on Windows.
- Add explicit Bash or shell script examples for Linux/macOS users, or note that Azure CLI commands work identically across platforms.
- Consider mentioning that Azure CLI is the recommended tool for Linux/macOS users.
- Add a short section or note about using Azure CLI and PowerShell on Linux/macOS, including installation links.
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but the PowerShell example is given equal prominence and detail. The prerequisites list Azure CLI and Azure PowerShell together, but does not mention Bash or other Linux-native tools. The PowerShell example is not marked as Windows-only, and both CLI and PowerShell are presented as equivalent options. The portal instructions are platform-neutral. There is minor bias in listing PowerShell as a primary tool, which may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
- Add explicit notes about cross-platform compatibility for Azure CLI and PowerShell.
- Consider providing Bash shell script examples for Linux users, or clarify that Azure CLI commands are suitable for Bash/zsh environments.
- Mention that Azure PowerShell can be installed on Linux/macOS, but Azure CLI is the default cross-platform tool.
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides Azure CLI and PowerShell examples for disabling routing to a regional gateway, but lists the PowerShell cmdlet ('set-azapimanagement') before the Azure CLI command ('az apim update'). There are no Linux-specific examples or explicit mention of Linux/macOS compatibility for the CLI commands. However, the main walkthrough and all critical steps are performed in the Azure portal, which is platform-agnostic. The CLI examples use Azure CLI, which is cross-platform, but PowerShell is mentioned alongside it, potentially implying Windows-first bias.
Recommendations
- Explicitly state that Azure CLI commands are cross-platform and can be used on Linux/macOS.
- Provide Linux/macOS-specific guidance or examples where relevant, such as shell syntax or installation instructions for Azure CLI.
- List Azure CLI examples before PowerShell examples to avoid Windows-first ordering.
- Clarify that PowerShell is available cross-platform, but highlight Azure CLI as the primary tool for Linux/macOS users.
API Management
Deploy a Self-Hosted Gateway to Azure Kubernetes Service
...to-deploy-self-hosted-gateway-azure-kubernetes-service.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows tools (Azure PowerShell) alongside Azure CLI and Azure Portal in the prerequisites, but does not provide Windows-specific examples or prioritize Windows tools elsewhere. All deployment steps use cross-platform tools (kubectl), and examples are generic. The only minor bias is listing Azure PowerShell before Linux equivalents in the prerequisites.
Recommendations
- Consider listing Azure CLI before Azure PowerShell in the prerequisites, as Azure CLI is cross-platform and more commonly used on Linux/macOS.
- Explicitly mention that all kubectl commands work on Windows, Linux, and macOS.
- If possible, provide links to Linux/macOS-specific guidance for creating AKS clusters (if any exists).
API Management
Backup and restore your Azure API Management instance for disaster recovery
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for backup and restore operations, but PowerShell examples are presented first and in greater detail. PowerShell is primarily a Windows-centric tool, and its prominence may create friction for Linux/macOS users. However, Azure CLI and REST API examples are also included, supporting cross-platform usage.
Recommendations
- Present Azure CLI examples before PowerShell, or at least equally, to emphasize cross-platform support.
- Expand CLI examples to cover managed identity scenarios, matching the detail provided for PowerShell.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Add notes clarifying that PowerShell Core is available on Linux/macOS, but Azure CLI is generally preferred for those platforms.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is most commonly used on Windows) and the explicit PowerShell example may create a Windows bias. Additionally, PowerShell is mentioned after Azure CLI, but both are given equal prominence. No Linux/macOS-specific tools or workflows are mentioned, and there are no explicit Linux/macOS examples or notes about platform parity.
Recommendations
- Clarify that Azure CLI is fully cross-platform and can be used on Linux/macOS as well as Windows.
- Add explicit notes or examples showing Azure CLI usage on Linux/macOS, such as shell syntax differences (e.g., bash vs PowerShell variable assignment).
- Consider mentioning that Azure PowerShell is available on Linux/macOS (via PowerShell Core), or provide guidance for Linux users.
- If possible, add troubleshooting tips or environment setup instructions for Linux/macOS users.
- Ensure that CLI examples use syntax compatible with bash/zsh, not just PowerShell.
API Management
Azure API Management virtual network injection - network resources
.../api-management/virtual-network-injection-resources.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is largely platform-neutral and does not provide command-line examples or tooling instructions that are specific to Windows or Linux. However, in the 'Related content' section, a link is provided to a PowerShell-based guide ('Connect virtual networks from different deployment models using PowerShell') without mentioning or linking to an equivalent Azure CLI or Linux-friendly approach. This subtly prioritizes Windows/PowerShell as the default automation method.
Recommendations
- In the 'Related content' section, add links to equivalent Azure CLI or ARM template documentation for connecting virtual networks, ensuring Linux/macOS users have clear, first-class guidance.
- Where PowerShell is referenced, clarify that Azure CLI and portal-based alternatives exist and provide links.
- Consider reviewing other cross-references throughout the documentation to ensure that automation and scripting guidance is not Windows/PowerShell-centric by default.
API Management
Azure API Management virtual network injection - network resources
.../api-management/virtual-network-injection-resources.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is generally platform-neutral, focusing on Azure networking concepts. However, there is a minor bias in the 'Related content' section, where a link is provided to a guide for connecting virtual networks using PowerShell, which is a Windows-centric tool. There are no explicit Linux/macOS command-line examples or references to cross-platform tools (such as Azure CLI), and PowerShell is mentioned before any Linux-equivalent tooling.
Recommendations
- In the 'Related content' section, add or prioritize links to cross-platform guides, such as connecting virtual networks using Azure CLI or Azure Portal.
- Where PowerShell is referenced, also mention or link to equivalent Azure CLI documentation, ensuring Linux/macOS users have clear guidance.
- Review other linked articles (e.g., VPN gateway configuration) to ensure Linux/macOS parity is maintained in referenced workflows.
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides instructions primarily via the Azure portal and Azure CLI, with a brief mention of Azure PowerShell as an alternative tool for disabling routing to a regional gateway. The PowerShell cmdlet is referenced after the Azure CLI example, and no Windows-specific tools or patterns are prioritized. There are no PowerShell-heavy sections, nor are Windows tools mentioned exclusively or before Linux equivalents. All CLI examples use Azure CLI, which is cross-platform. The only minor bias is listing PowerShell as an alternative tool, but this does not impact Linux/macOS users.
Recommendations
- Ensure that all command-line examples use Azure CLI (already done).
- If referencing PowerShell, clarify that Azure CLI is cross-platform and PowerShell is an alternative for Windows users.
- Consider adding explicit notes that all portal and CLI instructions are applicable to Linux/macOS users.
- If possible, provide Bash or shell script examples for automation alongside PowerShell examples.
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but the PowerShell example is given equal prominence and detail. The prerequisites list Azure CLI and Azure PowerShell together, but there are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell is primarily a Windows-centric tool, though it is cross-platform. The ordering of examples (CLI before PowerShell) is neutral, but the presence of PowerShell-specific instructions may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Add Bash shell examples for Azure CLI usage, demonstrating typical Linux/macOS workflows.
- Explicitly note that PowerShell is available cross-platform, but CLI is recommended for Linux/macOS users.
- Consider adding a section or callout for Linux/macOS users, highlighting any differences or best practices.
API Management
Deploy a Self-Hosted Gateway to Azure Kubernetes Service
...to-deploy-self-hosted-gateway-azure-kubernetes-service.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation briefly mentions Azure PowerShell as an option for creating an AKS cluster before mentioning Linux-friendly alternatives (Azure CLI and Portal). However, all deployment and operational examples use cross-platform tools (kubectl), and there are no Windows-specific commands, tools, or patterns prioritized. No critical steps are Windows-only.
Recommendations
- List Azure CLI as the first option for creating AKS clusters, as it is more universally available and preferred on Linux/macOS.
- Explicitly state that all deployment steps use cross-platform tools (kubectl) and are compatible with Linux/macOS terminals.
- Add a note clarifying that Azure PowerShell is optional and not required for Linux/macOS users.
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides command-line examples for disabling routing to a regional gateway using Azure CLI and references Azure PowerShell cmdlets. The PowerShell cmdlet (set-azapimanagement) is mentioned alongside Azure CLI, but no Linux/macOS-specific guidance or examples are provided. The Azure portal steps are platform-neutral, but in the CLI section, PowerShell is referenced before Linux alternatives, and no Bash or Linux-specific nuances are discussed.
Recommendations
- Ensure parity by providing explicit Bash/Linux/macOS examples where Azure CLI is used, including any OS-specific nuances.
- When referencing Azure PowerShell, clarify its cross-platform support or provide alternative instructions for Linux/macOS users.
- If PowerShell is mentioned, also mention Bash or other shells, and clarify that Azure CLI works on all platforms.
- Consider adding a note that all Azure CLI commands are cross-platform and can be run on Windows, Linux, and macOS.
API Management
Deploy a Self-Hosted Gateway to Azure Kubernetes Service
...to-deploy-self-hosted-gateway-azure-kubernetes-service.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows/PowerShell (Azure PowerShell) as an option for creating an AKS cluster before Linux alternatives (Azure CLI), but provides no actual PowerShell-specific examples. All deployment and verification steps use cross-platform tools (kubectl), and no Windows-only tools or patterns are shown. The bias is limited to listing Windows/PowerShell before Linux/CLI in the prerequisites.
Recommendations
- List Azure CLI before Azure PowerShell in the prerequisites, as Azure CLI is cross-platform and more commonly used on Linux/macOS.
- Explicitly note that all deployment steps use cross-platform tools (kubectl), and that the process is OS-agnostic.
- If mentioning Azure PowerShell, also mention that it is available on Linux/macOS, or clarify its platform support.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell. PowerShell is included as a primary workflow, which is Windows-centric, and is presented equally alongside CLI. There is no explicit Linux/macOS bias, but PowerShell is not natively available on most Linux/macOS systems, and no Bash or shell script examples are given. The CLI example is cross-platform, but PowerShell's inclusion and prominence may create friction for Linux/macOS users.
Recommendations
- Clarify that Azure PowerShell is available cross-platform (via PowerShell Core), but may require installation on Linux/macOS.
- Consider adding Bash or shell script examples for Linux/macOS users, especially for common tasks.
- Explicitly note that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users.
- If PowerShell is used, provide guidance for Linux/macOS installation or alternatives.
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides parity between Azure CLI and Azure PowerShell for importing SOAP APIs, but PowerShell examples are given equal prominence to CLI examples, and PowerShell is a Windows-centric tool. The prerequisites list both Azure CLI and PowerShell, but does not clarify that PowerShell is cross-platform (though it is, many users associate it with Windows). The portal instructions are platform-neutral. Azure CLI is shown before PowerShell, but both are presented as tabs, so ordering bias is minimal. No Linux-specific tools or shell examples are given, but Azure CLI is the standard cross-platform tool.
Recommendations
- Clarify that Azure PowerShell is available cross-platform (Windows, Linux, macOS) to avoid confusion.
- Consider adding a note for Linux/macOS users about installing Azure CLI and PowerShell, linking to platform-specific instructions.
- Explicitly mention that the Azure CLI example works on all major OSes, while PowerShell is also available cross-platform.
- If possible, provide a Bash shell example for invoking Azure CLI, to reinforce Linux parity.
API Management
Azure API Management virtual network injection - network resources
.../api-management/virtual-network-injection-resources.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is largely platform-neutral and focuses on Azure networking concepts, but there is a minor instance of Windows bias in the 'Related content' section, where a PowerShell-based guide is referenced for connecting virtual networks before any Linux/CLI alternatives are mentioned.
Recommendations
- In the 'Related content' section, add or prioritize links to equivalent Azure CLI or Azure Portal guides for connecting virtual networks, ensuring Linux/macOS users see relevant options.
- Where PowerShell is referenced, clarify that Azure CLI or Portal alternatives exist and provide links to those resources.
- Review cross-referenced articles to ensure parity in example coverage (PowerShell, CLI, Portal) and update links as needed.
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation primarily uses Azure Portal and Azure CLI examples, but when mentioning scripting tools for managing API Management instances, it lists Azure PowerShell before Azure CLI and REST API. The PowerShell cmdlet ('set-azapimanagement') is referenced alongside CLI and REST API, but no Linux/macOS-specific guidance or parity is provided. However, the CLI examples are present and usable on Linux/macOS, and no critical steps are Windows-only.
Recommendations
- When listing scripting tools, mention Azure CLI and REST API before PowerShell, or group them equally.
- Add explicit notes that Azure CLI is cross-platform and usable on Linux/macOS.
- Provide sample scripts or command-line snippets for both Azure CLI and PowerShell where appropriate.
- If referencing PowerShell, clarify that Azure CLI is recommended for Linux/macOS users.
- Ensure screenshots and portal instructions are not Windows-specific (e.g., avoid referencing Windows-only UI elements).