Governance
305
Total Pages
190
Linux-Friendly Pages
115
Pages with Bias
37.7%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
613 issues found
Showing 126-150 of 613 flagged pages
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is referenced repeatedly as the primary CLI example for policy management tasks, with no equivalent Bash, Azure CLI, or Linux shell examples provided. Windows-centric tools and patterns (such as PowerShell and references to Windows machines in sample policies) are mentioned exclusively or before Linux alternatives. There is a lack of parity in troubleshooting steps and code samples for Linux users, especially in sections involving policy duplication and compliance scans.
Recommendations
- Add equivalent Azure CLI and Bash examples alongside PowerShell commands for all policy management and troubleshooting tasks.
- Explicitly mention Linux and macOS compatibility for SDKs and tools where applicable.
- Provide sample policy definitions and troubleshooting steps for both Windows and Linux resource types, not just Windows machines.
- Ensure that references to Windows tools (e.g., PowerShell) are balanced with Linux alternatives (e.g., Bash, Azure CLI) and that examples are presented in parallel.
- Where portal or REST API instructions are given, clarify any OS-specific differences or limitations.
- Review and update sample scripts and code blocks to include Linux-friendly syntax and usage.
Create Pull Request
Governance
Tutorial: Create a custom policy definition
...ce/policy/tutorials/create-custom-policy-definition.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for discovering policy aliases, but the PowerShell example is given equal prominence to the CLI example, and no explicit Linux shell (bash) examples are provided. The tutorial references the Azure portal and VS Code extension, which are cross-platform, but does not mention Linux-specific tools or workflows. The cleanup steps are portal-centric and do not include CLI or script-based alternatives, which are more common in Linux environments.
Recommendations
- Add explicit bash shell examples for Azure CLI commands (e.g., showing usage in bash, including authentication and output parsing).
- Provide cleanup instructions using Azure CLI commands, suitable for Linux/macOS users, alongside portal-based steps.
- Clarify that Azure CLI is cross-platform and works natively on Linux/macOS, and consider listing CLI examples before PowerShell to avoid Windows-first impression.
- Mention Linux-native editors (e.g., Vim, nano) or workflows for editing policy definitions, in addition to VS Code.
- Ensure all code blocks specify the shell or environment (e.g., bash, PowerShell) for clarity.
Governance
Tutorial: Build policies to enforce compliance
...icles/governance/policy/tutorials/create-and-manage.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing PowerShell examples and Windows file paths, referencing Windows-centric tools and patterns, and omitting Linux-specific guidance. PowerShell is presented before Azure CLI, and file paths use Windows syntax (e.g., 'c:\policies\coolAccessTier.json') without Linux alternatives. There are no Bash or Linux shell examples, nor guidance for Linux users on file locations or command usage.
Recommendations
- Provide Linux/Bash shell examples alongside PowerShell, especially for file-based operations and scripting.
- Include Linux file path examples (e.g., '/home/user/policies/coolAccessTier.json') wherever Windows paths are shown.
- Ensure Azure CLI examples are presented before or alongside PowerShell examples, as CLI is cross-platform.
- Add notes or sections for Linux users regarding installation, environment setup, and command usage.
- Avoid assuming Windows as the default platform in examples and screenshots; clarify when instructions are platform-specific.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently presenting PowerShell examples alongside Azure CLI and Portal, with PowerShell often mentioned first or equally with CLI. There is no mention of Linux-specific shell usage (e.g., Bash), nor are there examples tailored for Linux environments. The prerequisites and instructions reference PowerShell modules and cmdlets, which are Windows-centric, without offering equivalent Bash or Linux-native instructions. The documentation assumes familiarity with PowerShell and does not address Linux users' needs or potential differences in experience.
Recommendations
- Add explicit Bash shell examples for Azure CLI commands, demonstrating usage in a Linux environment.
- Clarify that Azure CLI commands are cross-platform and provide instructions for installing and using Azure CLI on Linux.
- Reorder examples to present Azure CLI (Bash) first, followed by PowerShell, to reduce Windows-first perception.
- Include notes or sections addressing Linux users, such as troubleshooting tips, environment setup, or differences in authentication flows.
- Where PowerShell modules are referenced, also mention Linux alternatives or clarify that PowerShell Core is available cross-platform.
- Review screenshots and instructions to ensure they are not Windows-specific (e.g., avoid showing Windows-only UI elements or paths).
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page provides shell-specific guidance for escaping special characters, mentioning Bash, cmd, and PowerShell. PowerShell (Windows) is given a dedicated example, and cmd (Windows) is mentioned before Bash (Linux/macOS). There are no Linux-specific tools or examples (e.g., Azure CLI), and the only shell examples are for Bash and PowerShell, with cmd referenced as well. No Linux-first or Linux-only patterns are shown, and there is no mention of Linux-specific usage patterns or troubleshooting. The documentation does not provide parity in examples for Linux users beyond Bash, and Windows tools/shells are referenced at least as much as, if not more than, Linux equivalents.
Recommendations
- Add explicit Azure CLI examples for Linux/macOS users, especially for common query scenarios.
- Ensure Linux shells (Bash, Zsh) are mentioned before or alongside Windows shells (cmd, PowerShell) when discussing escape characters or shell-specific behavior.
- Provide troubleshooting tips or usage notes for Linux environments, such as differences in shell quoting or environment variables.
- Include links or references to Linux-specific documentation or guides for using Resource Graph queries.
- Where possible, balance examples between PowerShell and Bash/Azure CLI to ensure Linux users have equal guidance.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is historically Windows-centric, though now available on Linux/macOS) and the absence of any Linux shell-specific examples (e.g., Bash, curl, jq) or explicit mention of Linux usage patterns suggests a mild Windows bias. There are no examples using native Linux tools or shell scripting, and PowerShell is presented as a primary automation option alongside CLI.
Recommendations
- Add explicit Bash shell examples using az graph query for Linux users.
- Include notes or examples showing how to use the Azure CLI in Linux environments, such as piping output to jq for parsing.
- Clarify that Azure PowerShell is available cross-platform, or provide links to installation instructions for Linux/macOS.
- Consider adding a section comparing usage in Windows vs. Linux environments to highlight parity and differences.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation consistently provides both Azure CLI and Azure PowerShell examples for interacting with Azure Resource Graph, but does not include Linux-specific shell examples (such as bash scripting or piping to jq), nor does it mention Linux tools or patterns. Azure PowerShell, which is traditionally associated with Windows environments, is given equal prominence to Azure CLI, but no effort is made to highlight Linux-native workflows or tools. There are no examples of using the REST API with curl, nor any references to Linux-specific scripting or processing patterns.
Recommendations
- Add Linux shell examples, such as using bash with az graph query and piping output to jq for JSON processing.
- Include REST API usage examples with curl, demonstrating how Linux users can interact with Resource Graph directly.
- Mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Provide guidance or examples for integrating query results with common Linux tools (e.g., grep, awk, sed) for further processing.
- Consider reordering examples to show Azure CLI first, emphasizing its cross-platform nature, and clarify that PowerShell is available on Linux but is not required.
Governance
Run Azure Resource Graph query using REST API
...cles/governance/resource-graph/first-query-rest-api.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows bias by listing PowerShell as the first shell in prerequisites, providing PowerShell-specific instructions and escape syntax before Bash equivalents, and recommending Windows-centric tools like Visual Studio Code and Git Bash. Linux-native shells (e.g., standard Bash on Linux) are not mentioned, and Windows tools are referenced more prominently.
Recommendations
- List Bash (including native Linux Bash) before PowerShell in prerequisites and examples, or present both equally.
- Include instructions for running commands in native Linux environments (e.g., Ubuntu terminal), not just Git Bash.
- Mention Linux-native editors (e.g., Vim, Nano) alongside Visual Studio Code.
- Clarify that Azure CLI and REST API commands work identically on Linux, macOS, and Windows.
- Add explicit examples or notes for Linux/macOS users, including shell differences and file creation steps.
- Avoid recommending Windows-specific tools unless necessary, or provide cross-platform alternatives.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal for each query. While Azure CLI is cross-platform, Azure PowerShell is primarily a Windows-centric tool (though it is available on Linux, its usage is much more common on Windows). There are no explicit Linux shell (bash) examples, nor are Linux-native tools (e.g., curl, jq, bash scripting) mentioned. The ordering of examples always places Azure CLI first, which is positive for cross-platform parity, but the inclusion of PowerShell and absence of Linux-specific shell examples indicates a mild Windows bias.
Recommendations
- Add explicit bash/shell examples for running az graph query commands, showing output parsing with jq or similar Linux tools.
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide installation/usage notes for Linux users.
- Consider removing or de-emphasizing PowerShell examples unless there is a specific Windows-only use case.
- Where relevant, mention Linux-native alternatives for scripting and automation (e.g., bash, zsh, etc.).
- Ensure documentation is reviewed for parity in example coverage between Windows and Linux environments.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal, but omits explicit Linux shell (bash) examples. PowerShell examples are given equal prominence to CLI, and the tab order consistently lists PowerShell before Portal, which may reinforce a Windows-centric workflow. There is no mention of Linux-specific tools, nor any guidance for Linux users beyond the generic Azure CLI, which is cross-platform but often used in bash/zsh environments. No bash script or Linux command-line patterns are shown.
Recommendations
- Add explicit bash/zsh examples for each query, demonstrating usage in Linux environments.
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide sample shell usage (e.g., az graph query -q ... in bash).
- Consider listing Azure CLI and bash examples before PowerShell to avoid reinforcing a Windows-first workflow.
- Mention any Linux-specific considerations or troubleshooting steps for Arc-enabled servers, if applicable.
- If PowerShell is required for any advanced scenarios, note alternatives for Linux users (e.g., PowerShell Core, or equivalent bash scripting).
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides examples for Azure CLI (cross-platform), Azure PowerShell (Windows-centric), and the Azure Portal, but does not include any explicit Linux shell (bash) examples or mention Linux-specific tools. The PowerShell example is given equal prominence to the CLI, but PowerShell is primarily a Windows tool, and there is no guidance for Linux users beyond the CLI. There are no references to Linux-specific patterns or troubleshooting.
Recommendations
- Add explicit bash shell examples for running Azure CLI commands on Linux, including any necessary environment setup or authentication steps.
- Clarify that Azure CLI is cross-platform and provide notes or links for installing and using it on Linux.
- If PowerShell is mentioned, also mention PowerShell Core (pwsh) for Linux and macOS, or clarify platform compatibility.
- Include troubleshooting tips or notes for common Linux issues (e.g., authentication, environment variables, package dependencies).
- Consider reordering examples to present the cross-platform CLI first, followed by PowerShell, to emphasize platform neutrality.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways. Most queries and examples reference Windows-specific concepts (e.g., 'WindowsPendingReboot'), and there is a lack of parity for Linux-focused scenarios except for a single explicit Linux example. Windows terminology and assignment names are used without equivalent Linux examples, and the documentation does not provide Linux-specific guest configuration queries (e.g., pending reboot for Linux, installed applications for Windows). PowerShell is featured as a primary automation tool, which is traditionally Windows-centric, and Windows-related queries appear before Linux ones.
Recommendations
- Add equivalent Linux guest configuration assignment examples (e.g., 'LinuxPendingReboot', installed applications for Windows).
- Ensure examples for both Windows and Linux are provided for each scenario, not just one or the other.
- Where possible, use cross-platform terminology and avoid Windows-specific names unless also providing Linux equivalents.
- Include Bash or shell scripting examples for Linux users alongside PowerShell.
- Clearly indicate which queries/examples apply to Windows, Linux, or both, and strive for parity in coverage and detail.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is Windows-centric and is always presented alongside CLI, sometimes even before CLI in tab order. There are no explicit Linux shell (bash, zsh) examples, nor is there mention of Linux-specific usage patterns or tools. The documentation assumes familiarity with PowerShell and does not address Linux users directly.
Recommendations
- Add explicit bash/zsh examples for each query, demonstrating usage in a Linux shell environment.
- Clarify that Azure CLI is cross-platform and provide installation/usage notes for Linux and macOS.
- Reorder tabs to present Azure CLI before PowerShell, emphasizing cross-platform solutions first.
- Include troubleshooting or environment notes for Linux users, such as authentication or shell quoting differences.
- Avoid assuming PowerShell as a default; mention alternatives for Linux users where relevant.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Many queries and examples are generic to Azure Resource Graph and do not differentiate between Windows and Linux, but where OS-specific examples are given, Windows Server is typically presented first and in more detail. Windows terminology (e.g., KB IDs, update classifications like 'updateRollup', 'featurePack', 'servicePack') is prevalent, and PowerShell is featured as a primary automation tool. Linux-specific queries are present but less emphasized and sometimes appear after Windows equivalents. There is little discussion of Linux-specific update types or tools, and no mention of Linux command-line alternatives (e.g., Bash scripts) for automation.
Recommendations
- Ensure Linux-specific queries and examples are presented with equal prominence and detail as Windows examples.
- Where update classifications or terminology are Windows-centric, provide Linux equivalents or clarify differences.
- Include Linux command-line automation examples (e.g., Bash, shell scripts) alongside PowerShell for parity.
- When listing OS-specific queries, alternate the order or group them together to avoid always presenting Windows first.
- Expand documentation to discuss Linux patching tools and patterns (e.g., apt, yum, zypper) where relevant.
- Clarify in each query or example which OSes are supported and highlight any differences in output or behavior.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but the inclusion of PowerShell (a Windows-centric tool) and the explicit 'Azure PowerShell' tab indicate a bias toward Windows tooling. There is no explicit Linux shell (bash) example, and PowerShell is presented as a primary method alongside CLI, which may suggest a Windows-first approach. However, the Azure CLI example is cross-platform, which partially mitigates the bias.
Recommendations
- Add explicit bash/zsh shell examples to demonstrate parity for Linux/macOS users.
- Clarify in the Azure CLI section that it works on Windows, Linux, and macOS.
- If PowerShell is included, consider also including examples using native Linux tools or scripts where relevant.
- Order the tabs so that cross-platform tools (Azure CLI) appear before Windows-centric tools (PowerShell) to reinforce neutrality.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
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 Azure CLI, but there is no explicit mention of Linux shell equivalents (e.g., Bash), nor are there examples tailored for Linux users. The documentation also does not clarify cross-platform compatibility for the CLI or PowerShell commands, and does not provide Linux-specific guidance or troubleshooting.
Recommendations
- Add explicit Bash shell examples for Linux users, demonstrating the same Azure CLI command.
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- If PowerShell is mentioned, note that PowerShell Core is available cross-platform, or provide separate instructions for Windows PowerShell and PowerShell Core on Linux/macOS.
- Consider listing Azure CLI (which is cross-platform) before PowerShell to reduce perceived Windows-first bias.
- Include troubleshooting notes or environment setup instructions for Linux users where relevant.
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. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments, and its inclusion as a top-level example can signal Windows bias. There are no explicit Linux shell (bash, zsh) or scripting examples, nor are Linux-specific tools or usage patterns mentioned. The ordering of examples (CLI, PowerShell, Portal) puts PowerShell before any Linux-specific shell guidance, and there is no mention of Linux-native scripting or integration.
Recommendations
- Add explicit bash/zsh shell examples for running Azure CLI commands on Linux and macOS.
- Clarify that Azure CLI is cross-platform and provide usage notes for Linux/macOS environments (e.g., installation, authentication).
- If PowerShell is shown, also show equivalent bash scripts for parity.
- Mention Linux-native tools (such as jq for JSON parsing) where relevant.
- Consider reordering examples so that cross-platform or Linux-native options appear before Windows-specific tools.
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. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is traditionally Windows-centric) and the absence of explicit Linux shell examples (such as Bash or shell scripting) suggest a bias towards Windows tools and workflows. PowerShell is given its own dedicated example, and no Linux-specific instructions or alternative shell commands are provided.
Recommendations
- Add explicit Bash or shell script examples for Linux users, demonstrating how to run Azure CLI commands in a Linux environment.
- Clarify that Azure CLI is cross-platform and provide usage notes for both Windows and Linux terminals.
- If PowerShell is included, consider also including examples using native Linux shells to ensure parity.
- Mention any differences in command syntax or output formatting between Windows and Linux environments, if applicable.
Governance
Troubleshoot common errors for Azure Resource Graph
...cles/governance/resource-graph/troubleshoot/general.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for batch querying subscriptions, referencing Windows-centric tools (PowerShell, Azure CLI) without Linux or cross-platform equivalents, and omitting examples for Bash, shell scripting, or Linux-native workflows. The guidance for working with large numbers of subscriptions is exclusively shown in PowerShell, with no mention of how to accomplish the same in Bash, Python, or other cross-platform SDKs.
Recommendations
- Add equivalent examples using Bash and Azure CLI for Linux/macOS users, showing how to batch queries with subscription lists.
- Include Python SDK or REST API code samples for batch querying, demonstrating cross-platform approaches.
- Mention Linux and macOS explicitly when discussing tools and workflows, ensuring parity in troubleshooting steps.
- Reorder examples or provide parallel examples so that Windows and Linux approaches are presented side-by-side, rather than Windows-first.
- Reference cross-platform tools (e.g., jq, curl) when discussing REST API troubleshooting.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/overview.md
...s/blob/main/articles/governance/blueprints/overview.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 the only command-line example in the 'Next steps' section, with no mention of Linux-native tools or CLI alternatives. PowerShell is presented before REST API, and there is no reference to Azure CLI or bash scripting, which are common on Linux. No Linux-specific instructions, examples, or parity are provided.
Recommendations
- Add Azure CLI examples for blueprint creation and management, as Azure CLI is cross-platform and widely used on Linux.
- Include bash scripting or shell command examples where relevant, especially for automation scenarios.
- In the 'Next steps' section, list Azure CLI and REST API options before or alongside PowerShell to avoid Windows-first ordering.
- Explicitly state that PowerShell is available on Linux and macOS, or clarify platform compatibility for each tool.
- Provide links to Linux-specific documentation or usage guides for Azure Blueprints.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/assign-configuration/rest-api.md
...-configuration/how-to/assign-configuration/rest-api.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias primarily through its recommendation of the PowerShell Get-AzAccessToken cmdlet for authentication, without mentioning Linux alternatives (such as Azure CLI or other token retrieval methods). The only tool referenced for obtaining an Azure access token is a Windows-centric PowerShell cmdlet, and the link provided directs users to PowerShell documentation. While the main example uses curl (which is cross-platform), the authentication step is presented in a Windows-first manner, and there is no mention of Linux-native approaches or parity in tooling.
Recommendations
- Include Linux-native methods for obtaining Azure access tokens, such as using the Azure CLI (az account get-access-token) or environment variables.
- Provide examples or links for both PowerShell and Bash/Linux shell environments when discussing authentication.
- Add explicit notes or sections for Linux users, ensuring parity in instructions and tooling references.
- Where possible, avoid referencing only Windows tools; mention cross-platform alternatives first or alongside Windows-specific options.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/assign-configuration/azure-resource-manager.md
.../how-to/assign-configuration/azure-resource-manager.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates bias towards Windows by exclusively providing examples for Windows virtual machines and built-in configurations (e.g., AzureWindowsBaseline). There are no examples or references for Linux configurations, nor are Linux-specific built-in baselines mentioned. Additionally, the link to the ARM template tutorial defaults to Azure PowerShell, a Windows-centric tool.
Recommendations
- Add examples for Linux virtual machines, including ARM template snippets for assigning Linux-specific configurations.
- Include references to built-in Linux baselines (e.g., AzureLinuxBaseline) and show how to assign them.
- Provide links to ARM template tutorials that use cross-platform tools (e.g., Azure CLI, Bicep) or ensure parity in tool coverage.
- Explicitly mention Linux support and differences in configuration assignment, if any.
- Ensure that examples and guidance are balanced between Windows and Linux environments.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/develop-custom-package/3-test-package.md
...ration/how-to/develop-custom-package/3-test-package.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is presented as the primary interface for both Windows and Linux, with Windows-specific tools (SysInternals PSExec) mentioned explicitly and before the Linux equivalent (sudo). Windows paths and privilege escalation methods are described first, and the examples use Windows terminology and tools more prominently. There is no mention of native Linux configuration management tools or shell options, and macOS is explicitly excluded.
Recommendations
- Provide Linux-first or parallel examples, ensuring Linux commands and paths are listed before or alongside Windows equivalents.
- Include native Linux shell examples (e.g., bash scripts) where possible, not only PowerShell.
- Mention Linux privilege escalation (sudo) before or alongside Windows tools like PSExec.
- Clarify support for other shells or configuration management tools on Linux, if applicable.
- Add a note on why PowerShell is required for Linux, and whether alternatives exist.
- Consider including troubleshooting steps or file paths for Linux before Windows, or in parallel.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/assign-policy-rest-api.md
...n/articles/governance/policy/assign-policy-rest-api.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows and PowerShell environments. While it mentions Bash shells like Git Bash, all command-line examples use PowerShell-specific syntax (e.g., backtick for escaping, `@` for file input), and explanations focus on PowerShell behaviors. There are no explicit Linux-native shell (e.g., Bash) command examples, and Linux escape conventions are only briefly referenced in text, not in code blocks. The prerequisites list PowerShell before Bash, and the overall flow assumes a Windows-centric workflow.
Recommendations
- Provide explicit Bash/Linux shell command examples alongside PowerShell examples, including correct escape characters and file input syntax.
- In code blocks, label which shell (PowerShell or Bash) the example is for, and ensure parity between them.
- In the prerequisites, list Bash/Linux shells equally or before PowerShell to avoid Windows-first ordering.
- Expand explanations to cover both Windows and Linux behaviors, especially regarding escaping and file referencing.
- Where possible, avoid using PowerShell-specific syntax in generic examples, or provide alternatives for Linux users.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/whats-new/migrating-from-azure-automation.md
...iguration/whats-new/migrating-from-azure-automation.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based examples and commands, referencing Windows-centric modules and patterns, and omitting equivalent Linux shell or tooling instructions. While it mentions Linux compatibility in passing, all practical guidance, code samples, and troubleshooting steps are PowerShell-focused, with no Bash or Linux-native alternatives. Windows-specific modules and workarounds (e.g., running powershell.exe for compatibility) are discussed, but Linux migration scenarios and tools are not covered in detail.
Recommendations
- Provide equivalent Linux shell (e.g., Bash) examples for exporting configurations and managing modules, especially for users who do not use PowerShell on Linux.
- Include instructions for using native Linux tools or commands to interact with Azure Automation and DSC, such as REST API calls via curl or az CLI.
- Highlight Linux-specific migration considerations, such as differences in module compatibility, file paths, and execution environments.
- List Linux DSC resources and modules, and provide examples of their usage and troubleshooting.
- Ensure troubleshooting sections address common Linux/macOS issues beyond filename quirks, such as permissions, environment setup, and module installation.
- Balance references to Windows and Linux documentation, and avoid assuming PowerShell is the default shell for all users.