369
Pages Scanned
3
Pages Flagged
369
Changed Pages
0.8%
% Pages Flagged
Scan Information
Started At: 2025-07-14 21:48:14
Finished At: 2025-07-14 21:53:17
Status: completed
Target Repo: Azure
Current Phase: discovery
Files Queued: 369
Files Completed: 369
Problematic Pages
3 issues found
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v4-tier.md
...s/app-service/app-service-configure-premium-v4-tier.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by presenting Windows-specific information and tools first, providing PowerShell automation examples without equivalent Bash/Linux shell scripts, and referencing Windows patterns and terminology more prominently. Linux-specific instructions and parity in scripting examples are lacking, and the documentation sometimes assumes a Windows-centric workflow.
Recommendations
- Provide Linux shell (Bash) script examples alongside PowerShell for automation tasks, especially in the 'Automate with scripts' section.
- Ensure that Linux-specific instructions are given equal prominence and detail as Windows instructions, especially in sections about availability and deployment.
- When referencing tools or workflows (e.g., Azure PowerShell), also mention and provide examples for their Linux/CLI equivalents.
- Avoid presenting Windows information or tools before Linux equivalents unless there is a technical reason; consider grouping instructions by platform or providing parallel examples.
- Clarify any differences in feature support or behavior between Windows and Linux explicitly, and ensure both are covered in troubleshooting and error-handling sections.
Create Pull Request
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-kerberos-encryption.md
...es/azure-netapp-files/configure-kerberos-encryption.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation demonstrates a Windows bias by requiring the use of PowerShell commands (Set-ADComputer) and Windows-specific tools (RSAT) for essential Active Directory configuration steps. These instructions are presented before any Linux client configuration, and there are no equivalent Linux-based methods or alternatives provided for managing the necessary AD computer account settings. The documentation assumes access to a Windows environment for directory management, which may not be available to all Linux-focused administrators.
Recommendations
- Provide equivalent instructions for configuring the Kerberos encryption type on the AD computer account using Linux-based tools, such as 'ldapmodify' or 'adcli', for environments where Windows or RSAT is not available.
- Clearly indicate that the PowerShell/RSAT steps are required only if no Linux-based AD management tools are available, and offer cross-platform alternatives.
- Reorder sections to present Linux client configuration and mounting steps before or alongside Windows/AD configuration to avoid the impression of Windows primacy.
- Add a note or appendix with guidance for organizations that use Samba or other non-Windows AD-compatible services for directory management.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-network-features.md
...icles/azure-netapp-files/configure-network-features.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily through exclusive use of Azure PowerShell commands for feature registration status checks, with no equivalent Azure CLI (cross-platform) or Bash examples provided. The only command-line examples are in PowerShell, and there are no Linux-specific or cross-platform instructions for these tasks. The documentation also references the Azure portal (web UI), which is platform-neutral, but all scripting/automation is Windows-centric.
Recommendations
- Provide Azure CLI (az) command equivalents for all Azure PowerShell examples, especially for feature registration checks (e.g., az feature show --namespace Microsoft.NetApp --name ANFBasicToStdNetworkFeaturesUpgrade).
- Where possible, include Bash shell examples for scripting tasks, or clarify that the steps can be performed on any OS using the Azure CLI.
- Explicitly state that both Azure PowerShell and Azure CLI can be used for management tasks, and link to relevant cross-platform tool documentation.
- If any automation or scripting is shown, ensure parity by including both PowerShell and Bash/Azure CLI snippets.
- Review for any terminology or tool references that are Windows-specific and provide Linux/macOS equivalents where applicable.