Azure / Azure/bicep

Key Vault Api connection with Manage Identity

Open
#5,056 7 comments 0 reactions 0 assignees View on GitHub
provider bug types: swagger inaccuracy
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 2h
Merged PRs (30d)
79

Description

**Bicep version**
Bicep CLI version 0.4.613

**Describe the bug**
Hello All, I am using KeyVault in my logic app using Manage identity. When I try to create a APIConnection using Bicep, the template deployment is succeeded. But the status shows in Error. Also the authentication is Blank.
Currently Bicep does not support creating API connection to KeyVault using manage Identity ?

**To Reproduce**
1) Create a simple logic app with http trigger
2) Add Key Vault action to retrieve secret using Manage identity.
3) Deploy the Bicep file from Powershell or CLI
4) Check the API connection created. it will show error and Authentication as blank.

![KVApicon](https://user-images.githubusercontent.com/45224624/139815287-0cf215db-478a-4164-a4d7-2eacbbe8e5a4.jpg)

**Additional context**
Add any other context about the problem here.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the deployment described with Bicep CLI 0.4.613, a Logic App HTTP trigger, and a Key Vault API connection using managed identity. Inspect the deployed API connection's status and authentication fields; done means the connection is not in Error and its managed identity authentication is populated.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.