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 1-25 of 56 flagged pages
Cloud Services Extended Support Guest OS family 1 retirement notice | Microsoft Docs ...-support/cloud-services-guestos-family-1-retirement.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a strong Windows bias. The only script provided for identifying affected services uses Azure PowerShell, with no mention of cross-platform alternatives (such as Azure CLI or REST API). All OS families referenced are Windows Server-based, and migration instructions focus exclusively on .NET and Windows environments. There are no Linux/macOS examples or guidance for users managing Azure resources from non-Windows platforms.
Recommendations
  • Provide equivalent Azure CLI commands for identifying affected services, as Azure CLI is cross-platform.
  • Include REST API examples for users who may prefer scripting in bash or other environments.
  • Explicitly mention that the PowerShell script is Windows-only and offer alternatives for Linux/macOS users.
  • Clarify if there are any supported Linux-based Guest OS families, or state that only Windows Server families are available.
  • Add migration guidance for applications not based on .NET or Windows, if relevant.
GitHub Create Pull Request
Cloud Services Extended Support Learn about the latest Azure Guest OS Releases | Microsoft Docs ...tended-support/cloud-services-guestos-update-matrix.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is exclusively focused on Windows Server-based Guest OS releases for Azure Cloud Services. All examples, configuration strings, and compatibility notes reference only Windows Server versions and .NET Framework. There is no mention of Linux-based Guest OS families, nor any guidance, examples, or tooling for Linux or cross-platform scenarios. Windows tools (Visual Studio, RDP) are referenced without alternatives.
Recommendations
  • Explicitly state that Azure Cloud Services Guest OS is Windows-only, if that is the case, to avoid confusion for Linux users.
  • If Linux-based Guest OS families are supported or planned, add equivalent documentation sections for those, including release notes, configuration strings, and SDK compatibility.
  • Provide guidance or links for users seeking Linux-based solutions on Azure (e.g., Azure Virtual Machines, Azure App Service for Linux, Azure Kubernetes Service).
  • Where Windows tools (Visual Studio, RDP) are mentioned, suggest cross-platform alternatives or clarify their applicability.
  • Add a comparison table or FAQ explaining the differences between Cloud Services (classic), IaaS VMs, and Linux support in Azure.
GitHub Create Pull Request
Cloud Services Extended Support Azure Cloud Services (extended support) Def. WebRole Schema | Microsoft Docs ...loud-services-extended-support/schema-csdef-webrole.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, referencing IIS 7, ASP.NET, Windows Communication Foundation, and Windows certificate stores. All examples and schema elements assume Windows tooling and patterns (e.g., IIS, Windows certificate store names, CMD/batch scripts for startup tasks), with no mention of Linux equivalents or cross-platform alternatives. There are no Linux/macOS-specific examples or guidance, and Windows terminology and tools are used exclusively and presented first.
Recommendations
  • Add explicit notes about Linux support or lack thereof for Azure Cloud Services (extended support) web roles.
  • If Linux support exists, provide equivalent examples for Linux environments (e.g., using Apache/Nginx, Linux certificate stores, shell scripts for startup tasks).
  • Clarify which schema elements and features are Windows-only, and suggest alternatives for Linux users or direct them to relevant Azure Linux documentation.
  • Include cross-platform guidance for startup tasks (e.g., support for Bash scripts, file encoding requirements for Linux).
  • Mention any limitations or differences when deploying to Linux VMs, if supported.
GitHub Create Pull Request
Cloud Services Extended Support Apply the Key Vault VM extension in Azure Cloud Services (extended support) ...s-extended-support/enable-key-vault-virtual-machine.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows, referencing the Key Vault VM extension for Windows, Windows certificate store, and Windows-specific properties (e.g., 'certificateStoreLocation', 'LocalMachine', 'My'). There are no examples or guidance for Linux or cross-platform scenarios, and all instructions and code snippets assume a Windows environment.
Recommendations
  • Clarify whether the Key Vault VM extension is available for Linux VMs or Cloud Services running Linux.
  • If Linux support exists, provide equivalent instructions and examples for Linux, including certificate store paths and permissions.
  • Mention Linux-specific tools or patterns for certificate management and integration with Key Vault.
  • If the extension is Windows-only, explicitly state this limitation at the beginning of the 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
High 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 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, nor any mention of Linux-based guest OS families or migration paths. Windows tools and patterns (Visual Studio, .NET Framework, PowerShell) are referenced exclusively and prominently.
Recommendations
  • Include equivalent Azure CLI or Bash examples for determining affected services, which can be run on Linux/macOS.
  • Clarify whether Linux-based guest OS families are impacted, and provide guidance for Linux users if relevant.
  • Mention cross-platform tools (e.g., Azure CLI, REST API) before or alongside Windows-specific tools.
  • Add migration recommendations for Linux workloads if applicable, or explicitly state that the retirement notice only affects Windows guest OS families.
GitHub Create Pull Request
Cloud Services Extended Support Learn about the latest Azure Guest OS Releases | Microsoft Docs ...tended-support/cloud-services-guestos-update-matrix.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is exclusively focused on Windows Server-based Guest OS families for Azure Cloud Services. All examples, configuration strings, and recommendations reference Windows Server versions and Windows-centric tooling (e.g., Visual Studio, .NET Framework, RDP). There is no mention of Linux-based Guest OS support, nor any guidance, examples, or parity for Linux users. The documentation assumes the reader is deploying on Windows and omits Linux entirely.
Recommendations
  • Explicitly state in the introduction whether Linux-based Guest OS images are supported or not for Cloud Services. If not supported, clarify this limitation for cross-platform users.
  • If Linux Guest OS support exists or is planned, add equivalent tables and update notes for Linux distributions, including release cadence, configuration strings, and supported SDK versions.
  • Provide guidance for cross-platform development environments (e.g., VS Code, CLI tools) and deployment workflows that do not require Windows-specific tools.
  • Include links or references to documentation for Linux-based workloads on Azure (e.g., Azure Virtual Machines, App Service Linux) for users seeking non-Windows options.
GitHub Create Pull Request
Cloud Services Extended Support Available sizes for Azure Cloud Services (extended support) ...les/cloud-services-extended-support/available-sizes.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 retrieving VM sizes, referencing Windows-centric tools (PowerShell, Visual Studio), and omitting equivalent Linux/CLI examples. The deployment options list PowerShell and Visual Studio before mentioning templates, with no explicit mention of Azure CLI or Bash commands. This may disadvantage users working on Linux or cross-platform environments.
Recommendations
  • Add Azure CLI examples for listing available VM sizes, alongside the PowerShell example.
  • Explicitly mention Linux-compatible tools and workflows (e.g., Bash, Azure CLI) in deployment steps.
  • Balance the order of tool references so that cross-platform or Linux-native options (Azure CLI, ARM templates) are listed before or alongside Windows-specific tools.
  • Include notes or links for Linux users on how to perform equivalent tasks.
  • Consider adding sample commands for both Windows and Linux environments wherever code snippets or instructions are provided.
GitHub Create Pull Request
Cloud Services Extended Support Guest OS family 1 retirement notice | Microsoft Docs ...-support/cloud-services-guestos-family-1-retirement.md
High Priority View Details →
Scanned: 2026-01-10 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 page exclusively references Windows Server-based Guest OS families and provides only Azure PowerShell scripts for determining affected services. There are no examples or guidance for Linux-based cloud services, nor are cross-platform tools or CLI alternatives mentioned. Windows terminology and migration paths are presented without Linux parity.
Recommendations
  • Include examples for identifying affected services using Azure CLI or REST API, which are cross-platform and usable on Linux and macOS.
  • Clarify whether Linux-based cloud services are impacted, and if not, explicitly state this to avoid confusion.
  • Provide migration guidance for Linux-based workloads if applicable, or reference relevant documentation for Linux cloud service management.
  • Balance the presentation by mentioning both Windows and Linux Guest OS families (if supported), and provide equivalent instructions for each.
  • Add notes or links to resources for users managing cloud services from non-Windows environments.
GitHub Create Pull Request
Cloud Services Extended Support Azure Cloud Services (extended support) NetworkConfiguration Schema | Microsoft Docs ...-extended-support/schema-cscfg-networkconfiguration.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. The only tool mentioned for deployment is PowerShell, which is primarily a Windows-centric tool (though it is available on Linux, its usage is much less common in Linux environments). There are no examples or references to Linux-native tools (such as Azure CLI, Bash, or ARM templates) for managing or deploying network configuration. No Linux-specific patterns or examples are provided, and the documentation does not mention or demonstrate parity for Linux users.
Recommendations
  • Add examples using Azure CLI commands for deployment and configuration, alongside PowerShell examples.
  • Explicitly mention that PowerShell is available on Linux, but also provide Bash/CLI equivalents for common tasks.
  • Include references to ARM/Bicep templates for infrastructure-as-code scenarios, which are platform-neutral.
  • Where deployment tooling is discussed, present Linux and Windows options side-by-side, or clarify cross-platform support.
  • Review and update documentation to ensure Linux users are not required to infer steps from Windows-centric instructions.
GitHub Create Pull Request
Cloud Services Extended Support 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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the only command-line example for creating Key Vaults, requiring certificates in .PFX format (commonly used in Windows environments), and mentioning Visual Studio as a deployment tool. There are no examples or instructions for Linux users (e.g., using Azure CLI or OpenSSL), nor is there mention of Linux-compatible certificate formats or tools.
Recommendations
  • Add Azure CLI examples for creating Key Vaults and uploading certificates, alongside PowerShell.
  • Include instructions for generating and converting certificates using OpenSSL, which is standard on Linux.
  • Mention and support certificate formats commonly used on Linux (such as PEM or CRT), and provide guidance for converting to .PFX if required.
  • List Linux deployment tools and workflows (e.g., Azure CLI, VS Code) alongside Visual Studio.
  • Ensure that all steps and screenshots have Linux parity, or note any platform-specific differences.
GitHub Create Pull Request
Cloud Services Extended Support 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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily Windows-centric. All examples and instructions reference Windows Server OS families, PowerShell scripts, and Windows development tools (Visual Studio, .NET Framework). There are no Linux equivalents or migration paths discussed, and the only script provided is for Azure PowerShell, with no mention of Azure CLI or Bash alternatives.
Recommendations
  • Provide equivalent Azure CLI or Bash scripts for identifying affected services, as Azure CLI is cross-platform and widely used on Linux.
  • Clarify whether Linux-based cloud services are affected, and if not, explicitly state this to avoid confusion.
  • Include migration guidance for Linux-based workloads if applicable, or a note that this retirement only impacts Windows-based guest OS families.
  • Mention cross-platform development tools (e.g., VS Code, .NET Core/6+) where possible, not just Visual Studio and .NET Framework.
  • Reorder or supplement instructions so that cross-platform or Linux options are presented alongside or before Windows-specific tools.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/cloud-services-guestos-family-1-retirement.md ...-support/cloud-services-guestos-family-1-retirement.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 Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias. All technical examples, including the only script provided, use Azure PowerShell, with no mention of Azure CLI, Bash, or cross-platform alternatives. The OS families discussed are exclusively Windows Server-based, and migration recommendations focus solely on Windows Server versions and .NET frameworks. There are no Linux-based guest OS options or examples, and Windows tools and patterns are referenced exclusively and before any Linux equivalents (which are not mentioned at all).
Recommendations
  • Provide equivalent Azure CLI or Bash script examples for determining OS Family, ensuring cross-platform compatibility.
  • Mention and link to documentation for Linux-based guest OS options if available, or clarify if only Windows OS families are supported.
  • If Linux guest OS is not supported for this service, explicitly state this to avoid confusion.
  • When referencing tools or scripts, present cross-platform options (e.g., Azure CLI, REST API) before or alongside Windows/PowerShell examples.
  • Consider including a section addressing migration paths for workloads that could move to Linux-based services (such as Azure Virtual Machines with Linux OS) if relevant.
GitHub Create Pull Request
Cloud Services Extended Support 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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric tools and workflows. The 'Next steps' section lists PowerShell and Visual Studio (both Windows-focused) as deployment options, with no mention of Linux equivalents (such as Azure CLI or cross-platform editors like VS Code). The only code example link for queue storage uses a Windows environment variable tab by default. There are no explicit Linux or cross-platform command-line examples, and the portal screenshots and instructions do not address Linux users or alternative tooling.
Recommendations
  • Add Azure CLI examples for scaling and deployment, as Azure CLI is cross-platform and widely used on Linux.
  • Include references to cross-platform editors like Visual Studio Code, not just Visual Studio.
  • Ensure that links to quickstarts or tutorials include Linux/macOS tabs or examples, not just Windows/PowerShell.
  • Explicitly mention that the Azure portal is OS-agnostic, and clarify any steps that might differ on Linux.
  • Balance the order of tool mentions (e.g., list Azure CLI before or alongside PowerShell) to avoid 'windows_first' bias.
GitHub Create Pull Request
Cloud Services Extended Support 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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily Windows-centric: it only discusses the Key Vault VM extension for Windows, references the Windows certificate store, and provides no information or examples for Linux VMs or their certificate management. All instructions, settings, and terminology are specific to Windows environments, with no mention of Linux equivalents or cross-platform considerations.
Recommendations
  • Add information about the availability (or lack thereof) of the Key Vault VM extension for Linux VMs in Azure Cloud Services (extended support).
  • If a Linux equivalent exists, provide parallel instructions and examples for Linux, including how certificates are stored and managed.
  • Mention Linux certificate store locations and relevant configuration properties if supported.
  • If only Windows is supported, explicitly state this early in the documentation to set expectations.
  • Reference Linux tools, patterns, or Azure extensions where appropriate, and provide links to relevant documentation.
GitHub Create Pull Request
Cloud Services Extended Support 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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by frequently referencing PowerShell and Visual Studio as primary tools for deployment and configuration, with little or no mention of Linux equivalents or cross-platform alternatives. PowerShell is listed before Azure CLI, and Visual Studio is mentioned as a deployment tool without reference to cross-platform IDEs. There are no explicit Linux shell or CLI examples, and the documentation assumes familiarity with Windows-centric tools and patterns.
Recommendations
  • Provide Azure CLI examples alongside or before PowerShell examples, especially for common tasks like creating virtual networks and key vaults.
  • Mention cross-platform or Linux-friendly tools (e.g., Visual Studio Code, Azure CLI) wherever Visual Studio or PowerShell are referenced.
  • Ensure that all code snippets and instructions are platform-agnostic or include both Windows and Linux variants where applicable.
  • Add explicit Linux shell (bash) examples for tasks currently only shown with PowerShell.
  • Clarify when a tool or method is Windows-only, and suggest Linux-compatible alternatives.
GitHub Create Pull Request
Cloud Services Extended Support 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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias in several ways: all command-line examples for key vault and certificate management use PowerShell, with no Bash, Azure CLI, or Linux-native alternatives. The SDK code samples and extension configuration reference Windows-centric patterns (e.g., RDP, Microsoft.Windows.Azure.Extensions). Windows tools and terminology (PowerShell, RDP, .cspkg) are mentioned exclusively or before Linux equivalents, and there is no guidance for Linux users on how to perform these steps. The absence of Linux or cross-platform command-line examples and the prioritization of Windows-centric workflows indicate a significant bias toward Windows environments.
Recommendations
  • Add equivalent Azure CLI and Bash examples for all PowerShell commands, especially for key vault and certificate management.
  • Explicitly mention Linux support and provide instructions for Linux users, including how to install required SDKs and tools.
  • Include references to Linux-friendly remote access extensions (such as SSH) alongside RDP, and clarify cross-platform options.
  • Document how to generate and upload certificates from Linux environments (e.g., using OpenSSL and Azure CLI).
  • Review terminology and tool references to ensure parity (e.g., mention both .cspkg and .zip formats, clarify their use on Linux).
  • Add a section or callout for cross-platform deployment considerations, highlighting any differences or requirements for Linux users.
GitHub Create Pull Request
Cloud Services Extended Support 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 →
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 primarily references Windows-centric tools and workflows, such as PowerShell and Visual Studio, and does not provide Linux-specific examples or mention Linux tools (e.g., Azure CLI, Bash scripting). The order of deployment options also lists Windows tools before cross-platform or Linux-friendly alternatives, and there are no explicit Linux examples or screenshots.
Recommendations
  • Include Azure CLI examples for enabling monitoring and deploying Cloud Services, as Azure CLI is cross-platform and widely used on Linux.
  • List deployment options in a neutral or alternating order (e.g., Azure portal, Azure CLI, PowerShell, Template, Visual Studio) to avoid Windows-first bias.
  • Add explicit mention of Linux support and provide screenshots or instructions relevant to Linux users where applicable.
  • Reference Bash scripting or other Linux-native automation options alongside PowerShell.
  • Clarify that the Azure portal is accessible from any OS, and highlight any differences (if any) for Linux users.
GitHub Create Pull Request
Cloud Services Extended Support 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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
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 for managing the Remote Desktop extension use PowerShell, a Windows-centric tool, with no mention of Linux alternatives such as Azure CLI or Bash. The workflow assumes the use of RDP, which is natively a Windows protocol, and does not discuss Linux-compatible remote access methods (e.g., SSH, xrdp). The 'Next steps' section lists PowerShell and Visual Studio (both Windows-focused) before mentioning templates, and does not reference Linux-native tools or workflows.
Recommendations
  • Add Azure CLI examples for managing the Remote Desktop extension, as Azure CLI is cross-platform and works on Linux.
  • Include instructions or notes for connecting to Linux role instances, such as using SSH or xrdp, if supported.
  • Mention Linux-compatible remote desktop clients and workflows for users on non-Windows platforms.
  • Reorder 'Next steps' to present cross-platform options (Azure portal, Azure CLI, templates) before Windows-specific tools (PowerShell, Visual Studio).
  • Clarify whether the Remote Desktop extension is applicable only to Windows role instances, and provide guidance for Linux instances if relevant.
GitHub Create Pull Request
Cloud Services Extended Support 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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page provides only PowerShell and ARM template examples for applying the Azure diagnostics extension, with all command-line instructions using PowerShell (a Windows-centric tool). There are no examples or instructions for Linux users (e.g., using Azure CLI, Bash, or cross-platform scripting), and Windows tools/patterns are mentioned exclusively and first. This creates a strong Windows bias and limits accessibility for Linux users.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that PowerShell examples are Windows-centric and provide guidance for Linux users.
  • Include Bash scripting examples where relevant, especially for file manipulation or automation.
  • List cross-platform methods (e.g., Azure CLI, REST API) before or alongside Windows-specific tools like PowerShell.
  • Ensure that all schema download and configuration steps have Linux-compatible alternatives.
  • Review and update the 'Next steps' section to include Linux-friendly tools and workflows, such as Azure CLI and VS Code.
GitHub Create Pull Request
Cloud Services Extended Support 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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell as the primary or sole scripting interface for migration operations (e.g., abort/commit, retrieving deployments), with no explicit mention or examples for Linux users (such as Bash, Azure CLI, or cross-platform scripting). Where command-line tools are referenced, PowerShell is consistently listed before Azure CLI, and no Linux-specific workflows or examples are provided. This may make the documentation less accessible or clear for users on Linux or macOS platforms.
Recommendations
  • Provide Azure CLI examples alongside or before PowerShell examples for all migration operations, including abort, commit, and deployment retrieval.
  • Explicitly mention that Azure CLI is cross-platform and supported on Linux/macOS, and provide equivalent commands.
  • Where PowerShell is referenced for troubleshooting (e.g., retrying stuck operations), add Azure CLI and/or REST API alternatives.
  • Include a section or callout for Linux/macOS users, highlighting any platform-specific considerations or tools.
  • Review all references to scripting and command-line tools to ensure parity and clarity for non-Windows users.
GitHub Create Pull Request
Cloud Services Extended Support 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 →
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 provides explicit PowerShell examples and references to the Azure PowerShell module (New-AzCloudService), which is primarily a Windows-centric tool. There are no CLI (az cli), Bash, or Linux-native examples. The SDK example is in C#, a language most commonly associated with Windows development. No Linux-first or cross-platform command-line examples are provided.
Recommendations
  • Add equivalent Azure CLI (az cli) examples for setting allowModelOverride, as Azure CLI is cross-platform and widely used on Linux.
  • Include Bash or shell script examples where appropriate, especially for automation scenarios.
  • Mention cross-platform tools and approaches before or alongside PowerShell, rather than only providing PowerShell and C# examples.
  • Clarify in the documentation that the PowerShell example is also available on Linux (if true), or provide guidance for Linux users.
  • Consider adding SDK examples in languages popular on Linux, such as Python or Java, to improve parity.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/schema-cscfg-file.md ...s/cloud-services-extended-support/schema-cscfg-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 exhibits Windows bias by referencing only Windows file paths (e.g., C:\Program Files\Microsoft SDKs\Windows Azure\.NET SDK), mentioning Visual Studio and .NET SDK tools without Linux equivalents, and omitting Linux-specific instructions or examples for locating or using the schema files. There are no Linux or cross-platform examples or guidance.
Recommendations
  • Include Linux and macOS file paths for the Azure SDK schema installation location, or clarify cross-platform installation differences.
  • Mention and provide examples for using cross-platform tools (such as Azure CLI or VS Code) for schema validation and configuration, not just Visual Studio.
  • Add explicit instructions or notes for Linux users on how to obtain and use the .cscfg schema files.
  • Ensure that any references to SDK tools or workflows are accompanied by Linux/macOS equivalents or alternatives.
  • Consider providing a table or section that summarizes differences in usage or file locations between Windows and Linux environments.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/non-vnet-migration.md .../cloud-services-extended-support/non-vnet-migration.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page focuses exclusively on migration steps using the Azure portal and references PowerShell for further migration steps, without mentioning or providing examples for Linux users or CLI tools such as Azure CLI. The 'Next steps' section lists PowerShell before any Linux-friendly alternatives, and there are no Linux-specific instructions or screenshots.
Recommendations
  • Add equivalent migration instructions using Azure CLI, which is cross-platform and widely used on Linux.
  • Include examples or links for Bash scripting or automation, not just PowerShell.
  • In the 'Next steps' section, list Azure CLI and Linux-friendly options alongside or before PowerShell.
  • Add a note clarifying that all steps can be performed on Linux using Azure CLI, and provide links to relevant documentation.
  • Ensure screenshots and UI references are platform-agnostic or include notes for Linux users where appropriate.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/overview.md ...n/articles/cloud-services-extended-support/overview.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by listing Windows-centric tools (PowerShell, Visual Studio) before alternatives, referencing PowerShell as a primary automation method, and omitting Linux-native tools or CLI examples. There are no explicit Linux or cross-platform command-line examples (e.g., Azure CLI, Bash), and the guidance does not mention Linux development environments or editors.
Recommendations
  • Add Azure CLI examples alongside or before PowerShell for deployment and migration tasks, as Azure CLI is cross-platform and widely used on Linux.
  • Mention and provide examples using cross-platform editors (e.g., VS Code) in addition to Visual Studio.
  • Explicitly state that all deployment and management operations can be performed from Linux, macOS, and Windows, and link to relevant Linux documentation.
  • Reorder tool listings to avoid always listing Windows tools first; alternate or group by platform-neutral and platform-specific tools.
  • Provide Bash script examples where automation is discussed, or at least reference their availability.
  • Ensure that all referenced links for deployment (e.g., 'deploy-powershell.md', 'deploy-visual-studio.md') have Linux equivalents or alternatives (e.g., 'deploy-cli.md', 'deploy-vscode.md').
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/post-migration-changes.md ...ud-services-extended-support/post-migration-changes.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell and Windows-centric tools in its examples and instructions. PowerShell is mentioned repeatedly as the primary automation and scripting tool, with no equivalent Bash, Azure CLI, or Linux shell examples provided. References to Visual Studio (a Windows-only IDE) and the lack of explicit Linux or cross-platform guidance further reinforce the bias. Azure CLI is mentioned only once, and always after PowerShell, while REST API is presented as a generic alternative rather than a first-class cross-platform option.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts alongside PowerShell, especially for retrieving deployment files and managing resources.
  • Include explicit instructions or references for Linux/macOS users, such as using Azure CLI or REST API from non-Windows environments.
  • Mention cross-platform editors (e.g., VS Code) in addition to Visual Studio for deployment file updates.
  • Reorder examples so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell.
  • Add a section or note clarifying that all operations can be performed from Linux/macOS using CLI or REST API, and link to relevant documentation.
GitHub Create Pull Request
← Previous Page 1 of 3 Next →