Power Platform Community Forum Thread Details

I'm working on a Power Automate flow that should trigger email alerts when Azure Synapse Link table sync fails in a Power Apps (Dataverse) environment.I'm using these Dataverse tables:

Synapse Link Profile Entity States
Synapse Link External Table State

However, I noticed the following challenge:

The Sync Status shown in the Power Apps UI (e.g., “Failed with error FnO-812”) doesn't match the syncstate values returned in these backend tables.
For example, a table showing as Failed in UI still has syncstate = 2 (which typically means Success).
Also, using the Last Synchronized On timestamp doesn’t help because some tables only sync when source data changes, not daily.

Help me with the condition to be used for Flow.

@v-bofeng-msft @happyyear

Categories:

Building flows

@CU20060751-1

he webhook URL behavior in Power Automate is evolving, and your summary captures the key differences well. Here's a quick recap and some additional insights to help you choose the best approach:

🔍 Summary of Key Points

✅ Webhook URL Format

prod-logic.azure.com:
- Legacy format from Logic Apps infrastructure.
- Supports anonymous access via SAS token.
- Ideal for external systems without OAuth.
environment.api.powerplatform.com:
- New format from Power Platform infrastructure.
- Requires OAuth 2.0 authentication.
- Enforced in modern environments, especially with enhanced security.

🔐 Authentication Requirements

SAS token: Automatically included in legacy URLs.
OAuth token: Required for modern URLs. Must be obtained via Azure AD app registration and client credentials flow.

⚙️ Environment & Licensing Impact

Managed environments, premium licenses, or Teams-integrated flows often default to the secured format.
Developer or default environments may still allow legacy behavior.

🛠️ Implementation Options

If you need anonymous access for external systems:

Use Azure Logic Apps:
- Create a webhook-triggered Logic App.
- Use it to call Power Automate internally if needed.
Proxy with Azure Function or API Management:
- Accept anonymous requests.
- Internally authenticate and forward to Power Automate.
Use Power Automate in a legacy/default environment:
- Try creating the flow in a non-managed environment.
- Check if the legacy URL format is still generated.

🏷️ Tag me if you have any further questions or if the issue persists. ✅ Click "Accept as Solution" if my post helped resolve your issue—it helps others facing similar problems. ❤️ Give it a Like if you found the approach useful in any way.