Role Based Access Control
227
Total Pages
204
Linux-Friendly Pages
23
Pages with Bias
10.1%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
33 issues found
Showing 26-33 of 33 flagged pages
Role Based Access Control
Azure custom roles - Azure RBAC
...ain/articles/role-based-access-control/custom-roles.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page presents Azure PowerShell examples and references before Azure CLI equivalents in several sections, and PowerShell is mentioned as the primary command-line tool. While Azure CLI is covered and examples are provided, PowerShell is given prominence, which may create friction for Linux/macOS users who typically use Azure CLI. No sections are strictly Windows-only, and Linux users can complete all tasks using the CLI or REST API.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, especially in introductory and example sections.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Add a note clarifying that PowerShell Core is available on Linux/macOS, but CLI is often preferred on those platforms.
- Ensure parity in example depth and clarity between PowerShell and CLI sections.
- Consider adding links or brief instructions for installing and using Azure CLI on Linux/macOS.
Create Pull Request
Role Based Access Control
Azure role assignment condition format and syntax - Azure ABAC
...rticles/role-based-access-control/conditions-format.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page is mostly platform-neutral, focusing on Azure ABAC condition syntax and concepts. However, there are subtle signs of Windows bias: PowerShell is mentioned first as a tool for editing conditions, and special character handling references Azure PowerShell specifically. There is no explicit mention of Linux/macOS-specific tools or shell behaviors, and PowerShell is referenced before Azure CLI and REST API in the list of tools for adding the Exists operator.
Recommendations
- Mention Azure CLI and REST API before or alongside PowerShell when listing tools for managing conditions.
- Add notes about shell-specific escaping for Linux/macOS (e.g., bash) when discussing special characters.
- Ensure examples and tool references are balanced between PowerShell and CLI, or clarify that all tools are cross-platform.
- Include explicit references or links to Linux/macOS usage guides where relevant.
Role Based Access Control
FAQ for Azure role assignment conditions - Azure ABAC
...n/articles/role-based-access-control/conditions-faq.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation references PowerShell before Azure CLI and REST API when describing tools for adding the Exists operator to ABAC attributes. This ordering suggests a Windows-first approach and a slight bias toward PowerShell, which is traditionally associated with Windows environments. No explicit Linux/macOS examples or tool parity issues are present, but the emphasis on PowerShell may create a perception of Windows preference.
Recommendations
- List Azure CLI before PowerShell when mentioning cross-platform tools.
- Explicitly state that Azure CLI and REST API are fully supported on Linux/macOS.
- Provide example commands for both Azure CLI and PowerShell where relevant.
- Add a note clarifying that all mentioned tools are available on Linux/macOS.
Role Based Access Control
Prerequisites for Azure role assignment conditions - Azure ABAC
.../role-based-access-control/conditions-prerequisites.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation lists Azure PowerShell prerequisites before Azure CLI, with detailed module version requirements and installation notes specific to PowerShell. This ordering and emphasis may suggest a Windows-centric approach, as PowerShell is traditionally associated with Windows environments, even though it is now cross-platform. No explicit Linux/macOS examples or considerations are mentioned, and the CLI section is less detailed.
Recommendations
- Provide equal detail for Azure CLI prerequisites, including module or extension requirements if applicable.
- Explicitly mention that both Azure PowerShell and Azure CLI are cross-platform and provide links or notes for Linux/macOS installation.
- Add examples or notes for using these tools on Linux/macOS, especially for installation and environment setup.
- Consider alternating the order of PowerShell and CLI sections or combining them to avoid implicit prioritization.
Role Based Access Control
Add Azure role assignment conditions using Azure Resource Manager templates - Azure ABAC
...access-control/conditions-role-assignments-template.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for deploying the ARM template, but the PowerShell (Windows-centric) example is shown first. There is no explicit mention of Linux/macOS usage, nor are there any platform-specific notes or parity checks. The CLI example is cross-platform, but the ordering and lack of Linux/macOS context may subtly favor Windows users.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform.
- Explicitly mention that Azure CLI works on Linux/macOS and provide links to installation guides for those platforms.
- Add a note clarifying that PowerShell Core is available on Linux/macOS if users prefer PowerShell.
- Include brief instructions or links for running ARM template deployments on Linux/macOS.
Role Based Access Control
Create or update Azure custom roles using Bicep - Azure RBAC
...ticles/role-based-access-control/custom-roles-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 major steps, but PowerShell is given equal prominence and detail, which may create friction for Linux/macOS users who do not use PowerShell. There is no explicit mention of Linux/macOS-specific shell environments (e.g., Bash), nor are there examples tailored for those platforms. The ordering of examples is generally neutral, but the presence of PowerShell throughout can be considered a mild Windows bias.
Recommendations
- Add explicit Bash examples for variable assignment and command usage, especially for steps involving arrays and parameters.
- Clarify that Azure CLI commands work natively in Bash, Zsh, and other Unix shells, and provide syntax for those environments.
- Note that PowerShell examples are primarily for Windows users, and encourage Linux/macOS users to use Azure CLI in their native shell.
- Consider listing CLI (Bash) examples first, as CLI is cross-platform and more common for Linux/macOS users.
Role Based Access Control
Remove Azure role assignments - Azure RBAC
...s/role-based-access-control/role-assignments-remove.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides detailed examples for both Azure PowerShell and Azure CLI, but the PowerShell section appears before the CLI section and contains more example scenarios. PowerShell is traditionally associated with Windows, and its prominence may create a perception of Windows bias. However, the CLI section is present and offers equivalent functionality, mitigating the impact for Linux/macOS users.
Recommendations
- Present Azure CLI and PowerShell sections in parallel or alternate their order to avoid implicit prioritization.
- Ensure that the number and variety of CLI examples match those provided for PowerShell.
- Explicitly mention that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Add troubleshooting tips for CLI similar to those provided for PowerShell.
- Consider adding a brief note at the top clarifying that both CLI and PowerShell are supported on all major platforms.
Role Based Access Control
Assign Azure roles using Azure Resource Manager templates - Azure RBAC
...role-based-access-control/role-assignments-template.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation consistently presents Azure PowerShell (Windows-centric) examples before Azure CLI (cross-platform) examples in all command sections. PowerShell commands are shown first for obtaining object IDs and for deploying templates, which may subtly reinforce a Windows-first workflow. However, Azure CLI examples are provided for every scenario, ensuring Linux/macOS users can follow along. No Windows-only tools or patterns are mentioned, and no critical steps are missing for Linux users.
Recommendations
- Alternate the order of examples so Azure CLI commands are shown first in some sections, or present CLI and PowerShell examples side-by-side.
- Explicitly note that Azure CLI works on Linux/macOS and is recommended for cross-platform use.
- Add a short section or callout for Linux/macOS users, clarifying that all tasks can be completed with Azure CLI.
- Consider reducing the emphasis on PowerShell in introductory text and metadata, unless targeting Windows administrators specifically.