Recently the Geo to Geo migration was added for LCS projects, but this also brings an issue for Solutions, since it seems that Solutions on Lifecycle Services are limited to one Geo location, which to me is unexpected. It has been determined by Support that this is by design. To me it this is a limitation since there is a direct link between a Solution and the App-Source so isn't possible to set up and manage multiple Solutions (which in itself is not desired, one solution should be enough). The current advised work around would be to upload the Assets to the Asset Library manually for each LCS project that is not in the Solutions Geo location, which is not a satisfactory workaround and it defeats the purpose of having a Solution.

Example of the current situation: 

Solution is linked to the Geo location United States

LCS project was initially linked to the Geo location United States and it was possible to link the solution to this LCS project.

After migration of the LCS project to the Europe Geo location the link was no longer possible to make. The user that is used to create the link between Solution and LCS project isn't able to see the Solution at all when the Geo for the user is switched to for example the Geo Europe when you switch it back to United States it is visible again, which seems to imply that the Solution is fixed to the United States region.

The request is that I would like to have an option to make a Solution across Geo locations or to not have a link to a Geo location at all for solutions, so it will be possible for the user account to create a connection between a Solution and LCS projects that reside in any Geo locations. The user used for linking a Solution to an LCS project should be able to see the Solution for any Geo location to which the solutions was made available.

So that that there is only the need for one Solution on LCS that can be used for all and not limited to Geo location.