organization · inferred from evidence
Azure
The organization maintaining the Azure SDK and related services.
- Azure Key Vault CSI provider failed to get mounted files terminating pods Windows init jobs
Fixed in Secrets Store CSI driver v0.0.17 with AKV provider 0.0.10, which added checks to skip rotation and reconcile for deleting pods. Upgrade both the driver and the Azure provider to at least those versions and the terminating-pod mount
- Azure App Configuration 403 forbidden accessing with managed identity DefaultAzureCredential
IAM Reader is not enough: App Configuration data access requires a data-plane role. Assign the identity either the Azure App Configuration Data Reader or Azure App Configuration Data Owner role on the store. (The maintainers also noted that
- Azure Key Vault CSI driver driver name secrets-store.csi.k8s.io not found after AKS node upgrade
This is expected behavior on new nodes: pods referencing CSI volumes cannot start until the CSI driver registers on that node. During an AKS upgrade the node-driver-registrar image must be pulled onto the fresh node first, one reporter saw
- Azure App Configuration No managed identity endpoint found with ManagedIdentityCredential
This happens when the managed identity is not actually enabled on the host. In the Azure portal, open the App Service, go to Identity under Settings, and make sure Status is On under the System assigned tab. Also confirm the identity has th
- Azure Key Vault CSI Multiple user assigned identities exist please specify the clientId
Set `userAssignedIdentityID` to the client ID of the identity that has Key Vault access in your SecretProviderClass. The reporter confirmed this single change resolved the mount failure. The identity modes and this field are documented unde
- Azure Spring Boot feature flags not refreshed on cache expiration
The feature-flag naming issue behind this was fixed in the latest spring-cloud-azure-feature-management release, upgrade the library and the refresh works. One limitation confirmed by the maintainers remains: feature flags cannot currently
- Azure DevOps A task is missing The pipeline references a task called AzureAppConfigurationPush with version 6
This was caused by the release of task version 10, which broke resolution of the older task versions. The Azure team removed version 10 from the marketplace to restore the previous versions. Fix: revert your pipeline back to the task versio
- Disabling SSL verification in the Azure Document Intelligence client
Pass `connection_verify=False` when creating the client: `DocumentIntelligenceClient(endpoint=..., credential=..., connection_verify=False)`. This is documented in the azure-core configuration options and was confirmed by the Azure SDK main