Workspace transformation cost for native Entra ID connector
Hey team! I want to apply workspace transformation to the native Entra ID connector and it's log types to filter logs only for specific domain. While from KQL perspective this is not difficult, I'm doubting if the cost reduction effect will be applied also to the ingestion costs and not only to the retention costs. As from my understanding transformation happens prior the logs are being ingested into Sentinel (and therefore should not be any ingestion costs), however going thru the docs I found out this Custom data ingestion and transformation in Microsoft Sentinel | Microsoft Learn in which is mention only that this action will reduce the costs by reducing the storage requirements.
What is your opinion and someone from you already have experience with such use case ?