Storing Live Timeseries Data in SQL Server Azure Database
With that design it is expected that the query requires a full scan of the columnstore.  That should be very fast at that scale, but the IO stats show that you're reading from disk.  If you look at the wait stats for the actual execution plan you should see that it's more IO waits than CPU utilization.
You could scale up the database to get more cache memory, or perhaps partition the columnstore either by componentId or timestamp.  Whenever you partition a columnstore you want to ensure that partitions have at least 1M rows.