web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Answered

Audits and Agents (Part 2)

(0) ShareShare
ReportReport
Posted on by 105

For over a year, my team has been opening support tickets with Microsoft regarding missing Dataverse audit records.

Support tickets:

  • 2605030050000490
  • 2603040050002449
  • 2511040050004915
  • 2602180050002627

Each case followed a similar pattern. We spent several weeks re-verifying the same information with the support engineer. The case would then be escalated to the Product team, who typically responded that telemetry had expired and no further investigation was possible. Requests to escalate to a supervisor were never successful.

On more than one occasion we were also told that auditing was working correctly because audit entries existed before and after the missing period. That didn't explain the issue we were reporting, which was that audit records for specific periods had disappeared while both older and newer records still existed.

After a year of investigations, I believe we have finally identified the cause ourselves.

In the Power Platform Admin Center → Audit Settings, we found that "Retain these logs for" was configured to 30 days.

What made this difficult to identify is that our environment still contains audit records dating back to 2019. Because we still had years of historical data, it never occurred to us that a 30-day retention setting could be the cause. Instead, it appeared that intermediate periods were being deleted while both older and newer audit records remained.

At no point during these four support cases did anyone ask us to verify this setting or suggest that it might be responsible. Instead, we were repeatedly asked to confirm that field-level auditing was enabled (it was), and we spent several remote sessions proving that we were querying the audit history correctly.

We have now changed the retention setting to Forever.

Based on the Microsoft documentation and my current understanding, audit records that were created while the retention was set to 30 days will continue to expire according to that original retention period, while new audit records created after the change will be retained indefinitely. As a precaution, we are exporting the remaining audit history to CSV while it is still available.

We've also implemented a temporary Power Automate process that copies each day's audit information elsewhere so that we have an additional record while we rebuild our audit history.

I have three questions for the community:

  1. Can anyone with experience in Dataverse auditing confirm whether the retention behavior described above is correct? Specifically, do audit records created while the retention period was 30 days continue to expire even after the retention setting is changed to Forever?
  2. How can I provide feedback or escalate our support experience? Four support cases over the course of a year without anyone identifying this configuration issue has been extremely frustrating, and I'd like to ensure the feedback reaches the appropriate team so other customers don't have the same experience.
  3. Is there any way to determine what changed this retention setting? We believe the behavior changed around July 2025, but we have no way to determine whether the retention setting itself changed at that time.

Thank you.

Categories:
I have the same question (0)
  • Verified answer
    11manish Profile Picture
    1,194 Super User 2026 Season 2 on at

    Your current mitigation strategy is sound:

    1. Keep the retention period set to Forever (or another period that meets your compliance requirements).
    2. Continue exporting or archiving audit data if long-term retention is a business or regulatory requirement.
    3. Periodically review the audit retention configuration as part of your environment governance and health checks to ensure it hasn't changed unexpectedly.

    Regarding the support experience, it's understandable that the focus remained on whether auditing was enabled rather than on the retention configuration. Given the symptoms you described—historical records existing before and after the missing period—it would have been reasonable to verify the retention policy much earlier in the investigation. Providing that feedback through your active support case and CSAT survey can help improve future troubleshooting guidance.

  • unicorn_tech Profile Picture
    105 on at

    @11manish thank you for the feedback. We will implement a regular check of this setting.

    Regarding the support experience, I don't think it's understandable. 1 ticket maybe, but not 4, and not with the constant back and forth. I have provided feedback in surveys, and nothing changes or improves for the future.  There has to be a way to contact a supervisor about this.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
11manish Profile Picture

11manish 48 Super User 2026 Season 2

#2
Subra Profile Picture

Subra 42 Super User 2026 Season 2

#3
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 32 Super User 2026 Season 2

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans