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 51-75 of 240 flagged pages
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/elevate-access-global-admin.md ...le-based-access-control/elevate-access-global-admin.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. The Azure portal (a web UI, but often associated with Windows-centric workflows) is presented first and in greatest detail. PowerShell is given its own dedicated tab with explicit examples, while Linux-native shell or Bash examples are not provided. Although Azure CLI is included (which is cross-platform), there are no explicit Linux/Bash-specific instructions or screenshots, and the PowerShell tab precedes the CLI tab. No mention is made of Linux terminal conventions, and all command-line examples are either PowerShell or Azure CLI (with CLI examples not tailored for Linux users).
Recommendations
  • Add explicit Bash/Linux shell examples for all Azure CLI commands, including any necessary environment variable usage or authentication steps common on Linux.
  • Include notes or sections on running Azure CLI commands in Linux environments, addressing differences in quoting, authentication, and file redirection.
  • Reorder tabs or sections so that Azure CLI (the most cross-platform tool) appears before PowerShell, or at least give them equal prominence.
  • Add screenshots or terminal output examples from Linux environments where relevant.
  • Where the Azure portal is referenced, clarify that it is web-based and not Windows-specific, and consider including browser-agnostic language.
  • If possible, mention that PowerShell Core is available on Linux, or provide Bash equivalents for PowerShell commands.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/pim-integration.md .../articles/role-based-access-control/pim-integration.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a significant Windows bias by providing only PowerShell-based CLI examples for scripting and automation tasks, with no mention of Azure CLI (cross-platform) or Bash/Linux equivalents. All command-line automation is shown using PowerShell cmdlets, which are native to Windows and less commonly used on Linux or macOS. There is no guidance or parity for users on Linux or macOS platforms, and the documentation implicitly assumes a Windows-centric workflow.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all PowerShell scripts and tasks, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that PowerShell examples are provided and offer Bash or shell script alternatives where appropriate.
  • Reorder sections or provide parallel examples so that both Windows (PowerShell) and Linux/macOS (Azure CLI/Bash) users are equally supported.
  • Include notes or links to documentation on how to install and use Azure CLI on non-Windows platforms.
  • Consider referencing automation options available in Cloud Shell, which supports both Bash and PowerShell, to highlight cross-platform capabilities.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/troubleshoot-limits.md ...icles/role-based-access-control/troubleshoot-limits.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing PowerShell examples as the primary (and only) command-line scripting option for querying and managing Azure RBAC resources. References to PowerShell cmdlets (e.g., Get-AzRoleAssignment, Get-MgUser) are given before or instead of Azure CLI equivalents. There is no explicit mention or example of using Bash, Linux shell, or cross-platform scripting, and the only command-line snippets are in PowerShell syntax. Additionally, the documentation refers to 'Azure PowerShell commands' and 'PowerShell' as the default automation tool, which may alienate Linux/macOS users who prefer Bash or Azure CLI.
Recommendations
  • Provide Azure CLI (az) command examples alongside PowerShell for all scripting and automation steps, especially for querying and managing role assignments and users.
  • When referencing command-line tools, mention both PowerShell and Azure CLI, and avoid presenting PowerShell as the default or only option.
  • Include Bash/Linux shell scripting examples where relevant, or clarify that Azure CLI commands are cross-platform.
  • In lists or instructions, do not always mention PowerShell before Azure CLI; alternate or present both equally.
  • Explicitly state that all steps can be performed on Linux/macOS as well as Windows, and link to relevant cross-platform documentation.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/quickstart-role-assignments-template.md ...access-control/quickstart-role-assignments-template.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell examples and instructions for deploying and cleaning up resources. There are no examples or instructions for using Azure CLI, Bash, or other cross-platform tools commonly used on Linux/macOS. The workflow assumes the use of Azure Cloud Shell in PowerShell mode, and all scripts and command references are PowerShell-specific. There is no mention of Linux-specific tools or alternative command-line approaches, and the only linked tutorial is also PowerShell-focused.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all deployment and cleanup steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both environments.
  • Include Bash script examples for users who prefer scripting in Bash.
  • Ensure that references to commands and tools are not PowerShell-exclusive; provide links to both PowerShell and CLI documentation where appropriate.
  • Consider restructuring sections so that cross-platform tools (like Azure CLI) are presented before or alongside PowerShell, rather than only after or not at all.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/built-in-roles/hybrid-multicloud.md ...sed-access-control/built-in-roles/hybrid-multicloud.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows-centric technologies, specifically Azure Stack HCI and System Center Virtual Machine Manager (ScVmm), which are exclusive to Windows environments. There are no Linux-specific examples, roles, or tools mentioned, and the documentation does not address Linux or cross-platform scenarios, despite the 'Hybrid + multicloud' context. The structure and terminology assume a Windows-first audience and omit Linux equivalents or guidance.
Recommendations
  • Explicitly state the Windows-only nature of Azure Stack HCI and ScVmm roles at the top of the page, clarifying the lack of Linux support.
  • If Linux or cross-platform management is possible via Azure Arc or other tools, provide dedicated sections or links to Linux-specific documentation.
  • Include examples or references for managing hybrid/multicloud environments that include Linux servers, such as using Azure Arc-enabled servers for Linux.
  • Add a comparison table or guidance for users managing both Windows and Linux resources, highlighting differences and available role-based access controls.
  • Ensure that future documentation in the 'Hybrid + multicloud' category covers both Windows and Linux scenarios, or clearly scopes content to Windows if Linux is not supported.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/delegate-role-assignments-examples.md ...d-access-control/delegate-role-assignments-examples.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively provides Azure PowerShell examples for command-line automation, with no equivalent examples using cross-platform tools such as Azure CLI or REST API. This creates a bias toward Windows and PowerShell users, potentially excluding Linux/macOS users or those who prefer non-PowerShell automation. The documentation assumes familiarity with PowerShell and does not mention or demonstrate alternative, platform-agnostic methods.
Recommendations
  • Add equivalent Azure CLI examples for each scenario alongside the PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include REST API (HTTP request) examples for advanced users and automation scenarios, ensuring parity for all platforms.
  • Explicitly state that the examples are not limited to Windows and provide guidance or links for installing and using Azure CLI on Linux/macOS.
  • Consider reordering or grouping examples so that cross-platform solutions (Azure CLI, REST API) are presented before or alongside PowerShell to avoid the perception of Windows-first bias.
  • Review and update any references to tools or workflows that are exclusive to Windows or PowerShell, ensuring documentation is inclusive of all supported platforms.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/transfer-subscription.md ...les/role-based-access-control/transfer-subscription.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is largely cross-platform in its use of Azure CLI and Bash examples, which are suitable for both Windows and Linux users. However, there are some instances of Windows bias: (1) PowerShell is mentioned as a method for listing ACLs without providing a Linux alternative, (2) some linked quickstarts for managed identities reference Windows-specific guides (e.g., configuring managed identities on Windows VMs), and (3) there are no explicit Linux or cross-platform examples for tasks like listing ACLs for Azure Files/Data Lake Storage. These omissions may make it less clear for Linux users how to perform certain steps.
Recommendations
  • For sections mentioning PowerShell (e.g., listing ACLs), provide equivalent Bash/Azure CLI commands or explicitly mention Linux-compatible alternatives.
  • When linking to quickstarts or guides for managed identities, ensure both Windows and Linux VM scenarios are referenced, or clarify that the steps are similar for Linux.
  • Wherever possible, add explicit Linux/Bash examples alongside Windows/PowerShell ones, especially for resource management tasks like ACL listing or manipulation.
  • Review all external links to ensure Linux parity in referenced documentation.
GitHub Create Pull Request
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
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page is largely platform-neutral in its main content, as it focuses on listing Azure RBAC built-in roles and their permissions. However, there is evidence of Windows bias in the external links and references. For example, the 'Attestation Contributor' role's 'Learn more' link points to a PowerShell-specific quickstart, which is typically associated with Windows environments. There are no Linux/CLI/Bash equivalents or cross-platform instructions referenced alongside or instead of PowerShell. No Linux tools, shell commands, or cross-platform Azure CLI examples are provided, and where a platform-specific example is referenced, it is Windows/PowerShell.
Recommendations
  • Wherever a 'Learn more' or quickstart link is provided (e.g., for Attestation Contributor), ensure that both PowerShell (Windows) and Azure CLI (cross-platform) or Bash examples are linked, or provide a platform-neutral landing page.
  • Audit all external documentation links to ensure Linux and cross-platform users are equally supported, not just Windows/PowerShell users.
  • If role usage examples or automation scripts are added in the future, always provide both PowerShell and Azure CLI/Bash equivalents, and avoid assuming Windows as the default environment.
  • Consider adding a 'Platform support' note or table where relevant, clarifying that all roles and permissions are accessible via Azure CLI, Azure Portal, and PowerShell, with links to relevant guides for each platform.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/conditions-prerequisites.md .../role-based-access-control/conditions-prerequisites.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell (a Windows-centric tool) and its required modules in detail before mentioning Azure CLI. The PowerShell section is more detailed, specifying multiple module versions, while the Azure CLI section is brief. There are no explicit Linux-specific instructions or examples, and the focus on PowerShell may implicitly prioritize Windows users. No mention is made of Bash, Linux shell, or cross-platform scripting patterns.
Recommendations
  • Provide equal detail for Azure CLI usage, including any required extensions or modules, as is done for PowerShell.
  • Explicitly mention that both Azure CLI and PowerShell are cross-platform, and provide links or notes for Linux/macOS installation and usage.
  • Include example commands for both Azure CLI and PowerShell in relevant sections, or link to such examples.
  • If any steps differ on Linux/macOS (e.g., installation, authentication), add notes or links to platform-specific guidance.
  • Consider referencing Bash or shell scripting where appropriate, to acknowledge Linux/macOS workflows.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/built-in-roles/hybrid-multicloud.md ...sed-access-control/built-in-roles/hybrid-multicloud.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page is heavily focused on Azure Stack HCI and System Center Virtual Machine Manager (ScVmm), both of which are Windows-centric technologies. All role definitions and permissions revolve around managing Windows-based infrastructure, with no mention of Linux-specific tools, resources, or examples. There are no Linux or cross-platform equivalents referenced, and the documentation assumes a Windows environment by default.
Recommendations
  • Include explicit notes on Linux support or limitations for each role, especially where only Windows technologies (e.g., ScVmm, Azure Stack HCI) are supported.
  • Add examples or references for managing hybrid/multicloud Linux resources, if supported, or clarify if these roles are Windows-only.
  • Provide parity by listing any Linux-focused roles or permissions (such as for Linux VMs managed via Azure Arc) if available.
  • Link to documentation for Linux management in hybrid/multicloud scenarios, or clarify the scope is Windows-only if that's the case.
  • If possible, add a section comparing Windows and Linux management capabilities in Azure hybrid/multicloud environments.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/custom-roles-template.md ...les/role-based-access-control/custom-roles-template.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses Azure PowerShell commands and Cloud Shell for all deployment, verification, and cleanup steps, with no mention of Azure CLI, Bash, or Linux-native workflows. All code samples and instructions assume a PowerShell environment, which is more familiar to Windows users. There are no Linux or cross-platform command examples, and PowerShell is presented as the default and only method.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all deployment, verification, and cleanup steps, using Bash syntax where appropriate.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both environments.
  • Where possible, provide guidance for running commands on Linux/macOS terminals, not just Windows/PowerShell.
  • Reorder or parallelize examples so that Linux/Bash and Windows/PowerShell instructions are given equal prominence.
  • Include notes or links to documentation for installing and using Azure CLI and PowerShell on all supported platforms.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/delegate-role-assignments-examples.md ...d-access-control/delegate-role-assignments-examples.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only Azure PowerShell examples for command-line automation, with no mention of cross-platform alternatives such as Azure CLI (az), which is widely used on Linux and macOS. The exclusive use of PowerShell commands and the absence of bash/CLI examples or references to Linux-native tooling indicate a Windows-centric bias.
Recommendations
  • Add equivalent Azure CLI (az) command examples for each scenario alongside the PowerShell examples.
  • Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Where scripting is shown, provide both PowerShell and bash (or shell-agnostic) script examples.
  • If certain features are only available in PowerShell, clearly state this and provide workarounds or alternatives for Linux users.
  • Review the documentation for any terminology or instructions that assume a Windows environment and generalize them for cross-platform audiences.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/deny-assignments.md ...articles/role-based-access-control/deny-assignments.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples (which are Windows-centric), referencing Windows file paths (e.g., 'PS C:\>'), and omitting equivalent command-line examples for Linux users (such as Azure CLI/bash). The only command-line automation example is with Azure PowerShell, with no mention or example of Azure CLI, which is cross-platform and commonly used on Linux. Additionally, the PowerShell tab appears before REST API, and there is no explicit guidance for Linux users.
Recommendations
  • Add Azure CLI examples for all PowerShell command examples, showing equivalent commands for listing deny assignments at different scopes.
  • Use neutral file path prompts (e.g., '$' or no prompt) in code blocks, or provide both Windows (PS C:\>) and Linux ($) prompts.
  • Explicitly mention that Azure PowerShell can be used cross-platform, but also highlight Azure CLI as a first-class, cross-platform alternative.
  • Reorder or parallelize the documentation tabs so that Azure CLI (if added) appears alongside or before PowerShell, or at least not after.
  • Include a section or note for Linux/macOS users, clarifying tool availability and usage.
  • Where screenshots or UI instructions are given, clarify if there are any OS-specific differences or confirm that the Azure portal experience is identical across platforms.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/quickstart-role-assignments-template.md ...access-control/quickstart-role-assignments-template.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell examples for deploying and cleaning up ARM templates, with no mention or examples of equivalent steps using Azure CLI, Bash, or other cross-platform tools. The instructions assume use of Azure Cloud Shell for PowerShell, and all command-line steps and outputs are PowerShell-specific. There is no guidance for Linux/macOS users or those preferring Bash/Azure CLI, and the 'Next steps' section links only to further PowerShell-based tutorials.
Recommendations
  • Add equivalent Azure CLI (az) examples for all deployment and cleanup steps, using Bash syntax where appropriate.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both environments.
  • Include sample outputs for Azure CLI commands to match the PowerShell output shown.
  • In the 'Next steps' section, link to tutorials using Azure CLI and/or Bash, not just PowerShell.
  • Review terminology and instructions to ensure they are not PowerShell- or Windows-centric (e.g., avoid assuming familiarity with PowerShell cmdlets).
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/pim-integration.md .../articles/role-based-access-control/pim-integration.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for command-line operations, with no mention of cross-platform alternatives such as Azure CLI or Bash. All scripting and automation guidance is centered around PowerShell cmdlets, which are traditionally associated with Windows environments, and there are no Linux/macOS-specific instructions or examples. The structure also presents PowerShell-based solutions before any mention of REST APIs or other platform-agnostic tools.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell command sequences, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell can be used on Linux/macOS, or clarify any platform dependencies.
  • Include Bash scripting examples where appropriate, especially for automation scenarios.
  • When listing options for automation or scripting, present Azure CLI and REST API options alongside PowerShell, rather than only after or not at all.
  • Review all sections for assumptions of a Windows environment and ensure parity in instructions for Linux/macOS users.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/quickstart-role-assignments-bicep.md ...ed-access-control/quickstart-role-assignments-bicep.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all operations, but PowerShell is given equal prominence to CLI, and the 'Next steps' section exclusively promotes a PowerShell-based tutorial. PowerShell is a Windows-centric tool, and there is no mention of Linux-specific considerations or examples (e.g., Bash scripting, Linux shell nuances), nor is there any guidance for Mac/Linux users. The documentation implicitly assumes familiarity with Windows/PowerShell environments.
Recommendations
  • In the 'Next steps' section, offer both CLI-based and PowerShell-based tutorials, or default to CLI (which is cross-platform) to avoid Windows bias.
  • Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS, and consider including Bash script examples or notes for Linux/Mac users.
  • Clarify that PowerShell Core is cross-platform, but note that many users on Linux/macOS may prefer CLI or Bash.
  • Add a brief section or note for Linux/macOS users, highlighting any differences or confirming that the steps are fully supported on those platforms.
  • Ensure that CLI examples are presented first, as it is the most universally accessible tool, and consider de-emphasizing PowerShell unless there is a Windows-specific audience.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/troubleshoot-limits.md ...icles/role-based-access-control/troubleshoot-limits.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing Azure PowerShell examples as the primary or sole command-line automation method, mentioning PowerShell before Azure CLI in multiple places, and referencing Windows-centric tools and patterns. While Azure CLI is mentioned, it is always listed after PowerShell, and no explicit Bash or Linux shell examples are provided. There are no Linux-specific instructions or parity in automation examples.
Recommendations
  • Provide equivalent Azure CLI (az) command examples alongside all PowerShell examples, especially for common tasks like counting role assignments.
  • When listing automation options, mention Azure CLI before or alongside PowerShell to avoid implying PowerShell is the default/preferred tool.
  • Include Bash/Linux shell scripting examples where appropriate, especially for bulk operations or automation.
  • Explicitly state that all command-line examples work cross-platform, and clarify any OS-specific requirements.
  • Where links to PowerShell cmdlets are provided, also link to the equivalent Azure CLI documentation.
  • Consider adding a section or callout for Linux/macOS users, highlighting any differences or confirming parity.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/troubleshooting.md .../articles/role-based-access-control/troubleshooting.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides a significant number of examples and troubleshooting steps using Azure PowerShell cmdlets (e.g., Get-AzRoleAssignment, Remove-AzRoleAssignment), which are primarily associated with Windows environments. In several troubleshooting sections, PowerShell is presented as the main or only scripting interface, with detailed command-line examples and error outputs. While Azure CLI is mentioned and used in some examples (which is cross-platform), PowerShell is often given equal or greater prominence, and in some cases, only PowerShell examples are provided for certain troubleshooting flows. There are no explicit Linux shell (bash) or native Linux tool examples, and Windows/PowerShell patterns are sometimes described before CLI or REST alternatives.
Recommendations
  • For every PowerShell example, provide an equivalent Azure CLI (bash/shell) example, especially for common tasks like listing, assigning, or removing role assignments.
  • When showing troubleshooting steps or error messages, include both PowerShell and CLI outputs where applicable.
  • Where PowerShell is referenced, clarify that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
  • If possible, add bash script snippets or usage patterns for Linux users, especially for filtering or processing output (e.g., using jq or grep with az CLI).
  • In sections where PowerShell is presented first, consider presenting Azure CLI examples first or side-by-side to avoid a Windows-first impression.
  • Explicitly mention that all management tasks can be performed from Linux/macOS using Azure CLI or REST API, not just PowerShell.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/transfer-subscription.md ...les/role-based-access-control/transfer-subscription.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page primarily uses Azure CLI and Bash examples, which are cross-platform, but there are subtle signs of Windows bias. Specifically, instructions for listing ACLs on Azure Data Lake Storage Gen2 mention using the Azure portal or PowerShell, with no mention of Linux-native tools or commands. References to configuring managed identities on Azure VMs and VMSS link to documentation for Windows VMs first, and PowerShell is implied as a tool for some steps. There are no explicit Linux shell or command examples for these scenarios, and Linux tools are not mentioned where relevant.
Recommendations
  • Where PowerShell is mentioned for listing ACLs or other tasks, also provide equivalent Bash/Azure CLI or Linux-native command examples.
  • When linking to managed identity configuration guides, include both Windows and Linux VM documentation links, or clarify that the Azure CLI examples work on both platforms.
  • Explicitly mention that Azure CLI commands can be run from Bash on Linux, macOS, or Windows, and provide any platform-specific notes if needed.
  • If any step requires a tool or method only available on Windows (such as PowerShell), provide an alternative for Linux users or clarify cross-platform options.
GitHub Create Pull Request
Role Based Access Control Allow read access to blobs based on tags and custom security attributes - Azure ABAC ...ccess-control/conditions-custom-security-attributes.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. The main workflow is described using the Azure portal (which is cross-platform but often Windows-centric in screenshots and UI conventions). When command-line examples are given, Azure PowerShell is presented first and in greater detail, with full command sequences and error messages. Azure CLI examples are provided, but they appear after the PowerShell section. There is no mention of Linux/macOS-specific considerations, nor are there any examples using Bash scripting, native Linux tools, or platform-specific troubleshooting tips. The documentation assumes that users are familiar with PowerShell and Windows-style command windows, which may create friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
  • Include explicit notes or troubleshooting tips for Linux/macOS users, such as authentication differences, file path conventions, or environment setup.
  • Add Bash script examples for common tasks, especially for steps involving JSON manipulation or automation.
  • Clarify that all command-line steps can be performed on Linux/macOS, and specify any platform-specific requirements.
  • Use neutral terminology for command windows (e.g., 'terminal' instead of 'command window') and avoid Windows-centric screenshots where possible.
GitHub Create Pull Request
Role Based Access Control Azure permissions for Hybrid + multicloud - Azure RBAC ...-based-access-control/permissions/hybrid-multicloud.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation lists Azure permissions for hybrid and multicloud resource providers. While most of the content is platform-neutral, there is a notable Windows bias in the Microsoft.AzureStackHCI and Microsoft.HybridCompute sections, which reference Windows Admin Center (WAC) for administrative actions. These permissions specifically mention managing resources via WAC, a Windows-only tool, and do not mention Linux equivalents or alternatives. Additionally, the documentation references 'Windows administrator' before 'Linux root user' in privilege descriptions, suggesting a Windows-first perspective.
Recommendations
  • Add references to Linux management tools (such as SSH, Cockpit, or Azure CLI on Linux) where applicable, especially for administrative actions.
  • Clarify whether similar permissions/actions are available for Linux VMs and how they can be managed.
  • When describing login or admin actions, use platform-neutral language or list Linux options alongside Windows.
  • Provide parity in examples and tool references for both Windows and Linux environments.
GitHub Create Pull Request
Role Based Access Control Create or update Azure custom roles using an Azure Resource Manager template - Azure RBAC ...les/role-based-access-control/custom-roles-template.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses Azure PowerShell examples and instructs users to open Azure Cloud Shell for PowerShell, with no mention of Bash, CLI, or Linux/macOS workflows. All command-line instructions and output are PowerShell-centric, creating friction for Linux/macOS users who may prefer Bash or the Azure CLI.
Recommendations
  • Add equivalent Azure CLI (az) examples for all deployment, review, update, and cleanup steps.
  • Mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
  • Show Bash/CLI commands before or alongside PowerShell commands to avoid Windows-first perception.
  • Clarify any platform-specific requirements or limitations for each method.
GitHub Create Pull Request
Role Based Access Control Examples to delegate Azure role assignment management with conditions - Azure ABAC ...d-access-control/delegate-role-assignments-examples.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only Azure PowerShell examples for command-line automation, with no mention of Azure CLI or REST API equivalents. This creates a bias toward Windows and PowerShell users, as Linux/macOS users typically use Azure CLI or REST API for scripting and automation. The absence of cross-platform examples may hinder non-Windows users from easily following or automating the documented tasks.
Recommendations
  • Add Azure CLI examples for each scenario alongside Azure PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API example payloads or curl commands for users who prefer direct API interaction.
  • Explicitly state that Azure PowerShell can be installed and used on Linux/macOS, but highlight Azure CLI as the preferred cross-platform tool.
  • Consider reordering or parallelizing example tabs so that CLI and PowerShell are presented equally, not PowerShell-only.
GitHub Create Pull Request
Role Based Access Control Delegate Azure access management to others - Azure ABAC ...d-access-control/delegate-role-assignments-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for delegating Azure role assignment management with conditions. However, the PowerShell example is presented before the CLI example, and the CLI syntax uses Windows-style variable assignment (%var%), which is not compatible with Linux/macOS shells. There is no explicit Bash or Linux/macOS shell example, nor are there notes clarifying cross-platform usage for CLI commands. This creates friction for Linux/macOS users who may not be familiar with PowerShell or Windows command syntax.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to reflect CLI's cross-platform nature.
  • Provide explicit Bash/Linux/macOS shell examples for Azure CLI, using 'export VAR=...' or direct command-line arguments instead of Windows-style 'set VAR=...'.
  • Add notes clarifying that Azure CLI is cross-platform and provide guidance for both Windows and Linux/macOS users.
  • Consider including links or references to platform-specific documentation for both PowerShell and CLI usage.
  • Where possible, avoid Windows-centric syntax in CLI examples, or provide both Windows and Linux/macOS variants.
GitHub Create Pull Request
Role Based Access Control List Azure deny assignments - Azure RBAC ...articles/role-based-access-control/deny-assignments.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions and examples for listing Azure deny assignments using the Azure portal and Azure PowerShell, with PowerShell being the only CLI example given. There are no examples or mentions of Azure CLI (cross-platform), Bash, or Linux/macOS-specific workflows. The PowerShell examples and references (including output formatting and Cloud Shell) assume familiarity with Windows-centric tools, and the documentation does not clarify that PowerShell is available cross-platform or provide parity for Linux users.
Recommendations
  • Add Azure CLI examples for listing deny assignments, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell is available on Linux/macOS and provide installation guidance or links.
  • Include Bash script examples or note how REST API calls can be made using curl or similar Linux-native tools.
  • Present CLI examples in a neutral order (e.g., Azure CLI first, then PowerShell) to avoid Windows-first bias.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and show how to use each for this task.
GitHub Create Pull Request
← Previous Page 3 of 10 Next →