Role Based Access Control

106
Total Pages
82
Linux-Friendly Pages
24
Pages with Bias
22.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (36)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/conditions-prerequisites.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/delegate-role-assignments-portal.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation page exclusively describes how to delegate Azure role assignment management using the Azure Portal GUI, with no mention of command-line tools or scripts. There are no examples or references to Windows-specific tools (such as PowerShell), but there is also a complete absence of CLI-based instructions (such as Azure CLI or Bash), which are commonly used on Linux and cross-platform environments. This omission results in an implicit bias toward GUI-based workflows, which are often more familiar to Windows users, and does not address the needs of Linux users or those preferring automation and scripting.
Recommendations:
  • Add equivalent step-by-step instructions using Azure CLI commands for all major tasks described (e.g., assigning roles with conditions, editing conditions).
  • Provide sample scripts for both Bash (Linux/macOS) and PowerShell (Windows) where applicable.
  • Explicitly mention that all operations can be performed via the Azure CLI or REST API, and link to relevant documentation.
  • Ensure that screenshots and examples are balanced between GUI and CLI approaches to support both Windows and Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/conditions-faq.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The documentation mentions PowerShell before Azure CLI and REST API when listing tools for adding the Exists operator to ABAC attributes. This ordering may suggest a preference for Windows-centric tooling, as PowerShell is traditionally associated with Windows environments, even though it is now cross-platform. No exclusive Windows-only tools or missing Linux examples are present, but the ordering could imply a subtle bias.
Recommendations:
  • List Azure CLI before PowerShell when mentioning cross-platform tools, as Azure CLI is natively cross-platform and more familiar to Linux users.
  • Explicitly state that both PowerShell and Azure CLI are available on Windows, Linux, and macOS to reinforce cross-platform parity.
  • Where possible, provide example commands for both Azure CLI and PowerShell, or link to equivalent documentation for each.
  • Avoid defaulting to Windows-associated tools or terminology when describing general workflows.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/elevate-access-global-admin.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/pim-integration.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/troubleshoot-limits.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/resource-provider-operations.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The only potential evidence of Windows bias in this documentation is in the introductory paragraph, where the PowerShell cmdlet (Get-AzProviderOperation) is mentioned before the Azure CLI equivalent (az provider operation list). No other examples, tools, or patterns specific to Windows or PowerShell are present in the rest of the page, which is otherwise a neutral, tabular listing of Azure resource providers and their permissions. There are no command-line examples, screenshots, or tool references that are Windows-specific elsewhere in the document.
Recommendations:
  • When listing ways to retrieve permissions, mention Azure CLI (az provider operation list) before or alongside PowerShell (Get-AzProviderOperation), or present them in parallel to avoid implying a preference.
  • If possible, provide REST API or ARM template options as well, for full cross-platform parity.
  • Continue to avoid Windows- or PowerShell-specific examples elsewhere in the documentation, maintaining the current neutral approach.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/quickstart-role-assignments-template.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/built-in-roles/hybrid-multicloud.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/role-assignments.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation page demonstrates a mild Windows bias by providing a detailed Azure PowerShell example before mentioning Azure CLI or REST API alternatives. The PowerShell example is presented first and in more detail, which may implicitly prioritize Windows tooling. There are no explicit Linux or cross-platform command-line examples, and the PowerShell example may not be as accessible to Linux users.
Recommendations:
  • Provide Azure CLI examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Clearly indicate which examples are platform-specific and which are cross-platform.
  • Balance the order of examples so that cross-platform tools like Azure CLI are not always presented after Windows-centric tools.
  • Include explicit Linux/macOS usage notes or examples where relevant, especially for command-line operations.
  • Consider adding a table or section summarizing equivalent commands in PowerShell, Azure CLI, and REST API for parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/delegate-role-assignments-examples.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/transfer-subscription.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/built-in-roles/security.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/conditions-prerequisites.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/conditions-faq.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation page references PowerShell before Azure CLI and REST API when discussing tools for adding the Exists operator or grouping expressions. This ordering and mention of PowerShell (a Windows-centric tool) first, with no explicit Linux/Bash examples or mention of cross-platform parity, suggests a mild Windows bias. However, Azure CLI (which is cross-platform) is also mentioned, and no examples are given, so the bias is limited to tool ordering and naming.
Recommendations:
  • When listing tools, alternate the order (e.g., mention Azure CLI before PowerShell) or group them as 'Azure CLI, PowerShell, or REST API' to avoid Windows-first bias.
  • Explicitly state that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Where possible, provide example commands for both Azure CLI (Bash/shell) and PowerShell to ensure parity.
  • Avoid implying PowerShell is the primary or default tool for these operations.
  • Consider adding a note or section about using these features on Linux/macOS environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/built-in-roles/hybrid-multicloud.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/built-in-roles/security.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation page is largely platform-neutral in its main content, focusing on role definitions and permissions. However, there is evidence of Windows/Powershell bias in the external 'Learn more' links for some roles (e.g., Attestation Contributor), which point to PowerShell-based quickstarts or guides. There are no explicit Linux CLI or cross-platform examples, and where command-line guidance is referenced, it defaults to PowerShell/Windows-centric tooling.
Recommendations:
  • For every 'Learn more' or quickstart link that points to a PowerShell or Windows-specific guide, ensure there is an equivalent link or section for Azure CLI (az), Bash, or cross-platform scripting.
  • Where possible, provide both PowerShell and Azure CLI (or REST API) examples side by side, especially for common administrative tasks.
  • Audit linked documentation (such as quickstarts) to ensure Linux and Mac users are equally supported and referenced.
  • Explicitly state in the documentation introduction that all roles and permissions can be managed using cross-platform tools, and provide links to those tools.
  • Consider adding a 'Platform support' or 'How to use' section that lists all supported management interfaces (Azure Portal, Azure CLI, PowerShell, REST API) with links to relevant guides for each.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/classic-administrators.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation exclusively uses the Azure Portal (web UI) and Azure Resource Graph (via the portal) for all examples and instructions. There are no command-line examples provided for any platform (Windows, Linux, or macOS), but notably, there is a lack of Azure CLI, Bash, or PowerShell command examples. This omission is a form of bias because it does not address users who prefer or require command-line tools, especially on Linux or macOS platforms. The documentation implicitly assumes a GUI workflow, which is more common among Windows users, and does not mention or provide parity for Linux-oriented workflows.
Recommendations:
  • Add Azure CLI examples for all major operations described (listing classic administrators, removing/converting roles, etc.), as Azure CLI is cross-platform and widely used on Linux.
  • Where possible, provide both Azure CLI and PowerShell examples, and ensure Azure CLI (or Bash) examples are presented first or alongside PowerShell to avoid Windows-first bias.
  • Explicitly mention that all operations can be performed via command-line tools on any supported OS, and link to relevant Azure CLI documentation.
  • If certain operations are only available in the portal, clearly state this and provide a roadmap or alternatives for command-line users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/custom-roles-template.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/delegate-role-assignments-examples.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/custom-roles.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation demonstrates a mild Windows bias by consistently presenting Azure PowerShell examples and references before Azure CLI equivalents. PowerShell is traditionally associated with Windows, and its prioritization may suggest a Windows-centric approach. However, both PowerShell and CLI are covered, and no examples are exclusive to Windows or missing for Linux users. There are no explicit references to Windows-only tools or patterns, but the ordering and emphasis on PowerShell could be improved for cross-platform parity.
Recommendations:
  • Alternate the order of PowerShell and CLI examples or present them side-by-side to avoid implying a preferred platform.
  • Explicitly mention that both Azure PowerShell and Azure CLI are cross-platform and available on Windows, Linux, and macOS.
  • Include brief notes or links clarifying how to install and use Azure PowerShell and Azure CLI on Linux.
  • Where possible, provide bash or shell script snippets alongside PowerShell, especially for automation scenarios.
  • Ensure that all referenced tutorials and guides (in 'Next steps' and throughout) have both PowerShell and CLI versions, and list them in a neutral or alternating order.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/custom-roles-bicep.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation provides both Azure CLI and PowerShell examples for all operations, but consistently presents PowerShell examples alongside CLI, and sometimes before or with equal prominence. PowerShell is a Windows-centric tool, and the CLI examples use syntax that is compatible with both Windows and Linux, but there is no explicit mention of Linux or Bash-specific usage. There are no Linux-only examples, nor is there guidance for Linux users regarding shell differences (e.g., variable assignment differences between Bash and PowerShell).
Recommendations:
  • Explicitly mention that Azure CLI commands are cross-platform and provide Bash-specific syntax for variable assignment (e.g., myActions='["..."]' vs. myActions=(...)).
  • Add a 'Bash' tab or section for variable assignment and command usage, clarifying differences from PowerShell.
  • If PowerShell is included, clarify that it is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
  • Consider providing a short note or table at the start of the 'Deploy the Bicep file' section indicating which tools are available on which platforms.
  • Ensure that all examples are tested and shown to work on Linux shells (Bash, zsh) and not just Windows/PowerShell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/delegate-role-assignments-overview.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation provides both Azure PowerShell and Azure CLI examples for delegating role assignment management with conditions. However, the PowerShell example is presented before the Azure CLI example, which can be interpreted as a 'windows_first' bias. Additionally, the PowerShell example is more detailed and uses Windows-style variable assignment (e.g., $variable), while the Azure CLI example uses Windows batch syntax for variable assignment (set variable=value), which is not compatible with Linux shells. There are no explicit Linux shell (bash) examples, and the CLI example does not use cross-platform syntax, indicating a 'powershell_heavy' and 'windows_first' bias.
Recommendations:
  • Provide Azure CLI examples using bash-compatible syntax (e.g., export VAR=value or VAR=value) for variable assignment, rather than Windows batch 'set' commands.
  • Present Azure CLI (cross-platform) examples before or alongside PowerShell examples to avoid the perception of Windows-first bias.
  • Explicitly mention that Azure CLI commands are cross-platform and provide both Windows and Linux/macOS shell variants where variable assignment or scripting is involved.
  • Consider adding a note or tab for Linux/macOS users, especially in sections where scripting or environment setup differs between platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/delegate-role-assignments-portal.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation page exclusively describes how to delegate Azure role assignment management using the Azure Portal UI, with no mention of command-line tools, scripts, or automation. There are no examples or references to Windows-specific tools (such as PowerShell), but there is also a complete absence of CLI-based instructions (such as Azure CLI or Bash), which are commonly used on Linux and cross-platform environments. This omission may disadvantage Linux users or those preferring automation.
Recommendations:
  • Add parallel instructions for performing the same tasks using Azure CLI commands, which are cross-platform and commonly used on Linux.
  • If PowerShell examples are added in the future, ensure equivalent Bash/Azure CLI examples are also provided.
  • Include references to relevant automation or scripting documentation for both Windows and Linux environments.
  • Explicitly state that the described steps can be performed on any OS via the Azure Portal, but provide links or sections for CLI/API-based approaches for users who prefer or require non-GUI workflows.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/deny-assignments.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/permissions/hybrid-multicloud.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Windows First
Summary:
The documentation page is primarily a reference listing of Azure permissions for hybrid and multicloud resource providers. While most of the content is platform-neutral, there is evidence of Windows bias in the repeated mention of 'Windows Admin Center' as a management tool for certain actions (e.g., 'WACloginAsAdmin/Action'), and in the focus on Azure Stack HCI and SCVMM, which are Windows-centric technologies. The documentation does not provide Linux-specific management tool equivalents or mention Linux-first patterns, and the Windows Admin Center is presented as the default or only option for administrative access.
Recommendations:
  • Where actions reference Windows Admin Center, add notes or examples for Linux management tools (such as Cockpit, SSH, or Azure CLI on Linux) if supported.
  • Clarify in the description of actions like 'loginAsAdmin' that both Windows administrator and Linux root user privileges are supported, and provide parity in examples or references.
  • If Linux-based management or integration is supported for Azure Stack HCI or SCVMM, explicitly mention those options.
  • Consider including references or links to Linux management documentation alongside Windows Admin Center references.
  • Review the order and prominence of Windows-specific tools and ensure Linux equivalents are given equal visibility where applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/resource-provider-operations.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The only notable evidence of Windows bias is in the introductory paragraph, where the PowerShell cmdlet (Get-AzProviderOperation) is mentioned before the Azure CLI equivalent (az provider operation list). Otherwise, the documentation is platform-neutral, listing Azure resource providers and services without OS-specific examples, tools, or patterns.
Recommendations:
  • When mentioning both PowerShell and Azure CLI commands, alternate their order or explicitly state that both are cross-platform, to avoid implying a Windows-first approach.
  • Consider adding a note clarifying that both PowerShell (with Az module) and Azure CLI are available on Windows, Linux, and macOS, ensuring users know there is no platform restriction.
  • Review other related documentation to ensure Linux and cross-platform usage is equally represented, especially in command-line examples.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/quickstart-role-assignments-template.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/pim-integration.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/quickstart-role-assignments-bicep.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/role-assignments-external-users.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation exclusively describes how to assign Azure roles to external users using the Azure portal, with all instructions and screenshots focused on the graphical user interface. There are no command-line examples, nor are there references to platform-specific tools such as PowerShell, Azure CLI, or Bash. However, the absence of any command-line examples means that Linux users (who may prefer or require CLI-based workflows) are not served. There is an implicit bias in that only the portal (web UI) workflow is documented, with no mention of cross-platform alternatives.
Recommendations:
  • Add equivalent instructions for assigning Azure roles to external users using the Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • If relevant, provide PowerShell examples, but ensure Azure CLI examples are presented first or alongside them to maintain parity.
  • Include links to documentation for both Azure CLI and PowerShell role assignment workflows.
  • Explicitly mention that the Azure portal is web-based and platform-agnostic, but also acknowledge that some users may prefer or require command-line automation.
  • Consider adding a section comparing the portal, Azure CLI, and PowerShell approaches, highlighting their cross-platform compatibility.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/troubleshoot-limits.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/role-assignments.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation page shows a moderate Windows bias by providing its first and most detailed example using Azure PowerShell, which is most commonly used on Windows. The PowerShell example is presented before the Azure CLI and REST API examples, and is referenced multiple times as a primary tool for role assignment management. There are no explicit Linux-specific examples or mentions of Linux shell usage, and the CLI example is not shown in a Linux context.
Recommendations:
  • Provide parallel examples for both Azure PowerShell and Azure CLI, explicitly showing CLI usage in a Bash/Linux shell context.
  • When listing tools or examples, alternate the order or present Azure CLI examples before or alongside PowerShell to avoid 'Windows-first' perception.
  • Include explicit notes that Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
  • Wherever PowerShell is mentioned, clarify that it is available cross-platform, or provide Bash equivalents where appropriate.
  • Add a section or callout for Linux users, highlighting any differences or tips for managing Azure RBAC from Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/role-definitions.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The documentation page presents examples of Azure role definitions as displayed in both Azure PowerShell and Azure CLI, with PowerShell (a Windows-centric tool) consistently mentioned before the cross-platform Azure CLI. There are no Linux-specific examples or tools referenced, but the CLI is included, which is cross-platform. No exclusive use of Windows tools or patterns is present, but the ordering and emphasis slightly favor Windows/PowerShell.
Recommendations:
  • Alternate the order of examples so that Azure CLI (cross-platform) is sometimes presented before Azure PowerShell, or present both simultaneously without implied priority.
  • Explicitly mention that Azure CLI is available on Windows, Linux, and macOS to reinforce cross-platform support.
  • Where possible, include example commands or outputs for both PowerShell and CLI in parallel, and clarify that PowerShell Core is also available cross-platform.
  • If scripting examples are provided, consider including bash or shell script snippets alongside PowerShell where appropriate.
  • Add a brief note or section highlighting tool parity and platform support for managing Azure RBAC roles.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/troubleshooting.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/transfer-subscription.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.