Cloud Services Extended Support
45
Total Pages
14
Linux-Friendly Pages
31
Pages with Bias
68.9%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
234 issues found
Showing 226-234 of 234 flagged pages
Cloud Services Extended Support
Technical details and requirements for migrating to Azure Cloud Services (extended support)
...tended-support/in-place-migration-technical-details.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation consistently references PowerShell for migration operations and troubleshooting, with no mention of Linux/macOS equivalents or Azure CLI usage in procedural contexts. Windows tools (PowerShell) are presented as the primary or sole method for key tasks such as retrieving deployments, retrying stuck operations, and aborting/committing migrations. There are no explicit Linux/macOS command examples or guidance, and PowerShell is mentioned before REST API or other cross-platform options.
Recommendations
- Add Azure CLI examples alongside PowerShell for all operations, especially for aborting, committing, and retrieving deployments.
- Explicitly mention that REST API and Azure CLI are cross-platform and provide sample commands for Linux/macOS users.
- Where PowerShell is referenced, provide equivalent Azure CLI syntax and links to relevant CLI documentation.
- Clarify that migration tasks can be performed from any OS using Azure CLI or REST API, not just Windows/PowerShell.
- Consider reordering examples so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. Deployment options and examples prioritize Windows-centric tools such as PowerShell and Visual Studio, both in the main text and in the 'Next steps' section. Linux-native tools (such as Azure CLI or Bash scripting) are not mentioned, and PowerShell is listed before more platform-neutral options like ARM templates and the Azure portal. This may create friction for Linux/macOS users seeking parity in deployment and management workflows.
Recommendations
- Add explicit references and examples for Azure CLI and Bash scripting for deployment and migration tasks.
- Ensure that platform-neutral options (ARM templates, Azure portal) are listed before Windows-specific tools in all lists and instructions.
- Include Visual Studio Code as an alternative to Visual Studio for cross-platform development.
- Provide links to Linux/macOS specific guidance or troubleshooting where relevant.
Cloud Services Extended Support
Azure Cloud Services (extended support) post-migration changes
...ud-services-extended-support/post-migration-changes.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is frequently referenced as the primary or sole command-line tool for managing and retrieving deployment files (.csdef, .cscfg), with no mention of Linux/macOS equivalents (such as Azure CLI or Bash scripting) for these tasks. Examples and links for PowerShell are provided before CLI or REST API alternatives, and some operations (like updating certificates or deployment files) only mention PowerShell and REST API, omitting CLI or cross-platform tooling. Visual Studio is referenced for update workflows, which is predominantly a Windows tool, with no alternatives for Linux/macOS users. There are no explicit Linux/macOS examples or guidance for users on those platforms.
Recommendations
- Add Azure CLI examples and links for all operations currently described with PowerShell, especially for retrieving .csdef and .cscfg files.
- Explicitly mention cross-platform alternatives to Visual Studio (such as VS Code or command-line deployment tools) for update workflows.
- Where PowerShell is referenced, clarify that Azure CLI and REST API are also supported and provide parity in instructions.
- Include sample commands for Linux/macOS environments, and note any platform-specific caveats.
- Reorder examples so that cross-platform tools (CLI, REST API) are presented before or alongside Windows-specific tools.
Cloud Services Extended Support
Available States for Azure Cloud Services (extended support)
...ain/articles/cloud-services-extended-support/states.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page lists deployment options for Azure Cloud Services (extended support) with a notable emphasis on Windows-centric tools and workflows. PowerShell and Visual Studio, both primarily Windows tools, are mentioned explicitly as deployment methods, while Linux-native options (such as Azure CLI or Bash scripting) are absent. The ordering of deployment methods also places Windows tools before more cross-platform options like ARM templates.
Recommendations
- Add explicit instructions and examples for deploying Cloud Services (extended support) using Azure CLI and Bash, which are cross-platform and widely used on Linux/macOS.
- Reorder deployment options to present cross-platform methods (Azure portal, Azure CLI, ARM templates) before Windows-specific tools (PowerShell, Visual Studio).
- Include a note clarifying which deployment methods are available on Linux/macOS and provide links to relevant documentation.
- Where PowerShell is referenced, also provide equivalent Azure CLI commands for parity.
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
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page primarily focuses on using the Azure portal for monitoring, 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 Linux-specific examples or references to Linux tools for deployment or monitoring.
Recommendations
- Include Azure CLI examples for deployment and monitoring, as Azure CLI is cross-platform and widely used on Linux.
- Mention Bash scripting or other Linux-native tools where relevant, especially in the 'Next steps' section.
- Provide parity in examples and instructions for both Windows and Linux users, ensuring that Linux options are listed alongside or before Windows-centric tools.
- Clarify that PowerShell Core is available cross-platform, if referencing PowerShell, and provide instructions for both Windows and Linux environments.
Cloud Services Extended Support
Configure scaling for Azure Cloud Services (extended support)
...s/cloud-services-extended-support/configure-scaling.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates minor Windows bias by referencing Windows-centric tools and patterns before their Linux equivalents. Specifically, the 'Next steps' section lists PowerShell and Visual Studio (both Windows-focused) as deployment options before mentioning templates, and the referenced Azure Queue Storage quickstart link defaults to Windows environment variables and sign-in instructions. No Linux/macOS-specific examples or parity notes are provided.
Recommendations
- Explicitly mention and link to Linux/macOS deployment guides (e.g., Azure CLI, Bash, or cross-platform tools) alongside PowerShell and Visual Studio.
- Ensure referenced quickstart links include Linux/macOS tabs or examples, or clarify cross-platform applicability.
- Add notes or examples for configuring scaling using Azure CLI or REST API, which are platform-agnostic.
- Order deployment options in a neutral or alternating fashion, rather than listing Windows tools first.
Cloud Services Extended Support
Enable Monitoring in Cloud Services (extended support) using the Azure portal
...icles/cloud-services-extended-support/enable-alerts.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation 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 are mentioned before any Linux-native equivalents (such as Azure CLI or Bash scripting). No Linux/macOS-specific tools or examples are provided.
Recommendations
- Include Azure CLI as a deployment option alongside PowerShell, with links to equivalent documentation.
- Mention cross-platform editors (e.g., VS Code) in addition to Visual Studio.
- Ensure that examples and instructions are not limited to Windows-only tools and that Linux/macOS users are given equal consideration.
Cloud Services Extended Support
Configure scaling for Azure Cloud Services (extended support)
...s/cloud-services-extended-support/configure-scaling.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates mild Windows bias. In the 'Next steps' section, deployment options are listed as Azure portal, PowerShell, Template, and Visual Studio, with PowerShell and Visual Studio (both Windows-centric tools) mentioned before any Linux-friendly CLI or SDK options. The referenced Azure Queue Storage quickstart uses a link with 'environment-variable-windows' in its tab, suggesting Windows-first guidance. There are no explicit Linux/macOS examples or CLI instructions for scaling, and Visual Studio is only available on Windows.
Recommendations
- Add Azure CLI deployment instructions and examples, as CLI is cross-platform.
- Include Linux/macOS-specific environment variable guidance in referenced links.
- Mention cross-platform tools (e.g., Azure CLI, VS Code) before or alongside Windows-only tools like PowerShell and Visual Studio.
- Ensure referenced quickstarts and tutorials provide parity for Linux/macOS users.
Cloud Services Extended Support
Azure Cloud Services (extended support) Def. WorkerRole Schema | Microsoft Docs
...d-services-extended-support/schema-csdef-workerrole.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page for Azure Cloud Services (extended support) WorkerRole schema exhibits mild Windows bias. It references Windows-centric concepts such as certificate stores (CurrentUser, LocalMachine, My, Root, etc.), environment variables using Windows-style notation (%ROLEROOT%), and startup tasks referencing CMD/batch files and ANSI encoding. There are no explicit Linux/macOS examples or mentions of equivalent patterns, and Windows terminology is used throughout. However, the page is primarily schema-focused and does not include platform-specific command-line examples.
Recommendations
- Add explicit notes or examples for Linux/macOS users, such as how certificate storage and environment variables are handled on those platforms.
- Clarify whether startup tasks can use shell scripts (.sh) and provide guidance on file encoding for non-Windows scripts.
- Document cross-platform considerations for paths, environment variables, and startup scripts.
- Where Windows-specific terminology is used (e.g., certificate stores, CMD files), mention Linux/macOS equivalents or limitations.