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 226-240 of 240 flagged pages
Role Based Access Control
Elevate access to manage all Azure subscriptions and management groups
...le-based-access-control/elevate-access-global-admin.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure Portal (web), PowerShell, Azure CLI, and REST API. The PowerShell section is given its own tab, and PowerShell commands are shown before Azure CLI equivalents. There is a slight 'Windows-first' bias, as PowerShell is traditionally a Windows tool, and its examples are given equal prominence to Azure CLI, which is more cross-platform. However, Linux/macOS users are not blocked: all tasks can be performed via Azure CLI or REST API, which are cross-platform. No Windows-only tools or patterns are required, and Linux examples are not missing.
Recommendations
- Clarify that PowerShell Core is available cross-platform, or explicitly mention that Azure CLI is recommended for Linux/macOS users.
- Consider listing Azure CLI examples before PowerShell, or note their parity.
- Add a brief note in each tab indicating platform compatibility (e.g., 'Azure CLI works on Windows, Linux, and macOS').
- Ensure screenshots and UI references are not Windows-specific (e.g., avoid showing Windows-only UI elements).
Create Pull Request
Role Based Access Control
Azure permissions for Management and governance - Azure RBAC
...ccess-control/permissions/management-and-governance.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Summary
The documentation is a reference list of Azure permissions for management and governance resource providers. It is largely platform-neutral, but there is a minor Windows bias in the Microsoft.Automation section, which repeatedly references 'Powershell modules' as a core automation asset type. This may imply a Windows-centric approach to automation, even though Azure Automation supports Python as well. No explicit examples, instructions, or ordering favor Windows or PowerShell, and Linux/macOS users are not blocked from using the described features.
Recommendations
- In the Microsoft.Automation section, clarify that Azure Automation supports both PowerShell and Python runbooks and modules.
- Where 'Powershell module' is referenced, consider adding parallel references to Python modules/packages to reinforce cross-platform support.
- If examples or further documentation are linked, ensure Linux/macOS usage is equally represented.
Role Based Access Control
Quickstart: Assign an Azure role using Bicep - Azure RBAC
...ed-access-control/quickstart-role-assignments-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all key steps, ensuring Linux/macOS users can follow along using the CLI. However, PowerShell (a Windows-centric tool) is consistently presented alongside CLI, and in the 'Next steps' section, only a PowerShell tutorial is linked, with no equivalent CLI or Linux-native guidance. The presence of PowerShell throughout and its exclusive mention in further learning resources creates a subtle Windows bias.
Recommendations
- Add 'Next steps' links to tutorials using Azure CLI, not just PowerShell.
- Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for non-Windows users.
- Where PowerShell is referenced, clarify its availability on Linux/macOS, or provide links to installation instructions for those platforms.
- Consider listing CLI examples before PowerShell, or alternating order, to avoid implicit prioritization of Windows tools.
Role Based Access Control
Azure permissions - Azure RBAC
...e-based-access-control/resource-provider-operations.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page references both Windows PowerShell and Azure CLI for retrieving permissions, but lists the PowerShell cmdlet (Get-AzProviderOperation) first and links to it before the Azure CLI equivalent (az provider operation list). This ordering and mention may subtly prioritize Windows/PowerShell usage, which is more common on Windows systems. No explicit Linux/macOS examples or tools are missing, but the initial emphasis is on the Windows-centric tool.
Recommendations
- List Azure CLI (az provider operation list) before PowerShell cmdlet to avoid implicit prioritization of Windows tools.
- Explicitly state that both Azure CLI and PowerShell are cross-platform, and provide guidance for Linux/macOS users if needed.
- Add a note clarifying that all listed commands are available on Linux/macOS and provide links to installation guides for Azure CLI on those platforms.
- Consider including example usage for both CLI and PowerShell side-by-side, or in a tabbed format, to reinforce parity.
Role Based Access Control
Remove Azure role assignments - Azure RBAC
...s/role-based-access-control/role-assignments-remove.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides detailed examples for both Azure PowerShell and Azure CLI, but the PowerShell section appears before the CLI section and contains more example scenarios. PowerShell is traditionally associated with Windows, and its prominence may suggest a Windows-first approach. However, CLI examples are present and equally functional on Linux/macOS. No exclusive Windows tools or patterns are mentioned, and Linux users can complete all tasks described.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first perception.
- Ensure parity in the number and complexity of CLI examples compared to PowerShell.
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows.
- Add troubleshooting tips or notes relevant to Linux/macOS environments if any exist.
Role Based Access Control
Understand Azure role definitions - Azure RBAC
...articles/role-based-access-control/role-definitions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation consistently presents Azure PowerShell (a Windows-centric tool) examples and references before Azure CLI, which is cross-platform. However, both PowerShell and CLI examples are provided, and there are no sections that are Windows-only or that use Windows-specific tools or patterns exclusively. No Linux/macOS examples are missing, and the CLI is always included. No explicit Windows tools (like cmd.exe, Windows paths, or batch scripts) are referenced.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first to reflect its cross-platform nature.
- Explicitly mention that both Azure PowerShell and Azure CLI are available on Windows, Linux, and macOS.
- Where possible, provide examples using Bash or shell scripting to further support Linux/macOS users.
- Add a short section clarifying tool availability and platform compatibility at the start of the documentation.
Role Based Access Control
Transfer an Azure subscription to a different Microsoft Entra directory
...les/role-based-access-control/transfer-subscription.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation predominantly uses Azure CLI examples and references Bash in Azure Cloud Shell, which is cross-platform. However, there are minor instances of Windows bias: in the 'Update system-assigned managed identities' and 'Update user-assigned managed identities' sections, links to Azure CLI guides for Windows VMs and Windows VMSS are listed before Linux equivalents, and Linux-specific links are missing. Additionally, when listing ACLs for Azure Data Lake Storage Gen2, PowerShell is mentioned as an option, but Linux command-line alternatives are not explicitly referenced.
Recommendations
- Add explicit links and examples for Linux VM and VMSS managed identity configuration alongside Windows links.
- When referencing PowerShell for listing ACLs, also mention Bash/Azure CLI alternatives for Linux/macOS users.
- Ensure that any VM-related instructions or links are provided for both Windows and Linux platforms, or clarify that the Azure CLI commands work identically on all platforms.
- Review all linked guides to ensure Linux parity in step-by-step instructions.
Role Based Access Control
List Azure role definitions - Azure RBAC
...les/role-based-access-control/role-definitions-list.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Azure PowerShell examples before Azure CLI examples, and the PowerShell section is more detailed with multiple example queries and output formats. PowerShell is a Windows-centric tool, and its examples use Windows-style prompts (e.g., PS C:\>). While Azure CLI is cross-platform and well-represented, the ordering and depth of PowerShell coverage suggest a mild Windows bias. No critical Linux/macOS functionality is missing, and REST API coverage is platform-neutral.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform parity.
- Ensure example depth and output formats are equally detailed for Azure CLI and PowerShell.
- Use neutral prompt styles (e.g., $ or #) in CLI examples to avoid Windows-centric cues.
- Explicitly note that Azure CLI works on Linux/macOS and provide links to installation guides for those platforms.
- Add a short section or note clarifying that PowerShell Core is available on Linux/macOS, if PowerShell examples are retained.
Role Based Access Control
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/delegate-role-assignments-portal.md
...sed-access-control/delegate-role-assignments-portal.md
Low Priority
View Details →
Detected Bias Types
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.
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
Low Priority
View Details →
Detected Bias Types
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.
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
Low Priority
View Details →
Detected Bias Types
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.
Role Based Access Control
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/delegate-role-assignments-portal.md
...sed-access-control/delegate-role-assignments-portal.md
Low Priority
View Details →
Detected Bias Types
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.
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
Low Priority
View Details →
Detected Bias Types
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.
Role Based Access Control
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/role-based-access-control/role-assignments-external-users.md
...ased-access-control/role-assignments-external-users.md
Low Priority
View Details →
Detected Bias Types
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.
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
Low Priority
View Details →
Detected Bias Types
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.