What problem does it solve? Teams using Bitbucket Pipelines to deploy to Azure face a critical gap: Bitbucket's OIDC tokens cannot authenticate to Microsoft Entra ID, forcing teams to design workarounds for secure credential management, deployment gating, and cost control. ## Core Features & Use Cases - Azure Authentication Mitigations: Provides four concrete patterns for the OIDC gap, including per-environment service principal secrets with auto-rotation, a token broker Azure Function, Azure Pipelines as orchestrator, and HashiCorp Vault as intermediary. - Pipeline Configuration Reference: Covers bitbucket-pipelines.yml structure, YAML anchors, triggers, deployment environments, hosted vs self-hosted runners, and the full catalog of Microsoft/Atlassian Azure deployment pipes. - Platform Comparison and Costing: Compares Bitbucket Pipelines against GitHub Actions and Azure DevOps across OIDC support, hosted OS availability, approval gates, and pricing, with concrete migration trigger thresholds. - Use Case: An Azure shop committed to Jira needs to deploy to AKS from Bitbucket Pipelines without long-lived secrets; this Skill walks through building the token broker Azure Function that exchanges Bitbucket OIDC tokens for short-lived Azure credentials. ## Quick Start Ask how to authenticate Bitbucket Pipelines to Azure for deploying to AKS and receive the recommended credential pattern with working YAML.