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 176-200 of 240 flagged pages
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/conditions-role-assignments-template.md ...access-control/conditions-role-assignments-template.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for deploying the ARM template, but the PowerShell (Windows-centric) example is presented first. There is no mention of Linux-specific shell usage (e.g., Bash), nor are there any notes about platform differences or considerations for Linux users. The documentation implicitly assumes familiarity with PowerShell, which is primarily used on Windows, and does not offer parity guidance for Linux environments.
Recommendations
  • Alternate the order of examples so that Azure CLI (cross-platform) is shown before PowerShell, or present both side-by-side.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide a Bash shell example if relevant.
  • Add a note clarifying that PowerShell is typically used on Windows, while Azure CLI is available on all major platforms.
  • Include troubleshooting or platform-specific notes for Linux users, if there are any known differences or requirements.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/delegate-role-assignments-overview.md ...d-access-control/delegate-role-assignments-overview.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides platform-specific command-line examples for Azure PowerShell and Azure CLI. The PowerShell example is presented before the Azure CLI example, which may suggest a Windows-first bias. The PowerShell example uses Windows-specific syntax, while the Azure CLI example uses 'set' and '%' variable syntax, which is also Windows-centric (rather than Bash-style 'export' and '$' variables for Linux/macOS). There are no explicit Linux shell examples, and the CLI example does not use cross-platform conventions.
Recommendations
  • Provide Azure CLI examples using Bash syntax (e.g., 'export' and '$VARIABLE') to ensure Linux/macOS parity.
  • Add notes or tabs clarifying which examples are for Windows (PowerShell, CMD) and which are for Linux/macOS (Bash).
  • Ensure that CLI examples use cross-platform variable syntax, or provide both Windows and Linux/macOS variants.
  • Consider listing Azure CLI (cross-platform) examples before PowerShell to avoid Windows-first ordering.
  • Explicitly mention that Azure CLI is available on all platforms and provide installation/use guidance for Linux/macOS users.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/rbac-and-directory-admin-roles.md ...based-access-control/rbac-and-directory-admin-roles.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page consistently references the Azure portal as the primary interface for managing roles and subscriptions, with no mention of Linux-specific tools or workflows. While Azure CLI is briefly listed as a way to access role information, all screenshots, instructions, and examples focus on the Azure portal (a web UI), which is most commonly used on Windows. There are no examples using Linux shell commands, nor is there mention of Linux-native tools or patterns for role management. PowerShell is referenced in passing, but not heavily; however, the lack of parity for Linux command-line usage is notable.
Recommendations
  • Include examples for managing roles using Azure CLI commands, which are cross-platform and commonly used on Linux.
  • Add instructions or screenshots for role management using the Azure CLI in a Linux shell environment.
  • Explicitly mention that all role management operations can be performed from Linux, macOS, and Windows using Azure CLI and REST APIs.
  • Provide parity in documentation by listing Azure CLI and REST API methods before or alongside Azure portal and PowerShell instructions.
  • Consider adding a section or callout for Linux users, highlighting cross-platform tools and workflows.
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
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Azure PowerShell examples before Azure CLI examples, and provides detailed PowerShell command usage and output, including formatting and JSON conversion, which are most relevant to Windows and PowerShell users. While Azure CLI examples are present and comprehensive, there is a slight prioritization of Windows/PowerShell tooling and patterns over Linux-native equivalents. No explicit Linux shell (bash/zsh) examples or notes about cross-platform usage are provided, and PowerShell-specific formatting commands (FT, FL, ConvertTo-Json) are highlighted without Linux shell analogs.
Recommendations
  • Alternate the order of PowerShell and Azure CLI sections, or present CLI examples first to avoid implicit prioritization.
  • Add Linux shell (bash/zsh) examples, including usage of jq or grep for filtering and formatting JSON output from Azure CLI.
  • Explicitly note that Azure CLI is cross-platform and provide guidance for both Windows and Linux users.
  • Where PowerShell formatting commands are shown (e.g., FT, FL, ConvertTo-Json), provide equivalent Linux/CLI commands (e.g., jq, grep) for output manipulation.
  • Include a short section or callout on platform parity, clarifying that all CLI examples work on Linux, macOS, and Windows.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/permissions/hybrid-multicloud.md ...-based-access-control/permissions/hybrid-multicloud.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias primarily through the repeated mention and privileged placement of Windows-specific tools and patterns, such as Windows Admin Center (WAC) actions for administrative access and management. These actions are explicitly called out for several resource providers (e.g., Microsoft.AzureStackHCI, Microsoft.HybridCompute), with no equivalent Linux-focused tooling or examples provided. The terminology and feature set (e.g., 'loginAsAdmin' with Windows administrator or Linux root user privilege) also tend to mention Windows first, and the only named management tool is Windows Admin Center, with no Linux-native alternatives referenced.
Recommendations
  • Add examples and permissions for Linux-native management tools (e.g., Cockpit, SSH, Ansible) where applicable, especially for administrative and remote management actions.
  • When describing login actions, explicitly mention Linux root access first or equally alongside Windows administrator, and clarify parity in capabilities.
  • Provide documentation or links for Linux-specific workflows and tools for hybrid/multicloud scenarios, not just Windows Admin Center.
  • Ensure that any references to management actions (e.g., WACloginAsAdmin) are balanced with Linux equivalents or note if such equivalents do not exist.
  • Review terminology to avoid Windows-first ordering (e.g., 'Windows administrator or Linux root user' could be 'Linux root user or Windows administrator').
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/resource-provider-operations.md ...e-based-access-control/resource-provider-operations.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates Windows bias primarily in the introductory guidance for obtaining the latest permissions, where the Windows PowerShell cmdlet (Get-AzProviderOperation) is mentioned before the Azure CLI equivalent (az provider operation list). This ordering implicitly prioritizes Windows/PowerShell tooling. No Linux-specific tools or patterns are highlighted, and no explicit Linux examples are provided. The rest of the page is a service/resource provider listing and does not contain OS-specific instructions or examples.
Recommendations
  • List Azure CLI commands before PowerShell commands when both are available, as Azure CLI is cross-platform and more familiar to Linux users.
  • Explicitly mention that both Azure CLI and PowerShell are supported on Windows, Linux, and macOS, to avoid implying PowerShell is Windows-only.
  • Where possible, provide examples or links to usage on Linux (e.g., bash shell, Azure CLI on Linux) to reinforce parity.
  • Review other documentation pages linked from this one to ensure Linux parity in examples and tool recommendations.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/permissions/migration.md ...les/role-based-access-control/permissions/migration.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page lists Azure RBAC permissions for migration-related resource providers. While the content is mostly platform-neutral, there is evidence of Windows bias in the naming and focus of resource types and actions, especially in the 'Microsoft.OffAzure' provider, which heavily references Hyper-V (a Windows virtualization technology), IIS (Windows web server), and other Windows-centric concepts. These Windows technologies are mentioned explicitly and in detail, while Linux equivalents (such as KVM, Apache/Nginx, etc.) are not referenced. The ordering of providers also places Windows-centric tools (DataBox, DataBoxEdge, DataMigration, Migrate, OffAzure) before mentioning VMware, which is more cross-platform.
Recommendations
  • Add explicit references to Linux migration scenarios and technologies (e.g., KVM, LXC, Apache, Nginx) where applicable.
  • Include permissions and examples for Linux-based migration tools and resource types if supported.
  • Ensure parity in documentation by listing Linux and open-source migration scenarios alongside Windows/Hyper-V/IIS examples.
  • Consider reordering or grouping resource providers to avoid implicit prioritization of Windows technologies.
  • Provide links or references to Linux migration documentation and best practices.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/scope-overview.md ...n/articles/role-based-access-control/scope-overview.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. When describing how to determine the scope for a resource, it suggests using the Azure portal and then lists Azure PowerShell before Azure CLI as command-line options. The only explicit command-line example given is Azure PowerShell, with Azure CLI shown as output JSON rather than a command. There are no Linux-specific tools or shell examples (e.g., Bash), and PowerShell is mentioned first, which is more commonly associated with Windows environments.
Recommendations
  • Provide explicit Azure CLI command examples alongside Azure PowerShell, not just output.
  • Ensure Azure CLI (cross-platform) is mentioned before or equally with PowerShell in instructions.
  • Include Bash shell examples for Linux users where relevant.
  • Clarify that both Azure CLI and PowerShell are cross-platform, and provide installation/use guidance for Linux.
  • Avoid implying PowerShell is the default or preferred method unless justified by usage data.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/quickstart-role-assignments-bicep.md ...ed-access-control/quickstart-role-assignments-bicep.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all operations, but PowerShell is given equal prominence throughout, and the 'Next steps' section exclusively links to a PowerShell tutorial, reinforcing a Windows-centric workflow. There is no explicit mention of Linux-specific considerations or shell environments, nor are there examples tailored for Bash or other Linux-native tools.
Recommendations
  • Include explicit references to Bash or Linux shell environments where Azure CLI is used, clarifying cross-platform compatibility.
  • Balance 'Next steps' links by providing tutorials for both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric).
  • Add notes or sections highlighting that Azure CLI commands work natively on Linux, macOS, and Windows, while Azure PowerShell is primarily used on Windows.
  • Consider including troubleshooting or setup instructions for Linux users, such as installing Azure CLI on Linux.
  • Avoid defaulting to PowerShell in advanced or follow-up tutorials unless parity is maintained with CLI/bash alternatives.
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
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily uses Azure CLI and Bash examples, which are cross-platform, but there is evidence of Windows bias in the section about listing ACLs for Azure Data Lake Storage Gen2. It suggests using the Azure portal or PowerShell, but does not provide equivalent Linux or Bash CLI examples for listing ACLs. Additionally, links for configuring managed identities on VMs and VMSS point to guides for Windows VMs first, with no explicit mention of Linux VM guides or parity.
Recommendations
  • Provide explicit Azure CLI or Bash examples for listing ACLs on Azure Data Lake Storage Gen2 and Azure Files, ensuring Linux users are supported.
  • Include links and examples for configuring managed identities on Linux VMs and VMSS, not just Windows.
  • Where PowerShell or portal is mentioned, always offer an equivalent Azure CLI/Bash command or script.
  • Review all referenced guides to ensure Linux parity and add cross-platform notes where relevant.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/role-assignments.md ...articles/role-based-access-control/role-assignments.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by presenting Azure PowerShell examples and references before Azure CLI and REST API equivalents. The PowerShell example is given first, and links to PowerShell documentation precede those for CLI. While Azure CLI is mentioned and examples are provided, the ordering and emphasis favor Windows/PowerShell tools, which are more common on Windows platforms. No Linux-specific tools or shell examples (e.g., Bash) are provided, and the documentation does not discuss platform differences or considerations for Linux users.
Recommendations
  • Alternate the order of examples and references, sometimes presenting Azure CLI (cross-platform) before PowerShell.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide Bash shell examples where appropriate.
  • Add notes or sections highlighting parity between PowerShell and CLI, and clarify any platform-specific behaviors.
  • Ensure links to CLI and REST API documentation are as prominent as those for PowerShell.
  • Consider including screenshots or walkthroughs for Linux environments, not just Windows/PowerShell.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/role-assignments-remove.md ...s/role-based-access-control/role-assignments-remove.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides detailed examples for both Azure PowerShell and Azure CLI, but the PowerShell section is presented before the CLI section and includes more example scenarios. The PowerShell examples use Windows-style prompts (PS C:\>), which may reinforce a Windows-centric approach. There are no explicit Linux shell examples (e.g., bash), and no mention of Linux-specific considerations or alternative shells for Azure CLI usage.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Include explicit bash or Linux shell prompts (e.g., $) in CLI examples to demonstrate cross-platform usage.
  • Add notes clarifying that Azure CLI commands work on Linux, macOS, and Windows, and provide any platform-specific guidance if relevant.
  • Balance the number and complexity of CLI and PowerShell examples to ensure parity.
  • Avoid using Windows-specific prompts (PS C:\>) unless necessary, or provide equivalent Linux/macOS shell prompts.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/resource-provider-operations.md ...e-based-access-control/resource-provider-operations.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/role-assignments.md ...articles/role-based-access-control/role-assignments.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
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
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
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
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/custom-roles-bicep.md ...ticles/role-based-access-control/custom-roles-bicep.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/delegate-role-assignments-overview.md ...d-access-control/delegate-role-assignments-overview.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/permissions/hybrid-multicloud.md ...-based-access-control/permissions/hybrid-multicloud.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 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.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/role-assignments.md ...articles/role-based-access-control/role-assignments.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Role Based Access Control Azure built-in roles - Azure RBAC ...n/articles/role-based-access-control/built-in-roles.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation lists Azure built-in roles in a platform-neutral manner, but there are several roles and descriptions that reference Windows-specific technologies and tools (e.g., Windows Admin Center, Windows 365, NTFS permissions, SMB share ACLs). These Windows-centric roles are present without equivalent Linux/macOS roles or explanations, and Windows terminology appears more frequently and sometimes first in relevant sections. However, the documentation does include roles for Linux-centric technologies (e.g., Azure Red Hat OpenShift, Kubernetes), and does not provide command-line examples or usage patterns that would favor Windows or PowerShell over Linux/macOS.
Recommendations
  • Where Windows-specific roles or terminology are used (e.g., Windows Admin Center, NTFS/SMB ACLs), add clarifying notes about Linux/macOS equivalents or limitations.
  • For roles that reference Windows file server ACLs, provide context for Linux file permissions and clarify how Azure RBAC maps to POSIX ACLs.
  • Ensure that any platform-specific role (e.g., Windows 365 Network User) is balanced with Linux/macOS equivalents if available, or explicitly state that no equivalent exists.
  • Consider adding a section or table summarizing cross-platform role applicability, especially for compute and storage roles.
  • If examples or usage patterns are added in future revisions, ensure parity between Windows (PowerShell, Windows tools) and Linux/macOS (CLI, shell, native tools).
GitHub Create Pull Request
Role Based Access Control Azure built-in roles for Compute - Azure RBAC ...es/role-based-access-control/built-in-roles/compute.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page lists Azure built-in roles for Compute and is largely platform-neutral in its presentation of permissions and actions. However, there are explicit references to Windows-specific tools and branding, such as 'Windows Admin Center' and 'Windows 365', with roles named accordingly and documentation links pointing to Windows-focused guides. These Windows-specific roles and references appear before or without mention of equivalent Linux/macOS tools or workflows, indicating a mild Windows bias in naming and linked resources.
Recommendations
  • Add equivalent roles and documentation for Linux/macOS management tools where applicable (e.g., Linux Admin Center, if available, or SSH-based management).
  • Ensure that documentation links for login and management roles include both Windows and Linux/macOS guides, especially for cross-platform scenarios.
  • Clarify in role descriptions when permissions apply equally to Linux and Windows VMs, and provide parity in examples and linked resources.
  • Consider renaming roles or providing aliases that reflect cross-platform capabilities, not just Windows branding.
GitHub Create Pull Request
Role Based Access Control Azure built-in roles for Security - Azure RBAC ...s/role-based-access-control/built-in-roles/security.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation is largely platform-neutral, focusing on Azure RBAC roles and permissions. However, there is mild Windows bias in the 'Attestation Contributor' role, where the 'Learn more' link points to a PowerShell-based quickstart, which is primarily a Windows tool. There are no Linux CLI or cross-platform examples referenced, and PowerShell is mentioned before any Linux alternatives (if any exist). Most other roles link to general guides or are reference-only, so the impact is limited.
Recommendations
  • For roles where the 'Learn more' link points to PowerShell-specific guides (e.g., Attestation Contributor), add links to equivalent Azure CLI or REST API documentation that works cross-platform.
  • Where possible, ensure that examples and quickstarts are provided for both PowerShell and Azure CLI, with clear indications of platform compatibility.
  • Review referenced guides to confirm they include Linux/macOS instructions or alternatives.
  • Explicitly mention cross-platform options in introductory or 'Next steps' sections.
GitHub Create Pull Request
Role Based Access Control View activity logs for Azure RBAC changes ...les/role-based-access-control/change-history-report.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Azure PowerShell examples before Azure CLI examples, and provides more detailed PowerShell usage and output samples. This ordering and emphasis may subtly favor Windows users, as PowerShell is most commonly associated with Windows environments, while Azure CLI is more cross-platform. However, CLI examples are present and complete, and no critical functionality is missing for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before or alongside Azure PowerShell examples to emphasize cross-platform support.
  • Ensure output samples and filtering examples are equally detailed for both PowerShell and CLI.
  • Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, and link to installation guides for each platform.
  • Consider adding a short section or note for Bash scripting or other Linux-native workflows, if relevant.
GitHub Create Pull Request
← Previous Page 8 of 10 Next →