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 26-50 of 240 flagged pages
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/conditions-faq.md ...n/articles/role-based-access-control/conditions-faq.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits mild Windows bias by mentioning PowerShell and linking to PowerShell documentation before Azure CLI and REST API equivalents. Windows tools (PowerShell) are referenced by name, and the order of examples and tool mentions tends to favor Windows-first patterns. Linux parity is present via Azure CLI and REST API, but the prominence and ordering suggest a preference for Windows environments.
Recommendations
  • Alternate the order of tool mentions (e.g., list Azure CLI before PowerShell in some instances).
  • Explicitly state cross-platform compatibility for all tools, clarifying that Azure CLI and REST API are available on Linux and macOS.
  • Provide example commands for both PowerShell and Azure CLI side by side, or link to equivalent Linux/macOS usage guides.
  • Avoid using 'other tools, such as PowerShell...' phrasing that implies PowerShell is the primary or default option.
  • Add a note or table summarizing platform support for each tool mentioned.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/conditions-format.md ...rticles/role-based-access-control/conditions-format.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page shows mild Windows bias. The only explicit mention of command-line tooling is in the context of PowerShell, which is a Windows-centric tool, and the Azure portal. While the Azure CLI and REST API are mentioned, PowerShell is listed first when discussing tools for adding the Exists operator. There are no explicit Linux shell or bash examples, and the only special character guidance is for Azure PowerShell string escaping. No Linux-specific patterns or tools are referenced.
Recommendations
  • Ensure parity by providing examples for both PowerShell and Azure CLI, with CLI examples shown first or side-by-side.
  • Include Linux shell/bash usage notes where relevant, especially for special character escaping.
  • When listing tools, alternate or randomize the order between PowerShell and Azure CLI, or group them together as 'cross-platform'.
  • Add explicit examples or links for Linux users, such as using Azure CLI in bash or zsh.
  • Clarify that all features are available via Azure CLI and REST API, and provide links or code snippets for those platforms.
GitHub Create Pull Request
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways. The Azure portal (a GUI tool most commonly used on Windows) is presented first and in greatest detail for all workflows. PowerShell examples are provided in a dedicated tab, but there are no equivalent Bash or Linux shell script examples. The documentation does not mention Linux-specific tools or patterns, nor does it address platform differences in authentication or environment setup. While Azure CLI and REST API examples are included, there is no discussion of running these commands on Linux systems, nor any troubleshooting or environment notes for non-Windows users. The documentation implicitly assumes a Windows-centric workflow and audience.
Recommendations
  • Add explicit Bash/Linux shell script examples for all CLI and REST API workflows, including environment setup and authentication steps.
  • Include notes or troubleshooting tips for running Azure CLI and REST API commands on Linux and macOS, such as handling authentication, environment variables, and file paths.
  • Provide parity in example detail: ensure that CLI and REST API sections are as comprehensive as the Azure portal and PowerShell sections.
  • Mention cross-platform compatibility for all tools (Azure CLI, REST API, PowerShell), and clarify any platform-specific limitations or requirements.
  • Add links to Linux/macOS installation guides for Azure CLI and PowerShell, and reference official documentation for cross-platform usage.
  • Consider reordering sections so that cross-platform tools (CLI, REST API) are presented before or alongside Windows-centric tools (portal, PowerShell) to avoid implicit prioritization.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively provides Azure PowerShell examples for deploying and managing Azure role assignments, with all command-line instructions and scripts tailored to PowerShell and Azure Cloud Shell. There are no equivalent examples or guidance for Linux users using Bash, Azure CLI, or other cross-platform tools. The documentation implicitly assumes a Windows/PowerShell environment, which may disadvantage users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell scripts, including resource group creation, template deployment, and cleanup steps.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both environments.
  • Include guidance for Linux/macOS users, such as how to run commands in Bash or install necessary tools.
  • Ensure that links to tutorials and next steps include cross-platform options, not just PowerShell-focused resources.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides detailed instructions and examples for listing Azure deny assignments using the Azure portal and Azure PowerShell, with PowerShell commands and output shown exclusively. There are no examples or guidance for using Azure CLI (which is cross-platform and preferred on Linux), nor are there bash or Linux-specific instructions. PowerShell is featured as the only command-line tool, which is traditionally associated with Windows environments, and its use is described before REST API options. This creates a bias toward Windows users and leaves Linux users without parity in command-line examples.
Recommendations
  • Add equivalent Azure CLI examples for listing deny assignments, including sample commands and output.
  • Include bash shell usage instructions for Linux users, especially for REST API calls (e.g., using curl).
  • Mention that Azure CLI is available cross-platform and is the recommended tool for Linux/macOS users.
  • Present Azure CLI and PowerShell examples side-by-side, or at least in parallel tabs, to ensure equal visibility.
  • Clarify that PowerShell is available on Linux, but highlight CLI as the default for Linux environments.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Many troubleshooting steps and examples use Azure PowerShell cmdlets (e.g., Get-AzRoleAssignment, Remove-AzRoleAssignment) and show PowerShell-specific error outputs, which are primarily relevant to Windows users. In several sections, PowerShell is mentioned before Azure CLI, and some solutions are described only with PowerShell commands, with no equivalent Bash or Linux shell examples. There is a lack of parity in providing Linux-oriented command-line examples or guidance for users who prefer Bash or non-Windows environments.
Recommendations
  • Ensure all PowerShell examples have equivalent Azure CLI (Bash/shell) examples, especially for troubleshooting and error handling.
  • When listing tools or commands, present Azure CLI and PowerShell side-by-side, or alternate the order to avoid Windows-first bias.
  • Include troubleshooting steps and error outputs for both PowerShell and Azure CLI, and clarify which commands are cross-platform.
  • Add explicit guidance for Linux/macOS users, including common patterns for shell scripting and command usage.
  • Review and update sections that reference only PowerShell or Windows tools to include Azure CLI or REST API alternatives.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively uses Azure PowerShell commands and Cloud Shell (PowerShell) for all deployment, verification, update, and cleanup steps. There are no examples or instructions for Bash, Azure CLI, or Linux-native workflows. Windows-centric tools and patterns (PowerShell, New-AzDeployment, Get-AzRoleDefinition) are mentioned exclusively and before any Linux equivalents, which are entirely absent.
Recommendations
  • Add equivalent Azure CLI (az) examples for all deployment, verification, update, and cleanup steps.
  • Include instructions for using Bash in Azure Cloud Shell, not just PowerShell.
  • Present both PowerShell and CLI/Bash options side-by-side, or indicate which steps are platform-agnostic.
  • Explicitly mention that the steps can be performed from Linux/macOS terminals using Azure CLI.
  • Ensure screenshots and UI references are not Windows-specific.
  • Add a note about cross-platform compatibility and link to platform-specific guides if available.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/custom-roles.md ...ain/articles/role-based-access-control/custom-roles.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. Azure PowerShell is mentioned and exemplified before Azure CLI in most sections, and PowerShell-specific commands and output formats are highlighted. The examples and tutorials prioritize PowerShell, a Windows-centric tool, and do not mention Linux-specific shell usage or considerations. There is no explicit mention of Linux shell environments, nor are there examples using bash or Linux-native tools.
Recommendations
  • Alternate the order of Azure PowerShell and Azure CLI mentions and examples, or present Azure CLI first to reflect its cross-platform nature.
  • Include explicit references to Linux environments (e.g., bash, zsh) and clarify that Azure CLI works natively on Linux and macOS.
  • Provide example commands and outputs using bash or Linux shell syntax where relevant, especially in sections discussing command-line usage.
  • Add a note or section about cross-platform compatibility, including installation and usage differences for PowerShell and CLI on Linux and macOS.
  • Ensure that tutorials and links are balanced between PowerShell and CLI, and consider adding Linux-specific walkthroughs if any platform-specific nuances exist.
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: 2026-01-09 00:34
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 equivalent examples for Azure CLI or Bash scripting. This creates a bias toward Windows and PowerShell users, excluding Linux-first workflows and users who prefer cross-platform tools. The exclusive use of PowerShell and lack of Azure CLI or REST API examples limits accessibility for non-Windows environments.
Recommendations
  • Add equivalent Azure CLI examples for each scenario, showing how to perform the same operations using az role assignment commands.
  • Include Bash scripting samples where appropriate to demonstrate cross-platform automation.
  • Reference REST API methods for role assignment management, with example payloads and curl commands.
  • Clearly indicate that Azure PowerShell is available cross-platform, but also highlight CLI and REST options for Linux and macOS users.
  • Consider reordering or balancing example tabs so that CLI and PowerShell are presented with equal prominence.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides command-line examples exclusively using PowerShell cmdlets (Get-AzRoleEligibilitySchedule, New-AzRoleAssignment, etc.), which are native to Windows environments. There are no equivalent examples for Linux/macOS users, such as Azure CLI or REST API usage. The documentation assumes familiarity with PowerShell and does not mention cross-platform alternatives, resulting in a bias toward Windows tooling and patterns.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands shown, ensuring Linux/macOS users can follow along.
  • Include REST API request examples for listing and modifying role assignments, as these are platform-agnostic.
  • Explicitly mention that PowerShell cmdlets can be run on Linux/macOS (with installation instructions), or provide links to cross-platform setup guides.
  • Where possible, present Azure CLI or REST API examples before or alongside PowerShell examples to avoid Windows-first bias.
  • Clarify in the documentation that all operations can be performed from any supported OS, not just Windows.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently providing Azure PowerShell examples and references before (or instead of) Azure CLI equivalents. In several places, only PowerShell commands are shown for key tasks, with Azure CLI mentioned as an alternative but not exemplified. There are no explicit Linux/bash shell examples, and the use of PowerShell is assumed as the default scripting environment. This may disadvantage Linux users or those who prefer cross-platform CLI tools.
Recommendations
  • Provide Azure CLI (az) command examples alongside PowerShell for all tasks, especially for counting role assignments and querying user information.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and link to installation guides for non-Windows platforms.
  • Where scripting is shown, offer both PowerShell and bash (or shell-agnostic) syntax, or use tabs to let users select their preferred environment.
  • Review references to tools and commands to ensure Linux parity, e.g., avoid assuming PowerShell is the default and highlight cross-platform alternatives.
  • Add a section or note clarifying that all operations can be performed from Linux/macOS using Azure CLI and 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/role-definitions-list.md ...les/role-based-access-control/role-definitions-list.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed examples for Azure PowerShell, which is primarily a Windows-centric tool, and lists PowerShell instructions before Azure CLI. The PowerShell section includes formatting and JSON conversion examples using Windows-specific cmdlets (e.g., FT, FL, ConvertTo-Json), but there are no equivalent Bash or Linux shell examples. While Azure CLI is cross-platform and examples are included, there is no explicit mention of Linux or Bash usage, nor are there examples showing how to use CLI commands in a Linux shell environment. The documentation does not mention Linux-specific tools or patterns, and the PowerShell examples are more extensive and detailed than the CLI ones.
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI commands, including output formatting and piping (e.g., using jq for JSON parsing).
  • Clarify that Azure CLI is cross-platform and provide usage notes for Linux and macOS environments.
  • Balance the depth of examples between PowerShell and CLI sections, ensuring CLI examples cover similar scenarios (e.g., output formatting, filtering, JSON conversion).
  • Consider including a table comparing PowerShell and CLI commands for common tasks, with notes on platform compatibility.
  • Where PowerShell-specific formatting is shown (e.g., FT, FL), provide equivalent CLI/Bash approaches (e.g., grep, jq, awk).
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. While most command-line examples use Azure CLI (which is cross-platform), references to file ACLs and managed identities mention using the Azure portal or PowerShell for Azure Data Lake Storage Gen2, but do not provide equivalent Linux or Bash examples. In managed identity sections, links and examples reference Windows VM configuration before Linux alternatives. There is a lack of explicit Linux/Bash examples for some resource management tasks, and Windows-centric tools (PowerShell) are mentioned without Linux parity.
Recommendations
  • Provide explicit Bash or Linux command examples for listing and managing ACLs, especially for Azure Data Lake Storage Gen2 and Azure Files.
  • When referencing managed identities, include links and examples for both Windows and Linux VM configuration, or present Linux examples first.
  • Where PowerShell or Azure portal is mentioned, also provide Azure CLI or Bash alternatives for Linux users.
  • Review all resource management steps to ensure Linux users have clear, step-by-step CLI instructions, not just Windows/PowerShell-centric guidance.
  • Ensure documentation links and examples are balanced between Windows and Linux environments, or clarify cross-platform applicability.
GitHub Create Pull Request
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Azure portal (web UI, typically accessed from Windows environments) and PowerShell examples, with PowerShell commands given their own section and detailed usage. There is no mention of Linux-specific shell environments (e.g., bash), nor are there examples using native Linux tools or patterns. The Azure CLI is presented, but only generically, without explicit Linux context or troubleshooting. No Linux desktop tools or guidance for Linux users are provided, and the documentation assumes familiarity with Windows-centric workflows and terminology.
Recommendations
  • Add explicit Linux shell (bash/zsh) examples where Azure CLI is used, including environment setup and troubleshooting for Linux users.
  • Include notes or sections addressing differences in experience for Linux users (e.g., browser compatibility, authentication methods, file paths).
  • Mention cross-platform compatibility for Azure CLI and REST API, and provide guidance for installation and usage on Linux systems.
  • Provide parity in troubleshooting steps for Linux environments, such as common issues with Azure CLI on Linux.
  • Avoid assuming the use of Windows tools (such as PowerShell) as the default; clarify that PowerShell Core is cross-platform or offer bash alternatives.
  • Add references to Linux desktop environments and workflows, where relevant, to ensure inclusivity.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
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 exclusively providing PowerShell examples for command-line operations, without mentioning or providing equivalent instructions for Linux users (e.g., Azure CLI, Bash). All automation and scripting guidance relies on PowerShell, a Windows-centric tool, and there is no reference to Linux-native tools or cross-platform alternatives. The structure also presents Windows/PowerShell options before any mention of REST API or other platform-neutral approaches.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that PowerShell Core is available cross-platform, but also provide Bash/Azure CLI syntax for parity.
  • Include guidance for using REST API directly, with curl or other platform-neutral tools, especially for automation scenarios.
  • Where possible, provide side-by-side examples (PowerShell, Azure CLI, REST API) to ensure users on all platforms have clear instructions.
  • Clarify in introductory sections that both Windows and Linux users are supported, and link to platform-specific setup guides if needed.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias, primarily through its use of Windows/Powershell-centric references in 'Learn more' links (e.g., Attestation Contributor links to a Powershell quickstart, with no mention of CLI/Bash/Linux alternatives). There are no explicit Linux or cross-platform examples, and Windows tools/patterns are referenced before any Linux equivalents (if present). The lack of Linux-specific instructions or parity in example tooling is notable.
Recommendations
  • Add Azure CLI and Bash examples alongside Powershell references, especially in 'Learn more' links and quickstarts.
  • Explicitly mention cross-platform tools and workflows (e.g., Azure CLI, REST API) where Powershell is referenced.
  • Ensure that documentation for role management and security operations includes Linux/macOS usage scenarios and commands.
  • Where possible, provide links to both Windows and Linux guides for each role or operation.
  • Review all referenced quickstarts and troubleshooting guides to ensure Linux parity and visibility.
GitHub Create Pull Request
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
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides troubleshooting steps for Azure role assignment conditions and includes both Azure PowerShell and Azure CLI examples. However, PowerShell (a Windows-centric tool) is mentioned first in error message sections, and PowerShell-specific quoting rules and issues are discussed in more detail than Bash equivalents. The documentation also references Windows tools (e.g., Visual Studio Code) as recommended editors. While Azure CLI and Bash examples are present, the ordering and depth of PowerShell coverage indicate a mild Windows bias.
Recommendations
  • Alternate the order of PowerShell and CLI/Bash examples so that Linux tools are not always presented after Windows tools.
  • Provide equal depth of troubleshooting for Bash/Azure CLI as is given for PowerShell, including common Bash pitfalls and editor recommendations for Linux users.
  • Mention cross-platform editors (e.g., VS Code, nano, vim) alongside Windows-centric ones.
  • Explicitly state that all examples work on both Windows and Linux, and highlight any platform-specific caveats.
  • Add troubleshooting sections for common Linux shell issues (e.g., quoting, escaping) where relevant.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/custom-roles.md ...ain/articles/role-based-access-control/custom-roles.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell is frequently mentioned and used for examples, often before Azure CLI. The custom role example is first shown in Azure PowerShell format, and input/output formats for PowerShell are described before CLI and REST API. The Next Steps section lists the PowerShell tutorial before the CLI tutorial. There is a general emphasis on PowerShell, which is a Windows-centric tool, and no explicit mention of Linux-specific patterns, shell environments, or cross-platform scripting considerations.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to better support Linux users.
  • Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Provide bash or shell scripting examples alongside PowerShell, especially for automation scenarios.
  • Add notes or links for installing and using Azure CLI on Linux.
  • Clarify that PowerShell Core is available cross-platform, but highlight CLI as the default for Linux environments.
  • Ensure that all tutorials and walkthroughs have equal coverage for both PowerShell and CLI, and consider adding REST API/curl examples for advanced Linux users.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides only Azure PowerShell examples for scripting role assignment conditions, with no equivalent Azure CLI or REST API examples. Azure PowerShell is most commonly used on Windows, and its exclusive use here may disadvantage Linux/macOS users who typically prefer Azure CLI or REST. There is no mention of Linux-specific tools or cross-platform alternatives, and the scripting examples are all in PowerShell syntax.
Recommendations
  • Add equivalent Azure CLI examples for each scenario, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include REST API example payloads or curl commands to demonstrate how to perform these actions programmatically from any OS.
  • Explicitly mention that Azure PowerShell is available on Linux/macOS, but highlight Azure CLI as a first-class, cross-platform alternative.
  • Consider providing Bash script snippets alongside PowerShell, or use tabbed code blocks for PowerShell, CLI, and REST.
  • Review the documentation for any Windows-centric terminology or assumptions and clarify cross-platform support where relevant.
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: 2026-01-08 00:53
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 commands and scripts for all deployment, verification, update, and cleanup steps. There are no examples or instructions for using Azure CLI, Bash, or Linux-native tools. The workflow assumes use of the Azure Cloud Shell in PowerShell mode, which is more familiar to Windows users. No Linux or cross-platform alternatives are mentioned, and PowerShell is presented as the default/only method.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, including deployment, verification, update, and cleanup steps.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
  • Include sample Bash scripts for Linux users, especially for parameter input and template deployment.
  • Where possible, use cross-platform commands and tools, or clarify which steps are platform-agnostic.
  • Reorder examples so that CLI/Bash and PowerShell are presented with equal prominence, or alternate which is shown first.
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: 2026-01-08 00:53
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 explicit PowerShell commands and output. There is no mention of Azure CLI, Bash, or Linux-native tooling, nor are there examples for non-Windows command-line environments. The PowerShell section is prominent and detailed, while Linux users are left to infer usage from REST API examples or use the portal.
Recommendations
  • Add equivalent Azure CLI examples for listing deny assignments, including sample commands and expected output.
  • Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) and provide installation links.
  • Include Bash shell usage examples for REST API calls (e.g., using curl), with sample authentication and output parsing.
  • Reorder or parallelize the PowerShell and CLI sections so that neither is given priority over the other.
  • Clarify that PowerShell is available on Linux, but also highlight CLI and Bash options for Linux users.
  • Add a table comparing PowerShell, CLI, and REST API approaches, indicating platform compatibility.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently presenting Azure PowerShell commands as the primary or sole CLI example for scripting tasks, such as counting role assignments. References to PowerShell and Windows-centric tools (e.g., Get-AzRoleAssignment, Get-MgUser) are frequent and appear before or instead of Linux-friendly alternatives. While Azure CLI is mentioned for some user lookup tasks, it is not used for the main RBAC troubleshooting workflows. There are no Bash or Linux shell examples, and the documentation does not address cross-platform usage patterns or provide parity for Linux users.
Recommendations
  • Provide equivalent Azure CLI (az) examples alongside PowerShell commands for all scripting tasks, especially for counting and managing role assignments.
  • Explicitly mention that both Azure CLI and PowerShell are cross-platform, and clarify usage on Linux/macOS where appropriate.
  • Include Bash shell script snippets for common workflows, such as listing and removing role assignments.
  • Ensure that references to tools and commands do not default to Windows/PowerShell; alternate between CLI and PowerShell, or present both in tabs.
  • Add notes or sections for Linux/macOS users, highlighting any differences or considerations in command syntax or environment setup.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is frequently referenced for troubleshooting and examples, often with detailed command-line instructions and error messages. In several cases, PowerShell commands are presented before or instead of equivalent Azure CLI commands, and troubleshooting steps are described in a Windows-centric manner (e.g., referencing 'PS C:\>' prompts). There are few, if any, explicit Linux shell examples, and no mention of Linux-specific tools or patterns. The documentation implicitly assumes familiarity with Windows/PowerShell environments, which may disadvantage Linux users.
Recommendations
  • Provide equivalent Azure CLI (bash) examples alongside PowerShell commands, especially for troubleshooting and role assignment management.
  • Include Linux shell (bash/zsh) command examples and error outputs where PowerShell is used, to ensure parity.
  • Avoid using Windows-specific prompts (e.g., 'PS C:\>') in generic troubleshooting steps; use neutral formatting or show both Windows and Linux shell prompts.
  • Explicitly mention that Azure CLI works cross-platform and provide guidance for Linux/macOS users where relevant.
  • Where troubleshooting steps involve PowerShell, add parallel instructions for Azure CLI or REST API, and clarify when a solution is platform-agnostic.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively provides Azure PowerShell examples for deploying and cleaning up ARM templates, with all command-line instructions assuming use of PowerShell in Azure Cloud Shell. There are no CLI or Bash examples, nor any mention of Linux-specific workflows or tools. The 'Next steps' section also directs users to a PowerShell-focused tutorial, further reinforcing a Windows-centric approach.
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 guidance for users on Linux or macOS.
  • Include links to tutorials or documentation that use Azure CLI or REST API methods for role assignment.
  • Ensure that Linux and cross-platform workflows are represented equally and, where possible, presented before or alongside Windows/PowerShell examples.
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-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 detailed prerequisites for Azure PowerShell (a Windows-centric tool) before Azure CLI, and by listing multiple specific PowerShell modules and versions. The PowerShell section is more prominent and detailed than the Azure CLI section, which is brief. There is no mention of Linux-specific considerations, nor are there examples or notes about using these tools on Linux or macOS. The documentation implicitly assumes a Windows environment by focusing on PowerShell and omitting cross-platform guidance.
Recommendations
  • Provide equal detail for Azure CLI as for PowerShell, including any required extensions or modules for CLI.
  • Explicitly mention that both Azure PowerShell and Azure CLI are cross-platform and can be used on Windows, Linux, and macOS.
  • Include notes or examples for using these tools on Linux/macOS, such as installation instructions or environment-specific caveats.
  • Avoid listing PowerShell prerequisites before CLI unless there is a technical reason; consider presenting both options in parallel or in a neutral order.
  • If there are differences in behavior or prerequisites between platforms, document them explicitly.
GitHub Create Pull Request
← Previous Page 2 of 10 Next →