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 101-125 of 367 flagged pages
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/resources/troubleshooting/voice-video-calling/audio-issues/incoming-audio-low-volume.md
...ideo-calling/audio-issues/incoming-audio-low-volume.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by specifically referencing Windows volume mixer and app volume settings, including a screenshot of the Windows volume mixer, without providing equivalent guidance or visuals for Linux or macOS systems. No Linux-specific tools, commands, or troubleshooting steps are mentioned, and the only OS explicitly referenced is Windows.
Recommendations
- Add equivalent instructions and screenshots for checking and adjusting audio settings on popular Linux desktop environments (e.g., GNOME, KDE) and macOS.
- Mention Linux and macOS system volume controls and app-specific volume settings where applicable, not just Windows.
- Use neutral language such as 'on your operating system' or 'on Windows, Linux, or macOS' rather than only referencing Windows.
- Provide links or references to official documentation for audio troubleshooting on Linux and macOS.
- If including screenshots, provide them for all major platforms or use generic diagrams where possible.
Create Pull Request
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/resources/troubleshooting/voice-video-calling/audio-issues/speaker-issue.md
...ting/voice-video-calling/audio-issues/speaker-issue.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by specifically mentioning Windows volume mixer and app volume settings, including a screenshot of the Windows volume mixer, without providing equivalent guidance or screenshots for Linux or macOS systems. There are no Linux-specific troubleshooting steps or references to common Linux audio tools or settings, and Windows is the only OS called out by name in mitigation steps.
Recommendations
- Add equivalent troubleshooting instructions for Linux (e.g., checking PulseAudio or PipeWire volume controls, using pavucontrol, alsamixer, or system sound settings).
- Include screenshots of audio settings on popular Linux desktop environments (e.g., GNOME, KDE) alongside the Windows example.
- Mention macOS system sound settings and provide a screenshot or description for parity.
- Avoid singling out Windows in mitigation steps; instead, provide OS-agnostic instructions or parallel guidance for all major platforms.
- Reference common Linux and macOS audio troubleshooting tools where appropriate.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/resources/troubleshooting/voice-video-calling/references/how-to-collect-browser-verbose-log.md
...lling/references/how-to-collect-browser-verbose-log.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation provides only Windows-specific instructions and command-line examples for collecting verbose logs from Edge and Chrome browsers. It references Windows file paths, executable locations, and omits any mention of Linux or macOS equivalents. No Linux or cross-platform examples are provided.
Recommendations
- Add Linux and macOS command-line examples for launching Edge and Chrome with the same logging flags.
- Specify typical Linux and macOS paths for browser executables (e.g., /usr/bin/google-chrome, /Applications/Google Chrome.app/Contents/MacOS/Google Chrome).
- Describe where log files are stored on Linux and macOS (e.g., the --user-data-dir path and resulting log file location).
- Mention any platform-specific differences in logging behavior or file permissions.
- Present examples for all major platforms side-by-side or in separate sections to ensure parity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/resources/troubleshooting/voice-video-calling/references/how-to-collect-diagnostic-audio-recordings.md
...ferences/how-to-collect-diagnostic-audio-recordings.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates Windows bias by providing build instructions and prerequisites only for Windows (e.g., Visual Studio 2022, Windows-specific Chromium build instructions, and the .exe extension for the unpack_aecdump tool). There are no instructions or examples for building or running the tool on Linux or macOS, nor are any cross-platform alternatives mentioned.
Recommendations
- Add Linux and macOS build instructions for unpack_aecdump, including required dependencies and example commands.
- Mention cross-platform prerequisites (e.g., gcc/clang, Python 3, depot_tools) and link to the relevant Chromium/Linux/macOS build guides.
- Show example commands for running unpack_aecdump on Linux/macOS (e.g., ./unpack_aecdump audio_debug.5.aecdump).
- Clarify that unpack_aecdump can be built and used on platforms other than Windows, if applicable.
- Ensure screenshots and file paths are not Windows-specific, or provide equivalents for other platforms.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/email-resource-management.md
...nication-services/samples/email-resource-management.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell and Windows-specific tools in both the main content and code examples. PowerShell commands are provided for resource cleanup, while Linux/bash equivalents are missing. The structure and included files also suggest a preference for PowerShell and Windows-centric workflows.
Recommendations
- Provide equivalent bash/Azure CLI examples for all PowerShell commands, especially for resource cleanup and deletion.
- Ensure that Linux/macOS users are explicitly supported by including bash syntax and instructions.
- Reorganize the documentation to present cross-platform (CLI/bash) examples before or alongside PowerShell examples, rather than defaulting to Windows tools.
- Clearly indicate which commands are platform-specific and offer alternatives where possible.
- Review included files to ensure that Linux and macOS scenarios are as thoroughly documented as Windows/PowerShell scenarios.
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
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation shows evidence of Windows bias. The prerequisites link to resource creation instructions with a '?tabs=windows' parameter, suggesting Windows-first guidance. The sample project is .NET-based, which is cross-platform, but there are no explicit Linux or macOS instructions or examples. No Linux-specific tools or shell commands are mentioned, and the only run command shown is 'dotnet run' without clarification for non-Windows users. The documentation does not mention Linux equivalents or potential platform-specific considerations.
Recommendations
- Provide explicit Linux/macOS instructions or confirm cross-platform compatibility for all steps, especially for running the sample and configuring prerequisites.
- Include Linux/macOS tabs or sections in prerequisite links and setup instructions, not just Windows.
- Mention any platform-specific dependencies or troubleshooting tips for Linux users.
- Clarify that 'dotnet run' works on Linux/macOS if .NET SDK is installed, and provide installation links for those platforms.
- If using dev tunnels or other tools, note their cross-platform support and provide alternative commands if necessary.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/call-automation-azure-openai-js.md
...es/samples/includes/call-automation-azure-openai-js.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell, Windows terminal, and command prompt as the primary environments for running commands, with only a vague mention of 'the equivalent' for other platforms. There are no explicit Linux or macOS terminal examples, nor are platform-specific differences addressed. The instructions and examples assume familiarity with Windows tools and workflows, potentially leaving Linux users with ambiguity.
Recommendations
- Explicitly mention Linux/macOS terminals (e.g., Bash, Terminal.app) alongside Windows environments.
- Provide command examples for Linux/macOS where differences exist (e.g., environment variable setup, file paths).
- Avoid referencing PowerShell or Windows tools first; instead, use neutral language like 'Open a terminal (PowerShell, Command Prompt, Bash, etc.)'.
- Add notes or sections highlighting any platform-specific steps or caveats.
- Ensure all referenced quickstart links and documentation pivots include Linux/macOS tabs/examples.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/email-resource-management-azurecli-powershell.md
...ludes/email-resource-management-azurecli-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell scripting throughout all examples, including variable initialization, function definitions, and control flow. Prerequisite checks and installation links are Windows-centric, referencing PowerShell and Windows-specific Azure CLI installation instructions. There are no Bash, shell, or Linux-native script examples provided, nor any mention of how to adapt the workflow for Linux or macOS environments.
Recommendations
- Provide equivalent Bash or shell script examples for all PowerShell code blocks, showing how to perform the same automation tasks on Linux/macOS.
- Include installation instructions and prerequisite checks for Azure CLI and PowerShell on Linux and macOS, not just Windows.
- When referencing command-line usage, clarify cross-platform compatibility and note any differences in syntax or environment setup.
- Consider restructuring the documentation to present platform-agnostic Azure CLI commands first, followed by platform-specific scripting options (PowerShell for Windows, Bash for Linux/macOS).
- Explicitly mention that Azure CLI works on all major platforms and provide links to installation guides for each.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/ui-maui.md
...les/communication-services/samples/includes/ui-maui.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation prioritizes Windows and Mac environments, specifically referencing Visual Studio for Mac/Windows and requiring Windows-specific tools (e.g., GitBash, WSL) to run shell scripts on Windows. There is no mention of native Linux support or instructions for running the sample on Linux, despite .NET MAUI's partial Linux compatibility and the use of shell scripts that would naturally run on Linux.
Recommendations
- Add explicit instructions for running the sample on Linux, including prerequisites (e.g., supported distributions, .NET SDK installation, and any required dependencies).
- Provide Linux-specific guidance for running shell scripts, rather than only referencing GitBash or WSL for Windows users.
- Clarify whether Visual Studio Code or other cross-platform IDEs can be used on Linux, and provide relevant instructions if supported.
- Ensure that all examples and steps are presented for Windows, Mac, and Linux equally, or clearly state platform limitations if Linux is not supported.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/integrate-azure-communication-services-with-copilot-studio.md
...grate-azure-communication-services-with-copilot-studio.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exhibits Windows bias by referencing Windows-specific tabs (e.g., '?tabs=windows') in prerequisite links, mentioning Windows tools (such as 'dev tunnels') without Linux alternatives, and omitting any Linux-specific instructions or examples. There are no explicit Linux or cross-platform setup instructions, and all code samples are in C# with no mention of how to run or adapt them on Linux.
Recommendations
- Provide Linux-specific instructions or tabs alongside Windows in prerequisite links and setup steps.
- Mention and link to Linux-compatible alternatives for tools like 'dev tunnels' (e.g., 'ngrok', 'localtunnel', or Azure Dev Tunnels for Linux if supported).
- Clarify that the sample code can be run on Linux (e.g., using .NET Core/SDK on Linux) and provide any necessary instructions for Linux users.
- Ensure that all referenced documentation and quickstarts include Linux tabs or sections.
- Explicitly state cross-platform compatibility where applicable, and test the sample on Linux to confirm parity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/building-app-start.md
...communication-services/tutorials/building-app-start.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. The Node.js, nvm, and npm installation instructions and examples are Windows-centric, referencing a Windows-specific tutorial and using PowerShell commands. There are no equivalent Linux or macOS instructions or shell examples. File path examples and screenshots use Windows conventions (e.g., C:\Users\Documents\ACS\CallingApp), and there is no mention of Linux or macOS alternatives for common setup steps.
Recommendations
- Provide installation instructions and examples for Node.js, nvm, and npm for Linux and macOS, including shell/bash commands.
- Include file path examples using Linux/macOS conventions (e.g., ~/ACS/CallingApp) alongside Windows examples.
- Reference cross-platform documentation for nvm and npm, not just Windows-specific guides.
- Add screenshots or notes indicating how steps look on Linux/macOS, especially for Visual Studio Code and terminal usage.
- Explicitly state that the tutorial is cross-platform and highlight any OS-specific differences where relevant.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/chat-app-teams-embed.md
...mmunication-services/tutorials/chat-app-teams-embed.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Microsoft-centric tools (Visual Studio Code, Microsoft Teams Toolkit) and workflows, without mentioning or providing parity for Linux development environments or alternatives. All examples and tool recommendations assume a Windows or Microsoft 365 developer account context, with no explicit guidance for Linux users. There are no Linux-specific instructions, nor is there mention of cross-platform considerations or alternatives to the Microsoft Teams Toolkit for Linux.
Recommendations
- Explicitly state that Visual Studio Code and the Teams Toolkit are available on Linux and provide installation instructions for Linux users.
- Include command-line alternatives (e.g., using Yeoman generators, CLI tools, or manual setup) for users who may not use Visual Studio Code or prefer terminal-based workflows.
- Mention and link to any Linux-specific prerequisites or troubleshooting tips (such as package dependencies, Node.js installation on Linux, or permissions issues).
- Ensure that all screenshots and step-by-step instructions are not Windows-specific, or provide Linux equivalents where UI or paths differ.
- Clarify that a Microsoft 365 developer account can be used from any OS, and provide any relevant notes for Linux users (e.g., browser compatibility, Teams web app usage).
- If any features or tools are not supported on Linux, clearly state this and suggest workarounds or alternatives.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/collecting-user-feedback/collecting-user-feedback.md
...s/collecting-user-feedback/collecting-user-feedback.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias by referencing Azure services and tools (which are Microsoft-centric), and by omitting explicit Linux/macOS-specific instructions or examples. All setup and command-line instructions are platform-neutral in syntax (e.g., npm, Node.js), but there is no mention of Linux-specific considerations, nor are there any examples or troubleshooting tips for Linux users. The Azure portal and tooling are referenced without alternatives or parity notes for Linux users. The guide does not provide parity for Linux environments, such as systemd service setup, SELinux/AppArmor notes, or Linux file permissions, nor does it mention cross-platform testing or deployment.
Recommendations
- Add explicit instructions or notes for Linux/macOS users, such as how to install Node.js and npm on Ubuntu, Fedora, or macOS.
- Include Linux-specific examples for environment variable setup (e.g., using export in bash/zsh) and running the server as a background service (e.g., using systemd or pm2).
- Mention and link to Azure CLI and azcopy, which are cross-platform, as alternatives to the Azure portal for resource creation and management.
- Provide troubleshooting tips for common Linux issues (e.g., file permissions, firewall configuration, SELinux/AppArmor).
- Clarify that all code and instructions are cross-platform unless otherwise noted, and explicitly state any Windows-only steps.
- Consider adding a section or appendix with Linux/macOS-specific deployment best practices.
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
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation consistently references Visual Studio Code and its Azure Functions extension as the primary (and only) development environment, with all instructions and links tailored to this workflow. There are no explicit examples or instructions for Linux-specific tools, terminal commands, or alternative editors. The use of 'F5' for running the function and right-click context menu actions are more familiar to Windows users. There is no mention of running or deploying the function using command-line tools (e.g., Azure CLI, func CLI) that are cross-platform, nor are there Linux/macOS-specific instructions or screenshots.
Recommendations
- Add explicit instructions and examples for setting up and running the function using cross-platform command-line tools such as Azure Functions Core Tools (func CLI) and Azure CLI.
- Include Linux/macOS-specific instructions for running and deploying the function, such as terminal commands for starting the function locally and deploying to Azure.
- Provide alternative instructions for users who prefer editors other than Visual Studio Code, or clarify that all steps are cross-platform if that is the case.
- Avoid referencing only GUI-based actions (e.g., 'right-click' in VS Code, 'F5') and provide equivalent command-line alternatives.
- Add screenshots or terminal output examples from Linux/macOS environments to demonstrate parity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/twilio-to-acs-chat-android-tutorial.md
...orials/includes/twilio-to-acs-chat-android-tutorial.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by recommending Visual Studio (Windows-centric IDE) as the only development environment, providing only PowerShell-based package installation instructions, and omitting Linux alternatives (e.g., VS Code, dotnet CLI on Linux, Bash examples). There are no explicit references to Linux tools or workflows, and all command-line examples use Windows-first syntax.
Recommendations
- Include instructions for installing the Azure Communication Services Chat SDK using Bash (e.g., 'dotnet add package Azure.Communication.Chat') and clarify that this works cross-platform.
- Mention and provide guidance for using cross-platform editors such as Visual Studio Code or JetBrains Rider, in addition to Visual Studio.
- Add explicit notes that the SDK and CLI commands work on Linux and macOS, not just Windows.
- Where PowerShell is used, also provide Bash equivalents or clarify that the command is platform-agnostic.
- Add a section or callout for Linux/macOS developers, including any prerequisites or troubleshooting tips specific to those platforms.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/twilio-to-acs-chat-csharp-tutorial.md
...torials/includes/twilio-to-acs-chat-csharp-tutorial.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by recommending Visual Studio as the sole development environment, using PowerShell for package installation, and omitting Linux/macOS equivalents or cross-platform alternatives. All command-line and setup instructions assume a Windows environment, and there are no references to Linux tools (e.g., bash, dotnet CLI on Linux, VS Code) or guidance for non-Windows users.
Recommendations
- Include instructions for installing the SDK using the dotnet CLI on Linux/macOS (e.g., 'dotnet add package Azure.Communication.Chat' in bash/zsh).
- Mention cross-platform editors like Visual Studio Code and JetBrains Rider as alternatives to Visual Studio.
- Clarify that Azure CLI commands work on Linux/macOS and provide example shell commands.
- Add a 'Platform compatibility' note in prerequisites, explicitly stating support for Windows, Linux, and macOS.
- Provide troubleshooting tips or links for common issues on Linux/macOS (e.g., certificate errors, environment setup).
- Ensure all code and command snippets are platform-agnostic or provide platform-specific variants where necessary.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/twilio-to-acs-chat-js-tutorial.md
...s/tutorials/includes/twilio-to-acs-chat-js-tutorial.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows bias in the prerequisites section. It provides a link and instructions specifically for installing the Azure CLI on Windows, with no mention of Linux or macOS equivalents. The resource creation link also includes a 'tabs=windows' parameter, suggesting a Windows-centric approach. There are no Linux-specific instructions or examples, and no mention of cross-platform compatibility for CLI commands.
Recommendations
- Provide installation instructions or links for Azure CLI on Linux and macOS alongside Windows.
- Remove or generalize the 'tabs=windows' parameter in resource creation links, or add equivalent links for Linux/macOS.
- Explicitly state that the CLI commands are cross-platform, or provide platform-specific notes where differences exist.
- Include a short note in the prerequisites clarifying that all steps and commands work on Linux, macOS, and Windows, or highlight any platform-specific considerations.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/twilio-to-acs-video-ios-tutorial.md
...tutorials/includes/twilio-to-acs-video-ios-tutorial.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias in the prerequisites and setup sections. It provides only Windows-specific instructions and links for installing the Azure CLI, and references the Azure Portal with a Windows tab in the resource creation link. There are no Linux or macOS equivalents or instructions for these steps, despite the rest of the guide being platform-agnostic and focused on iOS development.
Recommendations
- Provide installation instructions and links for Azure CLI on Linux and macOS, not just Windows.
- Use neutral or multi-platform links for resource creation and CLI installation (e.g., tabs for Windows, Linux, macOS).
- Explicitly mention that the Azure CLI and other tools are available on multiple platforms, and link to the general installation guide.
- Ensure all command-line examples are platform-agnostic or provide platform-specific alternatives where necessary.
- Review the documentation for any other Windows-centric language or links and update them to be inclusive of Linux and macOS users.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/virtual-visits.md
...les/communication-services/tutorials/virtual-visits.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows/Microsoft ecosystem bias by exclusively referencing Microsoft 365, Teams, Bookings, Outlook, and Azure tools, with all examples and workflows centered around these services. There are no mentions of Linux, cross-platform alternatives, or non-Microsoft scheduling, communication, or deployment tools. The documentation assumes usage of Microsoft web applications and Azure portal, which are optimized for Windows environments, and does not provide parity guidance for Linux users.
Recommendations
- Add explicit notes on cross-platform compatibility for all web-based tools (e.g., clarify that Bookings, Teams, and Azure portal are accessible from Linux browsers).
- Include examples or guidance for deploying and managing the sample application using Linux command-line tools (e.g., Azure CLI on Linux, Bash scripts) in addition to or instead of ARM templates via the portal.
- Reference or link to documentation for using Teams and Bookings on Linux (e.g., Teams web client, supported browsers, known limitations).
- Provide alternative approaches for scheduling and notifications that could be integrated with non-Microsoft or open-source tools, or at least acknowledge their existence.
- Ensure that screenshots and walkthroughs do not assume a Windows environment (e.g., avoid showing only Outlook/Bookings in Windows UI, clarify that the experience is browser-based and OS-agnostic where possible).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/virtual-visits/sample-builder.md
...on-services/tutorials/virtual-visits/sample-builder.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation is heavily oriented around Microsoft and Azure tools, with all deployment and configuration steps occurring via the Azure Portal, Microsoft 365 Bookings, and Microsoft Teams. There are no explicit references to Linux tools, command-line interfaces, or cross-platform deployment patterns. All screenshots and instructions assume the use of the Azure Portal (a web UI), and all integration examples are with Microsoft products. There are no examples or guidance for deploying or managing the sample using Linux-native tools, CLI, or automation outside the Microsoft ecosystem.
Recommendations
- Add instructions for deploying the sample using Azure CLI and Azure Resource Manager templates from a Linux terminal.
- Provide examples for managing and configuring the application using cross-platform tools (e.g., Azure CLI, azcopy, curl) rather than only through the Azure Portal.
- Include notes or sections on how to automate deployment and integration steps using shell scripts or Linux-native tools.
- Mention and link to any relevant Linux or open-source tools that can be used for monitoring, deployment, or integration.
- Ensure parity in screenshots and instructions by including examples from both the Azure Portal and command-line interfaces accessible from Linux and macOS.
Communication Services
Automate email resource management
...nication-services/samples/email-resource-management.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page provides multiple PowerShell-based examples for resource cleanup, with only one Azure CLI example (for deleting the Communication Services resource). The Email Communication Services and Domain resource deletion steps are shown exclusively with PowerShell commands, which are Windows-centric. There are no Linux/macOS CLI equivalents or guidance for these tasks, and PowerShell examples are presented before or instead of cross-platform alternatives.
Recommendations
- Add Azure CLI examples for deleting Email Communication Services and Domain resources, ensuring Linux/macOS users can follow the same steps.
- Clearly indicate which commands are Windows-only and provide cross-platform alternatives where possible.
- Reorder examples to present cross-platform (Azure CLI) commands first, or group them by platform with equal prominence.
- Include notes or links for installing Azure CLI/PowerShell on non-Windows platforms if needed.
Communication Services
Teams Phone extensibility Troubleshooting
...terop/tpe/teams-phone-extensibility-troubleshooting.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a notable Windows bias in the troubleshooting steps for resolving Microsoft Entra App permission issues. Only PowerShell commands are provided for administrative tasks, with no mention of equivalent steps for Linux/macOS users (e.g., using Azure CLI, Bash, or cross-platform tools). The instructions assume access to PowerShell and Windows-specific modules, potentially excluding or complicating the process for non-Windows administrators.
Recommendations
- Provide equivalent Azure CLI or Microsoft Graph API examples for Linux/macOS users.
- Explicitly state whether PowerShell Core (pwsh) on Linux/macOS is supported for these commands, and provide installation guidance if so.
- Reorder examples to present cross-platform solutions first, or in parallel with Windows-specific instructions.
- Add troubleshooting steps for common Linux/macOS environments, including authentication and module installation.
Communication Services
Teams Phone extensibility overview
...epts/interop/tpe/teams-phone-extensibility-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a moderate Windows bias, primarily in the prerequisites and emergency calling sections. Licensing and policy management for Teams Phone are described using Windows-centric tools such as the TAC portal and PowerShell cmdlets, with no mention of Linux/macOS alternatives or cross-platform equivalents. Windows tools are referenced first and exclusively for administrative tasks, potentially creating friction for Linux/macOS users who may need to manage Teams Phone resources.
Recommendations
- Provide explicit guidance for Linux/macOS administrators, such as Azure CLI, Microsoft Graph API, or web-based alternatives for Teams Phone provisioning and policy management.
- Include examples or references for managing Teams Phone features using cross-platform tools, not just PowerShell or TAC portal.
- Clarify which administrative tasks can be performed via browser-based portals (which are OS-agnostic) and which require Windows-only tools, and offer alternatives where possible.
- Add notes or links to documentation on using Microsoft Graph API for Teams administration, which is accessible from any OS.
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
Missing Linux Example
Windows Tools
Summary
The documentation references Windows as a supported platform for the client-side SDKs, listing it before Linux, and does not mention Linux as a supported platform. Additionally, policy configuration references are linked to PowerShell modules (which are Windows-centric), with no mention of Linux/macOS equivalents or alternatives. No Linux-specific guidance, examples, or parity is provided.
Recommendations
- Explicitly mention Linux as a supported platform if applicable, or clarify its status.
- Provide examples or references for configuring Teams policies using cross-platform tools (e.g., Microsoft Graph API) instead of only PowerShell.
- Ensure that platform support lists include Linux/macOS where relevant, and avoid listing Windows before other platforms unless there is a technical reason.
- Add Linux/macOS-specific guidance or troubleshooting notes if there are differences.
Communication Services
Microsoft Teams shared line appearance
...pts/interop/teams-user/teams-shared-line-appearance.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a moderate Windows bias by referencing Windows-specific tools (Teams PowerShell) for delegate assignment and listing Windows as a platform in the SDK support note. Linux/macOS alternatives for delegate assignment are not mentioned, and PowerShell is referenced before any cross-platform or GUI options. However, some tasks can be completed using the Teams client, which is available cross-platform.
Recommendations
- Explicitly mention and provide Linux/macOS-compatible methods for assigning delegates, such as using Teams web client or cross-platform CLI tools if available.
- Clarify whether Teams PowerShell can be used on Linux/macOS (via PowerShell Core), and provide installation and usage instructions for those platforms.
- Avoid listing Windows tools or platforms first unless they are the only supported option; otherwise, present cross-platform options equally.
- Add examples or links for performing delegate assignment on Linux/macOS.