Large amount of API calls coming from Dynamics365Athena2

(1) Share

Report

Posted on by RandomDept

706

Greetings Braintrust.

Lately I have noticed a lot of API calls in most of our environments from the #Dynamics365Athena2 API.
When viewing the logs via the Power Platform Admin Center > Manage > Dataverse > Analytics > API calls statistics.

I am seeing up to 400 calls a day per environment, and it's taking us pretty close to the API peak limit.

Initial research seems states the Dynamics365Athena2 account is a Microsoft-managed system service used for background data processing, especially for analytics scenarios such as Azure Synapse Link or Microsoft Fabric.
The thing is, we only have one environment where we have Synapse / Fabric enabled, yet we are seeing this in almost every environment.
Even in another tenant where we don't have any Synapse / Fabric integration we are seeing this.

Does anyone else have the same issue or an explaination?

Thank you
RD

Categories:

Microsoft Dataverse with Power Apps

Governance & administering

General topics

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

sannavajjala87 824 Super User 2026 Season 2 on at

Like
a
(1)

Report
Copy link

Link copied!
Hi RD,

Yes, I've seen the same behavior across multiple tenants and environments, including environments where no Azure Synapse Link or Microsoft Fabric integration was explicitly configured.

According to Microsoft documentation, Dynamics365Athena / Dynamics365Athena2 is a Microsoft-managed application user that performs data integration and analytics-related background operations between Dataverse and Microsoft's data services. While it's commonly associated with Azure Data Lake, many admins have reported seeing API activity from this account even in environments that don't have Synapse Link or Fabric configured. Microsoft appears to use these service principals for various platform-managed telemetry, analytics, and data processing workloads that aren't always visible as customer-configured integrations.

In my experience, a few hundred calls per day per environment is fairly common and usually isn't something that can be disabled or managed directly by customers. If you're seeing unusually high volumes or approaching entitlement limits, I'd recommend:

Reviewing the API Calls by User details to identify which tables/operations Athena2 is performing.

Checking for any enabled features such as Customer Insights, Sales Insights, Dataverse analytics, data export capabilities, or other Dynamics 365 workloads that may rely on Microsoft-managed data processing.

Opening a Microsoft Support ticket if the consumption is significant enough to cause throttling, as Microsoft can inspect the backend activity tied to the service account.

You're definitely not the only one seeing this, and several community threads over the last couple of years report similar Athena2 activity in environments with no obvious Synapse/Fabric configuration.

Hopefully that helps shed some light on it. I'd be interested to hear if anyone has received a more definitive explanation from Microsoft Support.

Thanks & Regards,

Manoj Annavajjala

www.powerplatformengineer.com

Was this reply helpful? Yes No
Suggested answer

11manish 3,849 Super User 2026 Season 2 on at

Like
a
(1)

Report
Copy link

Link copied!
What you're observing is not unique, and several customers have reported seeing API activity from the Dynamics365Athena2 application across environments where Azure Synapse Link or Microsoft Fabric are not explicitly configured.

Based on Microsoft's architecture, Dynamics365Athena2 is a Microsoft-managed system service principal that supports various first-party platform capabilities. While it is commonly associated with Azure Synapse Link and Microsoft Fabric, it may also be used by other Dataverse background service.

Therefore, seeing API calls from this account does not necessarily indicate that Synapse Link or Fabric is configured in the environment.

If:

The environments have no Synapse/Fabric integration,

The API volume is increasing unexpectedly, or

You believe these Microsoft-managed calls are materially affecting your API entitlement,

then it would be advisable to open a Microsoft Support ticket. The support team can trace the Dynamics365Athena2 service activity using internal telemetry and confirm exactly which Microsoft service is generating the requests. This level of detail is not exposed through the Power Platform Admin Center.

Until Microsoft provides official documentation clarifying all scenarios where Dynamics365Athena2 is used, these API calls should generally be considered expected Microsoft-managed background activity rather than an indication of misconfiguration.

Was this reply helpful? Yes No
RandomDept 706 on at

Like
a
(1)

Report
Copy link

Link copied!

Thanks @sannavajjala87 and @11manish

I have a support ticket that we have been going back and forward with the Product team to try and determine the underlaying cause. So far...not much luck.

The official documentation obviously doesn't exist at this stage, which is why it keeps being pushed back to the product team.

I'll provide an update if we ever got a straight answer.

Was this reply helpful? Yes No
Suggested answer

Valantis 7,006 Super User 2026 Season 2 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @RandomDept,

The confirmed approach for sending Dataverse audit change notifications to Teams:

Use the Dataverse connector trigger "When a row is added, modified, or deleted" in Power Automate. This fires on actual data changes in real time and is more reliable for notifications than polling the audit log table.

Flow:

1. Trigger: When a row is added, modified, or deleted (Dataverse) → select your table, change type Modified
2. Post a message in Teams with the changed row details

For reading old/new values from the audit log specifically: query the audit table directly using List rows on the audits table filtered by objectid and recent createdon. But note a critical change: <cite index="70-1">starting in May 2026, Dataverse no longer includes before-and-after field change values in the audit events sent to Microsoft Purview. Audit events continue to flow, but detailed field-level value changes are excluded.</cite> This affects Purview-based audit solutions but NOT the Dataverse audit table queried directly via Power Automate.

The Dataverse audit table (auditbase) still stores the old/new values. Query it via:
List rows → Table: Audit → Filter: _objectid_value eq [record GUID] and createdon gt [timestamp]

Then post the changed field names and values to Teams.

Ref: https://learn.microsoft.com/en-us/power-platform/admin/manage-dataverse-auditing

Best regards,

Valantis ✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/ 💼 LinkedIn ▶️ YouTube

Was this reply helpful? Yes No