Currently, audit data becomes unavailable after maintenance activities and appears to reset, allowing users to view only usage and audit information generated after the maintenance window. This creates a gap in historical audit tracking and makes it difficult to perform long-term analysis, compliance reviews, troubleshooting, and trend monitoring.
We would like a capability to preserve and retain historical audit data across maintenance events so that users can continue accessing audit records from before and after maintenance without interruption.
1 Comment
- Gautam_Kumar01Post Partisanv-nandagm I completely agree with this. Losing audit history after maintenance creates a major gap for compliance reviews and long-term analysis. We’ve also faced issues where we can’t perform year-over-year trending because data resets after each maintenance window. Having continuous audit retention across maintenance events is critical for SOC2, GDPR, and security investigations. Please prioritize this. +1 from our team.
Recent ideas
Gestión. Visión artificial. Biometría. Automatización. Datos. Integración.
Estamos empezando a mostrar algo mucho más grande: una plataforma construida para llevar la Inteligencia Artificial al mundo real. Gestión. Visión artificial. Biometría. Automatización. Datos. Integ...luisfertl22 hours agoNew MemberNew5Views0likes0CommentsData Pipelines - Run only selected activities
For debugging and testing pipeline activities during development, allow us to select one or multiple activities and run only the selected pipeline activities. For example, I'm working on editing ...frithjof_v1 day agoCommunity ChampionNew620Views11likes2CommentsSemantic model connection bindings should be in source control (Git)
Semantic model data source connection bindings should be source controlled. A semantic model can contain multiple data source references, each of which can be mapped to a separate Fabric data connec...frithjof_v1 day agoCommunity ChampionNew22Views1like0Comments