Currently, Azure Functions does not provide a standard capability to detect changes in Microsoft Dataverse tables directly, especially in scenarios where polling or outbound-only communication is required.

In many enterprise environments, strict network security policies prohibit inbound communication, making it difficult to adopt event-driven architectures such as Webhooks or Business Events (Dataverse → Azure Functions). As a result, users are unable to implement change detection scenarios using Azure Functions when inbound connectivity is restricted.

If Azure Functions (or Dataverse) could support a standard mechanism for detecting changes via outbound communication (for example, polling with change tracking or a lightweight delta API optimized for Functions), it would significantly improve usability in restricted network environments.

This enhancement would enable:

• Implementation of change detection in environments where inbound communication is not allowed
• Greater flexibility in designing secure, outbound-only integrations
• Simplification of architectures that currently require additional services (e.g., Logic Apps, Power Automate) as intermediaries
• Broader adoption of Azure Functions for enterprise integration scenarios with Dataverse

Currently, users must rely on workarounds or alternative services, which increases complexity and operational overhead. Providing this capability as a standard feature would greatly enhance developer experience and expand supported architecture patterns.