Role Based Access Control
115
Total Pages
75
Linux-Friendly Pages
40
Pages with Bias
34.8%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
240 issues found
Showing 126-150 of 240 flagged pages
Role Based Access Control
Azure built-in roles for Compute - Azure RBAC
...es/role-based-access-control/built-in-roles/compute.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is largely neutral and platform-agnostic in its presentation of Azure built-in roles for Compute. However, there is some evidence of Windows bias in the naming and focus of certain roles (e.g., 'Windows 365 Network Interface Contributor', 'Windows Admin Center Administrator Login'), and in the use of Windows-specific tools (Windows Admin Center). Additionally, some 'Learn more' links and descriptions reference Windows-centric workflows or documentation before Linux equivalents, even when Linux is supported.
Recommendations
- For roles and descriptions that reference Windows-specific tools or workflows (such as Windows Admin Center), provide equivalent Linux management options or explicitly state Linux alternatives if available.
- Where 'Learn more' links or documentation references are Windows-centric, ensure that Linux-focused documentation is also linked or referenced in parallel.
- Review role names and descriptions to ensure they do not imply exclusivity to Windows unless that is a technical limitation; clarify Linux support where relevant.
- If any role actions or permissions are platform-specific (Windows vs. Linux), clearly document the differences and provide parity tables or notes.
- Consider adding examples or references for both Windows and Linux management scenarios in any future expansions of this documentation.
Create Pull Request
Role Based Access Control
Azure built-in roles for Hybrid + multicloud - Azure RBAC
...sed-access-control/built-in-roles/hybrid-multicloud.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page for Azure built-in roles in the Hybrid + multicloud category is heavily focused on Windows-centric technologies and tools, such as Azure Stack HCI and System Center Virtual Machine Manager (ScVmm). The roles and permissions described are almost exclusively for managing Windows-based infrastructure, with no mention of Linux-specific roles, examples, or tools. The documentation assumes the use of Windows environments and does not provide parity for Linux scenarios.
Recommendations
- Add equivalent roles and permissions for Linux-based hybrid/multicloud scenarios, such as those involving Linux VMs, containers, or non-Windows resource providers.
- Include documentation and examples for managing Linux resources using Azure Arc, including permissions for Linux VM lifecycle, patching, and monitoring.
- Reference Linux-native tools and workflows (e.g., SSH, cloud-init, Linux extensions) alongside or before Windows-specific tools like ScVmm.
- Provide cross-platform guidance and clarify which roles and actions apply to Linux, Windows, or both.
- Ensure that role descriptions and permission tables mention Linux compatibility where applicable, and link to Linux-focused documentation.
Role Based Access Control
Azure classic subscription administrators
...es/role-based-access-control/classic-administrators.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively uses the Azure portal (web UI) and Azure Resource Graph Explorer for all examples and instructions, without mentioning or providing command-line alternatives such as Azure CLI, PowerShell, or Bash. There is no reference to Linux-specific tools, nor are any cross-platform command-line instructions given. The workflow assumes use of the graphical portal, which is more commonly used on Windows, and omits parity for Linux users who may prefer CLI or automation.
Recommendations
- Add Azure CLI examples for all major workflows (listing classic administrators, converting/removing roles, etc.), ensuring commands work on Linux, macOS, and Windows.
- If relevant, provide PowerShell examples alongside CLI, but do not prioritize them over CLI.
- Explicitly mention that all steps can be performed on any OS using Azure CLI or REST API, and link to cross-platform tool documentation.
- Include a section or tab for 'Command-line' or 'Automation' for each major task, showing CLI and REST API usage.
- Avoid assuming use of the Azure portal as the only or primary method, and clarify that graphical and command-line options are available.
Role Based Access Control
Troubleshoot Azure role assignment conditions - Azure ABAC
...s/role-based-access-control/conditions-troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides troubleshooting guidance for Azure role assignment conditions. While it includes both Azure PowerShell (Windows-centric) and Azure CLI (cross-platform) examples, the PowerShell section is presented first and in more detail, with specific quoting rules and error handling. The CLI section follows, but is slightly less detailed and does not include Linux-specific troubleshooting outside of Bash quoting. There are no explicit Linux tool references, and the order of presentation may reinforce a Windows-first perspective.
Recommendations
- Alternate the order of PowerShell and CLI sections, or present CLI examples first to avoid implicit Windows prioritization.
- Expand CLI troubleshooting to include common issues on Linux and macOS, such as environment differences, shell compatibility, and file permissions.
- Include explicit references to Linux/macOS environments where relevant, such as using Bash, Zsh, or other shells.
- Add notes or examples for using Azure CLI in Windows, Linux, and macOS, highlighting any platform-specific considerations.
- Ensure parity in detail between PowerShell and CLI sections, including error messages, quoting rules, and editor recommendations.
Role Based Access Control
Add Azure role assignment conditions using Azure Resource Manager templates - Azure ABAC
...access-control/conditions-role-assignments-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides deployment examples using both Azure PowerShell (New-AzResourceGroupDeployment) and Azure CLI (az deployment group create), but the PowerShell example is listed first. There is a slight Windows bias in ordering, as PowerShell is more commonly associated with Windows environments. No Linux-specific tools or patterns are mentioned, and there are no explicit Linux shell examples (e.g., bash). However, the inclusion of Azure CLI does provide some cross-platform parity.
Recommendations
- Alternate the order of examples, sometimes listing Azure CLI first to avoid implicit prioritization of Windows/PowerShell.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide a bash shell example if relevant.
- Add a note clarifying that both PowerShell and Azure CLI are cross-platform, and users can choose either based on their environment.
- Consider including examples using ARM template deployment via the Azure portal or GitHub Actions for broader platform coverage.
Role Based Access Control
Delegate Azure access management to others - Azure ABAC
...d-access-control/delegate-role-assignments-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a moderate Windows bias in its technical examples. The Azure PowerShell example is presented before the Azure CLI example, and PowerShell is a Windows-centric tool. The CLI example uses Windows-style variable assignment (set), which may confuse Linux users, and there are no explicit Bash/Linux shell examples. There is no mention of Linux-specific tools or shell environments, and the documentation does not clarify cross-platform usage for CLI commands.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform support.
- Use Bash-style variable assignment (e.g., export or VAR=value) in CLI examples, or provide both Windows (cmd) and Linux (bash) syntax.
- Explicitly state that Azure CLI works on Linux, macOS, and Windows, and provide guidance for running commands in different environments.
- Add notes or tabs for Linux/macOS shell usage where command syntax differs.
- Consider including screenshots or instructions from Linux environments in addition to Windows/PowerShell.
Role Based Access Control
Azure permissions - Azure RBAC
...e-based-access-control/resource-provider-operations.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias in its introductory guidance, specifically by listing the Windows PowerShell cmdlet (Get-AzProviderOperation) before the cross-platform Azure CLI equivalent (az provider operation list) when instructing users how to retrieve the latest permissions. No Linux-specific tools or examples are mentioned, and the only command-line examples given are for PowerShell and Azure CLI. The rest of the page is a provider/service reference table and does not include platform-specific instructions or examples.
Recommendations
- List Azure CLI (az provider operation list) before PowerShell cmdlets to emphasize cross-platform usage.
- Explicitly mention that Azure CLI works natively on Linux, macOS, and Windows, while PowerShell is primarily a Windows tool (though available cross-platform).
- Where command-line instructions are given, provide examples for both Azure CLI and PowerShell, and clarify their platform compatibility.
- Add a note or section highlighting Linux and macOS support for Azure management tools, including links to installation guides for Azure CLI and PowerShell on non-Windows platforms.
- Avoid implying that PowerShell is the default or primary method for Azure management unless contextually appropriate.
Role Based Access Control
Azure permissions for Management and governance - Azure RBAC
...ccess-control/permissions/management-and-governance.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Summary
The documentation page lists Azure permissions for management and governance resource providers, but it demonstrates a subtle Windows bias. This is most evident in the Microsoft.Automation section, which repeatedly references 'Powershell modules' and 'DSC' (Desired State Configuration), both of which are traditionally Windows-centric technologies. There is no mention of Linux equivalents (such as Bash scripts or Ansible modules) or cross-platform automation tools. The terminology and examples are focused on Windows tools, and there is no explicit Linux or cross-platform parity in the descriptions.
Recommendations
- Include references to Linux-compatible automation options (e.g., Bash, Python, Ansible) alongside Powershell in the Microsoft.Automation section.
- Clarify which features (such as DSC, runbooks, modules) are available or supported for Linux environments, and provide examples or links to Linux-specific documentation.
- Use more neutral, cross-platform terminology (e.g., 'automation scripts' instead of 'Powershell modules') where possible.
- Add explicit notes or tables indicating platform support (Windows, Linux, cross-platform) for each permission or feature, especially in areas traditionally dominated by Windows tooling.
Role Based Access Control
Azure roles, Microsoft Entra roles, and classic subscription administrator roles
...based-access-control/rbac-and-directory-admin-roles.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page consistently references the Azure portal (a web UI), Azure PowerShell, and Microsoft tools, but does not provide examples or mention Linux-specific tools or command-line interfaces (such as Bash, Azure CLI on Linux, or automation via shell scripts). All screenshots and instructions are oriented around the Azure portal, which is platform-agnostic but the absence of Linux CLI or cross-platform automation examples suggests a subtle Windows bias. There is no mention of Linux-native workflows, nor parity in examples for Linux users.
Recommendations
- Add examples of role management using Azure CLI commands, which run natively on Linux, macOS, and Windows.
- Explicitly mention that Azure CLI and REST API can be used from any OS, and provide sample commands for common tasks (e.g., assigning roles) using Bash.
- Include links or sections for Linux users on how to automate role assignments and management via shell scripts.
- Balance screenshots and instructions by showing both portal-based and CLI-based workflows.
- Reference cross-platform tools before or alongside Windows-specific tools (such as PowerShell).
Role Based Access Control
Assign Azure roles using Azure Resource Manager templates - Azure RBAC
...role-based-access-control/role-assignments-template.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for all operations, but PowerShell commands are consistently listed first and referenced with more detail. This ordering and emphasis may subtly favor Windows users, as PowerShell is natively available on Windows and often associated with Windows workflows. There are no explicit Linux-specific instructions, nor are alternative Linux-native tools or shell patterns (e.g., bash scripting, environment variables) discussed. However, the use of Azure CLI does provide cross-platform parity, as it is available on Linux, macOS, and Windows.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or list Azure CLI first to reflect its cross-platform nature.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide links to installation instructions for each OS.
- Include Linux shell-specific tips, such as using environment variables or piping output, to make the documentation more welcoming to Linux users.
- Add a brief section or note highlighting that all examples are cross-platform unless otherwise stated, and clarify any OS-specific caveats.
- Consider including screenshots or terminal output from Linux environments alongside Windows examples.
Role Based Access Control
Remove Azure role assignments - Azure RBAC
...s/role-based-access-control/role-assignments-remove.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides detailed examples for Azure PowerShell and Azure CLI, but the PowerShell section appears first and is more extensive, with multiple examples and troubleshooting notes. PowerShell is a Windows-centric tool, and its prominence may suggest a Windows bias. There are no explicit Linux shell examples (e.g., Bash), nor is there mention of Linux-specific usage patterns or considerations. The CLI examples are cross-platform, but the ordering and depth favor Windows/PowerShell.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more commonly used on Linux.
- Add explicit Bash shell usage examples for Azure CLI to demonstrate Linux workflows (e.g., using variables, piping, jq for output parsing).
- Clarify that Azure CLI works natively on Linux and macOS, and provide installation or usage notes for those platforms.
- Balance troubleshooting and error notes between PowerShell and CLI, ensuring Linux users have parity in guidance.
- Consider adding a section on using Azure RBAC with automation tools common in Linux environments (e.g., shell scripts, Ansible).
Role Based Access Control
Understand Azure role assignments - Azure RBAC
...articles/role-based-access-control/role-assignments.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by presenting Azure PowerShell examples and references before Azure CLI and REST API equivalents. The first example of role assignment properties is shown using Azure PowerShell, with the Azure CLI and REST API examples following. Additionally, links and explanations often mention Azure PowerShell before cross-platform tools like Azure CLI, and there are no explicit Linux-specific examples or considerations.
Recommendations
- Present Azure CLI examples before or alongside Azure PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
- Include explicit notes or examples for Linux users, such as command-line usage or shell scripting patterns.
- Avoid ordering tools in a way that prioritizes Windows-centric tools (PowerShell) over cross-platform alternatives.
- Add references to Linux shell environments where relevant, and clarify that Azure CLI works natively on Linux and macOS.
- Ensure that all tooling instructions (e.g., for Bicep, ARM templates) mention cross-platform compatibility and do not assume a Windows environment.
Role Based Access Control
Understand Azure role definitions - Azure RBAC
...articles/role-based-access-control/role-definitions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a subtle Windows bias by consistently listing Azure PowerShell (a Windows-centric tool) before Azure CLI (cross-platform) when showing examples and referencing tools. Role definition examples are shown first in Azure PowerShell format, then in Azure CLI format. The 'Tools' section also lists Azure PowerShell before Azure CLI, and there are no explicit Linux shell or scripting examples (e.g., Bash), nor are Linux-specific usage patterns mentioned.
Recommendations
- Alternate the order of examples so that Azure CLI (cross-platform) is shown before Azure PowerShell in some sections.
- Include explicit Bash/Linux shell examples for role definition queries and manipulations, especially for Azure CLI.
- Clarify that Azure CLI is cross-platform and highlight its parity with PowerShell for Linux/macOS users.
- Add notes or links to Linux-specific installation and usage guides for Azure CLI and PowerShell.
- Where possible, provide examples of using REST API via curl or other Linux-native tools.
- Review other documentation pages for similar ordering and example bias to ensure consistent cross-platform parity.
Role Based Access Control
List Azure role definitions - Azure RBAC
...les/role-based-access-control/role-definitions-list.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides detailed, step-by-step examples for Azure PowerShell (a Windows-centric tool) before Azure CLI, including advanced formatting and JSON output. PowerShell examples use Windows-specific conventions (e.g., 'PS C:\>'), and the CLI section is less detailed, with no mention of Linux-specific shell usage or scripting. There are no Linux shell (bash/zsh) examples, nor is there guidance for Linux users regarding environment setup or command usage. The REST API section is platform-neutral, but the scripting examples overall favor Windows/PowerShell.
Recommendations
- Add Linux shell (bash/zsh) examples for Azure CLI commands, including sample output and usage in typical Linux environments.
- Provide parity in advanced examples (e.g., formatting, JSON output) for Azure CLI, showing how to use jq or other Linux tools for processing output.
- Include notes or sections on environment setup for Linux users, such as installing Azure CLI on Linux and running commands in bash.
- Avoid using Windows-specific conventions (e.g., 'PS C:\>') in examples unless also providing Linux equivalents.
- Ensure that CLI examples are as detailed and comprehensive as PowerShell examples, covering similar scenarios and output formats.
Role Based Access Control
Understand scope for Azure RBAC
...n/articles/role-based-access-control/scope-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by mentioning Azure PowerShell before Azure CLI when discussing command-line methods for determining scope. The only explicit command-line output example is for Azure PowerShell, with Azure CLI output shown as a JSON object. There are no Linux-specific tools or shell examples, and PowerShell is traditionally associated with Windows environments, though it is cross-platform now. No explicit Linux shell (bash) or OS-specific instructions are provided.
Recommendations
- Present Azure CLI examples before or alongside Azure PowerShell to avoid Windows-first ordering.
- Include explicit bash or Linux shell examples for common tasks, such as using az CLI in a Linux terminal.
- Clarify that both Azure PowerShell and Azure CLI are cross-platform, and provide guidance for users on Linux or macOS.
- Add notes or sections for Linux users, such as how to install and use Azure CLI or PowerShell on Linux.
- Ensure that screenshots and instructions are not Windows-centric (e.g., avoid showing only Windows UI elements or PowerShell prompts).
Role Based Access Control
Transfer an Azure subscription to a different Microsoft Entra directory
...les/role-based-access-control/transfer-subscription.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page provides command-line examples exclusively using Azure CLI and Bash, which are cross-platform, but when discussing file ACLs for Azure Data Lake Storage Gen2, it mentions listing ACLs using the Azure portal or PowerShell, with no mention of Linux tools or CLI alternatives. Additionally, in the managed identities section, links for configuring managed identities on VMs and VMSS point to guides for Windows VMs first, rather than providing parity or mentioning Linux VM guides. There are no explicit Linux-specific examples or references to Linux tools, and PowerShell is mentioned as a method for listing ACLs without a corresponding Bash/Azure CLI example.
Recommendations
- Provide explicit Azure CLI examples for listing and managing ACLs on Azure Data Lake Storage Gen2 and Azure Files, rather than referencing only PowerShell or the portal.
- Include links and examples for configuring managed identities on Linux VMs and VMSS, not just Windows.
- When referencing guides for VM/VMSS managed identities, mention both Windows and Linux options, or link to a general guide that covers both.
- Ensure that any PowerShell-specific instructions are accompanied by equivalent Azure CLI or Bash instructions.
- Review all referenced documentation to ensure Linux parity and cross-platform applicability in examples and linked guides.
Role Based Access Control
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/change-history-report.md
...les/role-based-access-control/change-history-report.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Azure PowerShell examples and explanations before Azure CLI equivalents, and provides more detailed PowerShell usage and output samples. PowerShell is a Windows-centric tool, and its prominence may disadvantage Linux users. While Azure CLI examples are present and generally cross-platform, the initial focus and depth of PowerShell coverage suggest a Windows bias.
Recommendations
- Present Azure CLI and PowerShell examples side-by-side, or alternate which comes first to avoid implicit prioritization.
- Ensure equal depth and detail in CLI and PowerShell sections, including output samples and filtering techniques.
- Explicitly note that Azure CLI works natively on Linux/macOS and provide any OS-specific tips if needed.
- Add a brief section on using Bash or shell scripting with Azure CLI for Linux users.
- Review screenshots and instructions for OS neutrality (e.g., avoid Windows-only UI cues or terminology).
Role Based Access Control
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/classic-administrators.md
...es/role-based-access-control/classic-administrators.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively provides instructions and screenshots for managing Azure classic administrators using the Azure portal, which is a web-based GUI and does not reference platform-specific CLI tools. However, there are no examples or guidance for performing these tasks via command-line interfaces such as Azure CLI, PowerShell, or REST API. Notably, there is no mention of Linux-native workflows or tools, and no parity examples for Linux users, which may disadvantage users who prefer or require command-line or automation approaches, especially on non-Windows platforms.
Recommendations
- Add equivalent instructions for managing classic administrator roles using Azure CLI, including example commands for listing, converting, and removing administrators.
- Include PowerShell examples for Windows users, but ensure Azure CLI examples are presented first or in parallel to avoid Windows-first bias.
- Provide REST API examples for advanced and cross-platform automation.
- Explicitly mention that all CLI and API methods work on Linux, macOS, and Windows, and clarify any platform-specific prerequisites.
- Add a section comparing GUI (portal) and CLI/API approaches, highlighting scenarios where CLI may be preferable (e.g., automation, scripting, remote management).
Role Based Access Control
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/built-in-roles.md
...n/articles/role-based-access-control/built-in-roles.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation for Azure built-in roles is generally platform-neutral in its descriptions, but there is evidence of Windows bias. Several roles and descriptions specifically reference Windows technologies (e.g., Windows Admin Center, Windows 365, NTFS permissions, SMB ACLs, Azure Stack HCI, SCVMM), and Windows terminology is used as the primary reference point for access control and file sharing. Linux equivalents (such as POSIX ACLs or NFS) are not mentioned, and there are no examples or references to Linux-specific tools or patterns. Windows-centric roles are present, but there are no corresponding Linux-centric roles or explanations.
Recommendations
- Add references to Linux equivalents (e.g., POSIX ACLs, NFS) in role descriptions where Windows technologies (NTFS, SMB) are mentioned.
- Include examples or notes for Linux-based environments, especially for roles that currently only reference Windows tools or patterns.
- Where access control is described in terms of Windows file servers, also describe how the same roles map to Linux file servers or containers.
- If possible, introduce roles or documentation sections that address Linux-specific management scenarios (e.g., SSH access, Linux VM extensions, Linux-based storage).
- Review and update terminology to be more inclusive of both Windows and Linux, especially in hybrid and multicloud sections.
Role Based Access Control
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/built-in-roles/compute.md
...es/role-based-access-control/built-in-roles/compute.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page lists Azure built-in roles for Compute, including several roles and features that are explicitly Windows-centric (e.g., Windows Admin Center, Windows 365). Some roles and descriptions reference Windows tools or patterns, such as Windows Admin Center and Windows 365, without mentioning equivalent Linux tools or workflows. In a few cases, links and descriptions prioritize Windows scenarios (e.g., login as administrator links to Windows-specific documentation), and Linux parity is not always clear or present.
Recommendations
- For roles and features that are Windows-specific (e.g., Windows Admin Center, Windows 365), explicitly state their platform limitations and, where possible, provide equivalent Linux workflows or tools (e.g., SSH, Linux VM management).
- Where login or management actions are described, clarify Linux support and provide links to Linux-specific documentation (e.g., Azure AD login for Linux VMs, SSH troubleshooting).
- Ensure that examples and documentation links are balanced between Windows and Linux scenarios, especially for cross-platform features like VM login, management, and monitoring.
- For roles that mention Windows tools or patterns, add notes or sections describing how similar tasks are performed on Linux, or reference relevant Linux documentation.
- Review role descriptions and permission tables for implicit Windows bias and update them to reflect Linux parity where supported.
Role Based Access Control
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/built-in-roles/storage.md
...es/role-based-access-control/built-in-roles/storage.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page for Azure built-in roles for Storage shows evidence of Windows bias primarily in the descriptions and role mappings for Azure File Sync and SMB file share roles. Several roles reference Windows concepts such as NTFS permissions, ACLs, and SMB, and some descriptions explicitly state equivalence to Windows file server ACLs or note the absence of built-in Windows equivalents. There is little to no mention of Linux-specific file system concepts, tools, or parity, and the documentation does not provide Linux-centric examples or mappings.
Recommendations
- Add Linux/NFS-specific role mappings and descriptions where relevant, especially for file share and ACL-related roles.
- Where roles reference Windows ACLs or NTFS permissions, provide equivalent Linux concepts (e.g., POSIX ACLs, NFS permissions) and clarify cross-platform applicability.
- Include examples or notes for Linux users, such as how RBAC roles interact with Linux-based clients or NFS mounts.
- Review and update documentation to ensure parity in describing both Windows and Linux scenarios, tools, and terminology.
- If certain roles are only applicable to Windows, explicitly state this and provide guidance for Linux users on alternative approaches.
Role Based Access Control
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/built-in-roles/security.md
...s/role-based-access-control/built-in-roles/security.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page is generally platform-neutral, listing Azure built-in roles and their permissions. However, there is evidence of Windows bias in the 'Attestation Contributor' role, where the 'Learn more' link points specifically to a PowerShell-based quickstart, which is a Windows-centric tool. There are no Linux CLI (az) or Bash examples referenced, and PowerShell is mentioned before any cross-platform alternatives. Other roles link to documentation that is not platform-specific or do not mention tooling at all.
Recommendations
- For every role that links to a PowerShell-based guide (e.g., Attestation Contributor), also provide links to equivalent Azure CLI (az) or Bash guides, or explicitly mention cross-platform alternatives.
- Ensure that introductory or 'Learn more' links do not default to Windows/PowerShell unless no other option exists; if only PowerShell is available, note the limitation and suggest alternatives where possible.
- Audit all referenced documentation for platform parity and update examples to include both Windows (PowerShell) and Linux/macOS (Azure CLI/Bash) usage.
- Consider adding a section or table summarizing cross-platform tooling for role management, highlighting both PowerShell and Azure CLI.
Role Based Access Control
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/conditions-custom-security-attributes.md
...ccess-control/conditions-custom-security-attributes.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. The main workflow and UI instructions are centered around the Azure portal, which is cross-platform, but the first and most detailed scripting example is Azure PowerShell (Windows-centric), with Azure CLI (cross-platform) presented after. There are no explicit Linux shell examples (e.g., Bash), and the PowerShell section is more verbose and detailed than the CLI section. The page does not mention Linux-specific tools or patterns, nor does it provide parity for Linux users in terms of troubleshooting or environment setup.
Recommendations
- Present Azure CLI examples before or alongside Azure PowerShell examples to emphasize cross-platform support.
- Add explicit Bash shell examples for common operations, especially for blob access and role assignment, to help Linux users.
- Include troubleshooting notes for Linux environments (e.g., authentication issues, file permissions).
- Clarify that both Azure PowerShell and Azure CLI are available on Windows, macOS, and Linux, and provide installation links for all platforms.
- Avoid language that implies PowerShell is the default or preferred tool; instead, encourage users to choose based on their OS and preferences.
Role Based Access Control
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/conditions-troubleshoot.md
...s/role-based-access-control/conditions-troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page provides troubleshooting guidance for Azure role assignment conditions. While it covers both Azure PowerShell (Windows-centric) and Azure CLI (cross-platform), the PowerShell section appears before the CLI section, and PowerShell-specific quoting rules and error handling are explained in detail. There is a slight 'Windows first' bias in the ordering and depth of examples, as PowerShell is traditionally associated with Windows environments. However, Linux/Bash users are also addressed with CLI and Bash-specific guidance.
Recommendations
- Alternate the order of CLI and PowerShell sections, or present them together under unified headings to avoid implicit prioritization.
- Ensure that examples for Azure CLI/Bash are as detailed as those for PowerShell, including troubleshooting tips and links to relevant Bash documentation.
- Explicitly state that both PowerShell and CLI are supported on Windows, Linux, and macOS, and provide platform-agnostic guidance where possible.
- Add notes or tables summarizing differences in quoting/escaping rules between PowerShell and Bash for clarity.
- Where screenshots or UI instructions are given, clarify any platform-specific differences or provide cross-platform visuals if applicable.
Role Based Access Control
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/delegate-role-assignments-overview.md
...d-access-control/delegate-role-assignments-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides command-line examples for Azure PowerShell and Azure CLI, with PowerShell presented before CLI. The PowerShell example uses Windows-style variable assignment and syntax, which is specific to Windows environments. The Azure CLI example also uses Windows batch-style 'set' commands, which are not compatible with Linux/macOS shells, and does not provide a Linux/bash equivalent. No Linux-specific shell examples (e.g., bash) are given, and the documentation does not mention cross-platform usage patterns for CLI commands.
Recommendations
- Provide Azure CLI examples using bash syntax (e.g., 'export' or direct variable assignment) alongside or before Windows batch syntax.
- Clarify that Azure CLI is cross-platform and provide explicit instructions for both Windows (cmd.exe) and Linux/macOS (bash/zsh) environments.
- Add notes or tabs indicating which command examples are for Windows and which are for Linux/macOS.
- Consider presenting Azure CLI examples before PowerShell, as CLI is more widely used across platforms.
- Explicitly mention cross-platform compatibility for tools and commands where relevant.