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 151-175 of 240 flagged pages
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
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page lists Azure PowerShell prerequisites in detail before Azure CLI, including specific module versions and installation notes. This ordering and emphasis on PowerShell (a Windows-centric tool) suggests a Windows-first bias. There are no Linux-specific examples or mentions of Linux tools, and PowerShell is highlighted more heavily than Azure CLI, which is more cross-platform.
Recommendations
  • Provide equal detail for Azure CLI prerequisites, including module/plugin requirements if applicable.
  • Explicitly mention cross-platform compatibility for both Azure CLI and PowerShell, including usage on Linux and macOS.
  • Add Linux-specific examples or notes where relevant, such as installation instructions or command syntax differences.
  • Consider listing Azure CLI before PowerShell to avoid implicit prioritization of Windows tools.
  • Reference Bash or other shell environments where appropriate, especially for scripting scenarios.
GitHub Create Pull Request
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-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides deployment examples using both Azure PowerShell and Azure CLI, but lists the PowerShell (Windows-centric) example first and references the PowerShell module directly. There is no mention of Linux-specific shell usage (e.g., Bash), nor are there any platform-specific notes or parity checks for Linux users. The documentation implicitly prioritizes Windows tooling and patterns.
Recommendations
  • Alternate the order of examples, sometimes listing Azure CLI (cross-platform) first.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash-specific usage notes where relevant.
  • Add a note clarifying that both PowerShell and CLI are available on all platforms, and link to installation guides for Linux/macOS users.
  • Consider including a Bash script example for deploying the ARM template using Azure CLI.
  • Avoid referencing PowerShell modules without also referencing cross-platform alternatives.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page lists Azure permissions for hybrid and multicloud resource providers, with a notable emphasis on Windows-centric technologies and tools. Several resource providers (e.g., AzureStackHCI, SCVMM) and actions reference Windows-specific management tools such as Windows Admin Center, and the overall structure prioritizes Windows-based solutions (Azure Stack, SCVMM, HCI) before Linux or cross-platform equivalents. There is little to no mention of Linux-specific management tools, nor are Linux examples or parity features highlighted.
Recommendations
  • Include explicit references to Linux management tools and workflows where applicable, such as Cockpit, Ansible, or native Linux CLI utilities.
  • Add examples or descriptions for Linux-based hybrid scenarios, ensuring parity with Windows-centric examples.
  • Where Windows Admin Center is mentioned, clarify if there are equivalent Linux management options or note limitations.
  • Reorder sections or provide cross-platform context to avoid the impression that Windows is the default or preferred platform.
  • Highlight Azure Arc's support for both Windows and Linux machines, and provide permission examples for Linux-specific operations.
  • Ensure documentation for hybrid and multicloud scenarios addresses both Windows and Linux environments equally, including troubleshooting and operational guidance.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/permissions/management-and-governance.md ...ccess-control/permissions/management-and-governance.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation page lists Azure permissions for management and governance resource providers, but the only technology-specific references are to PowerShell modules and assets within the Microsoft.Automation section. There is a notable emphasis on 'Powershell modules' as a primary automation asset, with no mention of Bash, shell scripts, or Linux-native automation equivalents. This suggests a bias toward Windows and PowerShell-centric automation patterns, potentially excluding Linux users or those using alternative scripting environments.
Recommendations
  • In the Microsoft.Automation section, add explicit references to Bash scripts, shell scripts, or other Linux-native automation assets alongside PowerShell modules.
  • Clarify that Azure Automation supports Python 2 and 3 packages, and provide parity in documentation for Linux scripting and automation workflows.
  • Where PowerShell modules are mentioned, also mention and document equivalent Linux automation patterns (e.g., Bash scripts, Python scripts, Ansible playbooks) to ensure cross-platform inclusivity.
  • Consider adding examples or references to Linux CLI tools and automation approaches in relevant sections to balance the Windows/PowerShell focus.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (a web GUI often accessed from Windows environments) for role management and assignment, without mentioning or providing examples for Linux-centric tools or workflows. There are no CLI or shell-based examples (e.g., Azure CLI, Bash), nor is there any mention of Linux-specific patterns or parity in role management. All screenshots and instructions focus on the GUI, which is most commonly used in Windows environments.
Recommendations
  • Add examples for managing Azure roles and Microsoft Entra roles using Azure CLI (az) commands, which are cross-platform and commonly used in Linux environments.
  • Include instructions or references for using REST APIs and scripting (e.g., Bash, Python) to assign and manage roles, highlighting Linux compatibility.
  • Mention that Azure CLI and PowerShell are available on Linux, and provide equivalent command-line examples alongside GUI instructions.
  • Add screenshots or walkthroughs for role management using CLI tools in a Linux terminal.
  • Explicitly state that all role management operations can be performed from Linux, Mac, and Windows environments using supported tools.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page shows mild Windows bias in the introductory guidance for obtaining the latest permissions. The PowerShell cmdlet (Get-AzProviderOperation) is mentioned first, before the Azure CLI equivalent (az provider operation list). This ordering subtly prioritizes Windows/PowerShell tooling. No Linux-specific examples, tools, or patterns are provided, and no explicit parity guidance is given for Linux users. However, the rest of the page is largely platform-neutral, focusing on Azure resource providers and services without OS-specific instructions.
Recommendations
  • List Azure CLI (az provider operation list) before PowerShell (Get-AzProviderOperation) to avoid Windows-first ordering.
  • Explicitly mention that both Azure CLI and PowerShell are cross-platform, and provide links to installation guides for Linux and macOS users.
  • Add a note or section clarifying that all resource provider permissions and role-based access control features are available and manageable from Linux, macOS, and Windows equally.
  • Where command-line examples are given, provide both Azure CLI and PowerShell syntax side-by-side, and clarify platform compatibility.
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-09 00:34
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 to CLI, and the 'Next steps' section exclusively links to a PowerShell tutorial. There is no explicit mention of Linux or Bash, nor any Linux-specific guidance, which may implicitly favor Windows users who are more likely to use PowerShell.
Recommendations
  • Add explicit references to Bash and Linux environments where Azure CLI is used, clarifying that CLI commands work cross-platform.
  • Include a 'Next steps' link to an Azure CLI or Bash-based tutorial, not just PowerShell.
  • Add a note highlighting that Azure CLI is available on Linux, macOS, and Windows, and provide installation instructions for non-Windows platforms.
  • Consider mentioning that PowerShell Core is cross-platform, but clarify that most Linux users will prefer Azure CLI.
  • Ensure that examples and guidance do not assume PowerShell as the default automation tool, and balance CLI and PowerShell references throughout.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides detailed examples for Azure PowerShell (which is most commonly used on Windows) before Azure CLI, and all PowerShell examples use Windows-style prompts (PS C:\>). There are no explicit Linux shell examples (e.g., bash), nor is there mention of Linux-specific considerations or parity in the PowerShell section. The ordering of sections (PowerShell before CLI) and the use of Windows-centric tools and patterns suggest a Windows-first bias.
Recommendations
  • Add explicit bash/Linux shell examples for Azure CLI commands, showing usage in a Linux terminal.
  • Clarify that Azure PowerShell can be used cross-platform and provide examples of running PowerShell on Linux/macOS (e.g., pwsh instead of Windows PowerShell).
  • Reorder the sections to present Azure CLI before Azure PowerShell, or mention that CLI is cross-platform and often preferred on Linux.
  • Include notes or tips for Linux users, such as differences in command syntax, environment setup, or authentication.
  • Avoid Windows-specific prompts (e.g., PS C:\>) in PowerShell examples, or provide alternative prompts for Linux/macOS.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/role-assignments-template.md ...role-based-access-control/role-assignments-template.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for all commands, but PowerShell (a Windows-centric tool) is consistently listed first in every example. There are no Linux-specific shell examples (e.g., Bash), nor are there references to Linux-native tools or workflows. The structure and ordering may subtly reinforce Windows/PowerShell as the primary or preferred environment, which could be interpreted as a Windows-first bias.
Recommendations
  • Alternate the order of Azure CLI and PowerShell examples, or list Azure CLI first to reflect its cross-platform nature.
  • Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, while PowerShell is primarily a Windows tool (though available cross-platform).
  • Include example shell environments for Linux (e.g., Bash) when showing Azure CLI usage, to clarify usage in non-Windows contexts.
  • Add a short section or note for Linux users, highlighting any differences or additional steps they may encounter.
  • Consider including links or references to Linux-specific documentation or troubleshooting guides.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by presenting Azure PowerShell examples and references before Azure CLI and REST API equivalents. The PowerShell example is shown first, and links to PowerShell documentation precede those for CLI. There is a notable emphasis on PowerShell tooling, which is primarily associated with Windows, while Linux-native tools and patterns (such as Bash scripting or Linux shell usage) are not highlighted or exemplified.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform and widely used on Linux.
  • Include explicit Linux/Bash shell usage examples where relevant, such as showing command output in a Linux terminal.
  • Balance references to tooling by mentioning Azure CLI and REST API first or equally with PowerShell.
  • Add notes or sections clarifying cross-platform support and usage, especially for Linux users.
  • Where infrastructure as code is discussed, provide examples using Linux-native tools and workflows (e.g., Bash scripts, Linux file paths).
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/role-definitions.md ...articles/role-based-access-control/role-definitions.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by consistently listing Azure PowerShell (a Windows-centric tool) before Azure CLI in examples and explanations. Role definition examples are shown first in PowerShell format, and references to viewing properties or role definitions often mention PowerShell before CLI or REST API. There are no explicit Linux-only examples, and no mention of Linux-specific tools or shell patterns. However, Azure CLI (cross-platform) is included in all relevant sections, and REST API references are present, so Linux users are not excluded, but Windows tools are prioritized in ordering and presentation.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or list CLI first in some sections to avoid implicit prioritization of Windows tools.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Provide example commands for both Azure PowerShell and Azure CLI side-by-side, especially in code blocks or walkthroughs.
  • Include a brief note or section on using these tools from Linux/macOS environments, possibly linking to installation guides for those platforms.
  • Where possible, add bash shell examples or usage patterns for Linux users, especially for scripting scenarios.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by mentioning Azure PowerShell before Azure CLI when describing how to list role assignments and determine scope. The example output for PowerShell is provided first, followed by Azure CLI. There are no Linux-specific tools or patterns referenced, and no explicit mention of Linux shell usage, but Azure CLI is cross-platform and included. No exclusive Windows tools are referenced, and both PowerShell and CLI examples are given, but the ordering and phrasing favor Windows/PowerShell slightly.
Recommendations
  • Present Azure CLI examples before Azure PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, while PowerShell is available on all platforms but is traditionally associated with Windows.
  • Include example commands for determining scope using Bash or other Linux-native shells if relevant.
  • Avoid language that implies PowerShell is the primary or preferred method unless justified by usage data.
  • Consider adding a short section highlighting cross-platform tooling and usage patterns for both Windows and Linux users.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/conditions-custom-security-attributes.md ...ccess-control/conditions-custom-security-attributes.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Azure PowerShell instructions and examples are presented before Azure CLI, and PowerShell is given a dedicated, detailed section. There are no explicit Linux-specific instructions, nor are Linux command-line patterns (e.g., bash, shell scripting) mentioned. The use of 'command window' and 'PowerShell window' language further implies a Windows-centric approach. However, Azure CLI is included, which is cross-platform, and no Windows-only tools are required for the core workflow.
Recommendations
  • Present Azure CLI instructions before or alongside PowerShell to emphasize cross-platform parity.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide example commands for bash/shell environments.
  • Avoid terms like 'PowerShell window' or 'command window'; use 'terminal' or 'shell' to be platform-neutral.
  • Add troubleshooting notes or tips for Linux/macOS users, such as authentication differences or file path conventions.
  • If graphical steps are required, clarify that the Azure portal is web-based and platform-independent.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
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 managing ABAC conditions, suggesting a Windows-first approach. PowerShell is a Windows-centric tool, and its mention before cross-platform alternatives like Azure CLI may indicate a bias toward Windows users. No explicit Linux examples or Linux-specific tools are provided.
Recommendations
  • List Azure CLI before PowerShell when mentioning cross-platform tools, as CLI is natively available on Linux and macOS.
  • Provide explicit examples for both Azure CLI and PowerShell to ensure parity.
  • Include a note clarifying that Azure CLI and REST API are fully supported on Linux and macOS.
  • Avoid implying PowerShell is the primary or preferred tool unless there is a technical reason.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/permissions/management-and-governance.md ...ccess-control/permissions/management-and-governance.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy
Summary
The documentation page lists Azure permissions for management and governance resource providers, but it shows evidence of Windows bias. Specifically, the Microsoft.Automation section heavily references 'Powershell modules' and 'DSC' (Desired State Configuration), which are Windows-centric technologies. There is no mention of Linux equivalents (such as Bash scripts or Ansible modules), nor are Linux automation tools or patterns referenced. The documentation does not provide parity in examples or terminology for Linux users.
Recommendations
  • In Microsoft.Automation, add references to Linux-compatible automation tools (e.g., Bash scripts, Python scripts, Ansible playbooks) alongside Powershell modules.
  • Clarify that Azure Automation supports both Windows and Linux runbooks, and provide examples for each.
  • Where 'Powershell module' is mentioned, also mention 'Python package' and other Linux-friendly formats.
  • Review other sections for terminology or examples that may be Windows-centric and add Linux equivalents.
  • Ensure that documentation for automation, configuration, and scripting is platform-neutral or includes both Windows and Linux perspectives.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/role-definitions.md ...articles/role-based-access-control/role-definitions.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 consistently presents Azure PowerShell (a Windows-centric tool) examples and references before Azure CLI (cross-platform) equivalents. Role definition property examples and sample outputs are shown first for Azure PowerShell, then for Azure CLI/REST. The phrase 'as displayed in Azure PowerShell and Azure CLI' is used, but PowerShell is always listed first and shown separately. There are no explicit Linux-specific examples or mentions of Linux shell usage, and no guidance for Linux users on how outputs may differ or how to use native Linux tools. The documentation assumes familiarity with PowerShell, which is traditionally a Windows tool, despite its recent availability on Linux.
Recommendations
  • Alternate the order of examples between Azure PowerShell and Azure CLI, or present CLI examples first to emphasize cross-platform parity.
  • Explicitly mention that Azure CLI is available and commonly used on Linux/macOS, and provide guidance for Linux users where relevant.
  • Include sample commands and outputs using Bash or other native Linux shells, especially for tasks that can be accomplished with Azure CLI.
  • Clarify that PowerShell is available on Linux, but that CLI is often the default on Linux systems.
  • Add a section or note on platform differences, if any, in tool usage or output formatting.
  • Ensure that REST API examples are presented as a fully cross-platform alternative, with curl or HTTPie usage shown.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/role-assignments-template.md ...role-based-access-control/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
Powershell Heavy Windows First
Summary
The documentation consistently provides both Azure PowerShell and Azure CLI examples for all commands and deployment steps. However, Azure PowerShell (a Windows-centric tool) is always listed first, and its usage is emphasized equally alongside Azure CLI, despite the CLI being cross-platform and more native to Linux environments. There are no explicit Linux-specific examples, nor are Linux shell patterns (e.g., bash scripting, environment variables) discussed. The documentation does not mention Linux tools or workflows, and there is no guidance for users who may be working exclusively in Linux environments.
Recommendations
  • Alternate the order of examples so that Azure CLI commands are listed before PowerShell in some sections, or default to CLI first as it is cross-platform.
  • Explicitly mention that Azure CLI works natively on Linux, macOS, and Windows, while Azure PowerShell is most commonly used on Windows.
  • Add Linux shell scripting examples (e.g., using bash, exporting variables, chaining commands) to demonstrate Linux-native workflows.
  • Provide guidance or links for installing and using Azure CLI on Linux systems.
  • Consider including a note for users who may not have PowerShell available, highlighting CLI as the recommended option for Linux.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/built-in-roles.md ...n/articles/role-based-access-control/built-in-roles.md
Medium Priority View Details →
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 for Azure built-in roles is largely platform-neutral in its descriptions and structure. However, there are several roles and descriptions that reference Windows-specific technologies and tools (e.g., Windows Admin Center, Windows file servers, Windows 365), and these are presented without equivalent mentions of Linux alternatives. The ordering and naming of some roles (such as 'Windows Admin Center Administrator Login', 'Windows 365 Network Interface Contributor', etc.) places Windows technologies prominently, while Linux-specific roles or references are absent or less visible. There are also references to NTFS permissions and SMB share ACLs mapped to Windows file server concepts, with no mention of Linux file server equivalents.
Recommendations
  • Where roles reference Windows-specific tools or concepts (e.g., Windows Admin Center, NTFS permissions), add parallel references or notes for Linux equivalents (e.g., Cockpit, ext4/xfs ACLs, Samba).
  • For roles that are mapped to Windows file server ACLs, clarify how these permissions map to Linux file servers or POSIX ACLs, or note the lack of direct equivalence.
  • Consider adding Linux-focused roles or examples where appropriate, such as roles for managing Linux VMs, Linux-based file shares, or Linux-specific management tools.
  • Review the ordering and naming of roles to ensure that Windows-specific roles are not always listed first or more prominently than cross-platform or Linux roles.
  • Where possible, provide examples or documentation links for both Windows and Linux administration scenarios, especially in sections that currently only mention Windows technologies.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/built-in-roles/storage.md ...es/role-based-access-control/built-in-roles/storage.md
Medium Priority View Details →
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 for Azure built-in roles for Storage shows mild Windows bias. Several roles and descriptions reference Windows-specific concepts, such as NTFS permissions, SMB, and file share ACLs, often comparing Azure roles to Windows file server equivalents. Windows terminology (NTFS, SMB, ACLs) is used as the primary reference point for describing access levels, and Windows file server parity is discussed more than Linux/NFS equivalents. There are no explicit PowerShell-heavy examples or Windows-only command references, but the framing and terminology are Windows-centric.
Recommendations
  • Add Linux/NFS parity notes where relevant, especially for file share roles. For example, clarify how permissions map to NFS or POSIX ACLs, not just NTFS/Windows ACLs.
  • Where roles are described as 'no built-in equivalent on Windows file servers', also mention Linux/NFS equivalents (or lack thereof) for completeness.
  • Balance terminology: when describing access levels (e.g., 'change', 'read'), reference both Windows and Linux/NFS concepts.
  • Include links or references to documentation for Linux/NFS file share access control in Azure, if available.
  • Review descriptions for implicit Windows-first framing and reword to be OS-neutral where possible.
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
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 lists Azure PowerShell prerequisites in detail before Azure CLI, with multiple specific module versions and installation notes. This emphasis on PowerShell (traditionally associated with Windows) and its placement before CLI may suggest a Windows-first and PowerShell-heavy bias. There are no explicit Linux-specific examples, nor are Linux tools or shell patterns mentioned.
Recommendations
  • Provide equal detail for Azure CLI prerequisites, including module/plugin requirements if applicable.
  • Include explicit examples or notes for Linux/macOS users, such as installation commands or environment considerations.
  • Balance the order of sections by listing Azure CLI before or alongside PowerShell, or clarify that both are cross-platform.
  • Mention that both Azure CLI and PowerShell are available on Linux and macOS, and link to platform-specific installation guides.
  • Add troubleshooting or usage notes for common Linux scenarios (e.g., shell compatibility, permissions).
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/best-practices.md ...n/articles/role-based-access-control/best-practices.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 by referencing Azure PowerShell before Azure CLI when discussing scripting and automation best practices. The link to PowerShell is listed first, and there is no mention of Linux-specific tools or shell environments. However, Azure CLI is also referenced, which is cross-platform, and no examples are given directly in the text, reducing the overall severity of the bias.
Recommendations
  • Ensure that Azure CLI examples and references are listed before or alongside PowerShell, emphasizing CLI's cross-platform nature.
  • Explicitly mention that Azure CLI works natively on Linux and macOS, and provide links to Bash or shell scripting examples where relevant.
  • Add a note or section highlighting Linux/macOS usage patterns for Azure RBAC, including automation and scripting.
  • Where scripting is discussed, provide parallel examples for both PowerShell and Bash/CLI to ensure parity.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/built-in-roles/compute.md ...es/role-based-access-control/built-in-roles/compute.md
Medium Priority View Details →
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 built-in roles for Compute and is generally platform-neutral in its role definitions and permissions. However, there is evidence of Windows bias in the naming and focus of certain roles (e.g., 'Windows Admin Center Administrator Login', 'Windows 365 Network Interface Contributor', 'Windows 365 Network User'), and in the linked 'Learn more' articles, which often reference Windows-specific tools or scenarios before Linux equivalents. Some roles and descriptions explicitly mention Windows tools (Windows Admin Center, Windows 365) and provide links to Windows-focused documentation, while Linux scenarios are less emphasized or referenced later (or not at all).
Recommendations
  • For each role that references Windows-specific tools (e.g., Windows Admin Center, Windows 365), add equivalent Linux scenarios and documentation links (e.g., SSH, Linux VM management).
  • Ensure 'Learn more' links and examples cover both Windows and Linux workflows, ideally with parity in depth and clarity.
  • Where roles mention login as administrator, clarify Linux root user scenarios and provide links to Linux authentication documentation.
  • Review role descriptions and permission tables for implicit Windows-first language and update to explicitly mention Linux support where applicable.
  • Add cross-platform examples and guidance for common tasks (e.g., VM login, patching, extension management) for both Windows and Linux.
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/change-history-report.md ...les/role-based-access-control/change-history-report.md
Medium Priority View Details →
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 and explanations before Azure CLI equivalents, and provides more detailed PowerShell usage and output samples. This ordering and emphasis may favor Windows users, as PowerShell is most commonly used on Windows, while CLI is more cross-platform. There are no explicit Linux-specific instructions, nor are Linux tools or shell patterns mentioned.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform parity.
  • Expand CLI sections with more detailed usage, output samples, and filtering examples, matching the depth of PowerShell coverage.
  • Explicitly mention that Azure CLI works natively on Linux/macOS and Windows, and provide shell-specific tips (e.g., using jq for output parsing).
  • Add a note or section for Linux/macOS users, highlighting any differences or additional steps if relevant.
  • Ensure screenshots and portal instructions do not assume a Windows environment (e.g., file paths, UI elements).
GitHub Create Pull Request
Role Based Access Control https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/classic-administrators.md ...es/role-based-access-control/classic-administrators.md
Medium Priority View Details →
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 exclusively provides instructions and screenshots for the Azure portal (web UI) and Azure Resource Graph Explorer, both of which are platform-agnostic but are typically accessed from Windows environments. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), nor are there references to Linux-specific tools or workflows. The absence of CLI instructions or examples means users on Linux or macOS do not see parity in how to perform these tasks outside the portal UI.
Recommendations
  • Add Azure CLI examples for listing, converting, and removing classic administrators, as Azure CLI is cross-platform and widely used on Linux.
  • Include PowerShell examples if relevant, but ensure Azure CLI or REST API instructions are presented first or alongside PowerShell to avoid Windows-first bias.
  • Explicitly mention that all portal and Resource Graph Explorer steps are accessible from any OS/browser, and provide links to CLI documentation for users preferring command-line workflows.
  • Add a section comparing how to perform these tasks using CLI tools on Linux/macOS vs. Windows, highlighting cross-platform support.
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
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 references Windows-specific tooling (Azure PowerShell) and provides guidance for escaping special characters in PowerShell before mentioning other tools. While it does mention Azure CLI and REST API as alternatives, PowerShell is listed first and receives more detailed explanation, indicating a subtle Windows bias. There are no explicit Linux or Bash examples, and no mention of Linux-specific considerations.
Recommendations
  • Provide explicit examples using Azure CLI and Bash, especially for escaping special characters and constructing conditions.
  • List cross-platform tools (Azure CLI, REST API) before or alongside PowerShell in all tool references.
  • Include notes or examples for Linux/macOS users, such as shell escaping and environment differences.
  • Ensure parity in troubleshooting and usage guidance for both Windows and Linux environments.
GitHub Create Pull Request
← Previous Page 7 of 10 Next →