Azure cost exports appear to have different column names present depending on the scope they are generated at. I have not found this documented anywhere in Azure docs, but from looking at a real report:

• Subscription level export, there is the expected `resourceid` column
• Resource Group level export, the column with the same information is called `instancename`

An investigation should be done on the different column names for the different scoped exports we support and we should determine what (if any) changes need to be made on the koku side. A mapping of columns/scope and what they normalize to in koku would be excellent as it would allow us to highlight columns in scopes that are not currently processed but should be.

First glance, this would at a minimum impact OCP on Azure processing as we look for `resourceid` or `instanceid` to match on and not `instancename`.