Yeah, there are many changes in the core and management resources.

Plan: 14 to add, 42 to change, 10 to destroy.

Lots of which are version changes in polices, so I'm sure something will break there lol.

Ah that makes sense. I'll try a quick plan on that and just provide the output as it might help you in the future when you work on that backlog item.

I have not yet checked core and management resources, but I can give those a try as well and see if any changes show up during a plan when running azurerm v4.

After that, when I run a plan, the only changes are Palo Alto Firewall-related and no other changes. So, allowing version 4 of azurerm does not seem to introduce changes, at least for the networking side.

No issues after making those updates, I am able to run both in the same state.

But if I fork your module and update the following:

It's the same state file currently.

With the constraints, I get the following:

│ Error: Failed to query available provider packages
4.27.0 does not match configured version constraint >= 3.0.0, >= 3.100.0, >= 3.103.0, ~> 3.107, ~> 3.108, < 5.0.0; must use terraform init -upgrade to allow

No worries, thanks for the update. We will figure something out in the interim.

I have a dependency on azurerm v4 for installing Palo Alto Cloud NGFW for Azure.