Location field for the Search Service is not consistent with other services
In my deployment templates I use [ResourceGroup().location] to specify the location for the resources in the group.
This works for all the services I've tried so far except for Search which requires the full string only, like "West Europe".
This is a little inconsistency that is very inconvenient as I now need to pass the Location parameter to all templates that deploy search. Search is a bit different than others on the length of the service name(15 chars only, reminds me of NetBIOS names). But this is a different story.
We found that this was an issue in how we processed locations and have fixed it now! Feel free to go ahead and use [ResourceGroup().location] the same as any other service