Closed slavizh closed 4 months ago
May be it is completely related to https://github.com/microsoftgraph/msgraph-bicep-types/issues/126 and does not require attention.
@jason-dou please investigate
@slavizh Looks like it's a permission issue with the application used to deploy the templates. Have you checked if the application was granted necessary permission to read the resources? And if the issue still exists after the permission is granted?
@jason-dou yes. I think the issue is related to issue #126. Because of that issue in certain way when you write the code the graph is somehow producing incorrect error. I guess it can be closed as #126 needs to be resolved.
@slavizh This could be a different issue than #126. Could you share what permissions are assigned to the application that deploys the template? Are they application permissions or Entra built-in permissions?
This could also be a transient issue with permission validation internally. Have you tried deploying the same template again, and do you still see the issue?
@jason-dou I think it is not as with the same application I was deploying the same groups. Due to issue 126 I tried to modify the code a little bit in order to see if I can come up with some workaround. That modification led to that issue. It is also not transient as I have tried several times.
@slavizh We've found multiple issues here with this template deployment:
existing
extensible resources not working as expected. A fix is in progress as mentioned in this comment https://github.com/microsoftgraph/msgraph-bicep-types/issues/126#issuecomment-2168780771applications
) which requires more than existing granted permissions to be managed, or grant your application necessary permissions to manage all permissions in the template.@jason-dou thanks. I think I will wait for know as the first issue is the bigger blocker for me. I have end up reaching the second issue by creating undesired workaround for the first issue.
@slavizh are you OK closing this issue? We're tracking the first issue with a separate item, and we think we've fixed the 2nd authz issue.
@dkershaw10 yes can be closed.
Bicep version Bicep CLI version 0.27.1 (4b41cb6d4b)
Resource and API version Microsoft.Graph/applications@v1.0, Microsoft.Graph/servicePrincipals@v1., Microsoft.Graph/groups@v1.0
Auth flow automated
Deployment details Basically I get this error:
when I try to deploy this template from another one:
I get the first error as it is related to another issue I have opened but the other two are not very logical. May be this is some issue in error handling.
Describe the bug described
To Reproduce described
Additional context Add any other context about the problem here. For example, what permissions does the identity have if it's a permission issue?