You're correct, the HTTP action is considered a premium feature in Power Automate. Under normal circumstances, it should not be available when you're only using the "Power Automate for Office 365" or "Power Automate Free" licenses.
However, there are several possible explanations for why it may currently be working in your case:
1. Developer Plan
You may have a Power Apps Developer Plan assigned to your account. This license is free and allows full access to premium features, including Dataverse and the HTTP action, but only in non-production environments. You can check your license status in the Power Platform Admin Center.
2. Legacy or Grace Period Behavior
If the flow or environment was created when licensing rules were more relaxed, or if Microsoft has granted a temporary grace period, the HTTP action might still work. This access can be revoked without warning once enforcement catches up.
3. Flow Created by a Premium-Licensed User
If the flow was authored by someone who has a premium license and you are only triggering or running it, the system may temporarily allow you to use it — though this behavior is not officially supported.
4. Delayed Enforcement
In some cases, Microsoft’s enforcement of premium connectors is not immediate. You may be seeing a delay between the feature use and the license check enforcement.
Recommendation
Even if the HTTP action is working for now, it’s safest not to rely on that behavior continuing indefinitely. If the HTTP action is critical to your process, it’s recommended to move to a compliant licensing model, such as Power Automate per user or per flow plans.
Always validate your license use through the Power Platform Admin Center to avoid unexpected disruptions.
If this solved your problem, please mark it as Solved to help others find the solution faster.
If you found it helpful, consider giving it a Like to support each other in this community!
Thanks, and happy building!