Sad Tux - Windows bias detected
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_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for command-line operations, referencing installation of Azure PowerShell (a Windows-centric tool), and omitting equivalent Azure CLI (cross-platform) or Bash examples. The PowerShell approach is presented before ARM templates, and there is no mention of Linux or macOS workflows. This may disadvantage users on Linux or macOS who prefer Azure CLI or Bash scripting.
Recommendations
  • Add Azure CLI examples for all operations currently demonstrated with Azure PowerShell, including creating and updating API Management instances with managed identities.
  • Include Bash script examples where appropriate, especially for ARM template deployments.
  • Explicitly mention that Azure CLI is cross-platform and provide installation links for Linux/macOS users.
  • Present Azure CLI and PowerShell examples side-by-side or in parallel tabs, rather than PowerShell-first.
  • Review references to 'install Azure PowerShell' and add corresponding instructions for Azure CLI.
  • Ensure screenshots and UI instructions are not Windows-specific, or clarify if they are universal.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2026-02-20 00:00 #402 in_progress Biased Biased
2026-02-19 00:00 #398 in_progress Biased Biased
2026-02-18 00:00 #394 in_progress Biased Biased
2026-02-17 00:00 #390 in_progress Biased Biased
2026-02-16 00:00 #386 in_progress Biased Biased
2026-02-15 00:00 #382 in_progress Biased Biased
2026-02-14 00:00 #378 in_progress Biased Biased
2026-01-15 00:00 #254 completed Biased Biased
2026-01-14 00:00 #250 in_progress Biased Biased
2026-01-13 00:00 #246 completed Biased Biased
2026-01-12 00:00 #243 cancelled Biased Biased
2026-01-11 00:00 #240 completed Biased Biased
2026-01-10 00:00 #237 completed Biased Biased
2026-01-09 00:34 #234 completed Biased Biased
2026-01-08 00:53 #231 completed Biased Biased
2026-01-08 00:00 #228 cancelled Clean Clean
2026-01-06 18:15 #225 cancelled Clean Clean
2025-09-10 00:00 #107 completed Biased Biased
2025-08-12 00:00 #78 cancelled Biased Biased
2025-08-11 00:00 #77 completed Biased Biased
2025-08-10 00:00 #76 completed Biased Biased
2025-08-09 00:00 #75 completed Biased Biased
2025-08-08 00:00 #74 completed Biased Biased
2025-08-07 00:00 #73 completed Biased Biased
2025-08-06 00:00 #72 completed Biased Biased
2025-08-05 00:00 #71 completed Biased Biased
2025-08-04 00:00 #70 cancelled Biased Biased
2025-08-03 00:00 #69 completed Biased Biased
2025-08-02 00:00 #68 cancelled Biased Biased
2025-08-01 00:00 #67 completed Biased Biased
2025-07-31 00:00 #66 completed Biased Biased
2025-07-30 00:00 #65 completed Biased Biased
2025-07-29 00:01 #64 completed Biased Biased
2025-07-28 00:00 #63 completed Biased Biased
2025-07-27 00:00 #62 completed Biased Biased
2025-07-26 00:01 #61 completed Biased Biased
2025-07-25 00:00 #60 completed Biased Biased
2025-07-24 00:00 #59 completed Biased Biased
2025-07-23 00:00 #58 completed Biased Biased
2025-07-22 00:01 #57 completed Biased Biased
2025-07-21 00:00 #56 completed Biased Biased
2025-07-20 00:13 #55 completed Biased Biased
2025-07-19 13:51 #54 completed Clean Clean
2025-07-17 00:00 #53 completed Biased Biased
2025-07-13 21:25 #47 cancelled Biased Biased
2025-07-13 20:48 #44 cancelled Clean Clean
2025-07-09 13:09 #3 cancelled Clean Clean
2025-07-08 04:23 #2 cancelled Biased Biased

Flagged Code Snippets

### Store and manage named values from Key Vault

You can use a system-assigned managed identity to access Key Vault to store and manage secrets for use in API Management policies. For more information, see [Use named values in Azure API Management policies](api-management-howto-properties.md). 

### Authenticate to a backend by using an API Management identity

You can use the system-assigned identity to authenticate to a backend service via the [authentication-managed-identity](authentication-managed-identity-policy.md) policy.

### Connect to Azure resources behind an IP firewall by using a system-assigned managed identity


API Management is a trusted Microsoft service to the following resources. This trusted status enables the service to connect to the following resources behind a firewall. After you explicitly assign the appropriate Azure role to the [system-assigned managed identity](../active-directory/managed-identities-azure-resources/overview.md) for a resource instance, the scope of access for the instance corresponds to the Azure role that's assigned to the managed identity.


- [Trusted access for Key Vault](/azure/key-vault/general/overview-vnet-service-endpoints#trusted-services)
- [Trusted access for Azure Storage](../storage/common/storage-network-security.md?tabs=azure-portal#trusted-access-based-on-system-assigned-managed-identity)
- [Trusted access for Azure Services Bus](../service-bus-messaging/service-bus-ip-filtering.md#trusted-microsoft-services)
- [Trusted access for Azure Event Hubs](../event-hubs/event-hubs-ip-filtering.md#trusted-microsoft-services)

### Log events to an event hub

You can configure and use a system-assigned managed identity to access an event hub to log events from an API Management instance. For more information, see [How to log events to Event Hubs in Azure API Management](api-management-howto-log-event-hubs.md).

## Create a user-assigned managed identity

> [!NOTE]
> You can associate an API Management instance with as many as 10 user-assigned managed identities.

### Azure portal

To set up a managed identity in the portal, you must first create an API Management instance and [create a user-assigned identity](../active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md). Then complete the following steps.

1. Go to your API Management instance in the portal.
1. In the left menu, under **Security**, select **Managed identities**.
1. On the **User assigned** tab, select **Add**.
1. Search for the identity that you created earlier and select it. Select **Add**.

   :::image type="content" source="./media/api-management-howto-use-managed-service-identity/enable-user-assigned-identity.png" alt-text="Screenshot that shows how to enable a user-assigned managed identity." border="true" lightbox="./media/api-management-howto-use-managed-service-identity/enable-user-assigned-identity.png":::

### Azure PowerShell

[!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]

The following steps lead you through creating an API Management instance and assigning it an identity by using Azure PowerShell.

1. If you need to, install Azure PowerShell by following the instructions in the [Azure PowerShell guide](/powershell/azure/install-azure-powershell). Then run `Connect-AzAccount` to create a connection with Azure.

1. Use the following code to create the instance. For more examples of how to use Azure PowerShell with API Management, see [API Management PowerShell samples](powershell-samples.md).