Communication Services
1044
Total Pages
900
Linux-Friendly Pages
144
Pages with Bias
13.8%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
656 issues found
Showing 526-550 of 656 flagged pages
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/events/includes/create-event-subscription-net.md
...tarts/events/includes/create-event-subscription-net.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on .NET and C# usage, which is most commonly associated with Windows development environments. There are no explicit Linux or cross-platform command-line examples, nor are there any references to Linux-specific tooling or shell usage. The installation and authentication steps assume a Windows-centric workflow (e.g., NuGet and dotnet CLI), and there is no mention of Linux or macOS environments, package managers, or shell commands. All code samples are in C#, and there is no guidance for users on Linux or alternative platforms.
Recommendations
- Explicitly mention that the .NET SDK and tools are cross-platform and provide installation instructions for Linux and macOS, including links to official documentation for those platforms.
- Include example shell commands for Linux/macOS (e.g., using bash/zsh) alongside Windows/PowerShell equivalents where relevant.
- Reference Linux package managers (such as apt, yum, or Homebrew for macOS) for installing prerequisites where appropriate.
- Clarify that the dotnet CLI and NuGet are available on all major platforms, and provide troubleshooting tips for common Linux/macOS issues.
- Consider including code samples or notes for other supported languages/platforms (such as Python, Java, or JavaScript) if the SDK is available, or at least acknowledge their existence and link to relevant documentation.
Create Pull Request
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/telephony/includes/phone-numbers-az-cli.md
...quickstarts/telephony/includes/phone-numbers-az-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows mild Windows bias by listing Windows-specific instructions and links before Linux/macOS equivalents. The Azure CLI installation link points only to the Windows installation page, and the environment variable section lists Windows instructions first, with Linux and macOS following. There is no direct Linux-specific Azure CLI installation link, and the Linux environment variable instructions assume the use of .bash_profile, which is not universal.
Recommendations
- Provide platform-agnostic or parallel links for Azure CLI installation (e.g., include links for Windows, Linux, and macOS).
- Present environment variable instructions in a more balanced order, such as using tabs or listing Linux/macOS first in some cases.
- Clarify that .bash_profile may not exist on all Linux distributions and suggest alternatives (e.g., .bashrc, .profile).
- Ensure all examples and instructions are equally detailed for all platforms.
- Consider using a platform selection tab for all setup steps, not just for environment variables.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/tpe/teams-phone-extensibility-access-teams-phone.md
...ts/tpe/teams-phone-extensibility-access-teams-phone.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation exhibits a mild Windows bias by describing user enablement for Teams exclusively through the Microsoft 365 admin center UI, which is a web-based tool but often associated with Windows-centric workflows. It also references the MicrosoftTeams PowerShell cmdlet (Get-CsOnlineApplicationInstance) as a method to retrieve the Resource Account ObjectId, without mentioning equivalent CLI or scripting options for Linux or cross-platform environments. No Linux-specific tools, shell commands, or alternative workflows are provided, and the only administrative tool mentioned is PowerShell.
Recommendations
- Provide equivalent instructions for enabling Teams users using cross-platform tools such as Azure CLI or Microsoft Graph API, which can be run on Linux, macOS, and Windows.
- When referencing PowerShell cmdlets, also include REST API or CLI alternatives for retrieving necessary identifiers (such as the Resource Account ObjectId) to ensure Linux users are not excluded.
- Explicitly state that all API calls can be made using any REST client (e.g., curl, Postman) and provide example commands for these tools.
- Where possible, avoid assuming the use of Windows-specific administrative tools, or at least present them alongside cross-platform options.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-user/teams-user-ios.md
...ce-video-calling/includes/teams-user/teams-user-ios.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a subtle Windows bias by referencing Windows-specific tools and patterns, such as requiring Teams users to be 'Enterprise Voice enabled' via a PowerShell-based process, and linking to Microsoft documentation that is primarily Windows-focused. No Linux or cross-platform alternatives are mentioned for these administrative steps.
Recommendations
- Provide Linux/macOS alternatives or clarify if the administrative steps (such as enabling Enterprise Voice) can be performed using cross-platform tools or web interfaces.
- Include links to platform-agnostic documentation or explicitly state if certain steps are Windows-only.
- If PowerShell is required, mention if PowerShell Core (which is cross-platform) can be used, and provide example commands for Linux/macOS environments where possible.
- Ensure that all prerequisite steps are accessible to users on non-Windows platforms, or provide guidance/workarounds if not.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-call-queue/teams-call-queue-javascript.md
...cludes/teams-call-queue/teams-call-queue-javascript.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by referencing the Teams Admin Center (a web-based tool but often associated with Windows environments) and providing resource creation links that default to Windows pivots. There are no explicit Linux-specific instructions or examples, and no mention of Linux terminal or shell environments. All setup and run instructions are generic but lack Linux parity checks or clarifications.
Recommendations
- Ensure that resource creation links and instructions are not Windows-specific; provide Linux and macOS pivots or clarify that the steps are cross-platform.
- Explicitly mention that all terminal commands (e.g., mkdir, npm install, npx webpack serve) work on Linux, macOS, and Windows, and note any OS-specific differences if applicable.
- Add a section or notes for Linux/macOS users, including any prerequisites (e.g., package managers, permissions) and troubleshooting tips.
- Avoid defaulting to Windows pivots in links; provide a neutral or multi-platform default.
- If screenshots or UI references are included, clarify if they look different on non-Windows platforms or in different browsers.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/trusted-service-js.md
...tion-services/tutorials/includes/trusted-service-js.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently references Visual Studio Code and Azure Functions tooling without specifying or demonstrating Linux-specific workflows. All instructions and links are oriented around Visual Studio Code, which, while cross-platform, is often associated with Windows, and there is no mention of Linux terminal usage, alternative editors, or command-line deployment methods. There are no explicit Linux or macOS examples, and the documentation assumes the use of GUI tools and workflows that may be less common on Linux.
Recommendations
- Include explicit instructions for Linux users, such as using the Azure Functions Core Tools CLI for function creation, local testing, and deployment.
- Provide terminal-based examples for common tasks (e.g., running, deploying, and testing the function) using bash or zsh.
- Mention and link to Linux-specific prerequisites, such as package installation commands for Node.js and Azure Functions Core Tools on Ubuntu or other distributions.
- Clarify that Visual Studio Code is cross-platform, and provide any Linux-specific caveats or setup steps.
- Offer alternative instructions for users who prefer not to use Visual Studio Code, such as using vim, nano, or other editors common on Linux.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/call-automation-ai-csharp.md
...services/samples/includes/call-automation-ai-csharp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tabs in prerequisite links (e.g., '?tabs=windows'), and does not provide explicit Linux/macOS instructions or examples for setup and execution. All instructions are generic but implicitly assume a Windows environment, especially given the .NET/C# sample and lack of cross-platform notes.
Recommendations
- Provide explicit Linux/macOS instructions or notes where setup or tooling may differ (e.g., for .NET, DevTunnels CLI).
- Ensure prerequisite links include Linux/macOS tabs or clarify cross-platform compatibility.
- Mention that the sample can be run on Linux/macOS if applicable, and provide any additional steps required.
- Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, port binding).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/call-automation-azure-openai-csharp.md
...amples/includes/call-automation-azure-openai-csharp.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page exhibits a mild Windows bias. The prerequisites link to a resource creation guide with a 'tabs=windows' parameter, suggesting a Windows-first approach. There are no explicit Linux-specific instructions or examples, and the sample project is .NET-based, which is cross-platform but often associated with Windows. No PowerShell or Windows-only command-line tools are shown, but there is also a lack of explicit Linux/macOS parity in instructions or troubleshooting.
Recommendations
- Update prerequisite links to use platform-neutral or multi-tab URLs (e.g., remove '?tabs=windows' or add Linux/macOS tabs).
- Explicitly mention that the sample can be run on Linux/macOS as well as Windows, and provide any necessary platform-specific notes.
- If there are any platform-specific steps (e.g., for dotnet or DevTunnels), provide Linux/macOS command-line examples or troubleshooting notes.
- Ensure all referenced quickstarts and guides have Linux/macOS parity and are linked appropriately.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/contact-center.md
...les/communication-services/tutorials/contact-center.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows-first bias, particularly in the quickstart and example links, which predominantly use 'windows' or 'uwp' tabs and pivots. There are no explicit Linux or cross-platform command-line examples, nor are Linux tools or environments mentioned. This could make it harder for Linux developers to follow or feel included.
Recommendations
- Provide Linux-specific examples and instructions alongside Windows ones, especially in quickstart links and code samples.
- Use neutral, cross-platform language and tabs (such as 'web', 'nodejs', or 'dotnet') instead of defaulting to 'windows' or 'uwp'.
- Explicitly mention Linux compatibility and any required steps for Linux environments.
- Where platform-specific instructions are necessary, present Windows and Linux instructions in parallel.
- Audit linked quickstarts and tutorials to ensure Linux users are not excluded or forced to adapt Windows-centric instructions.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/twilio-to-acs-video-android-tutorial.md
...rials/includes/twilio-to-acs-video-android-tutorial.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias in the prerequisites section, where instructions for installing the Azure CLI are provided only for Windows, with no mention of Linux or macOS alternatives. The link to create a Communication Services Resource also uses a 'tabs=windows' parameter, further reinforcing the Windows-centric approach. No Linux-specific instructions or parity are provided, especially in the setup and tooling sections.
Recommendations
- Provide installation instructions and links for Azure CLI on Linux and macOS alongside Windows, or use a tabbed interface to allow users to select their OS.
- Remove or supplement 'tabs=windows' in resource creation links with Linux/macOS equivalents or a generic/default tab.
- Explicitly mention cross-platform compatibility in the prerequisites and setup sections.
- Wherever CLI or tooling is referenced, ensure that examples and links are not Windows-specific unless there is a technical reason.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/log-file-retrieval-tutorial.md
...tion-services/tutorials/log-file-retrieval-tutorial.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides platform-specific instructions for Android (Java), iOS (Swift), and Windows (C#), but omits any mention of Linux or cross-platform desktop environments. The Windows example is included as the only desktop OS, with no Linux equivalent or guidance for Linux users.
Recommendations
- Add a Linux-specific section or example for log file retrieval, especially for scenarios where the SDK or application may be run on Linux desktops.
- If the SDK does not support Linux, explicitly state this limitation to avoid confusion.
- Consider including cross-platform .NET Core examples if applicable, and clarify OS compatibility.
- Ensure parity in documentation by providing equivalent instructions for all major desktop operating systems (Windows, macOS, Linux) where possible.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/url-shortener-csharp.md
...on-services/tutorials/includes/url-shortener-csharp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is heavily oriented toward .NET and Azure Functions in C#, which are cross-platform, but the workflow and examples assume development in Visual Studio Code and do not mention Linux-specific tools or workflows. There are no explicit PowerShell or Windows-only commands, but the guidance and examples are implicitly Windows-centric (e.g., referencing pressing F5 in VS Code, using .NET, and not mentioning Linux shell equivalents or alternative editors). There are no Linux-specific instructions, troubleshooting, or environment setup details.
Recommendations
- Include explicit instructions for running and testing the Azure Function on Linux (e.g., using the Azure Functions Core Tools in a bash shell, or running in a Docker container).
- Provide alternative examples for installing dependencies (e.g., using apt-get or yum for required tools, or dotnet CLI commands in a Linux terminal).
- Mention and show how to use editors commonly used on Linux (such as Vim, Emacs, or JetBrains Rider) or clarify that Visual Studio Code is cross-platform.
- Add notes on environment variable configuration for Linux shells (e.g., export commands, .env files) instead of only referencing Windows environment variable patterns.
- Clarify that all steps can be performed on Linux and provide troubleshooting tips for common Linux-specific issues.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/twilio-to-acs-chat-ios-tutorial.md
.../tutorials/includes/twilio-to-acs-chat-ios-tutorial.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in the prerequisites section by linking only to Windows installation instructions for the Azure CLI and referencing resource creation steps with a Windows-specific tab. There are no Linux or macOS equivalents or links provided for these steps, which may hinder users on non-Windows platforms. However, the rest of the documentation is platform-neutral and focused on iOS development.
Recommendations
- Provide installation instructions or links for Azure CLI on Linux and macOS alongside the Windows link.
- Ensure that resource creation quickstarts and links use platform-neutral or multi-platform tabs, or explicitly mention Linux/macOS options.
- Review all prerequisite steps to ensure parity for Linux and macOS users, especially for command-line and setup instructions.
- Consider adding a note that the CLI and SDK steps are cross-platform, and provide troubleshooting tips or references for non-Windows environments.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation mentions Windows-specific console environments (cmd, PowerShell) before Bash, and all command-line examples use the generic 'dotnet' CLI without platform-specific guidance. There are no explicit Linux/macOS instructions or troubleshooting notes, and the sample code is exclusively in C#/.NET, which is cross-platform but often associated with Windows. No Windows-only tools are used, but the documentation does not provide Linux/macOS parity in terms of environment setup, package management, or example ordering.
Recommendations
- Explicitly mention Linux/macOS compatibility for .NET and the Azure SDK.
- Provide Linux/macOS-specific instructions for installing .NET Core and running dotnet commands (e.g., using apt, yum, brew).
- List Bash before or alongside cmd/PowerShell when referencing console environments.
- Include troubleshooting notes for common Linux/macOS issues (e.g., permissions, path differences).
- Clarify that all commands work on Linux/macOS and provide example outputs from those platforms.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows command-line tools (cmd, PowerShell) before Bash when describing how to run commands, but otherwise provides cross-platform instructions and examples. All commands use 'dotnet', which is available on Windows, Linux, and macOS. No Windows-only tools or PowerShell-specific examples are present, and Linux/macOS users can follow the instructions without issue.
Recommendations
- List Bash before Windows command-line tools (cmd, PowerShell) when describing cross-platform steps.
- Explicitly state that all commands work on Windows, Linux, and macOS.
- Consider adding a note or section confirming Linux/macOS compatibility for the setup and execution steps.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows terminals (Command Prompt, PowerShell) before Bash when instructing users to open a terminal. However, all command-line instructions use cross-platform .NET CLI commands and do not rely on Windows-specific tools or patterns. No PowerShell-specific examples or Windows-only tools are present, and Linux/macOS users can follow the instructions without issue.
Recommendations
- List Bash (or 'terminal') before Windows-specific terminals to avoid implying Windows is the primary platform.
- Explicitly state that all commands work on Windows, Linux, and macOS.
- Consider including a short note or section confirming Linux/macOS compatibility, especially for .NET CLI usage.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows-specific terminals (PowerShell, Windows Terminal, Command Prompt) first when instructing users to open a shell to clone the repository, with only a vague 'or equivalent' for other platforms. No explicit Linux/macOS terminal examples or instructions are provided, but the rest of the instructions (git, npm, Azure CLI) are cross-platform.
Recommendations
- Explicitly mention Linux/macOS terminals (e.g., 'Open an instance of PowerShell, Windows Terminal, Command Prompt, Terminal (macOS), or your preferred shell (Linux)').
- Provide example commands or screenshots for Linux/macOS environments where appropriate.
- Ensure troubleshooting and deployment steps reference cross-platform tools and workflows, not just Windows-centric ones.
Communication Services
Pricing for Teams interop scenarios
...ion-services/concepts/pricing/teams-interop-pricing.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation demonstrates mild Windows bias, primarily through the use of Windows-specific tools (PowerShell cmdlet for Teams Phone setup) and references to the Teams Desktop client, which is most commonly associated with Windows. The instructions for enabling Teams Phone features rely on a PowerShell cmdlet without mentioning Linux/macOS alternatives or cross-platform management options. Additionally, in example scenarios, the Teams Desktop client is referenced before other platforms, and the customer support agent is described as using Windows/Chrome, reinforcing a Windows-centric perspective.
Recommendations
- Provide equivalent instructions for Teams Phone setup using cross-platform tools (e.g., Microsoft Graph API, Azure CLI) or clarify if PowerShell cmdlets can be run on macOS/Linux.
- Explicitly mention Teams Desktop client availability on macOS and clarify parity of features.
- Include example scenarios where users join from Linux or macOS clients, not just Windows.
- Ensure that all management and configuration steps are documented for Linux/macOS environments where possible.
Communication Services
Messaging Connect overview
...mmunication-services/concepts/sms/messaging-connect.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page does not provide any platform-specific command-line examples, but in the SDK tutorial section, only C# (.NET) and JavaScript examples are given. There are no Linux/macOS-specific instructions, nor are there examples for Python or Java SDKs (which are noted as 'coming soon'). The flow for provisioning and sending SMS is described entirely through the Azure portal and partner web portals, which are web-based and cross-platform, but the developer code samples prioritize Microsoft-centric technologies (C#/.NET) and do not mention Linux or macOS explicitly. There is a subtle Windows-first bias in the choice and order of SDK examples, and a lack of parity for Linux-preferred languages (Python, Java) or CLI usage.
Recommendations
- Add Python and Java SDK examples as soon as those SDKs are available.
- Explicitly mention that the Azure portal and partner portals are accessible from any OS/browser.
- Include a note or example showing how to use the REST API directly (e.g., with curl), which is platform-neutral.
- If relevant, add CLI (Azure CLI) instructions for provisioning and sending SMS, and clarify that CLI works on Linux/macOS/Windows.
- When listing SDKs, avoid listing C#/.NET first unless it is the only supported SDK; consider alphabetical order or grouping by availability.
Communication Services
Subscribe to events in Job Router
...cation-services/how-tos/router-sdk/subscribe-events.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows-specific shells (cmd, PowerShell) before Bash when instructing users to create a new C# application, suggesting a Windows-first approach. However, all commands provided (dotnet CLI) are cross-platform and work on Linux/macOS as well. No PowerShell-specific scripts, Windows-only tools, or missing Linux examples are present.
Recommendations
- List Bash (Linux/macOS) before Windows shells (cmd, PowerShell) or simply state 'any terminal' to avoid platform prioritization.
- Explicitly mention that all dotnet CLI commands work on Linux/macOS and Windows.
- Where possible, provide links or notes for Linux/macOS users regarding prerequisites (e.g., installing .NET SDK on Linux/macOS).
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows-specific console environments (Command Prompt, PowerShell) before Bash when describing where to run commands, but otherwise provides cross-platform .NET CLI instructions and does not use Windows-only tools or patterns.
Recommendations
- List Bash (Linux/macOS) before or alongside Windows consoles when describing where to run commands.
- Explicitly state that all CLI commands work on Linux/macOS terminals as well as Windows.
- Add a note confirming Linux/macOS compatibility for the .NET SDK and CLI commands.
- Provide links or references to Linux/macOS setup guides if available.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing Windows-specific consoles (cmd, PowerShell) before Bash, and by not providing explicit Linux/macOS instructions or examples for environment variable setup, file editing, or running commands. All examples are generic .NET CLI commands, which work cross-platform, but there is no mention of Linux/macOS-specific nuances or troubleshooting.
Recommendations
- Explicitly mention Linux/macOS platforms alongside Windows in all instructions.
- Provide Linux/macOS-specific examples for environment variable setup (e.g., export in Bash/zsh), file editing (e.g., using nano or vim), and running the application.
- Include troubleshooting tips for common Linux/macOS issues (e.g., permissions, path differences).
- List Bash/zsh as a first-class console option, not just as an afterthought.
- Clarify that .NET Core and CLI commands are cross-platform and provide links to platform-specific installation guides.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by listing Windows-specific console environments (cmd, PowerShell) before Bash when describing how to create a new C# application. There are no explicit Linux/macOS-specific instructions or examples, and no mention of platform-specific caveats or alternative tools for non-Windows users. All code and commands are generic, but the narrative subtly prioritizes Windows environments.
Recommendations
- List Bash (Linux/macOS) before or alongside cmd and PowerShell when mentioning console windows.
- Explicitly state that all commands and code examples work on Linux/macOS as well as Windows.
- Add a note or section highlighting any platform-specific considerations for .NET Core and SmtpClient usage on Linux/macOS.
- Provide troubleshooting tips for common Linux/macOS issues (e.g., SSL/TLS, firewall, package dependencies).
Communication Services
Send email with SMTP and XOAuth2 using .NET
...kstarts/email/send-email-smtp/send-email-smtp-oauth.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page shows a mild Windows bias by mentioning Windows-specific consoles (cmd, PowerShell) before Bash, and does not provide any Linux/macOS-specific instructions or troubleshooting steps. All examples are platform-neutral, but the language and order favor Windows users.
Recommendations
- Explicitly mention Linux/macOS terminals (e.g., Bash, zsh) alongside Windows consoles in all relevant sections.
- Add a note or section confirming that all commands and code samples work on Linux/macOS, and highlight any platform-specific differences if they exist.
- Provide troubleshooting tips for common Linux/macOS issues (e.g., package installation, environment variables, permissions).
- Ensure parity in instructions for verifying prerequisites (e.g., .NET installation commands for Linux/macOS).
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page presents examples and instructions that, while technically cross-platform, show a subtle Windows bias. Console examples mention 'cmd' and 'PowerShell' before 'Bash', and there are no explicit Linux/macOS-specific instructions or screenshots. All code samples and tooling references (dotnet CLI, Azure portal) are platform-neutral, but the language and ordering favor Windows environments.
Recommendations
- Explicitly mention Linux/macOS terminals (e.g., 'Terminal', 'zsh', 'bash') alongside Windows options in all instructions.
- Provide Linux/macOS-specific notes or screenshots where relevant (e.g., environment variable setup, file paths).
- Ensure ordering of examples alternates or starts with a neutral or Linux/macOS option.
- Clarify that all dotnet CLI commands work on Linux/macOS as well as Windows.
- Add troubleshooting tips for Linux/macOS users (e.g., permissions, path issues).