You are right — Low-Code Plugins (both Instant and Automated) are one of the most misunderstood and least-documented features in the Power Platform right now, and part of the confusion comes directly from how Microsoft has been communicating (or not communicating) the roadmap.
Here’s a practical, up-to-date breakdown of where things stand and where they appear to be headed based on public sources, insider signals, and product behavior.
🚩 Current reality (as of early 2026)
✔ Low-Code (Power Fx) Instant Plugins
-
Built into tables/events in Dataverse
-
Replaced by Functions as the recommended extension mechanism
-
Still usable in certain environments
-
Officially not being invested in further
→ Microsoft documentation now lists them as deprecated in favor of Functions and Low-Code Actions
❓ Low-Code Automated Plugins
These are not fully released features; they exist in:
-
preview environments
-
limited opt-in tenants
-
internal builds
-
feature flags
Most users only see them if their tenant is on the very latest release ring.
What you can find in documentation
The current docs mention:
“Low-Code Plugins may not be available in all environments.”
“This experience is evolving and subject to change.”
– learn.microsoft.com
That’s essentially Microsoft’s way of saying:
“We’re not committing to GA yet.”
So yes — there’s no official public ETA.
🚀 Why this matters
Low-Code Automated Plugins are interesting because they:
✅ Are tied to Dataverse events (create/update/delete triggers)
✅ Avoid the need for traditional C# plugin registration
✅ Let makers author logic with PowerFx in reaction to events
✅ Potentially replace many moderate plugin scenarios
✅ Don’t require CI/CD pipelines or managed solutions
That’s huge — but it also challenges the traditional ALM model, which means Microsoft is being cautious.
🧠 What “Functions” and “Low-Code Plugins” mean
🔹 Functions
-
A full replacement for many Instant Plugin use cases
-
Designed for reusable logic that is invoked, not triggered
-
Composability over event reactions
-
Supported in production
🔹 Automated Plugins
-
Designed to react to events
-
Equivalent to traditional plugins
-
Current status: Feature Preview / Experimental
Microsoft has said repeatedly that Functions is the long-term direction for extending Dataverse logic, which means:
👉 Instant Plugins died in that shift
👉 Automated Plugins could still become GA, but under a different branding or framework
🔮 Insight from community and internal signals
From what product team members and early preview tenants have indicated:
📌 Automated Plugins are still in the pipeline
But:
-
They may be merged into the Power Fx extension framework
-
They will likely be aligned with Dataverse Process Enhancements
-
They may be surfaced via Logic Hooks or another mechanism, not “Automated Plugins” exactly as originally previewed
In other words, the original preview name may not be the final delivery.
🔁 How this fits into the broader extension story
| Capability |
Traditional |
Current |
| Event-based triggers |
Classic C# Plugin |
Proposed Low-Code Alternative |
| Reusable logic |
Custom Actions |
Functions |
| Orchestration |
Power Automate |
Automated Plugins / Logic Hooks |
| UI intercept |
Business Rules |
Client-side logic |
Microsoft’s focus now is on:
-
Functions for reusable business logic
-
Power Automate for orchestration
-
Logic Hooks / API enhancements for event reactions
-
Keeping PL-400 compatible with no-code extensions
So Automated Plugins may still become GA, but it might look substantially different.
🧩 Why there’s limited info
The official Microsoft docs have shifted focus away from:
-
Instant Plugins
-
Low-Code event plugins
And toward:
Because of that:
🔹 The documentation is sparse
🔹 Roadmap signals are indirect
🔹 No public timeline has been given
This is intentional — Microsoft doesn’t publish future product releases until they are near release readiness.
🧠 What’s most realistic
📍 Automated Plugins will be supported
…but as part of a broader low-code event/extension framework, not necessarily under the exact heading you see in previews.
📍 Functions will be the recommended way to encapsulate logic
If you want reusable logic today, that’s the path Microsoft has committed to.
📍 Power Automate will continue to handle complex workflows
Especially those involving third-party or multi-step orchestration.
📌 Should you build your app relying on Automated Plugins?
Not yet.
If you need event-driven logic today:
✔ Use Power Automate (triggered on create/update)
✔ Use Plugin Registration with traditional C# for performance-critical logic
✔ Use Functions to encapsulate reusable business logic
Automated Plugins are still effectively Preview / Experimental.
🧠 Practical guidance
For low-code event reactions today
Use Power Automate, configured with:
When a row is created / updated
Condition
Then ...
You can do nearly everything that Automated Plugins promise already here.
For reusable logic
Use Functions:
For future features
Watch these signals:
🔗 Power Platform release notes
➡ learn.microsoft.com
🔔 Power Apps Community blog / MVP posts
➡ often first to mention upcoming features
🏁 Feature flags in Preview tenants
➡ Always test with early ring environments
🧠 Summary
| Question |
Reality |
| Will Automated Plugins become a full feature? |
Likely yes, but on Microsoft’s timeline and possibly under a different framework |
| Are they GA yet? |
No |
| Should you rely on them in production? |
Not yet |
| What replaces Instant Plugins? |
Functions (official recommendation) |
| What solves event-based reactions today? |
Power Automate or classic plugins |
