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 576-600 of 656 flagged pages
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 provides code examples only for C# (.NET) and JavaScript SDKs, with C# (a Windows-centric language/platform) shown first. There are no examples for Linux-native languages (e.g., Python, Java) or command-line tools, nor any mention of Linux-specific patterns or shell usage. The provisioning and developer experience sections focus on Azure portal GUI workflows, which are platform-agnostic but do not mention CLI alternatives (such as Azure CLI or Bash scripting), which are more common in Linux environments.
Recommendations
- Add code examples for Python and Java SDKs when available, and update the documentation as soon as these SDKs are released.
- Include CLI-based provisioning steps using Azure CLI or REST API calls, with sample commands for Bash/shell environments.
- Present SDK examples in a neutral order (e.g., rotate which language is shown first, or group by platform-neutral languages).
- Explicitly mention cross-platform compatibility for all SDKs and tools, and provide guidance for Linux/macOS users where relevant.
- When referencing partner documentation (e.g., Infobip), clarify any platform requirements or provide Linux/macOS-specific instructions if needed.
Create Pull Request
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. However, all commands shown are cross-platform and there are no Windows-only tools or examples. No Linux/macOS equivalents are missing, and the instructions are generally platform-agnostic.
Recommendations
- List Bash before or alongside cmd/PowerShell when referencing console windows to avoid implying Windows primacy.
- Explicitly state that all shown commands work on Linux/macOS as well as Windows.
- Consider adding a note or example for running the code on Linux/macOS, such as using Terminal or zsh.
Communication Services
Create a Communication Services resource in Azure Communication Services
...-services/quickstarts/create-communication-resource.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows a mild Windows bias: Windows examples and tooling (PowerShell, setx) are presented first or exclusively in some sections, and Windows-centric instructions (Visual Studio, app.config/web.config) are highlighted before Linux/macOS equivalents. However, Linux/macOS instructions are present and reasonably complete, especially for environment variables and Azure CLI usage.
Recommendations
- Present Linux/macOS examples before or alongside Windows examples, rather than after.
- Include .NET configuration examples for Linux/macOS (e.g., appsettings.json) in addition to app.config/web.config.
- Mention cross-platform editors (VS Code, JetBrains Rider) alongside Visual Studio.
- Clarify that Azure CLI is cross-platform and provide install links for Linux/macOS, not just Windows.
- Ensure parity in screenshots and instructions for portal navigation across OSes.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by referencing Windows-specific consoles (cmd, PowerShell) before Bash, and by not providing any Linux/macOS-specific instructions or examples. All code and tooling instructions are generic to .NET, but no explicit Linux/macOS terminal commands, environment variable setup, or troubleshooting notes are included.
Recommendations
- Explicitly mention Linux/macOS compatibility in all relevant sections.
- Provide Linux/macOS-specific instructions for environment variable setup and running commands (e.g., export vs set).
- Show Bash/zsh examples alongside Windows cmd/PowerShell where terminal commands are referenced.
- Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, .NET installation differences).
- Clarify that the .NET SDK and Email client work cross-platform, and link to OS-specific installation guides.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by listing Windows-specific console environments (cmd, PowerShell) before Bash when instructing users to create a new C# application. There are no explicit Linux/macOS-specific instructions or troubleshooting steps, and all examples are generic .NET/C# code, which is cross-platform, but the documentation does not clarify Linux/macOS nuances (e.g., package installation, environment setup).
Recommendations
- List Bash (Linux/macOS) first or alongside cmd/PowerShell when mentioning console windows.
- Add explicit instructions for installing .NET Core on Linux/macOS (e.g., apt, yum, brew commands).
- Include troubleshooting notes for common Linux/macOS issues (e.g., permissions, firewall, SSL certificates).
- Clarify that the examples work identically on Linux/macOS and Windows, or highlight any platform-specific differences.
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 examples use cross-platform .NET CLI commands, and there are no Windows-specific tools or patterns. No Linux/macOS examples are missing, and the instructions are generally platform-agnostic.
Recommendations
- List Bash (or 'terminal') before Windows-specific terminals to avoid implying Windows is primary.
- Explicitly state that all commands work on Linux/macOS as well as Windows.
- Consider adding a note or section confirming Linux/macOS compatibility, especially for .NET CLI usage.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by listing Windows-specific console environments (cmd, PowerShell) before Bash when describing how to create a new C# application. All command-line instructions use generic 'dotnet' commands, which work cross-platform, but there are no explicit Linux/macOS examples or notes about platform-specific differences. No Windows-only tools or PowerShell scripts are present, but the absence of Linux/macOS-specific guidance or troubleshooting may create friction for non-Windows users.
Recommendations
- Explicitly mention Linux/macOS terminals (e.g., Terminal, iTerm) alongside cmd and PowerShell.
- Add notes or examples for setting environment variables on Linux/macOS (e.g., export COMMUNICATION_SERVICES_CONNECTION_STRING=...)
- Include troubleshooting tips or links for .NET installation on Linux/macOS.
- Ensure screenshots or UI references (if any) are platform-neutral or include Linux/macOS variants.
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
Summary
The documentation demonstrates minor Windows bias by listing Windows consoles (cmd, PowerShell) before Bash when describing where to run commands. However, all code examples and instructions are cross-platform and do not rely on Windows-specific tools or patterns.
Recommendations
- List Bash (Linux/macOS) before or alongside Windows consoles (cmd, PowerShell) to avoid implicit prioritization.
- Explicitly state that all .NET commands and MailKit usage are cross-platform and work on Linux/macOS as well as Windows.
- Consider including a brief note or example showing the process on Linux/macOS, such as installing .NET Core or running the commands in a Bash terminal.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a slight Windows bias by listing Windows console environments (cmd, PowerShell) before Bash when describing how to run commands. All command-line instructions use .NET CLI commands, which are cross-platform, but there are no Linux/macOS-specific examples or notes. The documentation does not mention Linux/macOS-specific considerations, such as environment variable setting syntax, nor does it provide parity in example environments.
Recommendations
- Explicitly mention that all .NET CLI commands work on Linux and macOS, not just Windows.
- Provide examples of setting environment variables on Linux/macOS (e.g., 'export ENTRA_CLIENT_ID=...') alongside Windows methods.
- List Bash (Linux/macOS) first or equally when mentioning console environments.
- Add notes about using common Linux/macOS text editors (e.g., nano, vim) for editing Program.cs.
- Clarify any OS-specific differences in running the application, if applicable.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation references Windows-specific consoles (cmd, PowerShell) before Bash and does not provide any Linux/macOS-specific instructions or troubleshooting. All commands are generic .NET CLI, which are cross-platform, but there is a subtle preference for Windows environments in the wording and order. No Linux/macOS-specific environment setup, permissions, or example screenshots are provided.
Recommendations
- List Bash (Linux/macOS) first or equally alongside cmd/PowerShell when mentioning consoles.
- Include explicit instructions for Linux/macOS users, such as installation commands for .NET Core using apt, yum, or brew.
- Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, environment variables).
- Provide example screenshots or terminal output from Linux/macOS environments.
- Clarify that all commands are cross-platform and mention any OS-specific caveats.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions Windows-specific consoles (Command Prompt, PowerShell) before Bash when instructing users to create a C# application. This ordering subtly prioritizes Windows environments. However, all CLI commands shown are cross-platform (dotnet CLI), and there are no examples or instructions that are Windows-only. No Linux-specific tools or patterns are missing, but the initial console window examples could be more inclusive.
Recommendations
- List Bash (Linux/macOS) first or equally alongside Windows consoles when referencing command line usage.
- Explicitly state that all dotnet CLI commands work on Linux/macOS terminals.
- Consider adding a note or section confirming Linux/macOS compatibility and any OS-specific caveats.
- If there are any platform-specific steps (e.g., environment variable setup), provide examples for both Windows and Linux/macOS.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation references Windows-specific consoles (cmd, PowerShell) before Bash, and provides no Linux/macOS-specific instructions or examples. All commands and code are generic, but there is a subtle prioritization of Windows environments and no mention of Linux/macOS-specific considerations (e.g., environment variable setting, editor choices, or troubleshooting).
Recommendations
- Explicitly mention Bash and Linux/macOS terminal usage alongside Windows consoles.
- Provide examples for setting environment variables on Linux/macOS (e.g., export AAD_CLIENT_ID=...) in addition to Windows.
- Suggest common Linux/macOS text editors (e.g., nano, vim) when instructing users to edit Program.cs.
- Add troubleshooting notes for platform-specific issues (e.g., .NET SDK installation on Linux/macOS, permissions).
- Ensure parity in instructions for running and building the app, including any OS-specific nuances.
Communication Services
Access a user's Teams Phone separate from their Teams client
...ts/tpe/teams-phone-extensibility-access-teams-phone.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates mild Windows bias, particularly in the prerequisites section, where enabling a user for Teams is described exclusively via the Microsoft 365 admin center web UI—a workflow most commonly associated with Windows environments. Additionally, the only mention of a command-line tool is the MicrosoftTeams PowerShell cmdlet (Get-CsOnlineApplicationInstance), with no Linux/macOS alternative or Graph API example provided. However, the main API usage and SDK examples are platform-neutral, and REST calls are shown directly, which can be executed from any OS.
Recommendations
- Provide equivalent instructions for enabling Teams users via cross-platform tools, such as Microsoft Graph API or Azure CLI, alongside or instead of the Microsoft 365 admin center UI.
- When referencing command-line tools (e.g., PowerShell cmdlets), also include examples using platform-agnostic REST API calls or scripts that work on Linux/macOS.
- Explicitly state that all API and SDK operations can be performed from any OS, and link to cross-platform tooling documentation where relevant.
- Consider reordering examples so that platform-neutral or Linux/macOS-compatible methods are presented first, or in parallel with Windows-specific instructions.
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 terminal to clone the repository, with only a vague 'or equivalent' reference to non-Windows platforms. No explicit Linux/macOS terminal examples or instructions are provided, but all commands given are cross-platform (git, npm, Azure CLI).
Recommendations
- Explicitly mention Linux/macOS terminals (e.g., 'Terminal on macOS or Linux') alongside Windows options.
- Provide example commands for Linux/macOS where relevant, especially for file path or environment variable configuration.
- Clarify that all CLI commands are cross-platform and note any platform-specific considerations if they exist.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page shows a mild Windows bias by instructing users to 'Open a new PowerShell window' in the 'Run the application' section, without mentioning Linux/macOS terminals or alternatives. Additionally, some prerequisite links default to Windows tabs, suggesting Windows-first orientation.
Recommendations
- Replace 'Open a new PowerShell window' with 'Open a terminal window' and clarify that the instructions apply to Windows, Linux, and macOS.
- Provide explicit instructions or notes for Linux/macOS users where terminal commands or environment setup may differ.
- Ensure prerequisite links and instructions do not default to Windows tabs, or clearly indicate cross-platform options.
- Add a note confirming that the sample works on Linux/macOS and mention any platform-specific considerations.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation frequently references Windows-specific tools and patterns, such as opening PowerShell or Windows terminal, and lists these before mentioning generic or Linux/macOS equivalents. While most commands (git, npm, devtunnel) are cross-platform, the instructions and examples are written with a Windows-first perspective, which may create friction for Linux/macOS users.
Recommendations
- Explicitly mention Linux/macOS terminals (e.g., Bash, Terminal.app) alongside Windows tools in all steps.
- Provide example commands or screenshots for Linux/macOS environments where relevant.
- Avoid listing Windows tools first; use neutral language like 'Open a terminal' instead of 'Open PowerShell, a Windows terminal, or command prompt'.
- Clarify that all commands shown (git, npm, devtunnel) work on Linux/macOS as well.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows mild Windows bias, primarily in the prerequisites section where links default to Windows instructions (e.g., 'Create an Azure Communication Services resource' uses '?tabs=windows'). However, the setup and run instructions themselves use cross-platform commands (pip, devtunnel, python) and mention PowerShell, command prompt, and Unix terminal together, without exclusive Windows tooling or examples.
Recommendations
- Ensure prerequisite links include Linux/macOS tabs or mention cross-platform instructions explicitly.
- Add explicit notes or links for Linux/macOS users where platform-specific setup may differ.
- Review linked quickstarts and pivots to verify Linux/macOS parity and update if necessary.
Communication Services
Sign an HTTP Request with C#
...tion-services/tutorials/includes/hmac-header-csharp.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a slight Windows bias by listing Windows tools (cmd, PowerShell) before Bash when describing how to create a new C# application, and by recommending Visual Studio as the only IDE for C# development. There are no Linux-specific instructions or examples, and alternative Linux-friendly editors or workflows (such as VS Code or JetBrains Rider) are not mentioned. However, the core instructions use .NET CLI, which is cross-platform, and Bash is acknowledged as a possible console.
Recommendations
- Mention Linux/macOS explicitly in the prerequisites and setup steps.
- List Bash (and other Linux/macOS terminals) before or alongside cmd/PowerShell when describing console usage.
- Recommend cross-platform editors such as VS Code or JetBrains Rider in addition to Visual Studio.
- Clarify that all dotnet CLI commands work on Linux/macOS as well as Windows.
- Add a note that the instructions are valid for Linux/macOS, and highlight any platform-specific differences (e.g., file paths, environment setup).
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is largely cross-platform, but there is a subtle Windows bias in the order of examples: when suggesting console environments, 'cmd' and 'PowerShell' are mentioned before 'Bash'. No Linux-specific tools or instructions are missing, but the ordering may suggest a Windows-first perspective.
Recommendations
- List Bash (or 'terminal') before or alongside cmd and PowerShell when mentioning console environments, e.g., 'in a console window (such as Bash, cmd, or PowerShell)'.
- Explicitly state that all commands work on Windows, Linux, and macOS to reinforce cross-platform compatibility.
- If there are any OS-specific steps (e.g., environment variable setup, file paths), provide both Windows and Linux/macOS examples.
- Consider including a short note or table summarizing supported platforms and any platform-specific considerations.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows consoles (cmd, PowerShell) before Bash when describing how to run Maven commands, which may suggest a Windows-first perspective. However, all commands and instructions are cross-platform and do not rely on Windows-specific tools or patterns. No PowerShell-specific examples or Windows-only tools are present, and Linux users are not excluded from any steps.
Recommendations
- List Bash (Linux/macOS) before Windows consoles (cmd, PowerShell) when describing command-line usage, or mention all platforms equally (e.g., 'in a terminal such as Bash, cmd, or PowerShell').
- Explicitly state that all commands work on Windows, Linux, and macOS, to reassure non-Windows users.
- If platform-specific steps ever arise (e.g., environment variables, file paths), provide examples for both Windows and Linux/macOS.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows consoles (cmd, PowerShell) before Bash when describing how to run Maven commands, which is a subtle form of Windows-first bias. However, all code and tooling instructions are platform-neutral (Java, Maven), and there are no PowerShell-specific commands, Windows-only tools, or missing Linux examples.
Recommendations
- List Bash before cmd/PowerShell when referencing console windows, or use 'terminal (such as Bash, cmd, or PowerShell)' to avoid platform prioritization.
- Explicitly state that all commands work on Linux, macOS, and Windows, and provide any necessary notes for cross-platform usage.
- If there are platform-specific considerations (e.g., environment variables, file paths), include examples for both Windows and Linux/macOS.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a slight Windows bias by listing Windows command-line tools (cmd, PowerShell) before Bash when describing how to run commands. However, all commands shown are cross-platform (dotnet CLI), and there are no PowerShell-specific examples, Windows-only tools, or missing Linux equivalents. The documentation does not provide Linux-specific environment variable setup instructions or mention Linux text editors, but the core instructions are generally platform-agnostic.
Recommendations
- List Bash first or equally alongside cmd and PowerShell when mentioning command-line tools.
- Explicitly mention that all dotnet CLI commands work on Linux, macOS, and Windows.
- Provide examples for setting environment variables on Linux/macOS (e.g., export COMMUNICATION_SERVICES_CONNECTION_STRING=...).
- Suggest common Linux/macOS text editors (e.g., nano, vim, VS Code) when instructing users to edit Program.cs.
- Add a note confirming that the quickstart works on all major platforms and link to platform-specific setup guides if available.
Communication Services
Quickstart - Teams interop calls on Azure Communication Services
...video-calling/get-started-teams-interop-group-calls.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation exhibits mild Windows bias by referencing Windows-centric deployment and configuration steps, such as linking to Teams installation instructions that are primarily Windows-focused and requiring Teams Phone license enablement via PowerShell (a Windows tool). However, the main code samples and application instructions are cross-platform (JavaScript, web-based), and there are no critical steps that are Windows-only.
Recommendations
- Provide explicit Linux/macOS alternatives or notes for Teams deployment and configuration steps, especially where PowerShell is referenced.
- Clarify if Teams Phone license enablement can be performed via Microsoft 365 admin portal or Graph API, and link to those methods.
- Add a note or section on running the sample on Linux/macOS, including any platform-specific caveats for device access (camera, microphone) and browser compatibility.
- Ensure links to prerequisites (Teams deployment, enabling users) include Linux/macOS instructions where available.
Communication Services
Quickstart - Make a call to Teams user from a web app
...o-calling/includes/teams-user/teams-user-javascript.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias in the prerequisites section, where enabling Teams Phone features for users is referenced with a link to a PowerShell-based guide, and no Linux/macOS alternatives or parity are mentioned. The rest of the tutorial is cross-platform JavaScript and web-based, with no further Windows-specific instructions or tools.
Recommendations
- Add explicit notes or links for Linux/macOS users on how to enable Teams Phone features, including whether PowerShell Core on non-Windows platforms is supported, or provide Azure Portal GUI instructions if available.
- Clarify whether all prerequisite steps (such as enabling Enterprise Voice) can be completed on Linux/macOS, and if not, document any required workarounds or limitations.
- Where PowerShell is referenced, mention cross-platform compatibility or alternatives.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows-specific console environments (cmd, PowerShell) before Bash when describing where to run commands. However, all commands and code samples use cross-platform .NET CLI and C#, which work on Windows, Linux, and macOS. No Windows-only tools or patterns are present, and Linux/macOS users can follow the instructions without issue.
Recommendations
- List Bash (Linux/macOS) before or alongside cmd/PowerShell when referencing console windows.
- Explicitly state that all commands work on Linux/macOS terminals as well as Windows.
- Consider adding a brief note or example showing the same commands run in a Linux/macOS terminal to reinforce cross-platform support.