Thank you for your patience throughout this process. I have summarized our offline discussions below for community benefit.
Our documentation states that
And ExpressRoute Local is not available in Copenhagen peering location.
But as mentioned in your question you are still able to deploy the ExpressRoute Local SKU for Copenhagen region. I was able to reproduce this issue on my end and I had reached out to the team internally regarding this issue.
I received following update from the team.
The information mentioned in the documentation is correct Copenhagen is not associated with a local region and doesn’t support “local” sku.
The portal behavior observed above is by design. Azure Express Route currently does not block local circuit creation if there is no local region for a peering location. This check is done when customers try to add a Gateway connection. So based on your observation above you can create a local circuit in Copenhagen region but cannot create a connection to a Gateway in different region. Team will look into correcting this experience where circuit creation itself will be blocked in such cases, currently no timeline has been finalized on when this feature will be rolled out. Meanwhile, team will add an FAQ on this topic in the ExpressRoute documentation.
Hope this helps! Please let me know if you have any questions.
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.