Communication Services
2083
Total Pages
1869
Linux-Friendly Pages
214
Pages with Bias
10.3%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
367 issues found
Showing 276-300 of 367 flagged pages
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 demonstrates a Windows bias primarily through its use of Windows-specific tabs and pivots in quickstart links (e.g., '?tabs=windows'), and by referencing Windows-centric technologies (UWP) before or instead of Linux alternatives. There are no explicit Linux or cross-platform examples provided, and Linux tools, patterns, or instructions are absent throughout the page.
Recommendations
- Add Linux-specific tabs and pivots to quickstart links, ensuring parity with Windows examples.
- Include examples and instructions for running Azure Communication Services components on Linux environments.
- Reference cross-platform technologies (such as Electron, .NET MAUI, or web-based solutions) alongside or before Windows-specific ones.
- Explicitly mention Linux compatibility and provide troubleshooting steps for Linux users.
- Ensure that architectural diagrams and feature tables clarify platform support, including Linux.
Create Pull Request
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/call-duration.md
...cles/communication-services/tutorials/call-duration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides platform-specific guidance for Android, iOS, and Windows, but does not mention or provide examples for Linux. This omission suggests a bias towards Windows and mobile platforms, with Linux desktop support not addressed. Additionally, the Windows section is present without any mention of Linux, which may lead Linux developers to feel unsupported.
Recommendations
- Add a Linux-specific section or clarify Linux support status for the Calling SDKs.
- If the SDK supports Linux (e.g., via Electron, .NET Core, or other cross-platform frameworks), provide explicit Linux examples or instructions.
- If Linux is not supported, clearly state this in the documentation to set developer expectations.
- Ensure future documentation includes parity for all major desktop platforms, not just Windows.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/hmac-header-csharp.md
...tion-services/tutorials/includes/hmac-header-csharp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by listing Windows tools (cmd, PowerShell) before Bash when suggesting console environments, and by requiring Visual Studio for development without mentioning cross-platform alternatives. All examples use .NET CLI, which is cross-platform, but the setup instructions and tool recommendations prioritize Windows environments.
Recommendations
- List Bash or terminal first, or mention all environments equally when suggesting where to run commands.
- Explicitly state that Visual Studio Code or JetBrains Rider can be used as cross-platform alternatives to Visual Studio.
- Clarify that the .NET CLI and all code examples work on Windows, Linux, and macOS.
- Add a note that .NET SDK installation instructions are available for all platforms, with a link to official documentation.
- Avoid implying that only Windows tools are supported or required for the tutorial.
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 shows a Windows-first bias in the prerequisites by linking only to Windows-specific Azure CLI installation instructions and using a resource creation link with a Windows tab. There are no Linux or macOS equivalents or mentions for these steps, despite the iOS development context. All other code examples are platform-agnostic (Swift/iOS), but the setup steps assume Windows.
Recommendations
- Provide installation instructions for Azure CLI on Linux and macOS, or link to the cross-platform installation guide.
- Use a neutral or platform-appropriate tab (e.g., macOS, Linux) for resource creation links, or mention all supported platforms.
- Explicitly state that the Azure CLI and other tools are available on multiple platforms, and provide guidance for non-Windows users.
- Review all prerequisite steps to ensure parity for Linux and macOS developers, especially given the iOS development focus.
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
Missing Linux Example
Windows First
Summary
The documentation provides only C#/.NET and Azure Function examples, with all instructions and code samples tailored to the .NET ecosystem. There are no Linux-specific instructions, shell commands, or examples for other platforms or languages. The workflow assumes Visual Studio Code and .NET, which are cross-platform, but there is no explicit mention or demonstration of Linux-specific workflows, nor are there bash or Linux shell equivalents for setup or deployment. The only command-line example is 'dotnet add package', which is cross-platform, but the overall focus is on the Windows/.NET stack. The documentation does not mention or show Linux-specific tools, nor does it provide parity for Linux users in setup or troubleshooting.
Recommendations
- Add explicit instructions for Linux users, such as using bash/zsh for running the Azure Function locally and installing dependencies.
- Include examples for deploying and running the Azure Function using Linux-native tools and workflows (e.g., using Azure CLI in bash, or running with 'func host start' in a Linux terminal).
- Mention and show how to install the .NET SDK and Azure Functions Core Tools on Linux.
- Clarify that Visual Studio Code and .NET are cross-platform, and provide any Linux-specific caveats or troubleshooting tips.
- If possible, provide equivalent examples in other languages or frameworks popular on Linux (e.g., Node.js/Express, Python/Flask) or link to such resources.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/virtual-visits/extend-teams/before-and-after-appointment.md
...al-visits/extend-teams/before-and-after-appointment.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively references Microsoft-centric tools and platforms such as Power Automate, Logic Apps, Microsoft Graph API, and Azure Communication Services. There are no examples or mentions of Linux-native tools, open-source alternatives, or command-line automation (e.g., bash scripting, curl, or Linux scheduling tools). All automation and extensibility examples are built around the Microsoft ecosystem, which is most familiar to Windows users. No Linux-specific guidance or parity is provided.
Recommendations
- Include examples using cross-platform or Linux-native tools, such as demonstrating how to trigger flows or send messages using bash scripts, curl, or Python scripts with Microsoft Graph API.
- Mention and provide guidance for using REST APIs directly from Linux environments, including authentication and example commands.
- Highlight any CLI tools (such as Azure CLI) that are available on Linux and show how they can be used to perform similar tasks.
- Clarify that Power Automate and Logic Apps are web-based and accessible from any OS, and provide explicit instructions for Linux users where relevant.
- Consider referencing open-source workflow automation tools (e.g., n8n, Node-RED) that can integrate with Microsoft services for Linux users.
Communication Services
Calling capabilities for Teams users
...cation-services/concepts/interop/teams-user-calling.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page lists platform support for Teams calling capabilities, with Windows as a primary column and explicit references to Windows tools (e.g., Microsoft Entra user identifier via PowerShell and Microsoft Graph). There is a subtle Windows-first bias: Windows is listed before Android and iOS, and links to PowerShell modules are provided without Linux or cross-platform CLI alternatives. However, the feature matrix includes JavaScript (browser) as the first column, which is cross-platform, and most features are available across all platforms. There are no explicit Linux desktop examples or mentions, and macOS is not referenced outside of iOS (Objective-C).
Recommendations
- Add explicit Linux and macOS desktop support columns to the feature matrix, or clarify their support status.
- Provide cross-platform CLI examples (e.g., Azure CLI, Microsoft Graph API via REST) alongside PowerShell references.
- Avoid listing Windows before other platforms unless there is a technical reason; consider alphabetical or usage-based ordering.
- Mention any platform-specific limitations for Linux/macOS users, if applicable.
- Include links to documentation for Linux/macOS equivalents 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 does not provide any OS-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 using Linux-native tools or shell environments. The documentation refers to the Azure portal and SDKs without mentioning platform-specific differences, but the ordering of examples (C# first, then JavaScript) reflects a subtle Windows/.NET-first bias. There are no PowerShell or Windows tool references, but the absence of Linux CLI or shell examples and the lack of parity for Python/Java SDKs (marked as 'coming soon') may create friction for Linux/macOS users.
Recommendations
- Add Linux/macOS-specific instructions or notes where relevant, especially for CLI or SDK setup.
- Include example code snippets for Python and Java SDKs once available, and consider showing JavaScript (cross-platform) examples first.
- If there are CLI steps (e.g., az CLI), provide explicit examples for Linux/macOS shells.
- Clarify that the Azure portal and SDKs are cross-platform, and highlight any platform-specific caveats if they exist.
- When listing SDKs, avoid ordering that implies Windows/.NET primacy; consider alphabetical or usage-based ordering.
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 exhibits mild Windows bias by presenting Windows-specific instructions and tools before their Linux/macOS equivalents, especially in environment variable setup and references to PowerShell. Azure CLI examples are cross-platform, but installation instructions link to Windows by default. Configuration file examples (app.config/web.config) are .NET/Windows-centric, and there is more detail for Windows users in some sections.
Recommendations
- Provide equal prominence to Linux/macOS instructions, especially in environment variable setup (e.g., show all OS tabs together, not Windows first).
- Include examples for storing connection strings in configuration files commonly used on Linux/macOS (e.g., .env files, systemd environment files).
- Link to cross-platform Azure CLI installation instructions, not just Windows.
- Reduce reliance on PowerShell-specific examples or clearly indicate cross-platform alternatives.
- Add more context/examples for Linux/macOS users in sections that currently focus on Windows tooling or patterns.
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 consoles (cmd, PowerShell) before Bash when describing how to create and run the C# application, but otherwise provides cross-platform instructions using .NET CLI, which works on Windows, Linux, and macOS. No PowerShell-specific commands or Windows-only tools are used, and the examples are generally platform-agnostic.
Recommendations
- List Bash (Linux/macOS) before or alongside Windows consoles (cmd, PowerShell) when describing command-line usage.
- Explicitly state that all .NET CLI commands work on Linux/macOS as well as Windows.
- Provide a short note or section confirming Linux/macOS compatibility for the quickstart steps.
- Consider including screenshots or terminal output from Linux/macOS environments to reinforce parity.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Visual Studio is listed as a required prerequisite without mention of cross-platform alternatives. Package installation is shown using PowerShell syntax, and there is no explicit mention of Linux/macOS editors or development environments. While most CLI commands (dotnet, az) are cross-platform, examples and instructions tend to assume a Windows-centric workflow.
Recommendations
- Mention cross-platform IDEs (e.g., VS Code, JetBrains Rider) alongside Visual Studio in prerequisites.
- Clarify that dotnet and Azure CLI commands work on Linux/macOS, and provide explicit Bash/zsh examples where relevant.
- Show package installation using 'dotnet add package' in a generic console block, not PowerShell-specific.
- Add notes or links for Linux/macOS users regarding environment setup 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 where to run commands, but otherwise provides cross-platform instructions and examples. No PowerShell-specific commands, Windows-only tools, or missing Linux/macOS examples are present.
Recommendations
- List Bash (Linux/macOS) before Windows consoles (cmd, PowerShell) or mention all platforms equally, e.g., 'In a terminal (such as Bash, cmd, or PowerShell)...'
- Explicitly state that all commands are cross-platform and can be run on Linux, macOS, or Windows.
- Add a note confirming Maven and Java instructions work on Linux/macOS as well as Windows.
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. All command-line examples use the cross-platform 'dotnet' CLI, and no Windows-specific tools or patterns are present. There are no missing Linux/macOS examples, but the ordering of terminal examples shows a slight Windows-first bias.
Recommendations
- List Bash (Linux/macOS) first when mentioning terminal options, or present all platforms equally (e.g., 'Command Prompt, PowerShell, or Bash').
- Explicitly state that all commands work on Windows, Linux, and macOS to reassure non-Windows users.
- Consider adding a brief note about prerequisites for Linux/macOS users (e.g., installing .NET SDK).
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias: Windows-specific console environments (cmd, PowerShell) are mentioned first when creating the C# application, and all terminal instructions use generic 'console' syntax without explicit Linux/macOS shell examples. There are no Linux/macOS-specific instructions or troubleshooting notes, and the documentation does not mention platform-specific differences in environment variable setup or execution. However, the use of .NET Core and generic 'dotnet' commands means the instructions are technically cross-platform.
Recommendations
- Explicitly mention Linux/macOS environments alongside Windows (e.g., 'cmd, PowerShell, or Bash/zsh').
- Provide example commands for Linux/macOS shells where relevant (e.g., setting environment variables, running the app).
- Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, path separators, executable permissions).
- Clarify that all instructions apply equally to Linux/macOS, and link to .NET Core installation guides for those platforms.
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 instructing users to create a new C# application. All command-line instructions use generic 'dotnet' commands, which are cross-platform, but there are no explicit Linux/macOS examples or notes about OS-specific differences. No Windows-only tools or PowerShell scripts are present, but the absence of Linux/macOS-specific guidance or troubleshooting may create minor friction for non-Windows users.
Recommendations
- Explicitly mention that all 'dotnet' commands work on Linux and macOS as well as Windows.
- List Bash (Linux/macOS) first or equally alongside cmd/PowerShell when referencing console windows.
- Add notes or examples for common Linux/macOS terminal usage (e.g., export environment variables, file paths).
- Include troubleshooting tips for Linux/macOS users (e.g., permissions, .NET installation differences).
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-specific consoles (cmd, PowerShell) before Bash when describing how to create a new C# application. However, all code examples and instructions are cross-platform and do not rely on Windows-only tools or patterns.
Recommendations
- List Bash (Linux/macOS) first or equally alongside cmd/PowerShell when mentioning console windows.
- Explicitly state that all commands and code samples work on Linux/macOS as well as Windows.
- Consider adding a short note or section confirming Linux/macOS compatibility, especially for .NET Core and MailKit usage.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a slight Windows bias by listing Windows-specific console environments (cmd, PowerShell) before Bash when instructing users to create a new C# application. All terminal instructions use generic 'console window' terminology but mention Windows tools first. There are no explicit Linux/macOS examples or troubleshooting notes, and the .NET code samples are platform-neutral but do not address platform-specific nuances (e.g., certificate stores, firewall rules, or mail client differences) that may affect Linux/macOS users.
Recommendations
- List Bash (Linux/macOS) before or alongside cmd/PowerShell when referencing console windows.
- Add explicit Linux/macOS terminal instructions and screenshots where appropriate.
- Include troubleshooting notes for common Linux/macOS issues (e.g., firewall, SSL certificates, permissions).
- Clarify that .NET Core and SmtpClient work cross-platform, and note any platform-specific caveats.
- Provide links to .NET installation guides for Linux/macOS.
Communication Services
Quickstart - Manage a room call
...cation-services/quickstarts/rooms/manage-rooms-call.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page provides SDK code samples for C#, Java, JavaScript, and Python, with no explicit OS-specific commands, tools, or shell instructions. However, there is a subtle Windows bias in the link to the Rooms quickstart, which uses a 'tabs=windows' parameter and references Azure CLI with a 'platform-azcli' pivot, potentially surfacing Windows-centric instructions first. No PowerShell, CMD, or Windows-only tools are mentioned, and all SDK examples are cross-platform.
Recommendations
- Ensure that quickstart and reference links do not default to Windows tabs or pivots; provide equal visibility for Linux/macOS instructions.
- If CLI instructions are included, explicitly show both Windows and Linux/macOS command examples, or clarify cross-platform compatibility.
- Audit linked pages (such as Rooms quickstart) for Windows-centric instructions and update to provide parity for Linux/macOS users.
- Consider adding a note clarifying that all SDK code samples are cross-platform and not OS-dependent.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation frequently references Windows-specific tools and patterns, such as PowerShell and Windows terminal, and lists them before mentioning generic or cross-platform equivalents. While most commands (git, npm, devtunnel) are cross-platform, the instructions and examples are often framed in a Windows-centric way, which may create friction for Linux/macOS users.
Recommendations
- Explicitly mention Linux/macOS terminals (e.g., Bash, Terminal.app) alongside PowerShell and Windows terminal.
- Provide example commands or screenshots for Linux/macOS environments where appropriate.
- Avoid listing Windows tools first; use neutral language like 'Open a terminal window' instead of 'Open PowerShell, a Windows terminal, or command prompt'.
- Clarify that all commands (git, npm, devtunnel) work on Linux/macOS and provide troubleshooting notes for platform-specific issues if any.
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 does not provide any Linux/macOS-specific instructions or examples. All commands and setup steps are generic to .NET but lack explicit Linux/macOS guidance, such as environment variable setting or editor recommendations.
Recommendations
- List Bash (Linux/macOS) before or alongside cmd/PowerShell when referring to console windows.
- Provide explicit instructions for setting environment variables on Linux/macOS (e.g., export ENTRA_CLIENT_ID=...) and Windows (set ENTRA_CLIENT_ID=...).
- Mention common Linux/macOS editors (e.g., nano, vim, VS Code) alongside Windows editors.
- Add notes about .NET SDK installation for Linux/macOS, including package manager commands.
- Ensure all steps are clearly cross-platform, with any OS-specific caveats highlighted.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation mentions Windows-specific consoles (cmd, PowerShell) before Bash, and does not provide any Linux/macOS-specific instructions, troubleshooting, or environment setup details. All examples use .NET CLI commands, which are cross-platform, but there is no explicit Linux/macOS guidance or parity in environment variable setup, editor usage, or running the application.
Recommendations
- Explicitly mention Linux/macOS consoles (e.g., Terminal, Bash, zsh) alongside Windows consoles.
- Provide instructions for setting environment variables on Linux/macOS (e.g., export AAD_CLIENT_ID=...) as well as Windows (set AAD_CLIENT_ID=...).
- Include notes about compatible text editors for Linux/macOS (e.g., nano, vim, VS Code).
- Add troubleshooting tips for Linux/macOS users (e.g., permissions, .NET SDK installation).
- Show example commands for running the app on Linux/macOS, if any differences exist.
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' reference to non-Windows environments. No explicit Linux/macOS terminal examples or instructions are provided, though the rest of the steps are cross-platform.
Recommendations
- Explicitly mention Linux/macOS terminal options (e.g., Terminal, iTerm2, GNOME Terminal) alongside Windows terminals.
- Provide shell commands in a way that is clearly cross-platform, and clarify that all steps work on Linux/macOS.
- Add troubleshooting notes for Linux/macOS users if there are any platform-specific caveats.
- Consider listing Linux/macOS terminal options first or equally with Windows options to avoid implicit prioritization.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is primarily focused on .NET and C#, which are cross-platform, but it exhibits minor Windows bias by mentioning Windows console environments (cmd, PowerShell) before Bash and omitting explicit Linux/macOS-specific instructions or troubleshooting. All command-line examples use 'dotnet', which works on Linux, but there are no Linux/macOS-specific notes or examples, and no mention of platform-specific issues (e.g., permissions, package managers).
Recommendations
- Explicitly mention Linux/macOS compatibility in the prerequisites and setup sections.
- Provide Linux/macOS-specific instructions or troubleshooting tips (e.g., using Bash, handling permissions, installing .NET Core on Linux).
- List Bash or Linux terminal first or equally alongside Windows options when referencing console environments.
- Include a note about running the sample code on Linux/macOS, and link to platform-specific .NET installation guides.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation mentions Windows-specific consoles (cmd, PowerShell) before Bash, and all example commands are generic (dotnet CLI) but do not provide any Linux/macOS-specific guidance or troubleshooting. There are no explicit Windows-only tools, but the ordering and lack of Linux/macOS details suggest a subtle Windows-first bias.
Recommendations
- List Bash (Linux/macOS) before or alongside cmd/PowerShell when mentioning console windows.
- Add notes or troubleshooting tips for Linux/macOS users, such as permissions, path separators, or common issues with dotnet on those platforms.
- Explicitly confirm that all commands and steps work on Linux/macOS, or provide platform-specific instructions if needed.
- Include a brief section or link for installing .NET on Linux/macOS, as the current link is generic.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page is largely cross-platform, but there is a minor Windows bias in the section describing how to create a new C# application. It lists Windows-specific consoles (cmd, PowerShell) before Bash, which is more common on Linux/macOS. All commands shown are cross-platform and there are no Windows-only tools or patterns. No PowerShell-specific examples or Windows-only instructions are present.
Recommendations
- List Bash (Linux/macOS) first when mentioning console options, or clarify that all commands work equally in Bash, cmd, and PowerShell.
- Explicitly mention Linux/macOS terminals (e.g., Terminal, iTerm) alongside Windows consoles.
- Add a note confirming that the .NET SDK and all commands are supported on Linux and macOS.
- Provide troubleshooting tips for Linux/macOS users if there are known platform-specific issues.