Spring Apps
268
Total Pages
247
Linux-Friendly Pages
21
Pages with Bias
7.8%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
48 issues found
Showing 26-48 of 48 flagged pages
Spring Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/spring-apps/basic-standard/includes/quickstart-deploy-web-app/prepare-cloud-environment-azure-portal.md
...ploy-web-app/prepare-cloud-environment-azure-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation focuses exclusively on the Azure Portal web interface for resource deployment, without mentioning or providing examples for command-line alternatives such as Azure CLI or Bash scripts, which are commonly used on Linux. There are no references to Linux-specific tools, patterns, or workflows, and no parity examples for Linux users. The instructions and screenshots assume a graphical interface typical of Windows environments, potentially disadvantaging users on Linux or those preferring CLI automation.
Recommendations
- Add equivalent instructions for deploying resources using Azure CLI and Bash scripts, which are platform-agnostic and widely used on Linux.
- Include examples for both Windows (PowerShell) and Linux (Bash) command-line workflows for resource creation and management.
- Mention cross-platform tools (e.g., Azure CLI, Terraform) and provide links or references to their documentation.
- Clarify that the Azure Portal is accessible from any OS with a web browser, but highlight automation and scripting options for Linux users.
- Provide screenshots or terminal output examples from Linux environments to improve inclusivity.
Create Pull Request
Spring Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/spring-apps/basic-standard/includes/quickstart-deploy-web-app/web-prepare-cloud-environment-enterprise-azure-portal.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/spring-apps/basic-standard/includes/quickstart-deploy-web-app/web-prepare-cloud-environment-enterprise-azure-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation focuses exclusively on using the Azure Portal web interface for deployment, which is platform-agnostic but implicitly assumes a GUI workflow common to Windows users. There are no command-line examples (such as Azure CLI or Bash scripts) that would be more familiar to Linux users, nor are there references to Linux-specific tools or workflows. The absence of Linux-oriented instructions or parity in automation options suggests a Windows-first bias.
Recommendations
- Add Azure CLI and Bash script examples for resource deployment, showing how to perform the same steps from a Linux shell.
- Include instructions for deploying via ARM templates using command-line tools, not just the portal button.
- Mention cross-platform tools (e.g., Azure CLI, Terraform) and provide examples for both Windows (PowerShell) and Linux (Bash).
- Clarify that the Azure Portal is accessible from any OS and highlight alternative workflows for users who prefer command-line interfaces.
Spring Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/spring-apps/basic-standard/includes/quickstart/clean-up-resources-via-resource-group.md
...es/quickstart/clean-up-resources-via-resource-group.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation instructs users to use the Azure portal (a web-based GUI) to delete a resource group, which is a method commonly associated with Windows workflows. There are no examples or instructions for performing the same task using command-line tools such as Azure CLI or PowerShell, which would be more platform-agnostic and accessible to Linux users.
Recommendations
- Add instructions for deleting a resource group using Azure CLI, which works on both Windows and Linux.
- Provide PowerShell examples as an alternative, but ensure CLI examples are given equal or higher prominence.
- Explicitly mention that the Azure portal is accessible from any OS, but supplement with command-line options for users who prefer or require them.
Spring Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/spring-apps/enterprise/how-to-set-up-sso-with-azure-ad.md
...ing-apps/enterprise/how-to-set-up-sso-with-azure-ad.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows/Azure portal-centric approach, with all instructions and UI navigation steps tailored to the Azure portal interface. There are no command-line examples (neither PowerShell nor CLI), but also no Linux-specific or cross-platform instructions. The documentation assumes use of the Azure portal, which is platform-agnostic in theory, but in practice, this approach often aligns with Windows-centric workflows and omits Linux CLI or automation alternatives.
Recommendations
- Provide Azure CLI examples for all steps that can be performed via command line (e.g., app registration, adding redirect URIs, creating client secrets), ensuring parity for users on Linux, macOS, and Windows.
- Include references to automation or scripting options (such as Azure CLI or REST API) alongside portal instructions.
- Explicitly mention that all steps can be performed on any OS using the Azure portal, but highlight CLI alternatives for users who prefer or require non-GUI workflows.
- Add a section or callout for Linux users, pointing to relevant CLI documentation or scripts.
Spring Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/spring-apps/enterprise/quickstart-configure-single-sign-on-enterprise.md
...rise/quickstart-configure-single-sign-on-enterprise.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently provides command-line examples using Azure CLI and bash-style syntax (e.g., export, $(...), jq), which are compatible with Linux/macOS and Windows with WSL or Git Bash. However, there are no explicit examples or notes for Windows users using native Command Prompt or PowerShell, nor are there instructions for installing required tools (like jq) on Windows. The documentation implicitly assumes a Unix-like shell environment, which may disadvantage Windows users who do not use WSL or similar tools.
Recommendations
- Add explicit notes or sections for Windows users, clarifying how to run the commands in PowerShell or Command Prompt, or recommend using WSL or Git Bash.
- Provide Windows-native equivalents for commands that use Unix utilities (e.g., using jq, export, $(...), and piping). For example, show how to set environment variables and parse JSON in PowerShell.
- Include installation instructions for required tools (like jq and Azure CLI) specifically for Windows, with links to Windows installers.
- Where possible, provide both bash and PowerShell command examples side-by-side, or indicate which shell is required for each example.
- Add a 'Platform compatibility' note in the prerequisites, clarifying the expected shell environment and alternatives for Windows users.
Spring Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/spring-apps/enterprise/how-to-use-dev-tool-portal.md
...s/spring-apps/enterprise/how-to-use-dev-tool-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation presents configuration steps and CLI examples only in the context of the Azure portal and Azure CLI, without specifying or demonstrating any OS-specific commands. However, there is an implicit Windows bias: the Azure CLI installation and usage instructions do not mention Linux or macOS environments, nor do they provide any shell-specific guidance (e.g., Bash vs. PowerShell). There are no Linux-specific examples, troubleshooting tips, or references to Linux tools or shell environments, which may leave Linux users without clear guidance.
Recommendations
- Explicitly mention that Azure CLI commands are cross-platform and provide links or instructions for installing and using Azure CLI on Linux and macOS.
- Include example commands using both Bash (for Linux/macOS) and PowerShell (for Windows), or clarify that the given commands work in all supported shells.
- Add troubleshooting tips or notes for common issues on Linux (e.g., permissions, environment variables, dependency installation).
- Where UI navigation is described, clarify that the Azure portal is web-based and OS-agnostic.
- Consider adding a section or callout for Linux/macOS users to ensure parity and inclusivity.
Spring Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/spring-apps/basic-standard/how-to-custom-domain.md
...les/spring-apps/basic-standard/how-to-custom-domain.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is largely cross-platform, using Azure CLI and OpenSSL for most examples, which are platform-agnostic or Linux-friendly. However, there is a subtle Windows bias in the 'Export certificate to PFX' section, where Windows tools (IIS, Certreq.exe) are mentioned as alternatives to OpenSSL, and the export process for Windows is referenced with a link to a Windows Server-specific guide. The Windows tools are mentioned after OpenSSL, but no explicit Linux-only tools or workflows are described. There are no PowerShell-specific examples, but the documentation assumes familiarity with Windows certificate management tools for users who did not use OpenSSL.
Recommendations
- Provide explicit Linux workflows for certificate export, such as using OpenSSL or other Linux-native tools, and clarify that OpenSSL commands work on both Linux and Windows.
- When referencing Windows-specific tools (IIS, Certreq.exe), provide equivalent Linux guidance or links for users who generated certificates on Linux systems.
- Consider adding a note or section that highlights cross-platform compatibility, and explicitly mention that all Azure CLI and OpenSSL commands work on Linux, macOS, and Windows.
- If mentioning Windows tools, ensure Linux alternatives are mentioned with equal prominence and detail.
Spring Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/spring-apps/basic-standard/how-to-staging-environment.md
...ring-apps/basic-standard/how-to-staging-environment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently uses Windows-style path separators (e.g., target\hellospring-0.0.1-SNAPSHOT.jar) in CLI commands and does not provide Linux/macOS equivalents. There are no explicit Linux or macOS instructions or examples, and the only file paths shown are Windows-specific. This may cause confusion or errors for users on non-Windows platforms.
Recommendations
- Provide both Windows and Linux/macOS command examples, especially for file paths (e.g., use both target\hellospring-0.0.1-SNAPSHOT.jar and target/hellospring-0.0.1-SNAPSHOT.jar).
- Add a note clarifying that path separators differ between Windows (\) and Linux/macOS (/), and users should adjust accordingly.
- Where possible, use environment-agnostic commands or variables, or show cross-platform alternatives using tabbed code blocks.
- Explicitly mention that all CLI commands work on Linux/macOS as well as Windows, and reference any platform-specific prerequisites if needed.
Spring Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/spring-apps/basic-standard/includes/application-observability/clean-up-resources.md
...cludes/application-observability/clean-up-resources.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively describes how to delete resources using the Azure Portal, a graphical interface commonly associated with Windows environments. There are no examples or instructions for performing the same task using command-line tools (such as Azure CLI or Azure PowerShell), which are frequently used in Linux or cross-platform environments.
Recommendations
- Add instructions for deleting the resource group using Azure CLI (az group delete), which is cross-platform and widely used in Linux environments.
- If relevant, include Azure PowerShell examples, but ensure they are presented alongside CLI examples and not as the sole command-line option.
- Clearly indicate that the Azure Portal is accessible from any OS, but supplement with command-line instructions for users who prefer or require non-GUI workflows.
Spring Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/spring-apps/basic-standard/includes/quickstart-deploy-event-driven-app/validate-event-driven-app.md
...t-deploy-event-driven-app/validate-event-driven-app.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively references Service Bus Explorer, a tool that is only available for Windows, without mentioning or providing alternatives for Linux users. There are no examples or instructions for performing the same tasks on Linux, such as using cross-platform CLI tools or SDKs.
Recommendations
- Include instructions for sending and peeking messages using Azure CLI or Azure PowerShell, both of which are cross-platform.
- Mention and provide examples for using the Azure portal, which is accessible from any OS.
- Reference SDK-based approaches (e.g., using Python, Java, or Node.js) for interacting with Service Bus queues, with code samples.
- Explicitly state the platform limitations of Service Bus Explorer and suggest alternatives for Linux/macOS users.
Spring Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/spring-apps/basic-standard/includes/quickstart/clean-up-resources-via-resource-group.md
...es/quickstart/clean-up-resources-via-resource-group.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation instructs users to delete resources via the Azure portal, which is a graphical tool commonly associated with Windows environments. There are no command-line examples provided for Linux users (such as using Azure CLI or Bash scripts), nor is there mention of alternative methods suitable for non-Windows platforms.
Recommendations
- Add command-line instructions using Azure CLI (az group delete ...) that work cross-platform (Windows, Linux, macOS).
- Explicitly mention that the Azure portal is web-based and accessible from any OS, to avoid the impression of Windows exclusivity.
- Provide both GUI and CLI examples side by side to ensure parity for users on all platforms.
Spring Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/spring-apps/enterprise/how-to-set-up-sso-with-azure-ad.md
...ing-apps/enterprise/how-to-set-up-sso-with-azure-ad.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows/Azure portal bias by exclusively referencing the Azure portal GUI for configuration steps, with no mention of command-line alternatives (such as Azure CLI, PowerShell, or Bash scripts) that would be relevant for Linux users. All instructions assume use of the graphical Azure portal, which is more commonly used on Windows, and there are no examples or guidance for performing these tasks from a Linux environment or via cross-platform tools.
Recommendations
- Add equivalent instructions using Azure CLI commands for all configuration steps (e.g., app registration, client secret creation, redirect URI management), as Azure CLI is cross-platform and widely used on Linux.
- Provide sample scripts or command-line snippets for Linux users to automate or perform the same tasks without relying on the Azure portal GUI.
- Explicitly mention that all steps can be performed via the Azure CLI or REST API, and link to relevant documentation.
- Where screenshots are provided, consider including CLI output or terminal screenshots to illustrate parity.
- Review the documentation to ensure that Linux users are not required to use Windows-specific tools or interfaces, and that all steps are accessible from any OS.
Spring Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/spring-apps/enterprise/how-to-use-dev-tool-portal.md
...s/spring-apps/enterprise/how-to-use-dev-tool-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by exclusively providing instructions and examples using the Azure portal (web UI) and Azure CLI, without mentioning or providing examples for Linux-specific environments, shell differences, or alternative tools. There is no explicit mention of PowerShell, but the lack of Linux/macOS-specific notes or examples (such as bash-specific syntax, environment variable handling, or troubleshooting) may hinder Linux users. The Azure CLI is cross-platform, but the documentation does not clarify this or address potential differences in usage between Windows and Linux.
Recommendations
- Explicitly state that the Azure CLI commands work on Windows, Linux, and macOS, and provide any necessary notes about differences (e.g., line continuation characters, quoting).
- Include example commands using bash/zsh syntax where relevant, especially if there are differences in environment variable usage or command formatting.
- Add troubleshooting tips or notes for Linux/macOS users, such as permissions, path issues, or package manager installation steps for Azure CLI.
- If referencing the Azure portal, clarify that it is web-based and platform-independent.
- Consider adding a section or callout for Linux/macOS users to ensure parity and inclusivity.
Spring Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/spring-apps/enterprise/includes/tutorial-authenticate-client-with-gateway/clean-up-resources.md
...authenticate-client-with-gateway/clean-up-resources.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides instructions exclusively for deleting resources via the Azure Portal, which is a graphical interface commonly associated with Windows workflows. There are no command-line examples (such as Azure CLI or PowerShell), and no Linux-specific instructions or parity with non-Windows environments.
Recommendations
- Add Azure CLI examples for deleting a resource group, which work cross-platform (Windows, Linux, macOS).
- If mentioning PowerShell, also provide Bash equivalents.
- Explicitly state that the Azure Portal is platform-agnostic, but supplement with command-line instructions for users who prefer or require terminal-based workflows.
- Include a section or note for Linux/macOS users to ensure parity and inclusivity.
Spring Apps
Map an Existing Custom Domain to Azure Spring Apps
...les/spring-apps/basic-standard/how-to-custom-domain.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is generally cross-platform, using Azure portal and Azure CLI examples throughout. However, in the section on exporting certificates to PFX, Windows-specific tools (IIS, Certreq.exe) are mentioned before Linux alternatives, and the link provided for exporting certificates is to a Windows Server documentation page. The OpenSSL example is present, but Windows tooling is referenced first and more prominently.
Recommendations
- Provide explicit Linux/macOS instructions for exporting certificates to PFX, such as using OpenSSL, before or alongside Windows tools.
- Include links to Linux/macOS documentation for certificate export, not just Windows Server guides.
- Clarify that both Windows and Linux/macOS users can use OpenSSL for certificate management, and highlight cross-platform approaches first.
- If mentioning Windows tools, balance with equivalent Linux/macOS commands or references.
Spring Apps
Quickstart - Provision Azure Spring Apps Using an Azure Resource Manager Template (ARM Template)
...asic-standard/quickstart-deploy-infrastructure-vnet.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for resource group deletion, but PowerShell is presented as a primary tab alongside CLI, and no Linux/macOS-specific shell examples (e.g., Bash) are given. The instructions and examples do not mention Linux/macOS tooling or shell patterns, and PowerShell is featured equally with CLI, which may create mild friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
- Add explicit Bash examples for resource group deletion, or clarify that Azure CLI commands work natively in Bash on Linux/macOS.
- Note that PowerShell examples are primarily for Windows users, and Linux/macOS users should use Azure CLI in their preferred shell.
- Consider listing Azure CLI (which is cross-platform) before PowerShell in example tabs to emphasize Linux/macOS parity.
- Add a brief note in the prerequisites or cleanup section indicating that all steps are cross-platform except PowerShell, which is Windows-focused.
Spring Apps
Map an Existing Custom Domain to Azure Spring Apps
...les/spring-apps/basic-standard/how-to-custom-domain.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is generally cross-platform, focusing on Azure portal and Azure CLI workflows, which are available on Windows, Linux, and macOS. However, there is a notable Windows bias in the certificate export section: Windows tools (IIS, Certreq.exe) are mentioned as alternatives to OpenSSL, and the export instructions link to a Windows Server documentation page. The Windows tools are mentioned after OpenSSL, but no Linux/macOS-specific GUI alternatives are referenced. All CLI examples use Azure CLI, which is cross-platform.
Recommendations
- Add explicit instructions or links for exporting certificates to PFX format on Linux and macOS, such as using OpenSSL GUI tools or command line.
- When referencing Windows tools like IIS or Certreq.exe, provide equivalent Linux/macOS methods (e.g., using OpenSSL or graphical certificate managers).
- Include links to Linux/macOS documentation for certificate management, not just Windows Server pages.
- Clarify that Azure CLI commands work on all platforms and, where relevant, note any platform-specific considerations.
Spring Apps
Quickstart - Provision Azure Spring Apps Using Bicep
...tandard/quickstart-deploy-infrastructure-vnet-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation does not show explicit Windows bias in terms of using Windows-specific tools or PowerShell. All command-line examples use Azure CLI in Bash syntax, which is cross-platform. However, there is a subtle 'windows_first' bias: the documentation refers to 'Azure CLI or Azure PowerShell' for reviewing resources, but only provides Azure CLI (Bash) examples, with no PowerShell or Linux-specific alternatives. The instructions assume Bash is available, which may not be the default on Windows, and do not mention how to run these commands on Windows (e.g., using Command Prompt, PowerShell, or Windows Subsystem for Linux). There are no examples or notes for macOS users.
Recommendations
- Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and provide guidance for running Bash commands on Windows (e.g., via WSL, Git Bash, or Azure Cloud Shell).
- Add PowerShell examples for users who prefer PowerShell on Windows.
- Include notes or examples for macOS and Linux users, confirming that the instructions are valid for their platforms.
- Clarify any platform-specific prerequisites, such as installing Bash or Azure CLI on Windows.
Spring Apps
Quickstart - Provision Azure Spring Apps Using an Azure Resource Manager Template (ARM Template)
...asic-standard/quickstart-deploy-infrastructure-vnet.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for resource cleanup, but PowerShell (a Windows-centric tool) is given equal prominence and is presented immediately after the CLI example. There are no Linux/macOS-specific instructions or examples, and the documentation does not mention shell environments or considerations for non-Windows users. The overall flow assumes users are comfortable with either CLI or PowerShell, but does not clarify cross-platform compatibility or provide parity guidance.
Recommendations
- Explicitly state that Azure CLI is cross-platform and works on Windows, Linux, and macOS.
- Present Azure CLI examples first, as it is the most universally supported tool.
- Add notes or links for installing and using Azure CLI on Linux/macOS.
- Clarify that PowerShell examples are primarily for Windows users, and provide Bash examples for Linux/macOS where relevant.
- Avoid implying PowerShell is required for resource management tasks.
Spring Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/spring-apps/migration/migrate-enterprise-application-configuration-service.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/spring-apps/migration/migrate-enterprise-application-configuration-service.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display overt Windows bias in the form of Windows-specific commands, PowerShell usage, or Windows-first ordering. However, it lacks any explicit Linux or cross-platform shell examples, and does not mention OS-specific considerations. All command-line instructions are given using the Azure CLI, which is cross-platform, but there are no examples or notes about running these commands in Linux/macOS shells, nor are there any references to Linux-specific tools or environments.
Recommendations
- Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and provide any necessary notes about shell differences (e.g., line continuation syntax).
- Add example commands or screenshots from a Linux terminal to demonstrate parity.
- If there are any OS-specific prerequisites or behaviors (such as file path formats or authentication methods), document these for both Windows and Linux.
- Where screenshots are used, consider including at least one from a Linux environment.
- If referencing local development or testing, mention both Windows and Linux environments to ensure inclusivity.
Spring Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/spring-apps/migration/migrate-application-live-view.md
...spring-apps/migration/migrate-application-live-view.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display explicit Windows bias (such as PowerShell or Windows-only tools), but it also does not provide any OS-specific examples or instructions. All command-line examples use Azure CLI and bash-style commands, which are cross-platform but may be more familiar to Linux/macOS users. There are no references to Windows-specific tools, PowerShell, or Windows-first patterns. However, there is a lack of explicit Linux parity guidance or troubleshooting for Linux environments, and no mention of OS-specific considerations.
Recommendations
- Explicitly state that the Azure CLI and bash commands work on Linux, macOS, and Windows (with WSL or Azure CLI for Windows).
- If there are any OS-specific considerations (such as file path formats, environment variable syntax, or CLI installation steps), provide guidance for both Windows and Linux users.
- Add a note or section on how to run the Azure CLI commands in PowerShell or Command Prompt for Windows users, if relevant.
- Include troubleshooting tips for common issues that may differ between Linux and Windows environments (e.g., file permissions, line endings, etc.).
- Ensure that any screenshots or UI references are not Windows-centric and clarify if the experience differs on other platforms.
Spring Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/spring-apps/basic-standard/how-to-intellij-deploy-apps.md
...ing-apps/basic-standard/how-to-intellij-deploy-apps.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a subtle Windows bias by linking to the Windows section of the IntelliJ IDEA download page in the prerequisites, and by using backslashes (\) in folder paths (e.g., gs-spring-boot\complete), which is the Windows convention. There are no explicit Linux or macOS instructions, nor are there alternative path notations or download links for other platforms. However, the tutorial itself is largely platform-agnostic beyond these points.
Recommendations
- Update the IntelliJ IDEA download link to point to the general download page or provide links for Windows, Linux, and macOS.
- Use platform-neutral path separators (e.g., gs-spring-boot/complete) or provide both Windows (\) and Unix-style (/) path examples.
- Add a note clarifying that the instructions apply to all supported operating systems, and mention any OS-specific differences if relevant.
- If screenshots differ significantly across platforms, consider providing representative images for each major OS.
Spring Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/spring-apps/enterprise/quickstart-configure-single-sign-on-enterprise.md
...rise/quickstart-configure-single-sign-on-enterprise.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only Azure CLI and bash-style shell command examples, which are cross-platform but assumes a Unix-like (Linux/macOS) environment. There are no explicit Windows or PowerShell examples, nor any mention of Windows-specific tools or patterns. However, there is a lack of explicit guidance or examples for Windows users, especially those using PowerShell or Command Prompt, which may create friction for Windows-centric audiences.
Recommendations
- Add notes clarifying that the provided commands are intended for Unix-like shells (e.g., bash, zsh, WSL) and may not work as-is in Windows Command Prompt or PowerShell.
- Where environment variables and command syntax differ (e.g., 'export' vs. '$env:'), provide equivalent PowerShell/Windows Command Prompt examples or a link to a section on running Azure CLI in Windows environments.
- Explicitly mention that tools like jq may require additional installation steps on Windows, and provide installation instructions or alternatives for Windows users.
- Consider including a short section or callout box for Windows users, explaining how to adapt the examples or recommending the use of Windows Subsystem for Linux (WSL) if appropriate.