Service Connector

The documentation page lists Windows-centric tools (Azure PowerShell, Visual Studio) before Linux/macOS equivalents, and highlights them as primary client tools for Service Connector. While Azure CLI and Terraform are cross-platform, the ordering and emphasis on Windows tools (PowerShell, Visual Studio) suggest a Windows-first bias. No explicit Linux/macOS examples or tools (e.g., Bash, VS Code) are mentioned.

• Explicitly mention cross-platform compatibility for Azure CLI and Terraform.
• Add examples or references for Linux/macOS environments, such as using Bash or zsh.
• Include VS Code as a cross-platform IDE alternative to Visual Studio.
• Balance the ordering of client tools to avoid Windows-first impression (e.g., list CLI and Terraform before PowerShell and Visual Studio).
• Clarify that all major features are available on Linux/macOS, and provide links to relevant setup guides.

The documentation page lists Windows-centric tools (Azure PowerShell, Visual Studio) before Linux/macOS equivalents and does not provide parity in mentioning Linux-native tools or editors. The ordering and emphasis subtly favor Windows environments, though Azure CLI and Terraform are cross-platform.

• Explicitly mention cross-platform compatibility for Azure CLI and Terraform.
• Add examples or references for Linux/macOS users, such as VS Code (cross-platform) or JetBrains Rider.
• Reorder the list of client tools to start with cross-platform options (Azure CLI, Terraform) before Windows-specific ones.
• Clarify that Azure PowerShell is available on Linux/macOS, or provide Bash examples where relevant.
• Include a note about using Service Connector from Linux/macOS environments and any platform-specific considerations.