Azure Resource Manager
1002
Total Pages
808
Linux-Friendly Pages
194
Pages with Bias
19.4%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
492 issues found
Showing 51-75 of 492 flagged pages
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/managed-applications/tutorial-create-managed-app-with-custom-provider.md
...ns/tutorial-create-managed-app-with-custom-provider.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is used exclusively for scripting storage uploads, with no Bash or Linux shell equivalents provided. Windows/PowerShell tooling is presented first and in detail, while Linux alternatives are omitted. The use of Windows-specific tools (PowerShell cmdlets like Connect-AzAccount, New-AzResourceGroup, etc.) is prominent, and there is no mention of cross-platform or Linux-compatible approaches for these steps. Azure CLI is used for deployment, but the initial artifact upload relies solely on PowerShell, which is not native to Linux environments.
Recommendations
- Provide Bash/Azure CLI examples for uploading the application package to Azure Storage, alongside or before PowerShell examples.
- Explicitly mention cross-platform compatibility and clarify which steps can be performed on Linux/macOS.
- Add notes or links to documentation for Linux users, including installation and usage of Azure CLI and azcopy.
- Where PowerShell is used, offer equivalent Bash or Azure CLI commands to ensure Linux parity.
- Review all scripting sections to ensure both Windows and Linux users are supported equally.
Create Pull Request
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/azure-services-resource-providers.md
...anager/management/azure-services-resource-providers.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page demonstrates some Windows bias. It references Windows-specific tools (e.g., PowerShell) and APIs (e.g., Windows Azure Service Management API), and provides PowerShell examples alongside Azure CLI and Python. The mention of 'Azure Serial Console for Windows' and 'WindowsIoT' as services further reinforces the Windows-centric approach. In the 'Find resource provider' section, PowerShell is presented before Python, and the registration warning references Windows Azure Service Management API without mentioning Linux alternatives.
Recommendations
- Add explicit Linux/Bash examples alongside PowerShell, especially in 'Find resource provider' and other command-line sections.
- Reference cross-platform APIs or tools where possible, or clarify platform-specific limitations.
- When listing services or tools, avoid Windows-first ordering; present Linux and cross-platform options equally.
- In registration and security warnings, mention Linux/Unix equivalents or clarify that the advice applies to all platforms.
- For services like 'Azure Serial Console for Windows' and 'WindowsIoT', provide links or notes about Linux alternatives or clarify platform support.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/create-private-link-access-commands.md
...ager/management/create-private-link-access-commands.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples, but PowerShell is featured equally and sometimes before Linux-native tools. There are no explicit Linux shell (bash) or scripting examples, and PowerShell is a Windows-centric tool. References to PowerShell and its cmdlets may bias the documentation toward Windows users. REST API examples are platform-neutral, but there are no bash or Linux-specific scripting examples or notes. In the 'Add private endpoint' section, PowerShell is listed before CLI, and there is no mention of Linux-specific guidance.
Recommendations
- Add explicit bash/shell scripting examples for Linux users alongside PowerShell examples.
- Ensure that Azure CLI examples are always listed before PowerShell, as CLI is cross-platform.
- Include notes or sections highlighting any Linux-specific considerations or troubleshooting.
- Where PowerShell is referenced, clarify that Azure CLI is recommended for Linux/macOS users.
- Add links to Linux-specific documentation or tutorials where relevant.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/includes/tags.md
...les/azure-resource-manager/management/includes/tags.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. Azure PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI in every example demonstrates a 'powershell_heavy' and 'windows_tools' bias. Additionally, PowerShell is always presented immediately after Azure CLI, which can be interpreted as a 'windows_first' ordering, especially since no explicit Linux shell (such as Bash) or scripting examples are provided. There are no Linux-specific or cross-platform shell scripting examples, and the documentation does not mention or demonstrate usage from a Linux environment beyond the CLI, which is cross-platform.
Recommendations
- Add explicit Bash or shell scripting examples for Linux users, especially for scenarios where scripting is common.
- Clarify in the documentation that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Consider including examples using other cross-platform tools (e.g., REST API via curl, Python SDK) to provide parity for non-Windows users.
- If PowerShell is included, note that PowerShell Core is cross-platform, or provide both Windows PowerShell and Bash equivalents where possible.
- Reorder or randomize the presentation of CLI and PowerShell examples, or group them under a 'Command-line' section to avoid implicit prioritization.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/manage-resources-rest.md
...e-resource-manager/management/manage-resources-rest.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication and making REST API calls. However, Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some cases, PowerShell-specific patterns (such as Invoke-WebRequest) are used without mentioning Linux-native alternatives (e.g., curl or httpie in bash). Additionally, links to further deployment instructions reference Visual Studio Code and PowerShell, which are more commonly associated with Windows environments. There are no explicit Linux-only examples or mentions of Linux-native scripting environments beyond the use of curl.
Recommendations
- Provide bash and curl-only examples (without Azure CLI) for authentication and REST calls, to support Linux and macOS users who may not use PowerShell.
- When listing tabs for code examples, consider listing Azure CLI (bash) first, as it is cross-platform, and PowerShell second.
- Include references to Linux-native tools (e.g., httpie, wget) where appropriate.
- Add a section or callout explicitly stating that all REST API operations can be performed from Linux/macOS terminals using standard tools.
- When referencing further documentation, balance links to PowerShell and Visual Studio Code with links to Linux-friendly tools and editors.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/microsoft-resources-move-regions.md
...manager/management/microsoft-resources-move-regions.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by using Windows-style file paths (e.g., c:\export), referencing only Windows file system conventions, and omitting Linux/macOS equivalents. Both Azure PowerShell and Azure CLI examples use Windows paths, and there are no explicit Linux/macOS examples or notes about cross-platform usage. The documentation also links to deployment instructions that reference PowerShell, reinforcing a Windows-centric approach.
Recommendations
- Provide Linux/macOS examples using appropriate file paths (e.g., /home/user/export or ./export).
- Add notes clarifying that Azure CLI and PowerShell are cross-platform, and show how to run them on Linux/macOS.
- When giving file path parameters, show both Windows and Linux/macOS formats side by side.
- Link to deployment instructions that cover Bash or generic CLI usage, not just PowerShell.
- Explicitly mention any platform-specific considerations or differences in behavior.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/move-limitations/classic-model-move-limitations.md
...ent/move-limitations/classic-model-move-limitations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation references Azure PowerShell before Azure CLI when listing move operations, which suggests a Windows-first bias. There are no explicit Linux or cross-platform shell examples, and no mention of Bash or Linux-specific guidance. The examples and instructions focus on REST API calls and PowerShell, with no parity for Linux users.
Recommendations
- List Azure CLI before or alongside Azure PowerShell when mentioning supported tools.
- Provide explicit Bash/Azure CLI command examples for common operations, not just REST API or PowerShell.
- Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Add notes or sections addressing Linux/macOS users to ensure parity in guidance.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/move-limitations/cloud-services-extended-support.md
...nt/move-limitations/cloud-services-extended-support.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation references Azure PowerShell before Azure CLI and does not provide explicit Linux-specific examples or guidance. The mention of Azure PowerShell (commonly associated with Windows environments) before Azure CLI, and the lack of Linux or Bash-specific instructions, indicates a Windows-first bias. There are no Linux command-line examples or references to Linux tools.
Recommendations
- List Azure CLI before Azure PowerShell when presenting cross-platform options, or mention both together to avoid implying a preference.
- Provide explicit Linux/Bash examples for common operations, such as using Azure CLI commands in a Bash shell.
- Clarify that all operations can be performed from Linux, macOS, or Windows, and link to platform-specific instructions if available.
- Avoid implying that PowerShell is the default or primary method, especially for cross-platform documentation.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/request-limits-and-throttling.md
...ce-manager/management/request-limits-and-throttling.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided in detail, including both direct REST calls and Az module cmdlets, with additional debugging tips. These PowerShell examples appear before Azure CLI examples, and the only referenced scripting language outside of C# is PowerShell. There are no Bash/cURL or Linux-native scripting examples, and the PowerShell examples assume a Windows-centric workflow. The Azure CLI examples, while present, are less detailed and come after the PowerShell section.
Recommendations
- Add Bash/cURL examples for retrieving response headers, as these are common on Linux and macOS.
- Present Azure CLI examples before or alongside PowerShell examples to avoid the impression of Windows-first bias.
- Include examples using common Linux tools (e.g., grep, jq) to parse headers from REST API responses.
- Explicitly mention that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
- If referencing PowerShell, clarify that PowerShell Core is also available cross-platform, or provide examples using both Windows PowerShell and PowerShell Core.
- Ensure that all code snippets and debugging instructions are available for both Windows and Linux environments.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/preview-features.md
.../azure-resource-manager/management/preview-features.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides examples for the Azure Portal, Azure CLI, and Azure PowerShell. However, it shows a bias towards Windows environments by including extensive Azure PowerShell examples (a Windows-centric tool) and referencing PowerShell cmdlets throughout. The PowerShell examples are given equal prominence to Azure CLI, despite PowerShell being primarily used on Windows. There is no mention of Bash, shell scripting, or Linux-native tools, and no explicit Linux-specific guidance. The documentation also refers to the Azure Portal, which is cross-platform, but the command-line examples are limited to Azure CLI and PowerShell, with PowerShell being a Windows-first tool.
Recommendations
- Add explicit Bash or shell scripting examples for Linux users, especially for automation scenarios.
- Clarify that Azure CLI is cross-platform and highlight its use on Linux/macOS.
- De-emphasize PowerShell as a primary automation tool unless parity is provided for Linux users (e.g., PowerShell Core).
- Include a note or section about using Azure CLI in Bash on Linux, and provide sample commands with typical Linux shell usage (e.g., piping, jq for JSON parsing).
- If PowerShell is mentioned, clarify that PowerShell Core is available on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
- Consider adding REST API curl examples, which are universally available on Linux.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocate-evaluate.md
...azure-resource-manager/management/relocate-evaluate.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows/Azure bias by exclusively referencing Azure-specific tools and workflows, and by providing only PowerShell-based or Azure Portal instructions (e.g., for moving public IPs), without mentioning Linux CLI equivalents or cross-platform tools. There are no examples or guidance for Linux users, nor are Linux-native tools or scripts referenced. The documentation assumes the use of Azure and Windows-centric management patterns throughout.
Recommendations
- Include equivalent Azure CLI (az) commands alongside or instead of PowerShell/Portal instructions, as Azure CLI is cross-platform and widely used on Linux.
- When referencing automation or scripting, provide examples in both PowerShell and Bash (or Python), or explicitly mention that scripts can be written in any language supported by the user's environment.
- Reference cross-platform tools (such as Azure CLI, Terraform, or Ansible) for discovery and automation, not just Azure Portal or PowerShell.
- When linking to documentation (e.g., for moving public IPs), ensure that both PowerShell and CLI (az) instructions are included or linked.
- Explicitly state that all procedures can be performed from Linux, macOS, or Windows, and provide guidance for non-Windows users where appropriate.
- Consider including a section or callout for Linux-specific considerations, especially for teams that may not use Windows-based tooling.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-app-service.md
...anager/management/relocation/relocation-app-service.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates Windows bias by referencing Windows-specific paths (e.g., %HOME%\site), mentioning Kudu and FTP credentials (commonly used in Windows workflows), and providing links to PowerShell-based cloning guides as the only 'Next steps'. Examples and terminology (such as session affinity and Kudu) are presented with Windows conventions first or exclusively. There is a lack of explicit Linux or cross-platform command-line examples (e.g., Bash, Azure CLI), and Linux-specific considerations (such as file permissions, case sensitivity, or deployment patterns) are not addressed.
Recommendations
- Include Linux/Bash examples alongside or before PowerShell examples, especially for tasks like app cloning and backup/restore.
- Reference Azure CLI commands in addition to PowerShell for resource management and deployment steps.
- Clarify that Kudu and FTP credentials are available and relevant for both Windows and Linux App Service plans, or provide Linux-specific alternatives.
- Discuss Linux-specific considerations, such as file system case sensitivity, permissions, and deployment patterns (e.g., zip deploy, container-based workflows).
- Balance references to Windows paths (e.g., %HOME%\site) with Linux equivalents (e.g., $HOME/site), and explain any differences in environment variables or file system structure.
- Add links to Linux-focused documentation or guides in the 'Next steps' section.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-container-registry.md
...management/relocation/relocation-container-registry.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by frequently providing PowerShell examples (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster) without equivalent Bash or Linux shell alternatives. Windows/PowerShell commands are often mentioned before or instead of cross-platform Azure CLI commands, and some steps reference Windows-centric tools (e.g., unzipping a .zip file without specifying platform-agnostic methods). Linux-specific instructions, such as Bash scripts or command-line patterns, are underrepresented or missing in several key workflow steps.
Recommendations
- Provide equivalent Bash or Linux shell examples for all PowerShell commands (e.g., show how to enumerate repositories/tags and import images using Azure CLI and Bash).
- List Azure CLI (cross-platform) commands before PowerShell commands when both are available, or present them side-by-side.
- Explicitly mention Linux/macOS methods for tasks like unzipping files, scripting, and file manipulation.
- Avoid using Windows-specific tools or terminology exclusively; ensure all tooling and instructions are platform-agnostic or have clear alternatives.
- Add notes or sections clarifying any platform-specific differences in workflow, especially for automation and scripting.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-firewall.md
...e-manager/management/relocation/relocation-firewall.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides step-by-step instructions for relocating Azure Firewall using the Azure Portal and PowerShell, but does not include examples or guidance for Linux users or cross-platform CLI tools. PowerShell is featured as the only command-line automation method, and references to creating firewall policies or migrating configurations are linked to PowerShell-specific guides. There are no Bash, Azure CLI, or Linux shell examples, nor is there mention of alternative tooling or scripting approaches for non-Windows environments.
Recommendations
- Add Azure CLI (az) examples alongside PowerShell for all automation steps, including template export, modification, and deployment.
- Include Bash shell script samples for Linux users where applicable.
- Reference cross-platform documentation and tools, such as Azure CLI, before or alongside PowerShell.
- Ensure links to migration and policy creation guides include Azure CLI and REST API options, not just PowerShell.
- Explicitly state that all steps can be performed from Linux, macOS, or Windows, and provide platform-agnostic instructions where possible.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-functions.md
...-manager/management/relocation/relocation-functions.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific concepts (such as the %HOME% path variable) and mentioning Azure PowerShell alongside Azure CLI as deployment options, without providing parity for Linux-specific tools or examples. The examples and instructions do not include Linux shell equivalents, and Windows terminology appears before or instead of Linux alternatives. There is also a lack of explicit Linux-based deployment or scripting examples, and no mention of Linux-specific patterns or considerations beyond a brief note about mounting shares.
Recommendations
- Add Linux shell (bash) examples alongside or before PowerShell examples for deployment and scripting tasks.
- Replace or supplement Windows path variables (e.g., %HOME%) with Linux equivalents (e.g., $HOME) and clarify cross-platform differences.
- Explicitly mention Linux tools and workflows (such as Bash scripts, SSH, or Linux-based CI/CD pipelines) where relevant.
- Ensure that instructions and terminology are platform-neutral or provide both Windows and Linux variants.
- Highlight any Linux-specific considerations or best practices for Azure Functions, especially for file storage, authentication, and deployment.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-private-link.md
...nager/management/relocation/relocation-private-link.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as a primary automation option before Azure CLI, and does not provide explicit Linux-specific instructions or examples. There is no mention of Bash, Linux shell, or cross-platform scripting, and the examples and tool references (PowerShell, Azure portal) are more familiar to Windows users. Linux users may find the guidance less approachable due to the lack of parity in examples and tool recommendations.
Recommendations
- Provide explicit Linux/Bash examples alongside PowerShell, especially for command-line operations.
- List Azure CLI (which is cross-platform) before PowerShell when suggesting automation tools.
- Include references to Linux-native tools or shell environments where relevant.
- Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide sample commands.
- Ensure that all steps and screenshots are platform-agnostic or provide alternatives for both Windows and Linux users.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-event-hub.md
...-manager/management/relocation/relocation-event-hub.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell instructions and referencing Windows-centric tools (Azure PowerShell, Get-AzLocation) without offering equivalent Linux or cross-platform CLI examples. The PowerShell tab is present, but there is no Azure CLI tab or bash/shell example for Linux users. Where command-line instructions are given, they are exclusively for PowerShell, and links to Azure CLI are only mentioned in passing, not demonstrated. This may hinder Linux users or those preferring cross-platform tools from following the guide effectively.
Recommendations
- Add an Azure CLI tab alongside the PowerShell and portal tabs in all relevant sections, with full CLI command examples for each step.
- Where region codes are obtained via PowerShell (Get-AzLocation), provide the equivalent Azure CLI command (az account list-locations) and example output.
- Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI, and provide instructions for downloading and using the CLI.
- Ensure screenshots and instructions are not exclusively portal/Windows-centric; include CLI output and Linux terminal screenshots where appropriate.
- Review all references to automation and scripting to ensure parity between PowerShell and CLI/bash approaches.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-key-vault.md
...-manager/management/relocation/relocation-key-vault.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell-based instructions for all command-line operations, with no equivalent Azure CLI (cross-platform) or Bash examples. PowerShell is featured as the only scripting option, and all automation steps outside the portal are shown using PowerShell cmdlets, which are primarily used on Windows. There are no Linux/macOS-specific instructions or CLI examples, and PowerShell is presented before any mention of Azure CLI. The only mention of Azure CLI is in a passing reference for configuring service endpoints, with no actual CLI commands or walkthroughs provided.
Recommendations
- Add Azure CLI examples (az commands) for all PowerShell-based steps, including exporting and deploying templates, and managing resources.
- Present Azure CLI and PowerShell examples side-by-side or in tabs, ensuring parity for Linux/macOS users.
- Explicitly mention that PowerShell can be used cross-platform, but highlight Azure CLI as the recommended tool for Linux/macOS.
- Include Bash shell script examples where automation is discussed, or reference Bash scripting for Linux users.
- Ensure that references to tools and commands are not Windows-centric; provide equal visibility to cross-platform tools.
- Review and update the documentation to avoid assuming the reader is using Windows or PowerShell by default.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-storage-account.md
...er/management/relocation/relocation-storage-account.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows and PowerShell environments. All CLI examples are provided exclusively using Azure PowerShell, with no mention of Azure CLI (cross-platform) or Bash/Shell scripting alternatives. The PowerShell instructions are presented as the only command-line option, and there are no Linux-specific or cross-platform examples for exporting, modifying, or deploying templates. This may disadvantage users on Linux or macOS, who typically use Azure CLI or Bash.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, including exporting, modifying, and deploying Resource Manager templates.
- Include Bash/Shell script snippets where appropriate, especially for tasks like file manipulation and automation.
- Explicitly mention that AzCopy and Azure CLI are cross-platform tools, and provide usage instructions for Linux/macOS environments.
- Reorder or parallelize examples so that PowerShell and CLI/Bash instructions are presented side-by-side or in tabs, rather than PowerShell-only.
- Reference installation and usage guides for Azure CLI on Linux/macOS, and clarify that all steps can be performed on non-Windows platforms.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-virtual-network-nsg.md
...anagement/relocation/relocation-virtual-network-nsg.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides detailed instructions for relocating an Azure NSG using the Azure Portal and PowerShell, with all CLI examples and automation steps relying exclusively on PowerShell cmdlets. There are no examples or guidance for Linux users, such as using Azure CLI (az), Bash, or cross-platform editors. Windows tools like Notepad are referenced, and the PowerShell approach is presented as the sole scripting method, which may disadvantage users on Linux or macOS.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell steps, including authentication, resource export, template editing, deployment, and cleanup.
- Reference cross-platform text editors (e.g., VS Code, nano, vim) instead of or alongside Notepad.
- Explicitly mention that both PowerShell and Azure CLI are supported, and provide tabs for each where applicable.
- Ensure that instructions for obtaining region codes and other metadata include Azure CLI commands.
- Review and update prerequisites and process steps to avoid assuming a Windows environment or toolset.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/resource-providers-and-types.md
...rce-manager/management/resource-providers-and-types.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias. The Azure portal is referenced as the primary GUI, and the PowerShell section appears before Azure CLI and Python. The portal is a web application but historically associated with Windows environments. The documentation mentions the 'Windows Azure Service Management API' and does not reference Linux-specific tools or shell environments (e.g., Bash, zsh). There are no examples using Bash scripts, REST calls via curl, or Linux-native automation tools. PowerShell is given prominence, and there is no mention of cross-platform PowerShell Core or its usage on Linux/macOS. The CLI examples are present and parity is generally maintained, but the ordering and terminology favor Windows.
Recommendations
- Add explicit Bash or shell script examples using curl for REST API operations.
- Clarify that Azure PowerShell and Azure CLI are cross-platform, and provide installation/usage notes for Linux/macOS.
- Mention and provide examples for PowerShell Core on Linux/macOS, not just Windows PowerShell.
- Reorder sections so that Azure CLI (which is more popular on Linux/macOS) appears before PowerShell.
- Avoid references to 'Windows Azure Service Management API' unless necessary, or clarify its relevance to all platforms.
- Include notes or links for Linux users about authentication and environment setup (e.g., using environment variables, az login, etc.).
- Where screenshots are shown, clarify that the Azure portal is web-based and accessible from any OS.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/tag-mission-critical-workload.md
...ce-manager/management/tag-mission-critical-workload.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits mild Windows bias by listing Azure PowerShell (a Windows-centric tool) before Azure CLI and other cross-platform automation tools in the 'How to apply Azure tags' section. PowerShell is mentioned explicitly, and no Linux-specific shell examples (e.g., Bash) or platform notes are provided. The ordering and emphasis may suggest a preference for Windows/PowerShell environments.
Recommendations
- List Azure CLI before Azure PowerShell, as CLI is cross-platform and widely used on Linux.
- Provide explicit Bash/Linux shell examples for tag application, or clarify that Azure CLI commands work on Linux, macOS, and Windows.
- Add notes or examples for Linux users, such as using Bash scripts or integrating with Linux automation tools.
- Ensure parity in guidance for both Windows and Linux environments, possibly including screenshots or step-by-step instructions for each platform.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deploy-cli.md
...rticles/azure-resource-manager/templates/deploy-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While the main examples use Azure CLI (which is cross-platform), there are several instances where Windows-specific shells (CMD, PowerShell) are mentioned before or instead of Linux equivalents. Formatting for parameters and variables is explained for Windows shells, but Linux/Bash alternatives are not always provided or are described second. There is little explicit mention of Linux tools or patterns, and some examples (such as variable assignment and array formatting) are Windows-centric.
Recommendations
- Ensure all shell-specific instructions are provided for both Windows (CMD/PowerShell) and Linux (Bash) users, with equal prominence.
- When describing parameter formatting or variable assignment, give Bash/Linux examples first or side-by-side with Windows examples.
- Explicitly mention that Azure CLI is cross-platform and provide links or notes about using it on Linux/macOS.
- Include troubleshooting or usage notes relevant to Linux environments (e.g., file permissions, path formats).
- Add more examples that use Linux/Bash syntax, especially for variable assignment, parameter passing, and scripting.
- Avoid assuming Windows as the default environment; clarify instructions for both platforms where differences exist.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/tls-support.md
...icles/azure-resource-manager/management/tls-support.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows versions and tools first, focusing on .NET Framework and Visual Studio (Windows-only technologies), and providing guidance and troubleshooting links that are specific to PowerShell and WinHTTP (Windows components). There are no examples or recommendations for Linux environments, nor are Linux tools or patterns mentioned.
Recommendations
- Add explicit guidance for Linux users, such as how to check and enforce TLS 1.2 usage on common Linux distributions.
- Include examples using Linux command-line tools (e.g., OpenSSL, curl, wget) to verify TLS versions.
- Mention Linux equivalents to Windows tools like Fiddler (e.g., Wireshark, tcpdump) for inspecting TLS connections.
- Provide instructions for configuring TLS settings in popular Linux frameworks and runtimes (e.g., Python, Java, Node.js) on Linux.
- Balance references to .NET/Visual Studio with examples for cross-platform frameworks and editors (e.g., VS Code, JetBrains IDEs).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/copy-properties.md
...es/azure-resource-manager/templates/copy-properties.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific resources (e.g., a VM deployment template for Windows), mentioning Azure PowerShell before Azure CLI, and omitting explicit Linux-focused examples or links. The only example template provided is for deploying a Windows VM, and the 'Next steps' section directs users to PowerShell deployment instructions without equal emphasis on CLI or Linux-native tools.
Recommendations
- Include example templates for Linux VM deployments (e.g., link to a 'vm-linux-copy-datadisks' template alongside the Windows one).
- When referencing deployment tools, mention Azure CLI before or alongside Azure PowerShell, and provide links to both deployment guides.
- Add explicit statements or examples for deploying ARM templates from Linux/macOS environments, including Bash/CLI commands.
- Ensure parity in 'Next steps' by linking to both PowerShell and CLI deployment documentation.
- Review and balance the order of tool mentions to avoid implying Windows is the default or preferred platform.