1
It's quite limiting that right now when you create a new Business Central environment the Azure region is linked to the localization you pick. These should be 2 separate options as there's scenarios where you would like to use your native localization if you have subsidiaries or other departments abroad.

An example would be if you're Danish company with a department in Australia you're either forced to use Danish localization but the server located in Northern Europe (bad performance), or you have to go with Australian localization but you'll have better performance. Either option isn't really ideal, hence why I believe this should be changed.
STATUS DETAILS
Declined
Ideas Administrator

Thank you for submitting this idea.
This is not a scenario we want to support, as it brings complexities regarding data fencing and local legislation requirements.

Best regards
Søren Alexandersen, Program Manager, Business Central