You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have had a quick play around and this is interesting. I have tried it using two different azuread_application_template and it did not create the users for either. If no template is used then the owners are assigned as would be expected.
I will look into the template ID logic to see if there is something there or if this is an API/Logic problem.
We are working on a new resource azuread_application_from_template along with a host of additional resources including an azuread_application_owner resource, aimed at managing individual components of applications rather than monolithically like the azuread_application resource. I believe these resources together will resolve this issue of application ownership, by allowing you to launch an application from the template gallery and append additional owners as needed. These resources are in flight in #1214 and will land in the next provider release.
Our recommendation will be to adopt these new resource for launching applications from gallery templates, particularly in cases where the existing azuread_application conflicts with the starting properties for the new application. Accordingly, I've marked this issue for closure with #1214.
Community Note
Terraform (and AzureAD Provider) Version
Affected Resource(s)
azuread_application
Terraform Configuration Files
Debug Output
https://gist.github.com/DI-DaveGoodine/be0562e81b6f7a20815a58921d799537
Panic Output
n/a
Expected Behavior
Azure App is created with three App owners.
Actual Behavior
Azure App is created, however:
Steps to Reproduce
terraform apply
Important Factoids
The service principal has these permissions:
References
The text was updated successfully, but these errors were encountered: