The Cost History Report filter displays unexpected special characters in the Subscription Name field, even though the subscription names appear correctly elsewhere in the Azure Portal.
Non-standard Unicode characters should be avoided in subscription naming to prevent downstream data corruption. These characters often cause rendering failures and character-encoding mismatches in the reporting interfaces.
1. Avoid using Non-standard Unicode characters in the subscription name.
2. If you have already used them, please replace such Non-standard Unicode characters in Azure, so that the subscription name gets updated in CloudHealth and shows the correct name under the filter.
Example: If you have used En Dashes (–) in the subscription name replace it with hyphens(-)