E.g., in Azure Portal, the export of an Azure CDN profile resource contains “Global” with capital G. I am not sure if location names are case-insensitive in general (cannot find an authoritative answer), but I guess so. I just know that while “West Europe” is a canonical location name, “westeurope” (lower-case, without the space) is also accepted and works correctly.
Thanks for pointing this out. Locations in Azure RM have separate fields for name and displayName, and apparently both can be accepted as location values. For the global location, capitalized Global is a display name, while just global is a name.
I wasn’t aware that ARM accepts both forms. You are right, we should raise in neither of cases. I’ve created a ticket to adjust the rule’s behavior here.