A cloud-native SIEM solution that provides intelligent security analytics and threat detection across systems
Hello @Richard Eyres
Thank you for raising this issue.
I reviewed the Microsoft Sentinel GitHub repository, and I can confirm that the missing Dataverse and Power Platform connectors were caused by a packaging issue in the Microsoft Business Applications solution, rather than an intentional removal.
- What happened to the connectors?
In solution version 3.2.4, three connectors were unintentionally excluded during the solution packaging process:
Microsoft Dataverse: DataverseActivity
Microsoft Power Automate: PowerAutomateActivity
Microsoft Power Platform Admin Activity: PowerPlatformAdminActivity
The connector definitions were previously included directly in the ARM deployment template but were not registered correctly in the solution source files.
As a result, when the solution was repackaged, these connectors were omitted, while the associated analytics rules and hunting queries remained.
- Has Microsoft fixed the issue?
Yes. On November 12, 2026, Microsoft merged GitHub Pull Request #15611, which restores all three connectors in Microsoft Business Applications version 3.2.5.
The fix includes the missing connector definitions, Data Collection Rules, and polling configurations.
You can review the official GitHub pull request here:
https://github.com/Azure/Azure-Sentinel/pull/15611
Please note that the GitHub merge confirms the fix is included in version 3.2.5, although availability in the Microsoft Sentinel Content Hub may depend on the publishing rollout.
- How can you restore log ingestion?
I recommend the following steps:
- Navigate to Microsoft Sentinel > Content Hub.
- Search for Microsoft Business Applications.
- Check the installed solution version and update to 3.2.5 when available.
- Navigate to Configuration > Data connectors.
- Locate Microsoft Dataverse, Microsoft Power Automate, and Microsoft Power Platform Admin Activity.
- Open each connector and complete the connection process.
- Verify that the required Data Collection Rules have been deployed and that auditing is enabled in Microsoft Purview.
For Dataverse, ensure that auditing is enabled at both the environment and table levels. Dataverse activity logging through this integration is supported for production environments.
- How can you ingest Power Platform website logs?
If you are referring to Power Pages websites, the Microsoft Power Platform Admin Activity connector is the relevant integration for supported administrative and configuration events.
It collects supported Power Platform audit records from Microsoft Purview into the PowerPlatformAdminActivity table.
However, this should not be confused with collecting all website access logs, HTTP requests, or visitor activity.
For detailed Power Pages website diagnostics and request telemetry, you should evaluate the supported Application Insights integration separately.
- Verify ingestion
After enabling the connectors, you can run the following KQL query in Microsoft Sentinel:
union isfuzzy=true
DataverseActivity,
PowerAutomateActivity,
PowerPlatformAdminActivity
| summarize Events=count(), LastEvent=max(TimeGenerated) by Type
| order by LastEvent desc
This query helps identify which tables are receiving data and when the most recent events were ingested.
Microsoft recommends allowing approximately 60 minutes for Power Platform activity logs to appear after configuration and activity generation.
If version 3.2.5 is not yet available in your Content Hub, I recommend checking again after the publishing rollout or opening a Microsoft support request referencing GitHub PR #15611.
In summary, the removal was not intentional. The missing connectors have been restored in solution version 3.2.5, and updating the solution should restore their availability for configuration.
I hope this helps! If my answer resolves your question, please consider marking it as "Accepted Answer" so other community members experiencing the same issue can benefit from it.