Cloud Services Extended Support

90
Total Pages
61
Linux-Friendly Pages
29
Pages with Bias
32.2%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

56 issues found
Showing 26-50 of 56 flagged pages
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/schema-cscfg-networkconfiguration.md ...-extended-support/schema-cscfg-networkconfiguration.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation references PowerShell and template deployments as the only methods for configuring reserved IP allocation, without mentioning Linux-native tools (e.g., Azure CLI, Bash). There are no Linux or cross-platform command-line examples, and the only tool mentioned is PowerShell, which is traditionally associated with Windows. This may lead Linux users to believe that only Windows tools are supported or recommended.
Recommendations
  • Include Azure CLI examples for all configuration tasks, especially for reserved IP allocation, to provide parity with PowerShell.
  • Explicitly mention that Azure CLI and other cross-platform tools can be used from Linux, macOS, and Windows.
  • Add Bash or shell script examples where appropriate.
  • Clarify that PowerShell is available cross-platform, or provide links to documentation for using PowerShell on Linux if it remains the preferred method.
  • Ensure that any references to deployment methods (e.g., 'template and PowerShell deployments') also mention equivalent Linux-friendly options.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/schema-csdef-file.md ...s/cloud-services-extended-support/schema-csdef-file.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page references a Windows-specific file path for the Azure Diagnostics configuration schema and only mentions the .NET SDK installation directory on Windows. There are no Linux or cross-platform equivalents or examples provided, and the only tooling context is Windows-centric. This may lead Linux users to believe that the csdef schema and related tools are only available or supported on Windows.
Recommendations
  • Add equivalent Linux file paths or clarify where the schema files can be found when using the Azure SDK on Linux.
  • Mention cross-platform SDK installation methods (e.g., via dotnet CLI, package managers) and where schema files are located on non-Windows systems.
  • Provide examples or notes for both Windows and Linux environments when referencing tooling, file locations, or SDK usage.
  • Avoid referencing only Windows tools or directories; if Windows is mentioned, ensure Linux/macOS equivalents are also described.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/schema-csdef-workerrole.md ...d-services-extended-support/schema-csdef-workerrole.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page shows a Windows bias through its exclusive use of Windows-centric terminology and patterns. It references Windows certificate stores (CurrentUser, LocalMachine, My, Root, etc.), environment variables in Windows format (%ROLEROOT%), and startup scripts as CMD/batch files in ANSI format. There are no examples or mentions of Linux equivalents, such as Linux certificate stores, environment variable syntax, or shell scripts. All examples and descriptions assume a Windows environment, with no guidance for Linux-based deployments.
Recommendations
  • Add explicit examples and guidance for Linux-based worker roles, including shell script (sh/bash) startup tasks and Linux file formats.
  • Document Linux equivalents for certificate store locations and names, or clarify platform-specific differences.
  • Use cross-platform environment variable syntax (e.g., $ROLEROOT for Linux) and clarify how paths and variables are handled on Linux.
  • Where Windows-specific terms are used (e.g., CMD files, %ROLEROOT%), provide Linux alternatives or note platform differences.
  • Include a section or table summarizing platform-specific behaviors and configuration requirements for both Windows and Linux worker roles.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/states.md ...ain/articles/cloud-services-extended-support/states.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing PowerShell and Visual Studio (Windows-centric tools) as primary deployment methods, with no mention of Linux-native tools or CLI examples. PowerShell is referenced before more cross-platform options like ARM templates, and there is no explicit guidance for Linux users or parity in deployment instructions.
Recommendations
  • Add Azure CLI deployment instructions and links, as Azure CLI is cross-platform and widely used on Linux.
  • Include examples or references for deploying Cloud Services (extended support) from Linux environments.
  • Mention Linux-compatible editors (e.g., VS Code) alongside Visual Studio.
  • Reorder deployment options to present cross-platform methods (Azure portal, Azure CLI, ARM templates) before Windows-specific tools (PowerShell, Visual Studio).
  • Explicitly state that deployment can be performed from both Windows and Linux systems, and provide guidance for each.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/swap-cloud-service.md .../cloud-services-extended-support/swap-cloud-service.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows PowerShell (Get-AzRole) as the only CLI example for checking role status, mentioning Visual Studio and PowerShell as deployment options without Linux equivalents, and omitting Azure CLI or Bash examples. No Linux-specific tools or workflows are described, and Windows tools are mentioned before or instead of cross-platform alternatives.
Recommendations
  • Add Azure CLI examples (e.g., 'az' commands) for checking role status and performing swaps, as Azure CLI is cross-platform.
  • Include Bash or shell script examples where relevant, especially for REST API usage.
  • Mention cross-platform IDEs (such as VS Code) alongside Visual Studio, or clarify Visual Studio's availability on Windows only.
  • List deployment options in a neutral or alternating order (e.g., Azure portal, ARM template, Azure CLI, PowerShell, Visual Studio) to avoid Windows-first ordering.
  • Explicitly state that PowerShell examples are Windows-specific and provide equivalent commands for Linux/macOS users.
GitHub Create Pull Request
Cloud Services Extended Support About Azure Cloud Services (extended support) ...n/articles/cloud-services-extended-support/overview.md
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page for Azure Cloud Services (extended support) presents deployment options with a notable Windows/PowerShell bias. PowerShell and Visual Studio (Windows-centric tools) are listed before Linux-friendly alternatives, and there are no explicit CLI or Linux/macOS-specific examples or guidance. This may create friction for Linux/macOS users seeking parity in deployment and management workflows.
Recommendations
  • Add explicit Azure CLI examples for deployment and management tasks alongside PowerShell examples.
  • Include references to cross-platform editors (e.g., VS Code) in addition to Visual Studio.
  • Clarify which deployment methods are cross-platform and provide links or guidance for Linux/macOS users.
  • Where PowerShell is mentioned, note that Azure CLI is available and provide equivalent instructions.
  • Consider reordering deployment options so that platform-neutral or Linux-friendly methods (ARM templates, CLI, Portal) are listed before Windows-specific tools.
GitHub Create Pull Request
Cloud Services Extended Support About Azure Cloud Services (extended support) ...n/articles/cloud-services-extended-support/overview.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation references PowerShell and Visual Studio as primary deployment methods, both of which are Windows-centric tools. PowerShell is mentioned before alternatives, and Visual Studio is listed as a deployment option without mention of cross-platform equivalents. There are no explicit Linux/macOS CLI or automation examples, and the documentation does not highlight Azure CLI or other platform-neutral tools for deployment, which may create friction for non-Windows users.
Recommendations
  • Add explicit examples and links for deploying Cloud Services (extended support) using Azure CLI, which is cross-platform.
  • Clarify that PowerShell and Visual Studio are Windows-centric, and provide alternative instructions for Linux/macOS users.
  • Ensure deployment steps and automation scripts are available for Bash/shell environments.
  • List platform-neutral tools (e.g., Azure CLI, VS Code) before or alongside Windows-specific tools.
  • Include a note on supported platforms for each deployment method.
GitHub Create Pull Request
Cloud Services Extended Support Enable Monitoring in Cloud Services (extended support) using the Azure portal ...icles/cloud-services-extended-support/enable-alerts.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page primarily describes enabling monitoring via the Azure portal, which is cross-platform. However, in the 'Next steps' section, deployment options are listed as Azure portal, PowerShell, Template, and Visual Studio. PowerShell and Visual Studio are Windows-centric tools, and PowerShell is mentioned before any Linux-native alternatives (such as Azure CLI or Bash). There are no explicit Linux/macOS examples or references to Linux-friendly tools for deployment or monitoring.
Recommendations
  • Include Azure CLI examples for deployment and monitoring, as it is cross-platform.
  • Mention Bash or shell scripting alternatives where appropriate.
  • Add explicit notes or links for Linux/macOS users on how to perform equivalent tasks.
  • Avoid listing Windows-centric tools (PowerShell, Visual Studio) before cross-platform options.
  • Ensure screenshots and instructions do not assume a Windows environment.
GitHub Create Pull Request
Cloud Services Extended Support Azure Cloud Services (extended support) NetworkConfiguration Schema | Microsoft Docs ...-extended-support/schema-cscfg-networkconfiguration.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references PowerShell as a deployment method for reserved IPs, but does not mention or provide examples for Linux/macOS equivalents (such as Azure CLI or ARM templates). No command-line examples are given, but the only tool referenced is PowerShell, which is Windows-centric.
Recommendations
  • Explicitly mention Azure CLI and ARM template deployment methods alongside PowerShell.
  • Provide example commands for both PowerShell and Azure CLI for configuring reserved IPs and other network settings.
  • Clarify which steps or tools are cross-platform and which are Windows-specific.
  • Add notes or links for Linux/macOS users to relevant documentation.
GitHub Create Pull Request
Cloud Services Extended Support Guest OS family 2, 3, and 4 retirement notice | Microsoft Docs ...port/cloud-services-guestos-family-2-3-4-retirement.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily Windows-centric, focusing exclusively on Windows Server OS families and providing only Azure PowerShell scripts for determining affected services. There are no Linux/macOS command-line examples or guidance, and migration recommendations are tailored to Windows development environments (Visual Studio, .NET Framework).
Recommendations
  • Include equivalent Azure CLI or Bash examples for determining affected services, as Azure CLI is cross-platform.
  • Clarify whether Linux-based cloud services are impacted, and if not, explicitly state this for Linux users.
  • Provide migration guidance for Linux-based workloads if applicable, or note that the retirement is Windows-only.
  • Mention Linux tools or patterns where relevant, and avoid assuming Visual Studio/.NET as the only development environment.
GitHub Create Pull Request
Cloud Services Extended Support Deploy Azure Cloud Services (extended support) - ARM template ...les/cloud-services-extended-support/deploy-template.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a notable Windows bias. Throughout the instructions, Azure PowerShell is repeatedly referenced as the CLI tool for resource creation, file uploads, and deployment, with no mention of Azure CLI or Bash alternatives. Examples and links for creating resource groups, storage accounts, uploading blobs, and deploying templates are exclusively for Azure PowerShell, which is most commonly used on Windows. The extension profile example highlights the RDP extension (Windows-specific) and references Visual Studio (Windows-only) in tags and related content. There are no Linux/macOS-specific instructions or parity for command-line tooling.
Recommendations
  • Add equivalent Azure CLI (az) commands for all steps currently showing only Azure PowerShell.
  • Reference Bash or cross-platform scripting options for uploading files and deploying templates.
  • Include instructions for using the Azure portal and Azure CLI on Linux/macOS for resource creation and deployment.
  • Clarify that Visual Studio is Windows-only and suggest cross-platform alternatives (e.g., VS Code) where possible.
  • For extension profiles, mention Linux-compatible extensions if available, or clarify Windows-only functionality.
GitHub Create Pull Request
Cloud Services Extended Support Available sizes for Azure Cloud Services (extended support) ...les/cloud-services-extended-support/available-sizes.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. The only example for listing available VM sizes uses PowerShell, a Windows-centric tool, with no mention of Linux/macOS alternatives (such as Azure CLI or REST API usage from Bash). The 'Next steps' section lists Windows tools (PowerShell, Visual Studio) before Linux-friendly options (Azure CLI, ARM templates), and omits explicit Linux/macOS instructions or examples throughout.
Recommendations
  • Add equivalent Azure CLI examples for listing VM sizes, suitable for Linux/macOS users.
  • Explicitly mention REST API usage with curl or similar cross-platform tools.
  • In 'Next steps', list cross-platform tools (Azure CLI, ARM templates) before or alongside Windows-specific tools.
  • Where PowerShell is shown, provide parallel Bash/Azure CLI commands.
  • Clarify that all operations can be performed from Linux/macOS environments and link to relevant documentation.
GitHub Create Pull Request
Cloud Services Extended Support Store and use certificates in Azure Cloud Services (extended support) ...ervices-extended-support/certificates-and-key-vault.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. It references PowerShell as a primary CLI method for creating Key Vaults, omits explicit Linux/macOS CLI examples (such as Azure CLI or Bash), and lists Windows-centric tools like Visual Studio for deployment. The certificate format requirement (.PFX) is also more common in Windows environments, with no mention of conversion from Linux-preferred formats (e.g., PEM).
Recommendations
  • Add Azure CLI and Bash examples for creating and managing Key Vaults and certificates.
  • Include instructions for converting PEM certificates to PFX, addressing Linux/macOS workflows.
  • List deployment options in a platform-neutral order (e.g., Portal, CLI, Template, IDE), and explicitly mention cross-platform tools.
  • Provide screenshots or guidance for Linux/macOS users where UI or file format differences may exist.
GitHub Create Pull Request
Cloud Services Extended Support What is the Azure Cloud Service (extended support) model and package ...s-extended-support/cloud-services-model-and-package.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. Key packaging and deployment tools (CSPack, Compute Emulator) are described only in terms of their Windows installation paths and usage, with no mention of Linux/macOS equivalents or alternatives. Example commands are given in Windows CMD syntax, and Visual Studio is referenced as the primary IDE. The deployment section lists PowerShell and Visual Studio before mentioning templates, with no explicit Linux CLI or cross-platform instructions. There are no examples or guidance for Linux/macOS users on how to package or deploy cloud services.
Recommendations
  • Document how to install and use CSPack on Linux/macOS, if supported, or provide alternative cross-platform packaging instructions (e.g., via Azure CLI, Docker, or other tools).
  • Include example commands for Linux/macOS shells (bash/zsh), and clarify any differences in usage or file paths.
  • Mention and provide instructions for using cross-platform tools (such as Azure CLI) for deployment and packaging, alongside PowerShell and Visual Studio.
  • Explicitly state platform limitations for tools like Compute Emulator and CSPack, and suggest workarounds or alternatives for non-Windows users.
  • Reorder deployment options to present cross-platform methods (Azure CLI, templates) before Windows-specific tools.
GitHub Create Pull Request
Cloud Services Extended Support Extensions for Cloud Services (extended support) ...articles/cloud-services-extended-support/extensions.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a Windows bias by primarily referencing Windows-specific tools and patterns, such as PowerShell cmdlets and Windows Defender, especially in the Anti Malware Extension section. There is no mention of Linux/macOS equivalents or guidance for users on those platforms. The 'Next steps' section also lists PowerShell and Visual Studio (both Windows-centric) before mentioning more cross-platform options.
Recommendations
  • Include Linux/macOS-specific instructions or note platform limitations for each extension, especially for Anti Malware and Remote Desktop.
  • Provide CLI (az cli) examples alongside PowerShell for deployment and extension management.
  • Clarify which extensions are Windows-only and suggest alternatives or workarounds for Linux-based cloud services.
  • Reorder 'Next steps' to list cross-platform options (Azure portal, Template, CLI) before Windows-specific tools.
  • Explicitly state platform support for each extension to help users understand applicability.
GitHub Create Pull Request
Cloud Services Extended Support Migrate Azure Cloud Services (classic) to Azure Cloud Services (extended support) ...rvices-extended-support/in-place-migration-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is the only command-line example shown for critical migration steps, and Windows-centric tools (PowerShell, Visual Studio) are listed prominently as deployment options. There is no mention of Linux/macOS-specific tools or shell commands (e.g., Bash, Azure CLI examples), and PowerShell is referenced before CLI in provider registration instructions. This creates friction for Linux/macOS users who may not use PowerShell or Visual Studio.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line instructions, especially for resource provider registration and migration steps.
  • Include guidance for deploying Cloud Services (extended support) using cross-platform tools such as Azure CLI and SDKs in languages commonly used on Linux/macOS.
  • List deployment options in a neutral order (e.g., Portal, CLI, PowerShell, SDK, Visual Studio) or group by platform.
  • Explicitly mention Linux/macOS compatibility and provide links to relevant cross-platform documentation.
  • If Visual Studio is referenced, also mention alternatives like VS Code or other IDEs available on Linux/macOS.
GitHub Create Pull Request
Cloud Services Extended Support Override SKU information over CSCFG/CSDEF for Azure Cloud Services (extended support) ...ticles/cloud-services-extended-support/override-sku.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides explicit PowerShell examples for overriding SKU settings, but does not offer equivalent CLI or shell examples for Linux/macOS users. PowerShell is featured before SDK examples, and there is no mention of cross-platform tools like Azure CLI or Bash scripts. This creates friction for users on non-Windows platforms, who must adapt the instructions themselves.
Recommendations
  • Add Azure CLI examples for setting allowModelOverride, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash or shell script snippets where appropriate.
  • Clarify which tools are cross-platform and recommend them for non-Windows users.
  • Present examples in a neutral order (e.g., ARM template, CLI, PowerShell, SDK) rather than Windows-first.
GitHub Create Pull Request
Cloud Services Extended Support Azure Cloud Services (extended support) post-migration changes ...ud-services-extended-support/post-migration-changes.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, primarily through the frequent and prioritized use of PowerShell for examples and guidance. In several sections, PowerShell is mentioned before CLI or REST API alternatives, and in some cases, only PowerShell and REST API are provided as options for key tasks (such as retrieving .csdef and .cscfg files), with no explicit Azure CLI or Bash examples. There is also a lack of Linux/macOS-specific guidance or parity in automation/script references, and Visual Studio (a Windows-centric tool) is referenced for update workflows without alternatives for other platforms.
Recommendations
  • Add explicit Azure CLI examples for all tasks currently shown with PowerShell, especially for retrieving deployment files (.csdef, .cscfg).
  • Ensure CLI and REST API options are listed before or alongside PowerShell, not after.
  • Include Bash script samples or references for automation tasks where appropriate.
  • Mention cross-platform editors (such as VS Code) and provide update instructions for non-Windows environments.
  • Clarify that all API and CLI methods are cross-platform, and highlight any platform-specific limitations or requirements.
GitHub Create Pull Request
Cloud Services Extended Support Available States for Azure Cloud Services (extended support) ...ain/articles/cloud-services-extended-support/states.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page lists deployment options for Azure Cloud Services (extended support) and mentions Windows-centric tools (PowerShell, Visual Studio) before any Linux-friendly alternatives. PowerShell is highlighted as a deployment method, and Visual Studio is referenced, both of which are primarily Windows tools. There is no mention of Linux-native tools (such as Azure CLI or Bash scripting), nor are Linux/macOS-specific instructions or examples provided.
Recommendations
  • Add deployment instructions and examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • List Linux/macOS-friendly tools (e.g., Bash, Azure CLI) alongside or before Windows tools in the 'Next steps' section.
  • Provide parity in documentation by ensuring that all critical operations (deployment, monitoring, troubleshooting) have examples for both Windows and Linux environments.
  • Explicitly mention platform compatibility for each tool or method.
GitHub Create Pull Request
Cloud Services Extended Support Swap or switch deployments in Azure Cloud Services (extended support) .../cloud-services-extended-support/swap-cloud-service.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page shows evidence of Windows bias. In the 'Common questions' section, only Windows PowerShell ('Get-AzRole') is mentioned for checking instance status, with no Linux/macOS CLI equivalent. In the 'Next steps' section, PowerShell and Visual Studio (Windows-centric tools) are listed before ARM template, and no Azure CLI or Bash examples are provided. There are no Linux/macOS-specific instructions or parity for command-line operations.
Recommendations
  • Add Azure CLI examples for checking instance status (e.g., 'az vm list' or relevant cloud service commands) alongside PowerShell.
  • Include Bash or shell script examples where appropriate.
  • Mention cross-platform tools (Azure CLI, VS Code) before or alongside Windows-only tools (PowerShell, Visual Studio).
  • Clarify that all operations can be performed from Linux/macOS environments using Azure CLI or REST API.
  • Ensure that portal instructions are explicitly marked as cross-platform.
GitHub Create Pull Request
Cloud Services Extended Support Available sizes for Azure Cloud Services (extended support) ...les/cloud-services-extended-support/available-sizes.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for listing available VM sizes, referencing Windows-centric tools (PowerShell, Visual Studio), and omitting equivalent Linux/macOS CLI commands. The deployment section lists Windows tools before alternatives, and no Bash/Azure CLI examples are provided for Linux users.
Recommendations
  • Add Azure CLI (az) examples for listing available VM sizes, suitable for Linux/macOS users.
  • Include Bash shell command snippets alongside PowerShell examples.
  • Mention cross-platform tools (e.g., Azure CLI, ARM templates) before or alongside Windows-specific tools.
  • Clarify that Visual Studio and PowerShell are Windows-centric, and provide alternatives for Linux/macOS (e.g., VS Code, Azure CLI).
  • Ensure deployment instructions and code samples are platform-neutral or include both Windows and Linux/macOS options.
GitHub Create Pull Request
Cloud Services Extended Support Store and use certificates in Azure Cloud Services (extended support) ...ervices-extended-support/certificates-and-key-vault.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the only CLI method for creating Key Vaults, omitting Azure CLI or Bash examples. The certificate format required (.PFX) is most commonly associated with Windows, and there are no instructions for Linux/macOS users on how to generate or handle this format. Deployment options highlight PowerShell and Visual Studio (Windows tools) before mentioning templates, with no mention of Azure CLI or cross-platform alternatives.
Recommendations
  • Add Azure CLI and Bash examples for creating and managing Key Vaults and certificates.
  • Provide instructions for generating .PFX certificates on Linux/macOS (e.g., using OpenSSL).
  • List deployment options in a neutral order, and include Azure CLI as a cross-platform method.
  • Clarify that .PFX files can be generated and used on non-Windows platforms, with links to relevant guides.
GitHub Create Pull Request
Cloud Services Extended Support Guest OS family 1 retirement notice | Microsoft Docs ...-support/cloud-services-guestos-family-1-retirement.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. All example scripts for determining affected services use Azure PowerShell, with no equivalent Bash, Azure CLI, or cross-platform instructions. The OS families referenced are exclusively Windows Server versions, and migration recommendations focus on .NET and Windows-centric technologies. No Linux or macOS alternatives or guidance are provided for users managing Azure resources from non-Windows platforms.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for listing affected cloud services, which work on Linux/macOS.
  • Mention cross-platform tools (e.g., Azure CLI, REST API) alongside PowerShell, and link to their setup guides.
  • Clarify whether the migration steps (editing ServiceConfiguration.cscfg, redeploying) can be performed from any OS, and provide instructions if so.
  • Explicitly state that the guidance applies to Windows-based cloud services, and note if Linux-based services are unaffected or require different steps.
GitHub Create Pull Request
Cloud Services Extended Support Deploy Azure Cloud Services (extended support) - SDK ...articles/cloud-services-extended-support/deploy-sdk.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, especially in the sections related to certificate and key vault management. All command-line examples for these steps use Azure PowerShell, which is primarily a Windows tool, and there are no Bash/CLI equivalents or cross-platform alternatives provided. The use of PowerShell cmdlets for key vault operations and certificate management excludes native Linux/macOS workflows, and the RDP extension example is also Windows-centric. No Linux or macOS-specific instructions or examples are present for these critical steps.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell commands, especially for key vault and certificate management steps.
  • Explicitly mention that Azure CLI is cross-platform and show how to perform certificate and key vault operations using Bash or shell scripts.
  • Add notes or examples for Linux/macOS users, including how to generate and upload certificates from those platforms.
  • Consider including SSH extension examples alongside RDP for remote access, as SSH is the standard for Linux/macOS.
  • Reorder examples or provide parallel instructions so that Windows and Linux/macOS users are equally supported.
GitHub Create Pull Request
Cloud Services Extended Support Apply the Microsoft Azure diagnostics extension in Cloud Services (extended support) ...articles/cloud-services-extended-support/enable-wad.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based instructions and commands for applying the Azure diagnostics extension. There are no equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or cross-platform scripting), and Windows-centric tools and patterns (PowerShell, Visual Studio) are mentioned first or exclusively. This creates friction for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, including extension creation, configuration file download, and service updates.
  • Provide Bash or shell script snippets for downloading and manipulating configuration files.
  • Clarify which steps are platform-agnostic and which require Windows-specific tools.
  • Reorder examples so that cross-platform or Azure CLI instructions appear before or alongside PowerShell.
  • Mention and link to Linux/macOS documentation or troubleshooting guides where relevant.
GitHub Create Pull Request
← Previous Page 2 of 3 Next →