Allowed locations policies removed in version 2.6.0+

I noticed that the policies below are removed as from version 2.6.0 of the [NL BIO Cloud Theme V2 (d8b2ffbe-c6a8-4622-965d-4ade11d1d2ee)](https://www.azadvertizer.net/azpolicyinitiativesadvertizer/d8b2ffbe-c6a8-4622-965d-4ade11d1d2ee.html).
As a Dutch organization we want to ensure that our data is stored within (West/North)Europe. Especially today with the current geopolitical situation and the soverenity discussion.

Besides I don't understand why these policies are physically removed. We had some exemptions for some resources but these exemptions are failing now. If you keep the same policy definition ID which is currently the case why don't you make these policies obsolete with their effect parameter for instance to Disabled. This leads to breaking changes.

[Allowed locations (e56962a6-4747-49cd-b67b-bf8b01975c4c)](https://www.azadvertizer.net/azpolicyadvertizer/e56962a6-4747-49cd-b67b-bf8b01975c4c.html)
[Allowed locations for resource groups (e765b5de-1225-4ba3-bd56-1ac6695af988)](https://www.azadvertizer.net/azpolicyadvertizer/e765b5de-1225-4ba3-bd56-1ac6695af988.html)

Start by comparing the NL BIO Cloud Theme V2 version 2.6.0 definitions for Allowed locations (e56962a6-4747-49cd-b67b-bf8b01975c4c) and Allowed locations for resource groups (e765b5de-1225-4ba3-bd56-1ac6695af988) with the previous version. Determine why the definitions were removed and document whether preserving them with a Disabled effect is the intended resolution.

Written by the indexing model from the issue text.