Garrett H

Just wanted to add a note to mention that this feature is apparently no longer in Preview status, so it would definitely be helpful to integrate it into the provider.

Perhaps I wasn’t clear on the issue. All of my role aaasignments are still present, the problem is that when terraform refreshed the state it no longer sees the eligibility...

To add some more detail, i believe the issue here has to do with the distinction between a **roleEligibilitySchedule** and a **roleEligibilityScheduleRequest**. It looks like when you create an eligible...

Looking in my environment today i see that all of the "revoked" schedule requests have now completely vanished. It really seems like the only path forward to make this resource...

Is this not covered by the [azuread_directory_role_eligibility_schedule_request](https://registry.terraform.io/providers/hashicorp/azuread/latest/docs/resources/directory_role_eligibility_schedule_request) resource? In our own PIM implementation we use terraform to 1. Create groups for azure AD roles 2. Create Entitlement management access packages...