Document Details
Import Soap Api
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but it demonstrates a Windows bias by giving equal prominence to PowerShell (a Windows-centric tool), listing it immediately after CLI, and including detailed PowerShell setup instructions. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is presented as a primary automation method alongside CLI, despite CLI being more cross-platform. The prerequisites and examples do not mention or demonstrate Linux-native tools or workflows.
Recommendations
- Add explicit Bash or shell script examples for Linux users, especially for common automation scenarios.
- Clarify that Azure CLI commands are fully cross-platform and can be run on Linux, macOS, and Windows.
- De-emphasize PowerShell as a primary automation tool by listing Azure CLI first and PowerShell second, or by grouping PowerShell as an alternative for Windows users.
- Include notes or sections on how to install and use Azure CLI on Linux, and link to Linux-specific setup guides.
- If PowerShell is included, mention that PowerShell Core is available cross-platform, but provide native Bash alternatives where possible.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-02-19 00:00 | #398 | in_progress |
Biased
|
| 2026-02-18 00:00 | #394 | in_progress |
Biased
|
| 2026-02-17 00:00 | #390 | in_progress |
Biased
|
| 2026-02-16 00:00 | #386 | in_progress |
Biased
|
| 2026-02-15 00:00 | #382 | in_progress |
 Clean
|
| 2026-02-14 00:00 | #378 | in_progress |
Clean
|
| 2026-02-13 00:00 | #374 | in_progress |
Clean
|
| 2026-02-12 00:00 | #370 | in_progress |
Clean
|
| 2026-02-11 00:00 | #366 | in_progress |
Clean
|
| 2026-02-10 00:00 | #362 | completed |
Biased
|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
Biased
|
| 2026-01-12 00:00 | #243 | cancelled |
Biased
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Clean
|
| 2026-01-08 00:00 | #228 | cancelled |
Clean
|
| 2026-01-06 18:15 | #225 | cancelled |
Clean
|
| 2025-09-14 00:00 | #111 | completed |
Biased
|
| 2025-08-14 00:01 | #80 | cancelled |
Clean
|
| 2025-07-13 21:25 | #47 | cancelled |
Clean
|
| 2025-07-13 20:48 | #44 | cancelled |
Biased
|
| 2025-07-09 13:09 | #3 | cancelled |
Clean
|
| 2025-07-08 04:23 | #2 | cancelled |
Biased
|
Flagged Code Snippets
#### [PowerShell](#tab/powershell) The following example uses the [Import-AzApiManagementApi](/powershell/module/az.apimanagement/import-azapimanagementapi?) Azure PowerShell cmdlet to import a WSDL specification from the specified URL to an API Management instance named *apim-hello-world*. To import using a path to a specification instead of a URL, use the `-SpecificationPath` parameter. For this example WSDL, the service name is *OrdersAPI*, and one of the available endpoints (interfaces) is *basic*.