Skip to content

Graph Bicep module does not work with deployment stack #304

Description

@dozer75

Bicep version
Bicep CLI version 0.44.1 (28275db947)

Resource and API version
Which Microsoft.Graph resource and API version has the issue?

  • br:mcr.microsoft.com/bicep/extensions/microsoftgraph/v1.0:1.0.0
  • Microsoft.Graph/servicePrincipals@v1.0

Auth flow
CD deployment in Azure Devops pipelines using the AzureCLI@2 task and a managed identity with the required Application.Read.All and AppRoleAssignment.ReadWrite.All permissions.

Deployment details
Please refer to #302

Describe the bug
When deploying the bicep mentioned in #302 using deployment stack, the error (also described in #302) is triggered.

To Reproduce

  1. Create a bicep deployment that deploys the bicep in Assigning Graph roles to a managed identity #302.
  2. Have a managed identity that has the Application.Read.All and AppRoleAssignment.ReadWrite.All Graph permissions.
  3. Use that managed identity (e.g. in a CD pipeline in Azure DevOps) and run az stack sub create to deploy it.

Additional context
It is quite a showstopper since it doesn't work with deployment stacks...

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions