Tom Bamford

Yes, I'm hoping soon to audit the documented scopes for all resources and update accordingly.

Hi @hales8181, thanks for reporting this. The provider should never crash, however looking into this it seems like this may have been most likely caused by a network or connection...

Thanks @paul-hugill, if you can open an issue for AzureRM that'd be appreciated 👍

Hi @kaplik, @juicybaba is correct, `object_id` is the correct attribute to use here. You are correct, this is missing from the upgrade guide - sorry for that omission, I’ll look...

> > How about the `principal_id` issue as in below? > > ```hcl > -/+ resource "azurerm_role_assignment" "avd_customer_as_application_group_user" { > ~ principal_id = "0b8f0b8f-0b8f-0b8f-0b8f-0b8f0b8f0b8f" -> "/groups/0b8f0b8f-0b8f-0b8f-0b8f-0b8f0b8f0b8f" # forces replacement @mloskot...

It's quite difficult to choose here, since the API is clearly designed for multiple values but so far there's a limitation of one audience 🤔

Thanks for requesting @DevopsMercenary. I believe this is a [separate API](https://learn.microsoft.com/en-us/graph/api/rbacapplication-post-roleassignmentschedulerequests?view=graph-rest-1.0&tabs=http) so this would be implemented as a new resource.

API bug reported upstream: https://github.com/microsoftgraph/msgraph-metadata/issues/647

Note: merged in error, now reverted. This continues to be blocked.

Hi @garretth9, thanks for reporting this issue. I have been able to reproduce this error and spotted a bug in the provider that could be causing this. However, after reworking...