No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Does anyone know why <https://github.com/pulumi/pulumi-azuread/issues/2258|the PRs in pulumi-azuread for updating terraform-provider-azuread to v3.8.0> keep getting closed? I've been waiting for a bug fix in the TF provider.

I'll forward this on to engineering. This is definitely weird.

<@U02FZC2RE0Y> Have they had a chance to look into this yet? There have been 4 new PRs on the ticket in the meantime but nothing has been merged yet.

Still no idea. Asked again. Will set a reminder for a few hours from now if I have not heard back.

There's a new release with an even newer version of the TF provider: <https://www.pulumi.com/registry/packages/azuread/>

You also may have the option of just using Any TF Provider if that works for your scenario: <https://www.pulumi.com/docs/iac/concepts/providers/any-terraform-provider/>

Thanks, looks like pulumi-bot was finally successful at merging the PR (with a little help)! :slightly_smiling_face:

&gt; with an even newer version of the TF provider
Are you sure? <https://github.com/pulumi/pulumi-azuread/releases/tag/v6.9.0|According to the changelog>, pulumi-azuread v6.9.0 (which was released an hour ago) uses terraform-provider-azuread v3.8.0, which has been the most recent version of the TF provider since I started this thread here in early March.