Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 851-875 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cdn/cdn-overview.md
...ocs/azure-docs/blob/main//articles/cdn/cdn-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by specifically mentioning PowerShell as a management tool for Azure CDN endpoints, without referencing equivalent Linux or cross-platform CLI tools. The 'Next steps' section lists PowerShell before any mention of cross-platform alternatives, and there is no mention of the Azure CLI or Bash scripting, which are commonly used on Linux and macOS. This may give the impression that Windows environments are preferred or required for managing Azure CDN.
Recommendations
- Include Azure CLI examples and references alongside or before PowerShell, as Azure CLI is cross-platform and widely used on Linux.
- Mention Bash or shell scripting alternatives where automation is discussed, to ensure Linux users feel equally supported.
- Where management tools are listed, use neutral or cross-platform phrasing such as 'Azure portal, Azure CLI, or PowerShell' instead of only 'Azure portal or PowerShell'.
- Add explicit Linux/macOS guidance or links to relevant documentation for non-Windows users.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/certification/validate-device-edge-secured-core.md
...les/certification/validate-device-edge-secured-core.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes how to validate Edge Secured-core status using Windows GUI tools and navigation paths, with no mention of Linux or cross-platform methods. All screenshots and instructions are Windows-specific, and there are no equivalent steps or guidance for Linux users.
Recommendations
- Add a section explaining whether Edge Secured-core is relevant or available for Linux devices, and if so, how to check its status on Linux.
- If Linux equivalents exist (e.g., checking TPM version, device encryption, or memory integrity), provide command-line or GUI instructions for popular Linux distributions.
- Clarify in the introduction if the feature is Windows-only, or explicitly state platform support to avoid confusion.
- Include cross-platform terminology and avoid assuming all users are on Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cdn/cdn-map-content-to-custom-domain.md
...main//articles/cdn/cdn-map-content-to-custom-domain.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides detailed instructions and code samples for performing tasks using the Azure Portal (web UI) and Azure PowerShell, but does not include equivalent examples for Linux users, such as Azure CLI or Bash scripts. PowerShell is a Windows-centric tool, and its exclusive use in command-line examples may disadvantage users on Linux or macOS platforms. There is also no mention of cross-platform tools or guidance for non-Windows environments.
Recommendations
- Add Azure CLI examples alongside PowerShell for all command-line operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell Core is available cross-platform if PowerShell examples are retained, and provide installation guidance for non-Windows users.
- Where possible, include Bash or shell script examples for DNS record management, especially for common Linux DNS providers.
- Review all sections to ensure that Linux and macOS users are not required to use Windows-specific tools or patterns, and offer parity in instructions.
- Consider adding a table or section that summarizes available tools for each platform (Windows, Linux, macOS) and links to relevant documentation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cdn/monitoring-and-access-log.md
...s/blob/main//articles/cdn/monitoring-and-access-log.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides detailed step-by-step instructions and code samples exclusively using Azure PowerShell, a tool most commonly associated with Windows environments. There are no examples using Azure CLI, Bash, or cross-platform scripting, and no mention of Linux-specific workflows. The only automation examples are PowerShell-based, and the documentation's custom metadata even references 'azurepowershell'. This creates a strong Windows and PowerShell bias, making it less accessible for Linux or cross-platform users.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell-based configuration steps, including enabling diagnostics, setting retention, and configuring destinations.
- Include Bash shell scripting examples where appropriate, especially for automation scenarios.
- Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and clarify any platform-specific requirements.
- Update the documentation metadata to reflect cross-platform tooling, not just PowerShell.
- Where possible, provide a table or section comparing PowerShell and CLI commands for common tasks.
- Ensure screenshots and UI instructions do not assume a Windows environment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cdn/cdn-app-dev-net.md
.../azure-docs/blob/main//articles/cdn/cdn-app-dev-net.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased towards Windows development environments. It exclusively references Visual Studio (Windows-only version), uses Windows-specific UI terms and screenshots, and provides no guidance or examples for Linux or cross-platform .NET development. Package management is demonstrated only via the Visual Studio Package Manager Console (PowerShell-based), and the 'Next Steps' section promotes PowerShell for management, with no mention of Bash, CLI, or Linux-compatible alternatives.
Recommendations
- Add instructions for setting up and running the sample using .NET Core/SDK on Linux and macOS, including command-line steps (e.g., dotnet new, dotnet add package).
- Include screenshots or terminal examples for cross-platform editors (e.g., VS Code) and command-line workflows.
- Provide alternative package installation instructions using the dotnet CLI (e.g., 'dotnet add package ...') instead of only the Visual Studio NuGet Package Manager Console.
- Mention and link to Azure CLI documentation for managing CDN resources as an alternative to PowerShell.
- Avoid assuming Visual Studio 2015 as a requirement; clarify that .NET development can be done on any OS with the .NET SDK.
- Ensure that all code and instructions are cross-platform where possible, or clearly indicate when something is Windows-specific.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/in-place-migration-overview.md
...rvices-extended-support/in-place-migration-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by prioritizing and exclusively referencing Windows-centric tools and workflows, such as PowerShell and Visual Studio, for deployment and migration tasks. There are no explicit Linux or cross-platform CLI examples provided, and Windows tools are mentioned before or instead of their Linux equivalents. This may hinder Linux users from easily following the migration process.
Recommendations
- Include Azure CLI examples alongside PowerShell for all command-line operations, especially for resource provider registration and status checks.
- Mention cross-platform tools (such as Azure CLI and VS Code) before or alongside Windows-specific tools like PowerShell and Visual Studio.
- Provide explicit Linux/macOS instructions or notes where workflows differ, ensuring parity for non-Windows users.
- Where possible, use neutral language (e.g., 'command-line' instead of 'PowerShell') and link to both Windows and Linux tool documentation.
- Add a section or callout highlighting cross-platform support and any OS-specific considerations for migration.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/configure-scaling.md
...s/cloud-services-extended-support/configure-scaling.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and workflows (such as PowerShell and Visual Studio) before or instead of Linux equivalents. The 'Next steps' section lists PowerShell and Visual Studio as deployment options but omits explicit mention of cross-platform or Linux-native tools (such as Azure CLI or Bicep). Additionally, some linked quickstarts default to Windows environments, and there are no Linux-specific instructions or screenshots.
Recommendations
- Include Azure CLI examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
- Mention cross-platform editors (such as VS Code) in addition to Visual Studio.
- Ensure that quickstart and deployment links reference both Windows and Linux tabs or provide parity in instructions.
- Add explicit notes or sections for Linux users, including any differences or considerations.
- Where screenshots are shown, consider including examples from non-Windows environments or the Azure Cloud Shell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/deploy-sdk.md
...articles/cloud-services-extended-support/deploy-sdk.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell commands for key vault and certificate management steps, referencing Windows-specific tools (such as RDP and Visual Studio), and omitting equivalent Linux/CLI/Bash examples. The use of PowerShell is presented as the default, with no mention of cross-platform alternatives like Azure CLI or Bash scripts. This may hinder Linux users or those working in non-Windows environments.
Recommendations
- For every PowerShell example, provide an equivalent Azure CLI (az) command example, which is cross-platform and widely used on Linux.
- Mention and demonstrate how to use Bash or shell scripts for file uploads and automation steps, especially for storage and configuration file handling.
- When referencing RDP, also mention SSH as a remote access method for Linux-based roles, if applicable.
- List cross-platform tools (e.g., Azure CLI, VS Code) before or alongside Windows-specific tools (e.g., PowerShell, Visual Studio) in both instructions and related content.
- Add a note clarifying that all steps can be performed on Linux/macOS using Azure CLI and SDKs, and link to relevant documentation.
- Ensure that terminology and examples do not assume a Windows-only environment (e.g., avoid only referencing Windows file paths or tools).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/certificates-and-key-vault.md
...ervices-extended-support/certificates-and-key-vault.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and Visual Studio as primary tools for certificate and service deployment, without mentioning or providing equivalent Linux/CLI examples. The instructions and examples assume the use of .PFX certificate format (commonly associated with Windows), and do not address Linux-based workflows or tools such as Azure CLI or OpenSSL. The ordering of deployment options also places Windows-centric tools before cross-platform alternatives.
Recommendations
- Include Azure CLI examples for creating and managing Key Vaults and certificates, alongside or before PowerShell examples.
- Provide guidance for preparing certificates using OpenSSL or other Linux-native tools, including conversion to .PFX format if required.
- Explicitly mention cross-platform compatibility and provide Linux/macOS command-line instructions where relevant.
- Reorder deployment options to present cross-platform tools (Azure CLI, ARM templates) before Windows-specific tools (PowerShell, Visual Studio).
- Add a section or callout for Linux users, highlighting any differences or additional steps required.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/digital-twins/tutorial-end-to-end.md
...ob/main//articles/digital-twins/tutorial-end-to-end.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias by consistently referencing Windows-style paths (backslashes), using screenshots from Windows File Explorer, and referring to 'console windows' without clarifying cross-platform terminal usage. There are no explicit Linux/macOS instructions or screenshots, and file navigation assumes Windows conventions. While the CLI commands themselves are cross-platform, the supporting instructions and visuals are Windows-centric.
Recommendations
- Provide explicit instructions for Linux/macOS users, including example terminal commands and navigation using forward slashes.
- Include screenshots from Linux/macOS terminals or file managers alongside Windows screenshots, or use neutral, cross-platform visuals.
- Use the term 'terminal' or 'command line' instead of 'console window', and clarify that all steps work on Windows, Linux, and macOS.
- When referencing file paths, show both Windows (\) and Linux/macOS (/) formats, or use variables/placeholders.
- If zipping files, mention common Linux/macOS tools (e.g., zip command) in addition to Windows methods.
- Explicitly state that the .NET and Azure CLI commands are cross-platform, and provide troubleshooting tips for non-Windows environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/enable-wad.md
...articles/cloud-services-extended-support/enable-wad.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias by providing only PowerShell-based examples and commands for applying the Azure diagnostics extension. All CLI instructions use PowerShell cmdlets, and there is no mention of Bash, Azure CLI, or Linux-based workflows. The configuration file examples and schema downloads are also shown exclusively with PowerShell commands, and the 'Next steps' section lists PowerShell and Visual Studio (both Windows-centric) before other options. There are no Linux or cross-platform equivalents provided.
Recommendations
- Provide equivalent Azure CLI (az) commands for all PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash shell examples for file operations (e.g., downloading schema files) alongside PowerShell commands.
- Explicitly mention Linux support and any differences or limitations for Linux-based Cloud Services roles, if applicable.
- Reorder or balance the 'Next steps' section to mention cross-platform tools (Azure CLI, ARM templates, Azure portal) before or alongside Windows-centric tools (PowerShell, Visual Studio).
- Add a note clarifying that the instructions are applicable to both Windows and Linux roles, or specify if there are differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/cloud-services-model-and-package.md
...s-extended-support/cloud-services-model-and-package.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing on Windows-centric tools and workflows (such as Visual Studio, CSPack.exe, and the Azure Compute Emulator), providing only Windows command-line examples, referencing Windows file paths, and omitting Linux equivalents or instructions. There is no mention of how to perform packaging or deployment tasks on Linux or macOS, nor are cross-platform tools or CLI alternatives highlighted.
Recommendations
- Include explicit instructions and examples for packaging and deploying cloud services using cross-platform tools such as Azure CLI or Azure PowerShell Core, which run on Linux and macOS.
- Document the location and usage of CSPack or equivalent tools on Linux/macOS, if available, or clarify their absence and suggest alternatives.
- Provide Linux/macOS command-line examples alongside Windows examples, including file path formats and shell syntax.
- Avoid referencing Visual Studio or Windows-specific UI elements as the primary or only method; instead, mention cross-platform IDEs or editors where possible.
- Clarify any platform limitations (e.g., if the Compute Emulator or CSPack is Windows-only) and offer guidance for Linux/macOS users on how to test and package their services.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/certification/program-requirements-edge-secured-core.md
...ertification/program-requirements-edge-secured-core.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a 'Windows-first' bias: the Windows requirements are presented in full detail and with concrete, actionable requirements, while the Linux section is explicitly marked as 'not yet supported' and only describes 'expected requirements.' Windows-specific tools and features (e.g., BitLocker, VBS, HVCI, Microsoft Defender for Endpoint) are mentioned by name, with no Linux equivalents or examples provided. There is a lack of Linux-specific guidance, tools, or references, and the Linux section is less mature and actionable. In several places, Windows tools are referenced without parallel Linux alternatives, and the Linux section lacks practical implementation details or links.
Recommendations
- When referencing Windows-specific tools (e.g., BitLocker, VBS, HVCI), provide Linux equivalents (e.g., dm-crypt, IMA, SELinux, AppArmor) and link to their documentation.
- Ensure that Linux requirements are as detailed and actionable as the Windows section, including concrete configuration steps, supported distributions, and example commands.
- Add Linux-specific resources and references, such as links to CIS Linux benchmarks, Linux security baseline guides, and open-source security tools.
- Where possible, avoid presenting Windows requirements first; instead, present both platforms in parallel or clarify that both are equally supported (once Linux support is available).
- For features like security logging, provide Linux-native solutions (e.g., auditd, syslog, OSSEC) alongside Microsoft Defender for Endpoint.
- Update the Linux section as soon as support is available, and ensure it is not marked as 'not yet supported' for parity.
- Include example configurations or code snippets for both Windows (e.g., PowerShell) and Linux (e.g., shell commands) where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/deploy-prerequisite.md
...cloud-services-extended-support/deploy-prerequisite.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows such as PowerShell and Visual Studio, mentioning them before or instead of Linux equivalents. Examples and instructions for Linux users (such as Bash, Azure CLI, or cross-platform editors) are either missing or only mentioned after Windows tools. There are no explicit Linux command-line examples, and PowerShell is often the only scripting option referenced alongside the Azure portal.
Recommendations
- Include Azure CLI examples alongside or before PowerShell for all command-line instructions, as Azure CLI is cross-platform and widely used on Linux.
- Mention cross-platform editors (such as VS Code) in addition to Visual Studio, and clarify which steps can be performed on Linux.
- Provide explicit Linux/Bash command examples where relevant, especially for tasks like key vault creation or deployment.
- When listing deployment options, avoid listing Windows tools (PowerShell, Visual Studio) first unless there is a technical reason; alternate the order or group by platform.
- Clarify when a tool or workflow is Windows-only, and always provide a Linux-compatible alternative.
- Add a section or callout for Linux/macOS users, summarizing the parity of steps and tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/available-sizes.md
...les/cloud-services-extended-support/available-sizes.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for listing available VM sizes, omitting equivalent Linux/CLI/bash commands. The 'Next steps' section also lists PowerShell and Visual Studio (Windows-centric tools) before mentioning templates, and does not reference Azure CLI or Linux-native workflows. No Linux or cross-platform examples are provided for key tasks.
Recommendations
- Add equivalent Azure CLI (az) or Bash examples alongside PowerShell scripts for listing available VM sizes.
- In the 'Next steps' section, include Azure CLI and/or Bash deployment guides and place them on equal footing with PowerShell and Visual Studio.
- Explicitly mention that tasks can be performed from Linux/macOS as well as Windows, and link to cross-platform tooling documentation.
- Where possible, use neutral language and tool ordering (e.g., 'Azure portal, Azure CLI, PowerShell, Template, Visual Studio') to avoid implying Windows is the default or preferred environment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/deploy-template.md
...les/cloud-services-extended-support/deploy-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for resource creation and deployment, with no mention of Azure CLI or Bash alternatives. Windows-centric tools and patterns (such as Visual Studio and RDP extensions) are referenced, and Linux equivalents or cross-platform instructions are missing or relegated to secondary status. The absence of Linux or cross-platform command-line examples may hinder users on non-Windows platforms.
Recommendations
- Add Azure CLI (az) command examples alongside PowerShell for all resource creation and deployment steps, including resource group, storage account, blob upload, and ARM template deployment.
- Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and provide Bash shell examples where appropriate.
- When referencing tools like Visual Studio or RDP, also mention cross-platform alternatives (e.g., VS Code, SSH, or Bastion for remote access).
- Ensure that links to instructions (such as for creating resource groups or storage accounts) include both PowerShell and CLI options, or link to pages that offer both.
- Consider adding a table or section summarizing equivalent commands for PowerShell and Azure CLI for quick reference.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/cloud-services-guestos-update-matrix.md
...tended-support/cloud-services-guestos-update-matrix.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exclusively discusses Windows-based Guest OS families (Windows Server 2022, 2019, 2016, 2012 R2, 2012, 2008 R2) and .NET Framework versions, with no mention of Linux-based Guest OS options, examples, or support. All configuration strings, compatibility notes, and update processes are centered on Windows Server. There are references to Windows-specific tools (Visual Studio, RDP), and no Linux equivalents or cross-platform considerations are provided.
Recommendations
- Add a section explaining the availability (or lack thereof) of Linux-based Guest OS options for Azure Cloud Services, and clarify if this documentation is Windows-only by design.
- If Linux-based Cloud Services are supported, provide parity tables and update histories for Linux Guest OS images, including supported distributions and versions.
- Include examples or references for managing and updating Linux-based roles, if applicable, such as using SSH instead of RDP, and Linux-native tools or SDKs.
- Where Windows-specific tools (e.g., Visual Studio, RDP) are mentioned, offer Linux alternatives (e.g., VS Code, SSH) or clarify platform limitations.
- Explicitly state in the introduction or scope that this documentation is only relevant for Windows-based Cloud Services if Linux is not supported, to avoid confusion.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/dns-security-policy.md
...re-docs/blob/main//articles/dns/dns-security-policy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by only mentioning Azure PowerShell and the Azure portal as configuration methods, with no reference to cross-platform or Linux-native tools such as Azure CLI, REST API, or ARM templates. There are no Linux or bash examples, and the only command-line tool referenced is PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Include Azure CLI examples for all configuration steps, as Azure CLI is cross-platform and widely used on Linux.
- Mention and provide examples for using REST API or ARM/Bicep templates to configure DNS security policy, which are platform-agnostic.
- Explicitly state that PowerShell examples can be run on Linux/macOS if using PowerShell Core, or provide equivalent bash scripts.
- Ensure that any screenshots or UI walkthroughs are supplemented with command-line alternatives for automation and parity.
- Add a section or note highlighting cross-platform support and tools for managing DNS security policy.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/enable-alerts.md
...icles/cloud-services-extended-support/enable-alerts.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. The 'Next steps' section lists PowerShell and Visual Studio (both Windows-focused) before mentioning templates, and there are no references to Linux CLI tools or examples. The main workflow is entirely portal-based, which is cross-platform, but the supporting tooling and deployment options are Windows-oriented.
Recommendations
- Include Azure CLI examples for Linux/macOS users alongside or before PowerShell examples.
- Mention cross-platform tools (e.g., Azure CLI, Bicep) in the 'Next steps' section, not just PowerShell and Visual Studio.
- Add explicit notes or links for Linux/macOS users on how to perform equivalent tasks.
- Ensure deployment and automation examples are provided for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/enable-rdp.md
...articles/cloud-services-extended-support/enable-rdp.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples are provided exclusively in PowerShell, a Windows-centric tool, with no mention of Linux or cross-platform alternatives such as Azure CLI or SSH. The workflow assumes the use of Remote Desktop Protocol (RDP), which is primarily a Windows technology, and does not provide guidance for connecting from Linux or macOS clients. The 'Next steps' section also lists PowerShell and Visual Studio (both Windows-focused) before mentioning templates, with no reference to Azure CLI or Linux-native tools.
Recommendations
- Provide equivalent Azure CLI commands for all PowerShell examples to support Linux and macOS users.
- Include instructions or links for connecting to RDP from Linux/macOS clients (e.g., using rdesktop, FreeRDP, Remmina).
- Mention cross-platform tools and workflows (such as Azure CLI, VS Code) alongside or before Windows-specific tools.
- Clarify that RDP files can be opened with third-party clients on non-Windows systems.
- Add a section or note addressing Linux/macOS administrator scenarios, including any limitations or differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/cloud-services-guestos-family-2-3-4-retirement.md
...port/cloud-services-guestos-family-2-3-4-retirement.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily Windows-centric, focusing exclusively on Windows Server OS families and providing only PowerShell scripts and Windows-specific tools for management and migration. There are no references to Linux-based guest OS families, nor are there any examples or guidance for Linux users. The migration recommendations and tooling are all tailored to Windows environments.
Recommendations
- Include information about Linux-based guest OS families if supported, or clarify if Azure Cloud Services (classic) does not support Linux guests.
- Provide equivalent command-line examples using Azure CLI (cross-platform) or Bash scripts, not just PowerShell.
- Mention and document migration paths for Linux workloads, if applicable, or explicitly state that this guidance is Windows-only.
- List any Linux-compatible tools or SDKs where relevant, and ensure parity in instructions for both Windows and Linux administrators.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/enable-key-vault-virtual-machine.md
...s-extended-support/enable-key-vault-virtual-machine.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily Windows-centric: it explicitly refers to the Key Vault VM extension for Windows, describes certificate handling only in the context of the Windows certificate store, and uses Windows-specific terms (e.g., 'LocalMachine', 'My' store). There are no examples or mentions of Linux support, tools, or equivalent processes, and all instructions assume a Windows environment.
Recommendations
- Clarify early in the documentation whether the Key Vault VM extension is available for Linux VMs in Azure Cloud Services (extended support).
- If Linux support exists, provide parallel instructions and examples for Linux, including how certificates are handled and where they are stored.
- Mention Linux certificate stores (such as /etc/ssl/certs or similar) and how the extension interacts with them.
- If the extension is Windows-only, state this explicitly at the top of the article to set expectations for Linux users.
- Include references or links to Linux-specific documentation if available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-shell/overview.md
...azure-docs/blob/main//articles/cloud-shell/overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page for Azure Cloud Shell mentions both Bash and PowerShell, but repeatedly foregrounds PowerShell and Windows-centric tools. References to Azure PowerShell and related documentation are given equal or greater prominence than Bash/Linux equivalents, and there are no explicit Linux/Bash command examples or links. The description of the integrated editor and authentication focuses on Azure CLI and PowerShell, omitting mention of Bash scripting or Linux-native workflows.
Recommendations
- Provide explicit examples and documentation links for Bash/Linux workflows alongside PowerShell.
- When listing access points or tools, alternate or balance the order (e.g., 'Azure CLI documentation' before 'Azure PowerShell documentation').
- Highlight Linux-native features or tools available in Cloud Shell, such as common Linux utilities, and provide examples of their use.
- Mention Bash scripting and Linux command-line workflows in the context of the integrated editor and authentication.
- Ensure parity in documentation references, so that for every PowerShell mention, there is a corresponding Bash/Linux mention.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/in-place-migration-technical-details.md
...tended-support/in-place-migration-technical-details.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the primary or sole scripting interface for migration operations (e.g., abort/commit/retry), mentioning PowerShell before Azure CLI, and not providing any Linux-specific examples or guidance. There are no Bash, Linux shell, or cross-platform CLI examples, and the troubleshooting steps default to PowerShell usage. This may disadvantage users on Linux or macOS platforms.
Recommendations
- Provide Azure CLI examples alongside or before PowerShell commands, especially for common migration operations (validate, prepare, commit, abort).
- Explicitly mention that Azure CLI is cross-platform and can be used from Linux, macOS, or Windows.
- Include sample commands for both PowerShell and Bash (or generic shell) where scripting is referenced.
- Ensure troubleshooting steps offer CLI-based alternatives, not just PowerShell, and clarify that REST API calls can be made from any platform.
- Review all references to scripting interfaces to ensure parity and visibility for Linux/macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/override-sku.md
...ticles/cloud-services-extended-support/override-sku.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing a PowerShell example (which is Windows-centric) and referencing Windows-oriented tools and patterns (such as .cscfg/.csdef/.cspkg, which are historically tied to Windows Azure Cloud Services). There are no CLI (az cli), Bash, or Linux-native examples. The PowerShell example is presented before any cross-platform alternatives, and there is no mention of Linux or cross-platform tooling.
Recommendations
- Add Azure CLI (az cli) examples for setting allowModelOverride, as az cli is cross-platform and widely used on Linux.
- Include Bash or shell script examples where applicable.
- Explicitly mention cross-platform support and provide guidance for Linux/macOS users.
- Clarify whether the SDK example is cross-platform and, if so, provide language-agnostic or Linux-friendly SDK usage notes.
- Review the documentation for any assumptions about the user's operating system and adjust language to be OS-neutral where possible.