microsoftgraph / microsoftgraph/msgraph-bicep-types

List application/service principal secret

Open
#266 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
80
Forks
15
Avg merge
1h 21m
Merged PRs (30d)
3

Description

Is your feature request related to a problem? Please describe.
For Azure resources we have the capability get secrets from some services via list functions (https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-functions-resource#list) or getSecret (https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-functions-resource#getsecret) for Key Vault secrets. As far as I understand there is no such option for Entra applications and service principals.
There are still a lot of Azure services that require application and secret in order to configure something. One such example is credential provider for Azure APIM https://learn.microsoft.com/en-us/azure/api-management/credentials-how-to-azure-ad but of course there are many other. Of course the APIM option is in that format so it can allow external Entra tenants to the APIM instance but in Bicep would be good if you can pull the secret directly by referencing the application, instead of getting the secret value and storing it in Key Vault and pulling it from there. I do not know if this is possible as there might not be the option to pull secret at all from Application besides the first time it is being created. Is there possibility such option to be added? Other method would be to be able to create secrets from Bicep to Entra applications. In such scenarios we should be able to create the secret by specifying its value. We could pull the value from Key Vault so we can add the secret to the application/service principal.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Additional context
Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the repository's Microsoft Graph resource type definitions and the Azure/Bicep support relevant to Entra applications and service principals. Determine whether secret values can be listed or created through the available Graph operations, then define the supported resource behavior and validation needed for the requested scenarios.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
authentication, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.