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 426-450 of 656 flagged pages
Communication Services
Migrating from Twilio Conversations Chat to Azure Communication Services Chat C#
...orials/includes/twilio-to-acs-chat-android-tutorial.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: Visual Studio is listed as the only required IDE, and the only package installation example uses PowerShell syntax ('dotnet add package'), which is most commonly associated with Windows environments. There is no mention of Linux/macOS alternatives for development environments or package installation, nor are cross-platform CLI instructions (e.g., bash, zsh) provided. The Azure CLI example is cross-platform, but the overall setup and examples assume a Windows-first workflow.
Recommendations
- Explicitly mention that .NET and Azure Communication Services SDKs are cross-platform, and can be used on Linux/macOS as well as Windows.
- Provide alternative instructions for installing the SDK using bash/zsh (e.g., 'dotnet add package' in a Linux/macOS terminal).
- List VS Code or JetBrains Rider as alternative IDEs for Linux/macOS users, or clarify that Visual Studio is optional.
- Add a note that the Azure CLI works on all major platforms.
- Ensure that all code snippets and setup steps are platform-agnostic or provide platform-specific variants.
Create Pull Request
Communication Services
Govern Teams meeting experience with Azure Communication Services
...ts/interop/virtual-visits/govern-meeting-experience.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation focuses exclusively on Microsoft 365, Teams, and Azure tools and patterns, which are primarily Windows-centric. There are no examples, instructions, or references to Linux or cross-platform administration tools, nor any mention of how Linux users or administrators might perform equivalent tasks. All administrative actions are described in terms of Teams policies, roles, and options, which are typically managed via Windows-based interfaces or PowerShell, but no explicit PowerShell commands are shown. There is no discussion of Linux compatibility, CLI alternatives, or cross-platform considerations.
Recommendations
- Add explicit examples or instructions for managing Teams policies and meeting options using cross-platform tools, such as Azure CLI or Microsoft Graph API, which are available on Linux.
- Include notes or sections on how Linux administrators can perform equivalent governance tasks, highlighting any differences or limitations.
- Reference documentation or guides for Teams administration from Linux environments.
- Ensure that any tool or pattern mentioned (e.g., Azure Monitor Logs, Microsoft Purview) includes information about cross-platform access and usage.
Communication Services
Enable Closed captions with Teams Interoperability
...on-services/concepts/interop/enable-closed-captions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows as a primary supported platform ("client-side SDKs for Web, Windows, iOS and Android") and by linking Teams policies to PowerShell modules (with /powershell/module/skype/ URLs) without mentioning Linux equivalents or alternatives. There are no explicit Linux examples, nor is Linux called out as a supported platform for the client SDKs. The documentation also refers to Teams administration patterns that are typically Windows-centric (PowerShell), and does not provide parity for Linux administrators or developers.
Recommendations
- Explicitly mention Linux as a supported platform for Azure Communication Services client SDKs, if applicable.
- Provide Linux-specific examples or instructions, especially for administration tasks (e.g., Teams policy management) that are currently referenced via PowerShell.
- If Teams policy management can be performed via cross-platform tools (such as Microsoft Graph API or Azure CLI), include those examples alongside or before PowerShell references.
- Clarify any platform limitations for SDKs and tools, and provide guidance for Linux users where possible.
- Ensure that diagrams and sample architectures do not imply Windows-only usage, and include Linux scenarios if supported.
Communication Services
Teams Phone extensibility provisioning
.../interop/tpe/teams-phone-extensibility-provisioning.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Teams administration and provisioning processes that are typically performed using Windows-centric tools (e.g., Teams Admin cmdlets, Microsoft 365 Admin roles) without providing equivalent Linux or cross-platform examples. There are no explicit PowerShell or Windows tool commands shown, but the language and referenced workflows assume a Windows/Office 365 administrative environment and do not mention Linux-compatible alternatives or CLI tools.
Recommendations
- Add explicit examples using cross-platform tools such as Azure CLI, Microsoft Graph API via curl or other Linux-friendly methods.
- Clarify whether provisioning and authorization steps can be performed from Linux or macOS environments, and provide instructions if so.
- Include references to Linux-compatible administration portals or scripts where available.
- Ensure that any cmdlet or admin tool mentioned is accompanied by a note on cross-platform support or alternatives.
Communication Services
Messaging Connect overview
...mmunication-services/concepts/sms/messaging-connect.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page for Messaging Connect does not provide any platform-specific code examples or tooling instructions, but it does show a subtle Windows bias by referencing the Azure portal (which is most commonly used on Windows) and omitting any Linux-specific guidance or CLI examples. All SDK code samples are in C# and JavaScript, with no mention of Linux-friendly tools, shell commands, or cross-platform CLI usage. There are no references to Powershell, but the lack of Linux parity in examples and instructions is notable.
Recommendations
- Add examples using Azure CLI for provisioning and managing Messaging Connect resources, demonstrating usage from Linux/macOS terminals.
- Include Python and Java SDK examples as soon as they are available, and explicitly mention their cross-platform compatibility.
- Provide instructions for using Messaging Connect via REST API with curl or httpie, showing how to send SMS from Linux environments.
- Clarify that the Azure portal and Messaging Connect features are accessible from any OS/browser, and mention alternative workflows for Linux users.
- If any troubleshooting or diagnostics steps require platform-specific tools, ensure both Windows and Linux equivalents are documented.
Communication Services
SDKs and REST APIs for Azure Communication Services
...rticles/communication-services/concepts/sdk-options.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias, primarily in the SDK platform support section. Windows platforms and tools (UWP, WinUI3, .NET Framework/Core on Windows, Windows Server) are listed first and in greater detail than Linux or macOS equivalents. There is no mention of Powershell or exclusive Windows command-line examples, but Windows-specific deployment notes (such as unpackaged app support) and platform breakdowns are more prominent than Linux or macOS details. Linux support is mentioned only briefly and generically, with no distribution-specific guidance or parity in platform details.
Recommendations
- Provide equal detail for Linux and macOS platform support, including specific supported distributions and versions.
- Add examples or notes for Linux-specific deployment, troubleshooting, and environment setup, matching the detail given for Windows.
- If there are platform-specific limitations or features, document them for Linux and macOS as well as Windows.
- Consider listing platforms in a neutral order (e.g., alphabetical or grouped by OS family) rather than Windows-first.
- Include links to Linux/macOS package managers or installation guides where relevant, similar to NuGet for Windows.
Communication Services
Additional Prerequisites
...ity/includes/active-directory/service-principal-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively linking to setup guides and quickstarts for Windows VMs (via portal, PowerShell, CLI, ARM templates, SDKs), without mentioning or providing equivalent Linux VM resources. There are no Linux-specific examples or instructions for enabling managed identities or setting environment variables in Linux shells.
Recommendations
- Add links to managed identity setup guides for Linux VMs using portal, CLI, PowerShell, ARM templates, and SDKs.
- Provide Linux shell examples (e.g., bash/zsh) for setting environment variables, alongside Windows/PowerShell instructions.
- Ensure parity in documentation by mentioning both Windows and Linux environments where applicable, especially in authentication and environment setup sections.
- Include troubleshooting notes for Linux users (e.g., environment variable persistence, shell differences).
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by listing Windows console environments (cmd, PowerShell) before Bash when describing how to create a new C# application. There are no explicit Linux-specific instructions, troubleshooting, or examples, and no mention of Linux package managers or shell environments beyond a brief reference to Bash. All code examples use .NET CLI commands, which are cross-platform, but the documentation does not demonstrate Linux-specific patterns or address potential Linux differences.
Recommendations
- List Bash (Linux/macOS) before or alongside cmd and PowerShell when mentioning console environments.
- Explicitly state that all .NET CLI commands work on Linux and macOS, and provide links to .NET installation instructions for Linux.
- Include Linux-specific notes or troubleshooting tips (e.g., permissions, environment variables, file paths).
- Mention how to install .NET and NuGet packages on Linux, possibly referencing package managers like apt, yum, or Homebrew.
- Add screenshots or terminal output examples from Linux environments to demonstrate parity.
Communication Services
Subscribe to events in Job Router
...cation-services/how-tos/router-sdk/subscribe-events.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page shows mild Windows bias in its quickstart instructions. In the section 'Create a new C# application', the console window examples list 'cmd, PowerShell, or Bash', but the order places Windows shells first. All code and CLI examples use .NET CLI, which is cross-platform, but there are no explicit Linux/macOS-specific instructions, troubleshooting, or validation of Linux environments. No Linux-specific tools or patterns are mentioned, and no screenshots or guidance are provided for Linux users. The rest of the document is platform-neutral, focusing on event schemas and C# code.
Recommendations
- List Bash (Linux/macOS) before cmd/PowerShell when mentioning console options, or explicitly state that all commands work on Windows, Linux, and macOS.
- Add a note confirming that the .NET CLI and SDKs are fully supported on Linux/macOS, with a link to .NET installation instructions for those platforms.
- Include troubleshooting tips or environment validation steps for Linux/macOS users (e.g., checking dotnet installation, permissions).
- If possible, provide a sample run or screenshot from a Linux terminal to demonstrate parity.
- Explicitly mention that the code and instructions are cross-platform, and highlight any OS-specific caveats if they exist.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by mentioning Windows-specific consoles (cmd, PowerShell) before Bash when instructing users to create a new C# application. There are no Linux-specific instructions, examples, or troubleshooting notes, and the documentation does not address platform-specific differences in environment variable management, file paths, or package installation. All examples and instructions are generic but implicitly assume a Windows environment.
Recommendations
- Explicitly mention Linux and macOS as supported platforms for .NET Core and Azure Communication Services.
- Provide Linux/macOS-specific instructions and examples, such as using Bash or zsh terminals, and note any differences in environment variable setup.
- Include troubleshooting tips for common Linux issues (e.g., permissions, dependency installation).
- Ensure parity in screenshots, terminal commands, and file path conventions for both Windows and Linux.
- Clarify that the instructions apply equally to Windows, Linux, and macOS, or provide platform-specific tabs/sections where relevant.
Communication Services
Send email with inline attachments
...d-email-advanced/send-email-with-inline-attachments.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides pivots for multiple programming languages and tools, including Azure CLI and PowerShell. PowerShell is a Windows-specific tool and is given its own pivot, which may indicate a bias towards Windows environments. There is no explicit mention of Linux-specific tools or shell examples (e.g., bash), and PowerShell is presented alongside Azure CLI, which is cross-platform, but no Linux shell examples are provided. The troubleshooting and resource cleanup sections do not mention platform-specific steps, but the inclusion of PowerShell as a primary pivot suggests a Windows-first approach.
Recommendations
- Add explicit bash or Linux shell examples alongside PowerShell, especially for command-line tasks.
- Clarify in each pivot which platforms are supported (e.g., note that Azure CLI works on Linux/macOS/Windows, while PowerShell is primarily Windows-focused).
- Consider adding a 'programming-language-bash' or 'programming-language-linux-shell' pivot for parity.
- Where PowerShell is mentioned, provide equivalent Linux commands or scripts to ensure cross-platform accessibility.
Communication Services
Set up and obtain access tokens for Microsoft Entra ID users
...ntity/microsoft-entra-id-authentication-integration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides examples for creating service principals using Microsoft Graph REST API and Azure CLI, which are cross-platform. However, throughout the page, administrative actions and portal navigation are described using the Azure portal UI, which is most commonly used on Windows and does not mention Linux-specific tools or alternatives (such as bash scripts, automation via CLI, or PowerShell on Linux). There are no explicit Linux or macOS examples, nor is there mention of command-line automation for steps that could be performed outside the portal. The page does not reference Linux tools or patterns, and the developer examples are only referenced by language (C#/.NET and JavaScript), not by OS. There is a subtle 'windows_first' bias in the reliance on the Azure portal and lack of Linux-specific guidance.
Recommendations
- Provide explicit Linux/macOS command-line examples for administrative steps that can be performed via Azure CLI or REST API, especially for resource assignment and permission granting.
- Mention that Azure CLI and Microsoft Graph REST API are cross-platform and can be used on Linux/macOS as well as Windows.
- Include automation scripts or sample bash commands for common tasks, such as assigning access or registering applications.
- Add a section or note on how to perform portal-based steps using CLI or REST API for users who prefer or require non-GUI workflows.
- Clarify that developer SDKs (C#/.NET, JavaScript) can be used on Linux/macOS environments and provide links or notes to relevant setup guides.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation mentions Windows-specific console environments (cmd, PowerShell) before Bash, and does not provide any Linux/macOS-specific instructions or examples for environment variable setup or text editor usage. All examples and tooling are .NET-centric, which is cross-platform, but the setup and workflow implicitly favor Windows users.
Recommendations
- Explicitly mention Linux/macOS environments and provide equivalent instructions for common tasks (e.g., setting environment variables, opening files in editors like nano or vim).
- List Bash (Linux/macOS) first or equally when referencing console windows.
- Add notes or examples for setting environment variables on Linux/macOS (e.g., export ENTRA_CLIENT_ID=...).
- Include guidance for running the code and installing prerequisites on Linux/macOS, such as using terminal commands and package managers.
- Clarify that .NET SDK and related tools are cross-platform and provide links or instructions for non-Windows platforms.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation references Windows-specific console environments (cmd, PowerShell) before mentioning Bash, and does not provide any Linux/macOS-specific instructions or examples for environment variable setup, file editing, or running the application. All examples use generic .NET CLI commands, but there is an implicit Windows-first bias in the order and absence of Linux-specific guidance.
Recommendations
- Explicitly mention Linux/macOS terminal environments (e.g., Bash, zsh) alongside Windows options in all setup instructions.
- Provide examples for setting environment variables on Linux/macOS (e.g., 'export COMMUNICATION_SERVICES_CONNECTION_STRING=...') in addition to Windows methods.
- Include guidance for editing files using common Linux/macOS editors (e.g., nano, vim) as alternatives to Windows editors.
- Clarify that all .NET CLI commands work cross-platform and note any OS-specific differences if applicable.
- Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, path separators) if relevant.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation refers to 'console window (such as cmd, PowerShell, or Bash)' but lists Windows shells first and does not provide any Linux-specific examples or instructions. All commands and environment variable usage are generic, but there is no mention of Linux-specific considerations (such as environment variable setting, file editing, or shell differences). The documentation implicitly prioritizes Windows environments and omits Linux parity details.
Recommendations
- Explicitly mention Linux and macOS terminals (e.g., Bash, zsh) alongside Windows shells.
- Provide Linux/macOS-specific instructions for setting environment variables (e.g., export AAD_CLIENT_ID=...) and running dotnet commands.
- Include notes on editing files with Linux editors (e.g., nano, vim) as alternatives to Windows editors.
- Add troubleshooting tips for common Linux issues (e.g., permissions, .NET SDK installation differences).
- Ensure parity in example commands and shell usage across platforms.
Communication Services
Quickstart - How to call to Teams user from an Android app
...ideo-calling/includes/teams-user/teams-user-android.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates bias towards Windows by referencing Windows-specific tools and patterns, such as requiring Teams users to be 'Enterprise Voice enabled' via a PowerShell link, and linking to Teams deployment instructions that are primarily Windows-focused. There are no Linux equivalents or alternative instructions provided for enabling Teams features or deploying Teams, nor are Linux-friendly tools or command-line examples mentioned.
Recommendations
- Provide Linux/macOS alternatives for enabling Teams features (e.g., using Microsoft Graph API or cross-platform CLI tools instead of PowerShell).
- Include links or instructions for Teams deployment on non-Windows platforms, or clarify platform requirements.
- Explicitly state if certain steps (like enabling Enterprise Voice) can only be performed on Windows, and suggest workarounds or alternatives for Linux users.
- Ensure all referenced documentation (such as enabling users for Teams Phone) includes cross-platform instructions.
Communication Services
Quickstart - Make a call to Teams user from a web app
...o-calling/includes/teams-user/teams-user-javascript.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits Windows bias primarily in the prerequisites section, where enabling Teams Phone for users is described only via a PowerShell link, with no mention of Linux-compatible alternatives or cross-platform tools. The Teams deployment link also points to a Windows-centric installation guide. The rest of the guide is platform-neutral JavaScript and web instructions, but initial setup steps assume Windows environments.
Recommendations
- Include instructions or links for enabling Teams Phone and Enterprise Voice using cross-platform tools or via the Teams Admin Center web interface, if available.
- Provide explicit guidance for Linux/macOS users on how to perform prerequisite steps, such as Teams deployment and user enablement.
- Where PowerShell is referenced, note its availability on Linux/macOS and provide installation instructions or alternatives.
- Ensure all prerequisite steps are described in a way that does not assume a Windows environment.
Communication Services
Sign an HTTP Request with C#
...tion-services/tutorials/includes/hmac-header-csharp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows by listing Windows tools (cmd, PowerShell) before Bash in instructions for creating a new C# application. The prerequisites exclusively mention Visual Studio, a Windows-centric IDE, without alternatives for Linux users (such as VS Code or JetBrains Rider). No Linux-specific instructions, troubleshooting, or environment setup are provided, and there is no mention of Linux package managers or editors. All examples are platform-neutral C# code, but the surrounding context and tooling recommendations favor Windows.
Recommendations
- List Bash before or alongside cmd/PowerShell when mentioning console windows.
- Include Linux-friendly IDEs and editors in prerequisites (e.g., VS Code, JetBrains Rider).
- Provide explicit instructions for Linux users, such as installing .NET SDK via apt, yum, or other package managers.
- Mention cross-platform compatibility of the .NET CLI and HttpClient.
- Add troubleshooting notes for common Linux issues (e.g., permissions, environment variables).
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits Windows bias by listing Windows-specific terminals (PowerShell, Windows Terminal, Command Prompt) first and exclusively in the instructions for opening a terminal, without mentioning Linux or macOS equivalents (such as Bash, Terminal, or iTerm). There are no explicit Linux/macOS examples or references to their tools or shell environments, which may make Linux/macOS users feel less prioritized or supported.
Recommendations
- Explicitly mention Linux/macOS terminal options (e.g., Bash, Terminal, iTerm) alongside Windows terminals when instructing users to open a terminal.
- Add notes or examples for Linux/macOS users where file paths, commands, or environment setup may differ.
- Ensure that instructions and tooling references (such as Visual Studio Code and Node.js) clarify cross-platform compatibility.
- Where possible, provide platform-agnostic instructions or highlight any platform-specific steps.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exhibits Windows bias by referencing Windows-specific tabs in prerequisite links and instructing users to open a PowerShell window to run the application, without providing equivalent instructions for Linux or macOS environments. There are no Linux/macOS terminal examples or explicit cross-platform guidance for running the sample.
Recommendations
- Provide setup and run instructions for Linux and macOS, including terminal commands and environment-specific notes.
- Avoid referencing Windows-specific tools (e.g., PowerShell) as the default; use generic terms like 'terminal' or provide parallel instructions for multiple platforms.
- Ensure all prerequisite links and resource creation guides include Linux/macOS tabs or pivots where applicable.
- Explicitly state cross-platform compatibility and highlight any platform-specific differences in setup or usage.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows mild Windows bias, notably in the prerequisites section where links and instructions default to Windows tabs (e.g., 'Create an Azure Communication Services resource' uses '?tabs=windows'). There are no explicit Linux-specific instructions or examples, and platform-agnostic steps are described, but Windows is implicitly prioritized. No PowerShell-specific commands or Windows-only tools are present, but Linux parity is not explicitly addressed.
Recommendations
- Ensure all resource creation links and instructions offer both Windows and Linux tabs, or default to platform-neutral guidance.
- Explicitly mention that setup steps (e.g., running Python scripts, using devtunnel) work on Linux and macOS, and provide any necessary platform-specific notes.
- Add Linux/macOS-specific examples or troubleshooting tips where relevant, especially for environment setup and command-line usage.
- Review all quickstart and prerequisite links to ensure Linux instructions are equally accessible and not hidden behind Windows-first pivots.
Communication Services
Contact centers with Azure Communication Services
...les/communication-services/tutorials/contact-center.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its use of Windows-specific tabs and pivots in linked quickstarts (e.g., 'tabs=windows', 'tabs=uwp'), and by not providing Linux or cross-platform examples or instructions. There is a lack of explicit mention of Linux tools, patterns, or parity in the guidance, and the examples and links default to Windows-centric development environments.
Recommendations
- Provide Linux-specific examples and instructions alongside Windows ones, especially in quickstart links and code samples.
- Ensure tabs/pivots for Linux (e.g., 'tabs=linux') are available and visible in all relevant quickstart documentation.
- Mention and document cross-platform tools and SDKs, clarifying their compatibility with Linux environments.
- Include guidance for deploying and managing contact center applications on Linux servers and developer workstations.
- Review referenced quickstarts and tutorials to ensure Linux parity in setup, usage, and troubleshooting steps.
Communication Services
Additional Prerequisites
...ity/includes/active-directory/service-principal-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing only Windows VM-specific links for enabling managed identities (portal, PowerShell, CLI, ARM template, SDK), without mentioning Linux VM equivalents or providing Linux-specific guidance. Additionally, environment variable instructions do not reference Linux shell patterns (e.g., export commands), and there are no Linux-specific authentication examples.
Recommendations
- Include links and instructions for enabling managed identities on Linux VMs, not just Windows VMs.
- Provide Linux shell (bash/zsh) examples for setting environment variables (e.g., export AZURE_CLIENT_ID=...).
- Mention Linux development environments (such as VS Code on Linux) alongside Windows tools.
- Ensure parity in CLI examples and clarify that Azure CLI works cross-platform.
- Add notes or sections for Linux users where setup or authentication steps differ.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows mild Windows bias: in the prerequisites, links to resource creation use Windows tabs by default, and there is no explicit mention or example for Linux-specific setup steps or tools. The instructions for running the Python sample mention PowerShell and command prompt before Unix terminal, and do not provide Linux-specific guidance or troubleshooting.
Recommendations
- Ensure all quickstart and resource creation links default to a neutral or platform-agnostic tab, or provide both Windows and Linux tabs equally.
- Add explicit Linux setup instructions or troubleshooting notes where relevant (e.g., for dev tunnel installation, Python environment setup).
- When listing command-line options, mention Unix/Linux terminals first or equally alongside PowerShell and command prompt.
- Include any Linux-specific dependencies or caveats for the sample, if applicable.
Communication Services
Sign an HTTP Request with C#
...tion-services/tutorials/includes/hmac-header-csharp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by listing Windows tools (cmd, PowerShell) before Bash in the instructions for creating a new C# application. The prerequisites exclusively mention Visual Studio, a Windows-centric IDE, without referencing cross-platform alternatives. There are no Linux-specific instructions or examples, and the workflow assumes familiarity with Windows development environments.
Recommendations
- List Bash before or alongside cmd/PowerShell when mentioning console windows.
- Include instructions for installing .NET SDK and running C# code on Linux (e.g., using VS Code, JetBrains Rider, or CLI-only workflows).
- Mention cross-platform editors and tools in the prerequisites, such as VS Code or JetBrains Rider.
- Explicitly state that the steps work on Linux and macOS, and provide any necessary platform-specific notes (e.g., package installation, environment setup).
- Add troubleshooting tips for common Linux issues (e.g., permissions, environment variables).