Service Connector

115
Total Pages
102
Linux-Friendly Pages
13
Pages with Bias
11.3%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (18)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-connector/tutorial-python-functions-storage-blob-as-input.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows-first bias by exclusively referencing Visual Studio and Visual Studio Code workflows, using Windows-centric UI instructions (e.g., right-click, F5), and omitting explicit Linux/macOS terminal or editor alternatives. There are no Linux-specific examples or mentions of common Linux editors or command-line workflows, and troubleshooting steps assume Azure Portal or CLI usage without addressing platform-specific differences.
Recommendations:
  • Include explicit instructions for Linux and macOS users, such as using VS Code on Linux, or alternative editors like Vim or Nano for editing JSON files.
  • Provide terminal-based workflows for adding bindings and running/debugging the function, rather than relying solely on VS Code UI actions.
  • Mention keyboard shortcuts and UI actions for all supported platforms (Windows, Linux, macOS), not just Windows (e.g., clarify F5 vs. Cmd+F5, right-click vs. Ctrl+click).
  • Add troubleshooting steps that address common Linux/macOS issues, such as file permissions or environment variable setup.
  • Reference cross-platform tools and avoid suggesting Visual Studio (full IDE) for deployment unless a Linux/macOS equivalent is provided.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-connector/overview.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First
Summary:
The documentation page lists Azure PowerShell and Visual Studio (a Windows-centric IDE) as primary client tools for Service Connector, and mentions them before cross-platform or Linux-native alternatives. There is no explicit mention of Linux-specific tools or shell environments (e.g., Bash), and the examples and tool recommendations lean toward Windows-first workflows.
Recommendations:
  • Include explicit mention and examples for Linux environments, such as Bash shell usage with Azure CLI.
  • Highlight cross-platform editors and tools (e.g., VS Code) alongside or before Windows-only tools like Visual Studio.
  • Provide parity in examples and instructions for both Windows and Linux users, ensuring that PowerShell is not the only shell referenced.
  • Clarify that Azure CLI and Terraform are fully cross-platform, and consider providing links or notes for Linux installation and usage.
  • If possible, add a section or callout for Linux/macOS users to ensure inclusivity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-connector/includes/code-sql-me-id.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example
Summary:
The documentation consistently references Microsoft SQL Server and its associated drivers (e.g., ODBC Driver 18 for SQL Server, mssql-jdbc), which are primarily Microsoft technologies. There is no explicit mention of Linux-specific instructions, such as how to install the required ODBC driver on Linux, nor are there any examples or troubleshooting notes for Linux environments. The documentation implicitly assumes the reader is familiar with Microsoft-centric tooling, and omits Linux-specific caveats or installation steps.
Recommendations:
  • Add explicit instructions for installing ODBC Driver 18 for SQL Server on Linux distributions (e.g., Ubuntu, CentOS), including package manager commands.
  • Mention any platform-specific configuration or troubleshooting steps for Linux (e.g., required libraries, environment variable differences, permissions).
  • Where relevant, clarify that the code samples are cross-platform, or provide notes if any sample is Windows-specific.
  • Include links to official Microsoft documentation for installing SQL Server drivers on Linux.
  • If there are known issues or differences in behavior on Linux, document them or provide workarounds.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-connector/tutorial-portal-app-configuration-store.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation exclusively uses the Azure Portal UI for all instructions and does not provide any command-line examples for either Windows (PowerShell/CLI) or Linux (Bash/CLI). However, the only code sample provided is in .NET (C#), which is more commonly associated with Windows environments. There is no mention of Linux-specific tools, shell commands, or parity in scripting. The documentation assumes use of the Azure Portal, which is cross-platform, but the lack of CLI or Linux-oriented examples may disadvantage Linux users or those preferring automation.
Recommendations:
  • Add equivalent Azure CLI examples for all portal-based steps, showing how to create service connections and configure App Configuration from the command line. Use Bash syntax for Linux parity.
  • Include at least one example in a language commonly used on Linux (such as Python or Node.js) in addition to .NET/C#.
  • Explicitly mention that all steps can be performed on Linux, macOS, and Windows, and provide links to relevant CLI documentation.
  • If PowerShell or Windows-specific tools are referenced in future updates, ensure Linux equivalents are presented side-by-side or first.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-connector/tutorial-python-functions-storage-queue-as-trigger.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a mild Windows bias by referencing Visual Studio and the F5 keybinding for running/debugging, which are strongly associated with Windows development environments. There are no explicit Linux or macOS-specific instructions or examples, and the deployment section refers to Visual Studio (not cross-platform) without mentioning alternatives. The troubleshooting and clean-up sections also lack Linux/macOS-specific guidance.
Recommendations:
  • Explicitly mention that Visual Studio Code is cross-platform and provide alternative instructions for macOS/Linux users where keybindings or UI elements differ.
  • When referencing Visual Studio for deployment, also mention cross-platform deployment methods (e.g., Azure CLI, VS Code) and provide links or steps.
  • Include notes or examples for running/debugging the function on Linux/macOS, especially where keybindings or UI may differ.
  • In troubleshooting and clean-up sections, clarify that the Azure CLI commands work on all platforms and highlight any OS-specific considerations if applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-connector/tutorial-python-functions-storage-table-as-output.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation consistently references Visual Studio Code and Visual Studio, but does not provide any Linux-specific instructions or examples. While Visual Studio Code is cross-platform, the workflow and terminology (e.g., right-click, F5, workspace view) are more familiar to Windows users. There are no explicit Linux command-line or editor alternatives, and no mention of Linux-specific troubleshooting or deployment steps. The guide also references Visual Studio (not Code) for deployment, which is primarily a Windows tool, without offering alternatives for Linux users.
Recommendations:
  • Explicitly mention that Visual Studio Code instructions apply to Linux, macOS, and Windows, and provide any necessary Linux-specific notes (e.g., keyboard shortcuts, file paths).
  • Offer alternative instructions for deploying without Visual Studio (e.g., using Azure CLI only, or via VS Code on Linux).
  • Include Linux/macOS-specific troubleshooting tips, especially for common issues like file permissions or environment setup.
  • Clarify that Visual Studio (not Code) is not available on Linux, and provide equivalent steps for Linux users (e.g., using VS Code or CLI for deployment).
  • Where possible, use neutral terminology (e.g., 'select' instead of 'right-click') and provide keyboard shortcuts for all platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-connector/how-to-get-configurations.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation provides both Azure CLI and Azure PowerShell examples for retrieving connection configurations. However, it gives equal prominence to PowerShell (a Windows-centric tool), and does not provide Linux- or bash-specific examples or mention Linux-native tools. There is no explicit guidance for Linux users, and PowerShell is presented as a primary method alongside Azure CLI, which may not be as familiar or available to Linux users.
Recommendations:
  • Add explicit bash or shell script examples for Linux users, especially for parsing or consuming Azure CLI output.
  • Clearly indicate that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • If PowerShell is included, clarify that PowerShell Core is available cross-platform, or provide alternative Linux-native commands.
  • Consider listing Azure CLI (the more cross-platform tool) before PowerShell, or note that PowerShell examples are primarily for Windows users.
  • Add a section or note on how to install and use Azure CLI on Linux, and how to parse outputs with common Linux tools (jq, grep, etc.).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-connector/how-to-integrate-fabric-sql.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation exhibits subtle Windows bias. Connection string examples for Python use the ODBC Driver 17 for SQL Server, which is primarily a Windows driver (though available for Linux, it is less common and requires extra setup). There is no mention of Linux-specific drivers or connection methods (such as FreeTDS or pyodbc configuration for Linux). The instructions for creating the service connection reference 'Cloud Shell' or 'local Azure CLI' but do not clarify Linux-specific steps or differences. No explicit Linux shell or cross-platform CLI examples are provided, and there is no mention of Linux authentication caveats or troubleshooting. The documentation implicitly assumes a Windows environment for code and tooling.
Recommendations:
  • Provide explicit Linux-compatible connection string examples, mentioning Linux ODBC drivers (e.g., FreeTDS, unixODBC) and their installation.
  • Include notes or links about installing and configuring ODBC Driver 17 for SQL Server on Linux, or alternatives if not available.
  • Add sample code and environment variable setup for Linux shells (bash/zsh), not just Windows/PowerShell.
  • Clarify any differences or caveats for Linux users in the 'Share access' and Azure CLI steps.
  • Ensure screenshots and portal instructions are not Windows-centric and mention cross-platform compatibility where relevant.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-connector/how-to-integrate-redis-cache.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Windows First
Summary:
The documentation consistently uses Azure Redis endpoints in the form of '<RedisName>.redis.cache.windows.net', which is Windows-branded. There is no mention of Linux-specific tools, commands, or patterns, and the documentation does not provide any Linux shell or CLI examples. The documentation also refers to environment variable names and connection strings that are Windows-centric (e.g., '.windows.net'), and does not address Linux-specific deployment or configuration considerations. While the documentation is not overtly PowerShell-heavy, it implicitly assumes a Windows context by using Windows endpoints and not mentioning Linux environments.
Recommendations:
  • Include explicit Linux/Bash shell examples for setting environment variables and connecting to Redis.
  • Mention that the '.windows.net' endpoint is used regardless of the client OS, but clarify that the instructions apply equally to Linux and Windows environments.
  • Provide guidance or examples for common Linux deployment scenarios (e.g., using environment variables in Docker containers, Kubernetes secrets, or Linux-based Azure compute services).
  • If any platform-specific steps exist (such as certificate handling or SSL validation differences), document them for both Windows and Linux.
  • Consider using more neutral language and endpoint examples, or explicitly state that the endpoint naming is an Azure convention and not OS-specific.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-connector/includes/code-fabricsql-me-id.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example
Summary:
The documentation consistently references Windows-specific tools and drivers (e.g., 'ODBC Driver 17 for SQL Server'), and does not provide Linux-specific guidance or examples for installing or configuring these dependencies. There are no explicit instructions or troubleshooting notes for Linux or macOS users, and the driver names and installation patterns are Windows-centric.
Recommendations:
  • Include explicit instructions for installing required drivers (such as ODBC Driver 17 for SQL Server) on Linux and macOS, not just Windows.
  • Mention cross-platform driver alternatives (e.g., FreeTDS for Linux) where appropriate.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., driver not found, environment variable differences).
  • Where driver names are given (e.g., 'ODBC Driver 17 for SQL Server'), clarify that the name may differ on Linux/macOS and provide the correct names.
  • Provide at least one example of running the code on Linux/macOS, or a note confirming cross-platform compatibility and any required adjustments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-connector/includes/code-signalr.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation does not explicitly show Windows bias in terms of tools or ordering, but it lacks platform-specific examples or guidance for Linux users. It assumes environment variables are set and accessed in a platform-agnostic way, but does not clarify how to set or retrieve them on Linux versus Windows.
Recommendations:
  • Add explicit instructions or examples for setting and retrieving environment variables on both Windows (e.g., using PowerShell or Command Prompt) and Linux (e.g., using Bash).
  • Clarify that the code examples are platform-independent, or provide notes on any platform-specific considerations.
  • Include a table or section summarizing how to set environment variables in different operating systems to ensure parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-connector/includes/code-sql-secret.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example
Summary:
The documentation consistently references Microsoft SQL Server client drivers (e.g., ODBC Driver 13/18 for SQL Server, sqlsrv_connect, TinyTds), which are primarily developed and supported by Microsoft and have historically had better support and easier installation on Windows. There are no explicit instructions or troubleshooting for Linux users, such as how to install ODBC drivers or resolve common cross-platform issues. The PHP and Ruby sections direct users to Microsoft-centric resources. No Linux-specific package installation or driver configuration guidance is provided.
Recommendations:
  • Add explicit instructions for installing Microsoft ODBC drivers on Linux (e.g., using apt, yum, or zypper) for Python, Django, and other relevant languages.
  • Include troubleshooting notes or links for common Linux issues (e.g., driver compatibility, required system libraries).
  • Where possible, mention or provide examples using open-source or cross-platform drivers (e.g., FreeTDS for Python, PHP, Ruby) alongside Microsoft drivers.
  • For PHP and Ruby, provide Linux installation steps or reference Linux-specific documentation in addition to Microsoft documentation.
  • Clarify in each language section that the examples are cross-platform, and note any platform-specific caveats or steps.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-connector/overview.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Windows First
Summary:
The documentation lists Windows-centric tools (Azure PowerShell, Visual Studio) before or alongside cross-platform alternatives, and does not provide equivalent emphasis or examples for Linux-native tools or workflows. There are no explicit Linux or Bash examples, and the mention of Visual Studio (Windows-focused) is prioritized over cross-platform editors. Azure CLI and Terraform are cross-platform, but the order and tool selection show a subtle Windows bias.
Recommendations:
  • Add explicit mention of Linux-native workflows and tools, such as Bash scripting or integration with VS Code (which is cross-platform).
  • Provide example commands or usage scenarios for both Windows (PowerShell) and Linux (Bash) environments.
  • Reorder the list of client tools to start with cross-platform options (Azure CLI, Terraform, VS Code) before Windows-specific tools (PowerShell, Visual Studio).
  • Clarify that Azure CLI and Terraform are fully supported on Linux and macOS, and provide links to their installation guides for those platforms.
  • Consider including a section or note about using Service Connector in Linux environments, highlighting any differences or additional steps.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-connector/tutorial-connect-web-app-app-configuration.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools
Summary:
The documentation demonstrates a subtle Windows bias by using Windows-style path separators (backslashes) in 'cd' commands and referencing 'notepad' as a temporary storage tool. While the Azure CLI is cross-platform and the instructions are generally platform-agnostic, these details may confuse or inconvenience Linux/macOS users. There are no explicit PowerShell examples, but the path and tool references assume a Windows environment.
Recommendations:
  • Use forward slashes (/) in directory paths for 'cd' commands, or provide both Windows (\) and Linux/macOS (/) variants.
  • Replace references to 'notepad' with a generic instruction such as 'save the output in a temporary text file', or mention cross-platform editors (e.g., 'use a text editor of your choice').
  • Explicitly state that all CLI commands work on Windows, Linux, and macOS, and provide notes or tabs for OS-specific differences if relevant.
  • Consider including a short section or callout for Linux/macOS users to clarify any differences in command usage or environment setup.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-connector/tutorial-python-functions-storage-blob-as-input.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows-first bias by exclusively referencing Visual Studio Code and Visual Studio workflows, using Windows-centric UI actions (e.g., right-click, F5), and omitting explicit Linux/macOS terminal or editor alternatives. There are no Linux-specific instructions, screenshots, or terminal-based workflows, and all examples assume a GUI-based development environment typical of Windows users.
Recommendations:
  • Provide explicit instructions for Linux/macOS users, including terminal-based workflows for creating and managing Azure Functions projects.
  • Include examples using popular Linux editors (e.g., VS Code on Linux, Vim, nano) and command-line operations for editing JSON files and running/debugging functions.
  • Clarify keyboard shortcuts and UI actions for all platforms (e.g., specify macOS/Linux equivalents for F5, right-click, etc.).
  • Add troubleshooting steps and deployment instructions relevant to Linux environments, such as common permission issues or differences in file paths.
  • Mention and link to platform-specific installation guides for prerequisites (e.g., Python, Azure CLI) on Linux/macOS.
  • Consider providing a parallel section or callouts for Linux/macOS users to ensure parity and inclusivity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-connector/tutorial-python-functions-storage-queue-as-trigger.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by exclusively referencing Visual Studio Code and Visual Studio (both commonly associated with Windows), using Windows-centric UI instructions (e.g., pressing F5, referencing the Activity bar), and omitting any Linux- or macOS-specific instructions or terminal examples. There are no explicit Linux command-line or tool examples, nor any mention of Linux-specific workflows or troubleshooting steps.
Recommendations:
  • Include explicit instructions and screenshots for Linux and macOS users, such as how to run and debug in VS Code on those platforms.
  • Mention alternative editors or workflows that are popular on Linux, such as using the command line with func CLI instead of Visual Studio or Visual Studio Code.
  • Provide terminal-based examples for running and debugging the function locally, including relevant shell commands for Linux/macOS.
  • Clarify that Visual Studio Code is cross-platform, and provide any platform-specific setup notes (e.g., how to install Python or Azure CLI on Linux).
  • Add troubleshooting steps that are relevant to Linux environments, such as checking permissions or environment variables.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-connector/tutorial-portal-app-configuration-store.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation exclusively uses the Azure Portal UI for all steps and does not provide any command-line examples (such as Azure CLI or PowerShell). There are no references to Windows-specific tools, but the absence of CLI examples means Linux users (who often prefer CLI workflows) are underserved. The only code sample is in .NET, which is cross-platform, but there are no examples for other languages or for Linux-native workflows. The documentation implicitly assumes a GUI-first (and thus, often Windows-centric) approach.
Recommendations:
  • Add Azure CLI examples for all major steps (creating connections, configuring App Configuration, etc.), ensuring parity with portal instructions.
  • Explicitly mention that all steps can be performed on Linux, macOS, and Windows using the CLI.
  • Provide at least one example using a Linux shell (e.g., Bash) to demonstrate cross-platform compatibility.
  • Include code samples in additional languages commonly used on Linux (such as Python or Node.js), or link to such samples.
  • Where screenshots are used, clarify that the Azure Portal is web-based and accessible from any OS.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-connector/tutorial-python-functions-storage-table-as-output.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation consistently references Visual Studio Code and Visual Studio as the primary development environments, with instructions such as right-clicking files and using GUI elements that are most familiar to Windows users. There are no explicit examples or instructions for Linux-specific workflows, terminal-based alternatives, or common Linux editors. The use of Visual Studio (not Code) for deployment is mentioned without Linux alternatives, and all command-line examples use Azure CLI, which is cross-platform, but the overall workflow assumes a Windows-centric development environment.
Recommendations:
  • Include explicit instructions for Linux users, such as using terminal commands to add bindings or edit JSON files, rather than relying on right-click context menus.
  • Provide alternative deployment instructions using only Visual Studio Code or the Azure CLI, as Visual Studio is not available on Linux.
  • Clarify that Visual Studio Code is cross-platform and provide any Linux-specific notes or troubleshooting tips.
  • Mention and demonstrate how to use common Linux editors (e.g., vim, nano) for editing configuration files.
  • Ensure all steps that reference GUI actions have equivalent CLI or keyboard-driven alternatives for Linux parity.