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 276-300 of 656 flagged pages
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/email-detect-sensitive-content.md
...ion-services/samples/email-detect-sensitive-content.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits Windows bias by referencing Windows-specific tools and patterns first (e.g., 'cmd', 'PowerShell', registry queries), providing examples that assume a Windows environment (such as using 'reg query' to check .NET installation), and omitting equivalent Linux instructions or examples. The environment setup and troubleshooting steps are tailored to Windows users, with no mention of Linux alternatives for verifying prerequisites or running commands.
Recommendations
- Provide Linux equivalents for all Windows-specific commands, such as instructions for checking .NET installation (e.g., 'dotnet --info' or package manager queries).
- Mention Linux and macOS terminal options alongside Windows ones (e.g., 'cmd, PowerShell, or Bash').
- Include troubleshooting steps for Linux environments, such as verifying environment variables and .NET installation paths.
- Ensure screenshots and navigation instructions are OS-agnostic or include notes for Linux users where UI or workflow differs.
- Review all code and setup instructions to confirm they work cross-platform, and explicitly state platform compatibility where relevant.
Create Pull Request
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 for automation, referencing Windows-specific installation links for both Azure PowerShell and Azure CLI, and omitting any Linux or cross-platform shell examples (such as Bash). All code samples are written in PowerShell, with no mention of how to perform the same tasks on Linux or macOS. The prerequisite checks and scripting patterns assume a Windows environment, potentially alienating users on other platforms.
Recommendations
- Provide equivalent Bash shell examples for all automation steps, demonstrating how to use Azure CLI commands in a cross-platform manner.
- Include installation instructions and links for Azure PowerShell and Azure CLI for Linux and macOS, not just Windows.
- Clearly state that Azure CLI is cross-platform and can be used from Bash, zsh, or other shells, and show how to check prerequisites on Linux/macOS (e.g., 'az --version', 'pwsh --version').
- Offer guidance on running scripts in non-Windows environments, such as using Bash scripts or PowerShell Core (pwsh) on Linux/macOS.
- Consider restructuring the documentation so that Windows and Linux/macOS instructions/examples are presented side-by-side or in separate tabs for parity.
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 page exhibits a Windows bias by referencing PowerShell, Windows terminal, and command prompt as the primary environments for running commands, while only mentioning 'the equivalent' for other platforms without providing explicit Linux or macOS examples. The instructions for running the app locally specifically mention opening a PowerShell window and do not provide alternative terminal instructions for Linux or macOS users. There are no Linux-specific commands, tools, or screenshots, and the documentation does not address platform differences in detail.
Recommendations
- Explicitly mention Linux and macOS terminals (e.g., Bash, Terminal.app) alongside PowerShell and Windows terminal.
- Provide example commands and instructions for Linux/macOS environments, including any platform-specific considerations (such as environment variable syntax, file paths, or permissions).
- Avoid using Windows-centric language like 'PowerShell window' as the default; instead, use neutral terms like 'terminal window' and provide platform-specific notes as needed.
- Include screenshots or code blocks showing the process on Linux/macOS if possible.
- Review all referenced quickstart links and ensure they do not default to Windows tabs or pivots unless alternatives are equally visible.
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
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing PowerShell examples for resource cleanup and management, referencing PowerShell-specific commands and patterns, and omitting equivalent Linux/bash examples. The CLI example is present, but PowerShell commands are given more prominence and detail, and there is no explicit mention of Linux shell usage or alternative commands for non-Windows platforms.
Recommendations
- Add bash/Linux shell equivalents for all PowerShell commands, especially for resource deletion and domain management.
- Ensure that Azure CLI examples are presented before or alongside PowerShell examples to avoid Windows-first ordering.
- Clarify which commands are platform-agnostic and which are Windows-specific, and provide guidance for Linux/macOS users.
- Include a section or pivot for Linux users, demonstrating how to perform the same tasks using bash or other common Linux tools.
- Review included files to ensure parity in example coverage for all platforms.
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 primarily through its prerequisites and setup instructions. It recommends installing Visual Studio (Windows-centric), and the only package installation example is given in PowerShell, with no mention of Linux alternatives (such as dotnet CLI on bash or VS Code). There are no references to Linux tools, editors, or cross-platform development environments, and no explicit Linux setup instructions or examples.
Recommendations
- Add instructions for installing the .NET SDK and Azure Communication Services Chat package using bash/zsh on Linux and macOS (e.g., 'dotnet add package' in a terminal).
- Mention and provide examples for using VS Code or JetBrains Rider as cross-platform IDEs, in addition to Visual Studio.
- Clarify that the Azure CLI and .NET SDK are cross-platform, and provide explicit steps for Linux/macOS users (including installation links).
- Where PowerShell is used, also show the equivalent bash/zsh command for Linux/macOS.
- Include troubleshooting notes or environment setup tips for Linux users (e.g., permissions, dependency installation).
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 page exhibits Windows bias by exclusively referencing Windows tools and workflows. The prerequisites require Visual Studio (Windows-centric), and the only package installation example uses PowerShell syntax. There are no Linux or cross-platform alternatives mentioned for development environment setup, package installation, or tooling. The documentation does not provide parity for Linux users, such as instructions for using VS Code, .NET CLI on Linux, or alternative package managers.
Recommendations
- Provide Linux and macOS equivalents for all setup steps, including installation instructions for .NET SDK and package management using the dotnet CLI in bash/zsh.
- Mention cross-platform editors like VS Code or JetBrains Rider alongside Visual Studio.
- Replace or supplement PowerShell examples with bash/zsh equivalents (e.g., 'dotnet add package Azure.Communication.Chat' in a bash terminal).
- Clarify that Azure CLI commands work on all platforms and provide explicit instructions for Linux/macOS installation.
- Add a section or callout for Linux/macOS users, listing required dependencies and setup steps.
- Ensure all code snippets and instructions are platform-agnostic unless a platform-specific difference is necessary.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/tpe/teams-phone-extensibility-answer-teams-calls.md
...ts/tpe/teams-phone-extensibility-answer-teams-calls.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by providing only PowerShell commands for critical setup steps (such as creating Teams resource accounts and associating them with Communication Services), referencing Windows-centric tools (PowerShell, Set-CsOnlineApplicationInstance), and omitting equivalent Linux/bash/CLI instructions. The DevTunnel setup also uses PowerShell syntax without clarifying cross-platform support. No Linux or macOS alternatives are mentioned, and the workflow assumes familiarity with Windows tooling.
Recommendations
- Provide equivalent bash/CLI commands for all PowerShell examples, especially for Teams resource account creation and association steps.
- Explicitly state whether the PowerShell commands can be run on Linux/macOS via PowerShell Core, or provide alternatives using Azure CLI, Microsoft Graph API, or REST where possible.
- For DevTunnel setup, clarify if the tool and commands are cross-platform, and if so, provide examples in both PowerShell and bash syntax.
- Add a note in the prerequisites about platform compatibility for all required tools, and link to installation instructions for Linux/macOS users.
- Where only Windows tooling is available, acknowledge this limitation and suggest workarounds or alternatives for non-Windows users.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-faq.md
.../concepts/interop/tpe/teams-phone-extensibility-faq.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell cmdlets and the Teams Admin Center (TAC) portal as the only methods for configuring emergency calling policies, without mentioning or providing Linux/macOS alternatives. There are no examples or guidance for Linux users, and the documentation assumes the use of Windows-centric tools for administration.
Recommendations
- Explicitly mention if Teams administration and configuration tasks (such as policy assignment) can be performed using cross-platform tools or REST APIs, and provide links or examples for Linux/macOS users.
- If PowerShell is required, clarify whether PowerShell Core (pwsh), which is cross-platform, is supported and provide installation instructions for Linux/macOS.
- Include alternative command-line or scripting examples for Linux environments, or acknowledge any current limitations for non-Windows users.
- Reference the Teams Admin Center web portal as a cross-platform option, if applicable, and clarify any features that are only available on Windows.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-overview.md
...epts/interop/tpe/teams-phone-extensibility-overview.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its exclusive mention of Windows-specific tools and patterns, such as PowerShell and the Teams Admin Center (TAC portal), for administrative tasks. There are no examples or guidance for performing equivalent operations on Linux or cross-platform environments. The documentation assumes the use of Windows-centric administration without acknowledging or providing alternatives for Linux users.
Recommendations
- Provide equivalent command-line examples for Linux environments, such as using Azure CLI, Microsoft Graph API, or Bash scripts, alongside or instead of PowerShell.
- When referencing administrative tools like the TAC portal or PowerShell, clarify if these are available cross-platform or provide links to cross-platform alternatives.
- Explicitly mention any platform limitations or requirements for the administrative steps, and offer guidance for Linux-based administrators where possible.
- Include a section or callout that addresses cross-platform support and best practices for both Windows and Linux environments.
- Review all prerequisite and configuration steps to ensure they are not exclusively tailored to Windows, and update them to be inclusive of Linux workflows.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/virtual-visits/plan-user-experience.md
...oncepts/interop/virtual-visits/plan-user-experience.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation references the Teams Admin Center and PowerShell as the primary methods for learning and configuring Teams meeting settings, without mentioning Linux-compatible alternatives or command-line tools. There are no examples or guidance for Linux users, and Windows tools are presented as the default or only options.
Recommendations
- Include equivalent instructions for Linux users, such as using the Teams web interface or cross-platform CLI tools where available.
- Mention that PowerShell is primarily a Windows tool and provide alternatives (e.g., Azure CLI, Microsoft Graph API) that are cross-platform.
- When referencing the Teams Admin Center, clarify that it is web-based and accessible from any OS, not just Windows.
- Provide explicit Linux/macOS examples or note when a tool or method is Windows-only.
- Encourage the use of platform-agnostic APIs (like Microsoft Graph) for configuration and management tasks.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-troubleshooting.md
...terop/tpe/teams-phone-extensibility-troubleshooting.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing troubleshooting steps and code examples that assume the use of Windows-specific tools (Visual Studio, NuGet Package Manager Console, PowerShell) without mentioning or providing alternatives for Linux or macOS users. Instructions for package installation and Microsoft Entra configuration are exclusively given using PowerShell commands, and there are no corresponding CLI or cross-platform instructions. This may hinder users on non-Windows platforms from following the guidance effectively.
Recommendations
- Provide equivalent instructions for Linux/macOS environments, such as using the .NET CLI (dotnet add package) for NuGet package installation instead of only referencing Visual Studio and the Package Manager Console.
- Include Azure CLI or Microsoft Graph CLI examples for Microsoft Entra ID administrative tasks, not just PowerShell.
- Explicitly mention cross-platform alternatives and note any platform-specific limitations or differences.
- Reorder or parallelize instructions so that Windows and Linux/macOS guidance are presented together, rather than Windows-first.
- Add a section or callout for users on non-Windows platforms, linking to relevant setup or troubleshooting resources.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/pricing/teams-interop-pricing.md
...ion-services/concepts/pricing/teams-interop-pricing.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation shows a subtle Windows bias by referencing the Teams Desktop client (which is primarily associated with Windows) in all usage examples, and in one scenario, explicitly mentions 'Windows, Chrome browser' for a user. The only command-line tool referenced is a PowerShell cmdlet (Set-CsPhoneNumberAssignment), with no mention of Linux or cross-platform alternatives. There are no examples or explicit mentions of Linux clients, tools, or environments, and all example scenarios use Windows-centric language or tools.
Recommendations
- Include explicit references to Linux and macOS Teams clients where applicable, e.g., 'Teams web, desktop (Windows, macOS, Linux), and mobile clients'.
- Provide command-line examples using cross-platform tools (such as Azure CLI or REST API) alongside or instead of PowerShell cmdlets.
- Avoid specifying 'Windows' in user scenarios unless necessary; if specifying OS, also mention Linux and macOS where supported.
- Add example scenarios where users join from Linux desktops or browsers on Linux, to demonstrate parity.
- Clarify that Teams web client and SDKs are cross-platform and supported on Linux, not just Windows.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/voice-video-calling/manage-call-quality.md
...es/concepts/voice-video-calling/manage-call-quality.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the section on Quality of Service (QoS), where it references 'Windows Group Policy objects' as the method for implementing QoS and does not mention Linux or cross-platform alternatives. There are no Linux-specific tools, commands, or examples provided for network configuration, diagnostics, or log collection. The documentation assumes a Windows-centric approach in network management and does not provide parity for Linux environments.
Recommendations
- Include Linux-specific instructions or references for implementing QoS, such as using 'tc', 'iptables', or 'firewalld' for traffic shaping and prioritization.
- Mention cross-platform or Linux-native tools for network diagnostics and monitoring, such as 'iftop', 'nload', or 'netstat', alongside any Windows tools.
- When discussing configuration or troubleshooting steps (e.g., log collection, network setup), provide examples or links for both Windows and Linux environments.
- Avoid referencing Windows-specific features (like Group Policy) as the only or primary method; instead, present platform-agnostic approaches first, or in parallel with Windows methods.
- Add a section or callout for Linux administrators to ensure they can achieve the same outcomes as Windows users.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/teams-interop-call-automation.md
...w-tos/call-automation/teams-interop-call-automation.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation demonstrates a Windows bias by referencing Microsoft Teams PowerShell cmdlets (e.g., Set-CsTeamsAcsFederationConfiguration, Set-CsExternalAccessPolicy) for tenant configuration, without mentioning or providing alternatives for Linux or cross-platform environments. The prerequisite and authorization steps assume access to Windows-centric tools and administrative patterns, and PowerShell is referenced as the primary method for configuration. No Linux-native or cross-platform CLI alternatives are discussed, and the order of presentation puts Windows tooling first.
Recommendations
- Provide equivalent Azure CLI or REST API instructions for tenant-level and user policy configuration steps, so Linux and macOS users can follow along without relying on PowerShell.
- Explicitly mention whether the PowerShell modules used (MicrosoftTeams, SkypeForBusiness) are available and supported on non-Windows platforms, and provide installation guidance for those environments if possible.
- Add notes or links to cross-platform tools or scripts for administrative steps, or clarify if certain steps must be performed on Windows.
- Where possible, present cross-platform or OS-neutral methods (such as Graph API or Azure Portal) before or alongside Windows-specific tools.
- Include example commands for Linux/macOS shells (bash, zsh) where relevant, especially for steps involving API calls or scripting.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/get-started-teams-interop-group-calls.md
...video-calling/get-started-teams-interop-group-calls.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. It references enabling Teams Phone features via PowerShell, links to Windows-centric Teams deployment documentation, and does not provide Linux-specific guidance or examples for any administrative steps. All code samples are cross-platform JavaScript, but prerequisite and setup steps assume a Windows/PowerShell environment, with no mention of Linux alternatives or parity.
Recommendations
- Where PowerShell is referenced for enabling Teams Phone features, provide equivalent instructions for Linux/macOS users (e.g., using cross-platform PowerShell Core, or via the Teams Admin Center web UI).
- When linking to Teams deployment documentation, clarify if the instructions are Windows-only or provide links to cross-platform or web-based alternatives.
- Explicitly state that the JavaScript code samples and development workflow (using Node.js, webpack, etc.) are cross-platform and can be run on Linux/macOS as well as Windows.
- If any administrative steps (such as retrieving Teams user IDs or managing licenses) can be performed via the Azure Portal or web interfaces, highlight these as OS-neutral options.
- Add a note in the prerequisites section to reassure Linux/macOS users that the quickstart is not Windows-specific and provide any needed platform-specific tips.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/python-application-setup.md
...essaging/whatsapp/includes/python-application-setup.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation provides a file creation command using the Windows-specific 'type nul > messages-quickstart.py' pattern, without offering an equivalent Linux/macOS example (such as 'touch messages-quickstart.py'). This prioritizes Windows tooling and omits guidance for users on other platforms.
Recommendations
- Provide both Windows and Linux/macOS commands for file creation, e.g., 'type nul > messages-quickstart.py' (Windows) and 'touch messages-quickstart.py' (Linux/macOS).
- Wherever possible, use cross-platform language in instructions, or explicitly note platform differences.
- Review the documentation for other implicit Windows-first patterns and ensure parity for Linux/macOS users.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-python.md
...d-messaging/whatsapp/includes/common-setting-python.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias in its instructions for setting environment variables. All examples use the Windows-specific 'setx' command, and there are no equivalent instructions or examples for Linux or macOS users. Additionally, references to restarting Visual Studio as an editor reinforce a Windows-centric perspective. There are no bash or cross-platform shell examples provided.
Recommendations
- Provide equivalent Linux/macOS instructions for setting environment variables, such as using 'export' in bash/zsh or editing ~/.bashrc or ~/.zshrc.
- Include both Windows (setx) and Linux/macOS (export) commands side by side or in tabbed sections.
- Mention cross-platform editors (e.g., VS Code) in addition to or instead of Windows-only editors like Visual Studio.
- Add a note clarifying that the instructions apply to Windows, and provide links or guidance for other operating systems.
- Ensure screenshots and references are not exclusively Windows-centric, or supplement them with cross-platform alternatives.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-email-resource-powershell.md
...rts/email/includes/create-email-resource-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively uses PowerShell commands and Windows-centric tooling (Az PowerShell module) for all examples and instructions. There are no CLI, Bash, or cross-platform alternatives provided, and all command-line examples are presented in a Windows PowerShell context. This creates a strong Windows bias and may hinder Linux or macOS users.
Recommendations
- Provide equivalent Azure CLI (az) command examples for all resource management tasks, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Mention and link to installation instructions for Azure CLI alongside Az PowerShell.
- Clearly indicate that the PowerShell examples work on PowerShell Core (cross-platform) if applicable, or specify any Windows-only limitations.
- Include Bash or shell script examples where appropriate, especially for automation scenarios.
- Reorder sections or provide parallel examples so that Linux/macOS users are not required to translate Windows/PowerShell instructions themselves.
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 a Windows bias by specifically referencing Windows system tools (volume mixer, app volume settings) and providing a screenshot of the Windows volume mixer, without mentioning or illustrating equivalent controls on Linux or macOS. No Linux-specific instructions or examples are provided for checking or adjusting system or application audio settings.
Recommendations
- Add parallel instructions for checking and adjusting audio settings on Linux (e.g., using PulseAudio Volume Control/pavucontrol, ALSA mixer, or system sound settings).
- Include screenshots of audio settings dialogs from popular Linux desktop environments (such as GNOME or KDE) alongside the Windows example.
- Mention macOS audio controls and provide similar guidance for users on that platform.
- Use neutral language such as 'system volume settings' and provide platform-specific steps in subsections or callouts, rather than focusing on Windows first.
- Where possible, provide cross-platform command-line instructions (e.g., amixer for Linux, or referencing system settings for macOS) to ensure parity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/call-automation/includes/quickstart-make-an-outbound-call-using-callautomation-python.md
...tart-make-an-outbound-call-using-callautomation-python.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates some Windows bias, particularly in the 'Run the code' section, where Visual Studio Code and Visual Studio are the only editors/IDEs mentioned, with Visual Studio (a Windows-only tool) given a dedicated section. There are no explicit Linux-specific instructions or examples, and no mention of Linux-native editors or terminal usage patterns. The documentation assumes familiarity with Windows-centric tools and omits guidance for Linux users.
Recommendations
- Add a section for running the application on Linux, including instructions for using common Linux editors (e.g., Vim, Emacs, GNOME Text Editor) and terminal commands.
- Include instructions for running the Python application from a generic terminal, not just from within Visual Studio Code or Visual Studio.
- Mention cross-platform editors/IDEs such as PyCharm, Sublime Text, or JetBrains Fleet, and provide generic instructions that apply to all platforms.
- Clarify that Visual Studio is Windows-only, and suggest equivalent steps for Linux users (e.g., running 'python main.py' from the terminal).
- Ensure that all command-line instructions (such as those for Azure DevTunnels and pip) are verified to work on both Windows and Linux, and note any platform-specific differences if they exist.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/events/includes/register-provider-powershell.md
...starts/events/includes/register-provider-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides only PowerShell (Windows-centric) commands for registering the Event Grid resource provider, with no mention of equivalent Azure CLI or Bash commands suitable for Linux or cross-platform users. This prioritizes Windows tools and patterns, potentially excluding Linux and macOS users.
Recommendations
- Add equivalent Azure CLI commands (e.g., 'az provider register --namespace Microsoft.EventGrid') alongside PowerShell examples.
- Present both PowerShell and CLI/Bash examples, or default to Azure CLI for cross-platform compatibility.
- Explicitly mention that the PowerShell commands are for Windows users and provide guidance for Linux/macOS users.
- Consider reordering examples or providing a tabbed interface for different platforms to ensure parity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-custom-managed-domain-resource-powershell.md
...es/create-custom-managed-domain-resource-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses PowerShell commands and Azure PowerShell modules for all examples and instructions, with no mention of Linux-compatible alternatives such as Azure CLI, Bash, or cross-platform scripting. The prerequisite section only references the Azure Az PowerShell Module, and all code snippets are PowerShell-specific, which may not be natively available or preferred on Linux or macOS environments. There is no guidance for users on non-Windows platforms.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
- In the prerequisites, mention both Azure PowerShell and Azure CLI as options, with links to their respective installation guides.
- For each operation (create, update, list, delete, verify), provide both PowerShell and Azure CLI/Bash examples side by side or in tabs.
- Explicitly state that the instructions apply to all platforms, and clarify any platform-specific requirements or differences.
- Consider including a note or section on how to use these commands in Bash or other shells commonly used on Linux.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-auto-attendant/teams-auto-attendant-ios.md
...ludes/teams-auto-attendant/teams-auto-attendant-ios.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows-centric tools and workflows, particularly in administrative steps involving Teams. It exclusively references the Teams Admin Center (a web interface optimized for Windows/Edge environments) and Microsoft Graph Explorer, and does not mention or provide alternatives for Linux users. There are no examples or guidance for performing equivalent administrative or setup tasks using Linux-friendly tools (e.g., Azure CLI, PowerShell Core on Linux, or REST API calls via curl). The page also omits any mention of Linux environments for development or administration, despite referencing macOS for app development.
Recommendations
- Provide alternative instructions for managing Teams Auto Attendants and Resource Accounts using cross-platform tools such as Azure CLI, Microsoft Graph API via curl, or PowerShell Core (which runs on Linux).
- Include explicit Linux-compatible examples for obtaining Object IDs and managing Teams resources, such as sample curl commands for Microsoft Graph API.
- Clarify that the Teams Admin Center is a web-based tool accessible from any OS, but also mention any browser or OS limitations if they exist.
- Add a note or section for Linux users, outlining any differences or additional steps required for setup or administration.
- Where possible, present cross-platform or Linux-first alternatives before or alongside Windows-centric tools.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/chat/includes/chat-csharp.md
...tion-services/quickstarts/chat/includes/chat-csharp.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by listing Windows tools (cmd, PowerShell) before Bash when describing console usage, using PowerShell syntax for package installation, and omitting explicit Linux/macOS instructions or examples for setup and execution. All examples and setup steps assume a .NET/C# environment, which is cross-platform, but the supporting instructions and tools are presented with a Windows-first perspective.
Recommendations
- When mentioning console windows, list Bash (Linux/macOS) first or equally alongside cmd and PowerShell.
- Provide explicit Linux/macOS installation and usage instructions, such as using terminal and package managers relevant to those platforms.
- Show package installation commands in both PowerShell and Bash syntax, or use a generic 'dotnet' command block.
- Clarify that .NET Core and the Azure Communication Services SDK are cross-platform, and provide any Linux/macOS-specific prerequisites (e.g., installing .NET SDK on Ubuntu/macOS).
- Include notes or troubleshooting tips for common Linux/macOS issues (e.g., file permissions, path differences).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-advanced/includes/attachments-net.md
.../email/send-email-advanced/includes/attachments-net.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by using a Windows-style file path (C:\Users\Documents\attachment.pdf) in the code example, without mentioning or providing a Linux/macOS equivalent. There are no examples or notes for Linux users regarding file paths or environment differences. The sample code and instructions assume a Windows environment, and there is no guidance for cross-platform usage.
Recommendations
- Provide file path examples for both Windows (C:\Users\Documents\attachment.pdf) and Linux/macOS (/home/user/Documents/attachment.pdf) in the code sample or add a note about cross-platform file paths.
- Explicitly mention that the .NET SDK and the example code are cross-platform and can be run on Windows, Linux, and macOS.
- Add a section or note about running the sample on Linux/macOS, including any relevant differences (such as file permissions or path separators).
- Ensure that all examples and instructions are inclusive of non-Windows environments to improve accessibility for Linux users.