Tom Bamford

@mariussm Thank you for requesting this. I can see that the current design may have made some assumptions, however we can expand the support as needed. Thanks for writing the...

@alexanderfrei Thanks for reporting, as this is a different error please could you open a new issue with the details, and also configmring whether you are getting the error consistently...

Thanks again for reporting this issue, and for the explanation around this use case. We're releasing a new set of resources for application management, which are being built to enable...

We'll be including an `azuread_application_known_clients` resource in the next release of the provider.

Sorry it has been awhile since I've been able to look to this. We are releasing a number of new resources including `azuread_application_from_template` and a host of others for managing...

Hi all, since it seems there is no traction as yet with fixing this in the API, I am proposing a potential fix for this error by retrying the group...

We intend to approach this by incorporating invite functionality into the `azuread_user` resource rather than expand the `azuread_invitation` resource.

We'll be adding the `azuread_application_api_access` resource in the next release, which represents a decoupled `required_resource_access` from the `azuread_application` resource. There are also other narrowly-scoped resources for managing different parts of...

We are working on a new resource `azuread_application_from_template` along with a host of additional resources for managing individual components of applications, which I believe will resolve this issue of clobbering...

I'm going to close this one out due to inactivity. If there is continued interest in this request, please feel free to reply and we'll happily re-open it, but at...